On Tue, May 5, 2009 at 8:07 AM, Ross Boylan <ross@xxxxxxxxxxxxxxxx> wrote: > # cryptsetup --hash sha1 --cipher cbc-essiv:sha256 --key-size 256 > luksFormat /dev/turtle/var2 > # cryptsetup luksOpen /dev/turtle/var2 /dev/mapper/turtle-var2_crypt > Enter LUKS passphrase: > Command failed: No key available with this passphrase. I would have said your second argument should not have the /dev/mapper prefix. What's weird is that in my case, if I try the same thing, I get: Enter LUKS passphrase: key slot 0 unlocked. Command failed: dm_task_set_name: Device /dev/mapper/turtle-var2_crypt not found The error message is different. As I understood it, the <name> you use in luksOpen could be *anything*; it doesn't have to have any relation or relevance to the luksDevice you're opening. Whatever name you choose becomes the new device (with /dev/mapper/ prefixed) for other operations like mount.
