Just to add another data point, I've just seen the same, or a very similar problem with Hardy alpha (up to date as of March 6, 2008). And I saw it another time somewhere in the last month.
What I just saw: I get a fsck at boot on an ext3 fs that hasn't been checked in a while (so it's not an fs with errors), it displays the progress on the boot splash, but hangs at 83%. (The display of progress on the boot splash seems to be a recently added feature.) When I switch to the console, I see output that seems to indicate that the fsck has actually finished, however, there's no output after the fsck, and the boot does not continue. There's no more disk activity either. Pressing Ctrl+Alt+Del at that point actually seems to make the boot continue. I get various errors which seem to indicate that the root fs is still mounted read-only though. X won't start either. It requires a second Ctrl+Alt+Del to start a reboot, which then works just fine. My fstab records, I think the fsck was on sda5 (mounted at /otheros): proc /proc proc defaults 0 0 # /dev/sda2 UUID=b2905f36-9a1a-4199-b2f8-8f527cef7eef / ext3 errors=remount-ro,relatime 0 1 # /dev/sda6 UUID=c9d56401-32c0-42c8-8eec-28bb0d0c240d /data ext3 defaults,relatime 0 2 # /dev/sda5 UUID=ec1b5cb8-c8b7-4c69-bf6e-734b75f2f605 /otheros ext3 defaults,relatime 0 2 # /dev/sda1 UUID=8048A4E648A4DBE2 /windows ntfs defaults,umask=007,gid=46 0 1 # /dev/sda3 UUID=588534c7-7b82-4129-abd1-cf16bd1963b7 none swap sw 0 0 /dev/scd0 /media/cdrom0 udf,iso9660 user,noauto,exec 0 0 # NAS filesystems //nas/muziek /nas/muziek smbfs credentials=...,uid=1000,gid=1000 0 0 //nas/backups /nas/backups smbfs credentials=...,uid=1000,gid=1000 0 0 //nas/net /nas/net smbfs credentials=...,uid=1000,gid=1000,noauto 0 0 -- Boot failed to complete after fsck https://bugs.launchpad.net/bugs/83831 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
