Hi Ralf,
have you tried decrypting it manually? Either typing in the password or decrypting the keyfile in /tmp/ (or some other location) and using the --key-file option to pass it to cryptsetup?
If that doesn't work, then it's probably a corrupted header, but if that works it's only a configuration problem.have you tried decrypting it manually? Either typing in the password or decrypting the keyfile in /tmp/ (or some other location) and using the --key-file option to pass it to cryptsetup?
Claudio
On Mon, Dec 2, 2013 at 4:53 PM, Ralf Ramsauer <ralf+dm@xxxxxxxxxxxxxxxxxxxxxx> wrote:
On 12/02/2013 05:47 PM, Ralf Ramsauer wrote:Little mistake, <device> should of course be your header backup file.
> cryptsetup luksHeaderRestore /dev/sdaX --header-backup-file <device>
Regards
_______________________________________________
dm-crypt mailing list
dm-crypt@xxxxxxxx
http://www.saout.de/mailman/listinfo/dm-crypt
_______________________________________________ dm-crypt mailing list dm-crypt@xxxxxxxx http://www.saout.de/mailman/listinfo/dm-crypt
