Fsck is trying to read an uninstalled hard drive *because* *you* *told* *it* *to* *do* *so*. "Doctor, doctor, it hurts when I stick a sharp ice-pick in my eye!" "Well, don't do that!"
The problem is that fstab was really fundamentally intended for key filesystems that must be present in order for the system to run correctly at boot time. If /usr is on a separate device, and it can't be found, you *want* the boot process to stop, and not just "don't worry, be happy", and let the system keep going with critical parts of the system missing. If you have a mission critical database in /u1, and the drive is off-line, it is better to let the system *not* come up and then let your High Availability system, such as Linux-HA, let the backup system take over than just let the system come up but not actually be able to do anything useful (or worse yet, return inaccurate/wrong information!) This problem could be solved by having a way to mark a filesystem as "optional", and add support for fsck to check to see if a disk is present, and to skip the fsck if it is not there. And mount could potentially do the same thing. But it's really not a complete solution since it doesn't handle what happens if the removable disk is inserted some time after the boot sequence is finished. I suspect the real right answer is to extend the support we currently have for CD-ROM's to support removable hard drives, which we currently actually already have if you are using the Ubuntu/GNOME desktop, although as far as I know the GNOME desktop doesn't automatically run fsck on a disk after it is inserted and before it automounts it. The whole paradigm of boot-time fsck to check removable drives is really just all wrong. -- fsck - Trying to Verify Removed Removable Drives https://bugs.launchpad.net/bugs/128792 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
