Sam, In your original report, you said:
>I did the nosplash thing and got the following > >* Checking root file system... >1254 >fsck 1.40.8 (13-Mar-2008) >/dev/sda9 contains a file system with error, check forced. >Checking drive /dev/sda9: 0% (stage 1/5, 1/79) >Checking drive /dev/sda9: 1% (stage 1/5, 1/79) >... >Checking drive /dev/sda9: 11% (stage 1/5, 1/79) >/dev/sda9: Inodes that were not part of a corrupted orphan linked list found. >fsck died with exit status 4 Was this *really* all you saw? There should have been a message saying that you needed to run e2fsck without the -p (preen) option, and it should offered to drop you into single user mode, after demanding a root password. Did you see any evidence of this, in spash or nospash mode? And when you say "reboot loop", did you have to hit return or otherwise decline to enter single-user mode? It should have **not** been necessary to boot a rescue floppy to recover from this. You don't have to on Ubuntu Gutsy in non-splash mode, nor on any other major distribution as far as I know. I leapt to the assumption that this was an upstart problem, since upstart was new to Hardy, but maybe it's something else..... -- fsck not repairing corruption on boot https://bugs.launchpad.net/bugs/209416 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
