Skip to contentSkip to conversation

unable to mount my encrypted drive

dm-crypt Rick Farina 3 participants 5 messages Dec 2, 2013 – Dec 3, 2013

lore
Share & tools
lore
#0 lore raw

All of a sudden, I'm unable to mount my encrypted drive anymore. I don't really reboot a lot, so I'm sure a lot has changed since my last luksOpen including kmod version and cryptsetup being updated from 1.4.3 to 1.6.2.

I typically decrypt with something like this:

zero@ozzie ~ % gpg --batch --decrypt /run/usbstick/slicehdd.gpg 2> /dev/null | sudo cryptsetup luksOpen /dev/sdb1 slice -d -

But now all I'm getting is this:

No key available with this passphrase.

here is some additional information:

zero@ozzie ~ % sudo cryptsetup luksDump /dev/sdb1
LUKS header information for /dev/sdb1

Version:       	1
Cipher name:   	aes
Cipher mode:   	xts-essiv:wp256
Hash spec:     	sha1
Payload offset:	4096
MK bits:       	512
MK digest:     	removed
MK salt:       	removed
MK iterations: 	removed
UUID:          	removed

Key Slot 0: ENABLED
Iterations: removed
Salt: removed
Key material offset: removed
AF stripes: removed
Key Slot 1: DISABLED
Key Slot 2: DISABLED
Key Slot 3: DISABLED
Key Slot 4: DISABLED
Key Slot 5: DISABLED
Key Slot 6: DISABLED
Key Slot 7: DISABLED

Please let me know what else is needed for troubleshooting.

Thanks for the support, and the great software. Been using cryptsetup for years and loving it.

-Zero

#1 lore raw

It looks like your luks header is corrupted.

If you did backup your header, you can restore it using
cryptsetup luksHeaderRestore /dev/sdaX --header-backup-file <device>

Regards
Ralf

Quoted 17 lines · Rick Farina
MK digest:     	removed
MK salt:       	removed
MK iterations: 	removed
UUID:          	removed

Key Slot 0: ENABLED
Iterations: removed
Salt: removed
Key material offset: removed
AF stripes: removed
Key Slot 1: DISABLED
Key Slot 2: DISABLED
Key Slot 3: DISABLED
Key Slot 4: DISABLED
Key Slot 5: DISABLED
Key Slot 6: DISABLED
Key Slot 7: DISABLED

#2 lore raw
Quoted 1 line · Ralf Ramsauer
  cryptsetup luksHeaderRestore /dev/sdaX --header-backup-file <device>

Little mistake, <device> should of course be your header backup file.

Regards

#3 lore raw

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.

Regards,

Claudio

Quoted 10 lines · Ralf Ramsauer
Quoted 1 line · Ralf Ramsauer
  cryptsetup luksHeaderRestore /dev/sdaX --header-backup-file <device>

Little mistake, <device> should of course be your header backup file.

Regards
_______________________________________________
dm-crypt mailing list
[email protected]
http://www.saout.de/mailman/listinfo/dm-crypt

#4 lore raw

I meant "Rick", not "Ralf". Sorry :P

Quoted 29 lines · Claudio Moretti

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.

Regards,

Claudio

Quoted 10 lines · Ralf Ramsauer
Quoted 1 line · Ralf Ramsauer
  cryptsetup luksHeaderRestore /dev/sdaX --header-backup-file <device>

Little mistake, <device> should of course be your header backup file.

Regards
_______________________________________________
dm-crypt mailing list
[email protected]
http://www.saout.de/mailman/listinfo/dm-crypt