Even after updating for the package fix referred to in bug #287879 my issue is still not fixed. I could really use some help debugging this!
Here's my current state:
Every time I boot my system, I'm dropped to an initrd busybox prompt with a notice that my root device can't be found. The root device can't be found because the initrd hasn't bothered to try opening my luks-encrypted partition yet. A simple "cryptsetup luksOpen..." from the prompt will unlock the partiton, then my LVM volumes are automatically found and activated. I've typed one command and pressed ctrl+d and everything continues roughly as usual.
After I've manually unlocked my encrypted partition, I'm actually asked for the passphrase for it a few seconds later (even though it's already unlocked). This says to me that the cryptsetup stuff in the initrd is happening far too late.
Even after updating for the package fix referred to in bug #287879 my issue is still not fixed. I could really use some help debugging this!
Here's my current state:
Every time I boot my system, I'm dropped to an initrd busybox prompt with a notice that my root device can't be found. The root device can't be found because the initrd hasn't bothered to try opening my luks-encrypted partition yet. A simple "cryptsetup luksOpen..." from the prompt will unlock the partiton, then my LVM volumes are automatically found and activated. I've typed one command and pressed ctrl+d and everything continues roughly as usual.
After I've manually unlocked my encrypted partition, I'm actually asked for the passphrase for it a few seconds later (even though it's already unlocked). This says to me that the cryptsetup stuff in the initrd is happening far too late.
Help!