http://bugzilla.novell.com/show_bug.cgi?id=565646
http://bugzilla.novell.com/show_bug.cgi?id=565646#c7
Petr Uzel
I have to use both options.
Sorry, I did not notice that you're using 'noauto' already.
With "noauto" it doesn't attempt to mount during boot, true, but it will try to fsck it;
What if you set fs_passno to 0 (6th filed in /etc/fstab) - does it still fail on fsck if the device is not present?
if the device does not exist, the boot sequence fails completely dropping into emergency rescue mode. The solution, which was given to me on Bug #461294 and Bug #375248, is to add the "nofail" option.
The idea is simply to get a successful boot sequence. The unexpected consequence is what I reported on this bugzilla, that on a manual attempt it doesn't even give a warning message (not an error).
Well, that's exactly the documented and expected behavior of 'nofail' option. If you want this to be changed (to give a warning), then it is something for upstream IMHO. What I think is most reasonable (to get successful boot sequence): - fix the LABEL in /etc/fstab entry - add nofail back (and keep noauto) options, so that the boot sequence does not fail if the device is not present at boot time -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.