From: Milan Broz <mbroz@redhat.com>
To: Willie <tumbleweed@fastmail.net>
Cc: dm-crypt@saout.de
Subject: Re: [dm-crypt] Hosed encrypted drive. Is disaster recovery possible?
Date: Mon, 02 Aug 2010 11:58:58 +0200 [thread overview]
Message-ID: <4C5696E2.1000509@redhat.com> (raw)
In-Reply-To: <1280738327.12803.1387859489@webmail.messagingengine.com>
On 08/02/2010 10:38 AM, Willie wrote:
> I still have
> "/dev/mapper/udisks-luks-uuid-c1a534b4-d1ba-40d0-adb8-6d2490f06ade-uid9330
> on /media/Seagate_1.5 type xfs (rw,nosuid,nodev,uhelper=udisks)", and
> obviously I have the pass phrase.
If you have live mapping still, you are not lost completely yet.
Do not reboot! First run "dmsetup table --showkeys" and "dmsetup info -c"
and store the full mapping to some file.
If you see dm-crypt mapping there mapped to proper drive, you can still recreate
LUKS header with some some magic.
(If you have saved that dmsetup mapping, I'll describe hot to save you data
- still depends how many of fs was overwritten.)
If you want help with that, paste here "dmsetup table" (*without* using --showkeys,
we do not want see your master key:-). For recovery you will need to know that key,
so be sure you have full table with key stored as written above.
(Table is created according to LUKS header which is lost, so after reboot you are
lost completely. BTW Passphrase will not help here at all.)
Milan
next prev parent reply other threads:[~2010-08-02 9:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-01 21:11 [dm-crypt] Hosed encrypted drive. Is disaster recovery possible? Willie
2010-08-01 21:26 ` Christoph Anton Mitterer
2010-08-01 23:01 ` Arno Wagner
2010-08-01 23:20 ` Willie
2010-08-02 0:27 ` Arno Wagner
2010-08-02 8:38 ` Willie
2010-08-02 9:05 ` Arno Wagner
2010-08-02 9:58 ` Milan Broz [this message]
2010-08-02 10:21 ` Mikko Rauhala
2010-08-02 13:43 ` [dm-crypt] How to gather LUKS parameters from active device (if LUKS header lost) Milan Broz
2010-08-02 17:33 ` Willie
2010-08-02 17:36 ` Arno Wagner
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=4C5696E2.1000509@redhat.com \
--to=mbroz@redhat.com \
--cc=dm-crypt@saout.de \
--cc=tumbleweed@fastmail.net \
/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.