What version of Ubuntu is this?
If a particular filesystem is not always present, then you should
configure the disk so that the fsck pass number is 0, and that mount
option "noauto" is present so that the filesystem is not mounted at boot
time. Then it will not interrupt the boot process, and the system will
not try to mount the filesystem (and fail if it is not present). You
can optionally add the "user" mount option to allow the user to manually
mount the filesystem; with appropriate desktop software installed, it
will also automatically mount the filesystem when it is inserted at the
specified mount point. For example, I have the following in my
/etc/fstab file:
UUID=a8f27eb6-1759-4f48-859d-a4c3b4bcac13 /wd1 ext3
noauto,user,exec,nosuid 0 0
As far as "shutdown -h now" inside the shell causing the boot to resume,
yes I've noticed this as well. That appears to be a bug in the upstart
package. You can also see this behavior by hitting control-alt-delete
during the fsck process.
** Also affects: upstart (Ubuntu)
Importance: Undecided
Status: Unconfirmed
** Changed in: e2fsprogs (Ubuntu)
Status: Unconfirmed => Rejected
--
Failed file system check, weird behaviour
https://bugs.launchpad.net/bugs/68589
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
