Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#27588 - [iniscripts] Booting with missing devices in /etc/fstab not possible
Attached to Project:
Arch Linux
Opened by Stefan J. Betz (encbladexp) - Thursday, 15 December 2011, 19:31 GMT
Last edited by Jan de Groot (JGC) - Friday, 16 December 2011, 12:46 GMT
Opened by Stefan J. Betz (encbladexp) - Thursday, 15 December 2011, 19:31 GMT
Last edited by Jan de Groot (JGC) - Friday, 16 December 2011, 12:46 GMT
|
DetailsTo produce the error i had some logical volumes in my /etc/fstab, these had set the noauto option. On the next reboot my system hangs with the message "FILE SYSTEM CHECK FAILED", because he tried to check these file systems with e2fsck.
initscripts should consider whether a device node in the system actually exists before a check is attempted. |
This task depends upon
Comment by Jan de Groot (JGC) -
Thursday, 15 December 2011, 22:27 GMT
This is more or less a configuration error. Initscripts calls fsck with the default autocheck option. The manpage for fsck says nothing about auto/noauto, and the fstab manpage mentions only mount -a behaviour for auto/noauto. If you want fsck to pass if devices don't exist, you should either add nofail to the options, or set a 0 for the field that tells fsck what to do.
Comment by Stefan J. Betz (encbladexp) -
Friday, 16 December 2011, 12:13 GMT
Thx, nofail does the trick!