http://bugzilla.novell.com/show_bug.cgi?id=556931
http://bugzilla.novell.com/show_bug.cgi?id=556931#c4
Ludwig Nussel changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |NEEDINFO
CC| |aschnell@novell.com
Info Provider| |llipavsky@novell.com
--- Comment #4 from Ludwig Nussel 2009-11-19 16:45:41 UTC ---
it's stupid fsck failing due to non-existing device. add nofail to the mount
options to skip fsck. boot.crypto will do it later then.
Alternatively chkconfig boot.crypto-early on to unlock the device before fsck.
You should also set timeout=0 in crypttab then to avoid the fsck failure in
case of timeout.
However either method may not work depending on whether sda3 contains the luks
volume and then lvm or first lvm and then luks. We'd need some kind of
probe/unlock/fsck/mount loop during boot to really resolve such problems.
So how is the setup? sda3->luks->lvm or sda3-lvm->luks?
--
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.