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 18:14:56 +0200 [thread overview]
Message-ID: <20160702161456.GA24756@tansi.org> (raw)
In-Reply-To: <57779A93.20805@braegelmann.net>
Hi Bernd,
On Sat, Jul 02, 2016 at 12:42:27 CEST, Bernd Brägelmann wrote:
> Hi Arno,
>
> thanks for answering. I created the partition table within /dev/md2 and
> the raid is still working.
Ok, so we ignore the RAID.
> My current last hope is that the salt might be in a redundant part of
> the raid array.
Those will have gotten synced immediately, RAID inconsistencies
live only for as long as they are in the write queue. No hope
there.
Ok, the LUKS superblock (or what is left of it) will be at
the start of /dev/md2. Can you post the following (will
not compromise your datta, that is protected by the
passphrase(s)):
head -c 1k /dev/md2 | hd
This allows a manual look of what is left of the LUKS header.
Regards,
Arno
--
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 16:14 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
2016-07-02 10:42 ` Bernd Brägelmann
2016-07-02 16:14 ` Arno Wagner [this message]
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=20160702161456.GA24756@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.