* [dm-crypt] unable to mount my encrypted drive
@ 2013-12-02 16:22 Rick Farina
2013-12-02 16:47 ` Ralf Ramsauer
0 siblings, 1 reply; 5+ messages in thread
From: Rick Farina @ 2013-12-02 16:22 UTC (permalink / raw)
To: dm-crypt
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
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [dm-crypt] unable to mount my encrypted drive
2013-12-02 16:22 [dm-crypt] unable to mount my encrypted drive Rick Farina
@ 2013-12-02 16:47 ` Ralf Ramsauer
2013-12-02 16:53 ` Ralf Ramsauer
0 siblings, 1 reply; 5+ messages in thread
From: Ralf Ramsauer @ 2013-12-02 16:47 UTC (permalink / raw)
To: dm-crypt
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
On 12/02/2013 05:22 PM, Rick Farina wrote:
> 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
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [dm-crypt] unable to mount my encrypted drive
2013-12-02 16:47 ` Ralf Ramsauer
@ 2013-12-02 16:53 ` Ralf Ramsauer
2013-12-02 20:14 ` Claudio Moretti
0 siblings, 1 reply; 5+ messages in thread
From: Ralf Ramsauer @ 2013-12-02 16:53 UTC (permalink / raw)
To: dm-crypt
On 12/02/2013 05:47 PM, Ralf Ramsauer wrote:
> cryptsetup luksHeaderRestore /dev/sdaX --header-backup-file <device>
Little mistake, <device> should of course be your header backup file.
Regards
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [dm-crypt] unable to mount my encrypted drive
2013-12-02 16:53 ` Ralf Ramsauer
@ 2013-12-02 20:14 ` Claudio Moretti
2013-12-03 12:21 ` Claudio Moretti
0 siblings, 1 reply; 5+ messages in thread
From: Claudio Moretti @ 2013-12-02 20:14 UTC (permalink / raw)
To: Ralf Ramsauer; +Cc: dm-crypt@saout.de
[-- Attachment #1: Type: text/plain, Size: 771 bytes --]
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
On Mon, Dec 2, 2013 at 4:53 PM, Ralf Ramsauer <
ralf+dm@ramses-pyramidenbau.de> wrote:
> On 12/02/2013 05:47 PM, Ralf Ramsauer wrote:
> > cryptsetup luksHeaderRestore /dev/sdaX --header-backup-file <device>
> Little mistake, <device> should of course be your header backup file.
>
> Regards
> _______________________________________________
> dm-crypt mailing list
> dm-crypt@saout.de
> http://www.saout.de/mailman/listinfo/dm-crypt
>
[-- Attachment #2: Type: text/html, Size: 1378 bytes --]
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [dm-crypt] unable to mount my encrypted drive
2013-12-02 20:14 ` Claudio Moretti
@ 2013-12-03 12:21 ` Claudio Moretti
0 siblings, 0 replies; 5+ messages in thread
From: Claudio Moretti @ 2013-12-03 12:21 UTC (permalink / raw)
To: Ralf Ramsauer; +Cc: dm-crypt@saout.de
[-- Attachment #1: Type: text/plain, Size: 931 bytes --]
I meant "Rick", not "Ralf". Sorry :P
On Mon, Dec 2, 2013 at 8:14 PM, Claudio Moretti <flyingstar16@gmail.com>wrote:
> 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
>
>
> On Mon, Dec 2, 2013 at 4:53 PM, Ralf Ramsauer <
> ralf+dm@ramses-pyramidenbau.de> wrote:
>
>> On 12/02/2013 05:47 PM, Ralf Ramsauer wrote:
>> > cryptsetup luksHeaderRestore /dev/sdaX --header-backup-file <device>
>> Little mistake, <device> should of course be your header backup file.
>>
>> Regards
>> _______________________________________________
>> dm-crypt mailing list
>> dm-crypt@saout.de
>> http://www.saout.de/mailman/listinfo/dm-crypt
>>
>
>
[-- Attachment #2: Type: text/html, Size: 1859 bytes --]
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2013-12-03 12:21 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-12-02 16:22 [dm-crypt] unable to mount my encrypted drive Rick Farina
2013-12-02 16:47 ` Ralf Ramsauer
2013-12-02 16:53 ` Ralf Ramsauer
2013-12-02 20:14 ` Claudio Moretti
2013-12-03 12:21 ` Claudio Moretti
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.