Red Hat Bugzilla – Bug 82229
non existent label mounts even with the 'noauto' option cause boot time drop to emergency shell
Last modified: 2014-03-16 22:33:42 EDT
Description of problem:
I have a removable disk drive that I want to mount using a filesystem label.
The drive contains an ext3 filesystem labeled as /mnt/shemp
I also have the following entry in /etc/fstab:
LABEL=/mnt/shemp /mnt/shemp ext3 noauto 1 1
Upon rebooting without /mnt/shep available in the system, I am dropped to
a filesystem repair shell (of course first prompting for the root password).
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Add a non-existent label mount to /etc/fstab with the noauto option
3. watch it prompt you for your root password and to fix your filesystem
You are prompted to fix the filesystem
The non-existent label with the noauto option should simply be ignored since
you are not going to mount the filesystem automagically anyhow.
Did this happen previously?
I could have sworn it worked before, but I just tried on an advanced server
2.1 with all current updates and it indeed failed.
However, on a hunch I changed the fs_freq and fs_passno fields both to 0 and
the system booted without complaint. Weird.
Is it semantically correct behaviour?
I will test the beta4 box again tonight when I get home to ensure that the same
Closing bugs on older, no longer supported, releases. Apologies for any lack of
If this persists on a current release, such as Fedora Core 4, please open a new bug.