On a freshly installed Fedora Core 6 x86_64 system (with SE/Linux in Permissive mode because otherwise Emacs can't load fonts!), I am attempting to create a new partition as follows: cryptsetup luksFormat /dev/sdb2 /tmp/foo cryptsetup --key-file=/tmp/foo luksOpen /dev/sdb2 sdb2 Often--but not always--I get the error "No key available with this passphrase" from the luksOpen operation. Once it works, it works reliably--that is, subsequent luksClose and luksOpen operations work as expected, as long as I don't do another luksFormat. The error seems to occur randomly, but once it starts to happen for a given partition, it keeps happening pretty reliably. It always (so far) works after a reboot, at least twice for each partition. It doesn't seem dependent on the specific partition, in that it's failing both for partitions on either raw disk (e.g., /dev/sdb2) and for RAID partitions. The failure occurs both when the passphrase is entered directly and when the passphrase is stored in a key file. It also seems to be independent of cipher specification (I've tried both plain "blowfish" and "aes-cbc-essiv:sha256"). FC6 has cryptsetup v1.0.3 (and kernel 2.6.18), but nothing in the v1.0.4 description led me to believe it addresses this problem. Any suggestions on where I should look next to try debugging this? I've had plenty of satisfactory experience with FC5 on this system (although with no serious use of dm-crypt), and I have no evidence of hardware instability. Cheers -- Olin --------------------------------------------------------------------- dm-crypt mailing list - http://www.saout.de/misc/dm-crypt/ To unsubscribe, e-mail: dm-crypt-unsubscribe@xxxxxxxx For additional commands, e-mail: dm-crypt-help@xxxxxxxx
