I had a similiar problem too. It turned out to be similiar to the solutions mentioned above, where my /etc/fstab file was using /dev/sdXX to refer to a drive, rather than a UUID number. However, in the past, for some reason the UUID number for a particular USB drive just didn't work, so I was forced to use /dev/sdXX. It seems this problem is now fixed with the recent Ubuntu 8.04 updates (the version I am using) and using UUID numbers for all my drives in /etc/fstab fixed the error posted by the original poster (the fsck died with exit code 8).
What I was wondering though, wouldn't it be better if fsck didn't use /etc/fstab at all? Since it runs with the drives unmounted, it doesn't need /etc/fstab. Can it not work out what the drives are (i.e. filesystem type) by itself? This would mean you don't get fsck errors if /etc/fstab is wrong..just a thought. -- error on booting up mounting an external usb-drive https://bugs.launchpad.net/bugs/97206 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
