From: Sitaram Chamarty <sitaramc@gmail.com>
To: David Backer <doark@mail.com>, dm-crypt@saout.de
Subject: Re: [dm-crypt] Data recovery recomendations needed
Date: Tue, 21 Apr 2015 10:46:20 +0530 [thread overview]
Message-ID: <5535DD24.9040609@gmail.com> (raw)
In-Reply-To: <trinity-8214a650-98c4-471e-9376-8e7b48b9a9be-1429591086003@3capp-mailcom-lxa02>
On 04/21/2015 10:08 AM, David Backer wrote:
> Even if they just copied off the raw sectors, I could use
> them to recover the data if I moved it to a new drive
> provided that the LVM info and the LUKS headers are intact
> right?
This may be very naive of me, but it seems to me you need to do it in 3
steps:
- get the raw data off (maybe DIY using 'ddrescue' or some such
program, or farm it out).
- assuming the LUKS headers etc are ok, mount the rescued data as a
"drive" (or figure out some way of applying the same decryption that
dm-crypt's block-by-block enc/dec does). Read off the raw blocks,
this time unencrypted, and write them to another device.
- use that device to recover the actual data. This is where knowledge
of the internals of your filesystem will be needed, and you will
probably need to farm it out. I'm assuming that's why those
specialists exist.
next prev parent reply other threads:[~2015-04-21 5:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-21 4:38 [dm-crypt] Data recovery recomendations needed David Backer
2015-04-21 5:16 ` Sitaram Chamarty [this message]
2015-04-21 9:34 ` Sven Eschenberg
2015-04-21 18:49 ` Arno Wagner
2015-04-21 20:29 ` Sven Eschenberg
2015-04-21 18:18 ` David Christensen
2015-04-21 18:45 ` Arno Wagner
-- strict thread matches above, loose matches on Subject: below --
2015-04-21 4:40 David Backer
2015-04-21 3:18 David Backer
2015-04-21 3:45 ` David Christensen
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=5535DD24.9040609@gmail.com \
--to=sitaramc@gmail.com \
--cc=dm-crypt@saout.de \
--cc=doark@mail.com \
/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