From: Arno Wagner <arno@wagner.name>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] Incidentaly partitioned LUKS device - header lost?
Date: Sat, 2 Jul 2016 12:25:17 +0200 [thread overview]
Message-ID: <20160702102517.GA23072@tansi.org> (raw)
In-Reply-To: <20160702102000.GA22828@tansi.org>
Ah, sorry, I am confused. The first question is whether
you killed the RAID as well or whether you created the
msdos partition table within /dev/md2. In the latter
case we do not need the RAID info.
Regards,
Arno
On Sat, Jul 02, 2016 at 12:20:00 CEST, Arno Wagner wrote:
> Hi Bernd,
>
> data-recovery for this is typically relatively easy or completely
> impossible. To determine which it is, we need to find out what
> happened exactly. The only really irreplaceable values in the header
> are the salts (see FAQ Item 6.12). These are not secret, but
> each is 256 bits of crypto-grade randomness and they cannot
> be reconstructed or guessed.
>
> The first question is what was overwritten by that partition
> sector. Traditionally, Linux software RAID has the RAID superblock
> at the end, but unfortunately some people "improved" this, so
> it can now be at the end, at the start and at 4kB from the start.
>
> This is relevant becauese it influences the data offset, i.e.
> the place where the LUKS header is put.
>
> Hence we need the output of
>
> mdadm --detail /dev/md2
>
> whichs dumps the RAID metadata.
>
> Regards,
> Arno
>
>
> On Sat, Jul 02, 2016 at 08:33:09 CEST, Bernd Brägelmann wrote:
> > Hi there,
> >
> > i think i destroyed my luks data.
> >
> > I accidentally created a msdos partition table on the luks device. I
> > think the device was not partitioned. The device is a raid5 mdadm at
> > /dev/md2.
> >
> > Now i cannot luksOpen the device anymore.
> >
> > I already try to hexdump|grep for the LUKS header but until now i
> > haven't found it. In the Luks-FAQ 6.1 the problem is described as a
> > common user error and it is very common that the partitioning has
> > destroyed the LUKS header.
> >
> > My question is: Is my data destroyed beyond recovery? It would really
> > help me to cope with this. Is it possible to "manually" fix a partially
> > destroyed LUKS header? Are there other ways to recover the data? I would
> > gladly pay for a recovery solution.
> >
> > Regards,
> >
> > Bernd
> >
> > --
> > Bernd Brägelmann - FA für Radiologie
> > Robert-Koch-Straße 42 28277 Bremen
> > www.berndbraegelmann.de +4915141457796
> > _______________________________________________
> > 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
> _______________________________________________
> 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:[~2016-07-02 10:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-02 6:33 [dm-crypt] Incidentaly partitioned LUKS device - header lost? Bernd Brägelmann
2016-07-02 10:20 ` Arno Wagner
2016-07-02 10:25 ` Arno Wagner [this message]
2016-07-02 10:42 ` Bernd Brägelmann
2016-07-02 16:14 ` Arno Wagner
2016-07-02 18:11 ` Bernd Brägelmann
2016-07-02 18:55 ` Arno Wagner
2016-07-02 20:06 ` Bernd Brägelmann
2016-07-02 21:53 ` Arno Wagner
2016-07-03 20:40 ` Michael Kjörling
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=20160702102517.GA23072@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox