https://bugzilla.novell.com/show_bug.cgi?id=743717
https://bugzilla.novell.com/show_bug.cgi?id=743717#c13
Steve Revilak changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |steve@srevilak.net
--- Comment #13 from Steve Revilak 2012-02-22 04:43:03 UTC ---
I have also been affected by this issue, although in my case, the
problem manifested itself exactly as described in
https://bugzilla.novell.com/show_bug.cgi?id=724912.
I have an encrypted /home partition (/dev/mapper/cr_md1), where the
underlying volume is a mirrored raid partition (/dev/md1).
In about 1/3 of boots, I'm not asked for a password to unlock cr_md1,
and systemd-cryptsetup fails with
[ 22.030435] systemd-cryptsetup[868]: crypt_init() failed: Block device
required
When this occurs, `cat /proc/mdstat' shows md1 as "inactive".
In this state, `cryptsetup isLuks /dev/md1' exits with status 4.
Normally, this command exits with status 0.
I will attach /etc/fstab, /etc/crypttab, and dmesg.
For now, I have worked around this by replacing
systemd-sysvinit-37-3.6.1.x86_64 with
sysvinit-init-2.88+-66.58.2.x86_64.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.