From: Uwe Menges <uwe.menges@web.de>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] Fwd: Recover a LUKS partition
Date: Thu, 27 May 2010 19:13:01 +0200 [thread overview]
Message-ID: <4BFEA81D.3090606@web.de> (raw)
In-Reply-To: <AANLkTiknOylZHrXayZdXYIbKIUHGuL4OxGmfF7ihMDLM@mail.gmail.com>
On 05/27/2010 02:46 PM, fred smith wrote:
> I am desperate to try to recover this disk - it has important stuff on
> it. Any suggestions or pointers?
A good start would be to get some things straight. In your first email
you eg. left open if /dev/sdc1 or /dev/sdc2 is the partition supposed to
be encrypted. A bit of history would probably also help (initial
partition layout, what you did that it's different now, etc.).
> I know the passphrase, but is there any way of recover the first part
> of the partition? I have attached the drive via an external interface
> and 'gparted' shows:
>
> /dev/sdb1 fat32 200MiB first sector 40 last sector 409689
> /dev/sdb2 hfs+ 931.19GiB first sector 409640
Does not look good to me, because (sdb2 first sector) < (sdb1 last sector).
You could scan the disk for LUKS header (eg. here "hexdump -C /dev/sda2
| less" shows that the first bytes are "LUKS" (4c 55 4b 53)).
"testdisk" may also help. Good practice is to always work on a copy of
the disk to recover, not the original.
If you have lost the LUKS header, recovery is impossible, because that's
exactly what crypto stuff is for. Reconsider your backup strategy.
Yours, Uwe
next prev parent reply other threads:[~2010-05-27 17:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-24 15:45 [dm-crypt] Recover a LUKS partition fred smith
2010-05-27 12:46 ` [dm-crypt] Fwd: " fred smith
2010-05-27 17:13 ` Uwe Menges [this message]
2010-05-27 17:54 ` fred smith
2010-05-27 19:13 ` fred smith
2010-05-27 17:53 ` orinoco
2010-05-27 22:08 ` 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=4BFEA81D.3090606@web.de \
--to=uwe.menges@web.de \
--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