Cryptsetup (and Cryptsetup-LUKS)randomly fail to open encrypted lvm2 volume on boot and from console Tested ebuild versions cryptsetup-1.0.5-r1 cryptsetup-luks-1.0.4-r3 cryptsetup-luks-1.0.4-r1 cryptsetup-luks-1.0.4 cryptsetup-luks-1.0.3-r3 according search, problem exist in other distributives and in fact result of conflict between cryptsetup and udev implementation Kernel 2.6.22 udev 115-r1 Workarond: 1. repeat open step till all volumes eventually will be open 2. alter initrd script Other distro's: (and more info) http://www.mail-archive.com/debian-bugs-dist@.../msg399849.html https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/105266 http://www.nabble.com/-Bug-35017--cryptsetup,-NEW:-Cryptsetup-operations-fails-randomly-td13384821.html Console output: Failed to setup dm-crypt key mapping. Check kernel for support for the aes-cbc-essiv:sha256 cipher spec and verify that /dev/mapper/secure contains at least 261 sectors. Failed to read from key storage Command failed: No key available with this passphrase. Reproducible: Sometimes Steps to Reproduce: 1.just try to open several lvm2 volumes encrypted with cryptsetup-luks it occurs ~50/50 2. 3.
Reassigning back to herd since Benjamin has retired as a Gentoo developer (#89719).
looks like a timing issue with udev ... in some cases, cryptsetup runs before udev finishes everything
this is fixed actually with cryptsetup-1.0.6
