From: Arno Wagner <arno@wagner.name>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] Broken LUKS header
Date: Wed, 3 Sep 2014 13:32:33 +0200 [thread overview]
Message-ID: <20140903113232.GA429@tansi.org> (raw)
In-Reply-To: <BLU184-W956C554A2837B7CB6A0EDDE8C40@phx.gbl>
Hat do you mean by the keyslot checker "did not work at all"?
Have you tried it after the wrong offsets were corrected?
I suspect the damage has existed for a time and you only
now found it. Wrong offsets can in principle only be
corruption done from external, as these do not get
written after header creation, AFAIK.
Arno
On Wed, Sep 03, 2014 at 11:03:46 CEST, Andreas Aßmann wrote:
> Hi everyboy,
>
> I got a (serious) problem with a broken LUKS header.
>
> A little background:
> I've
> been using dm-crypt / LUKS for many years without ever having any
> problems until now. On one of my Linux boxes, I have three encrypted
> volumes for root (/dev/sda2), swap (/dev/sda3) and home (/dev/sdb1).
>
> My problem:
> A
> few days ago, I tried to add a key file to all three volumes using
> 'cryptsetup luksAddKey'. The command succeeded for sda2 and sda3. Adding
> the key file to sdb1, however, failed with 'Invalid Key Slot 6, Invalid
> Key Slot 7'. It seems the LUKS header of sdb1 was corrupted in the
> process. Probing the header using 'cryptsetup luksDump' fails with the
> same error message.
>
> Fortunately, sdb1 was unlocked and mounted
> when this happened - I was still able to access data on this volume and
> from what I've seen, everything is still intact, so I created a complete
> backup right away using rsync. However, I would feel much better if I
> could repair the header to verify that the backup I made actually
> contains all data from sdb1.
>
> I also created a 1:1 backup of sdb1
> using dd. On this backup, I tried 'keyslot_checker' and 'cryptsetup
> repair'. The first didn't work at all, the latter reported invalid
> offsets for key slots 6 and 7 and fixed them. However, I was unable to
> open the volume using my normal passphrase afterwards, so that didn't
> work out as expected.
>
> Help would be greatly appreciated. Sorry for my bad English, I am not a native speaker.
>
> _______________________________________________
> dm-crypt mailing list
> dm-crypt@saout.de
> http://www.saout.de/mailman/listinfo/dm-crypt
--
Arno Wagner, Dr. sc. techn., Dipl. Inform., Email: arno@wagner.name
GnuPG: ID: CB5D9718 FP: 12D6 C03B 1B30 33BB 13CF B774 E35C 5FA1 CB5D 9718
----
A good decision is based on knowledge and not on numbers. -- Plato
If it's in the news, don't worry about it. The very definition of
"news" is "something that hardly ever happens." -- Bruce Schneier
next prev parent reply other threads:[~2014-09-03 11:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-03 9:03 [dm-crypt] Broken LUKS header Andreas Aßmann
2014-09-03 11:32 ` Arno Wagner [this message]
2014-09-03 14:56 ` Robert Nichols
-- strict thread matches above, loose matches on Subject: below --
2014-09-03 9:00 Andreas Aßmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140903113232.GA429@tansi.org \
--to=arno@wagner.name \
--cc=dm-crypt@saout.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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.