Good Day . . .
Thank You for the reply.
Unfortunately you addressed my nice to know stuff (noauto) and did not
address the need to know bug which was a stopped boot process.
For your information, I did read the man pages for fstab, fsck and
fsck.ext3. None addressed the issue of the bug.
My
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
This isn't a bug. noauto just means, don't mount the filesystem by
default. See the fstab(5) man page.
If you want to have something in /etc/fstab, but you don't want it to be
mounted by default *and* you don't want it to be checked by default, you
need to set the fsck pass number to 0. Again,
As promised. This is the log file. /dev/hdb1 and /dev/hdd1 are the two
unlocked removable hard drives.
Log of fsck -C -R -A -a
Fri Jul 27 19:20:52 2007
fsck 1.40-WIP (14-Nov-2006)
fsck.ext3: No such file or directory while trying to open /dev/hdb1
/dev/hdb1: fsck.ext3: No such file or directory
