http://bugzilla.novell.com/show_bug.cgi?id=556931
http://bugzilla.novell.com/show_bug.cgi?id=556931#c6
--- Comment #6 from Ludwig Nussel
(In reply to comment #4)
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.
Nofail helped, but the /data is not mounted during boot (since it's decrypted after the fstab is processed)
I overlooked that. After thinking about it I know it can't work :-) boot.crypto looks for the unlocked device in fstab but it's not there, just the lvm volumes it contains. Therefore boot.crypto-early is the only way to activate such devices. I'll try to get a patch upstream that makes fsck honor the nofail option itself so we don't need to skip fsck entirely. If that gets rejected fstype 'auto' would work too. Arvin: boot.crypto-early skips devices that don't exist yet so it should be safe to have yast just enable both init scripts. To avoid a warning message the 'noearly' option could be used for all crypto volumes that don't sit directly on top of a physical device but that's not mandatory. -- 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.