DM-Crypt Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Milan Broz <mbroz@redhat.com>
To: Mario 'BitKoenig' Holbe <Mario.Holbe@TU-Ilmenau.DE>
Cc: dm-crypt@saout.de
Subject: Re: [dm-crypt] Is partial LUKS recovery possible?
Date: Thu, 02 Dec 2010 18:04:01 +0100	[thread overview]
Message-ID: <4CF7D181.7020907@redhat.com> (raw)
In-Reply-To: <slrniffi91.9qh.Mario.Holbe@darkside.dyn.samba-tng.org>

On 12/02/2010 05:28 PM, Mario 'BitKoenig' Holbe wrote:
> Milan Broz <mbroz@redhat.com> wrote:
>> On 12/02/2010 04:45 PM, Mario 'BitKoenig' Holbe wrote:
>>> It is not easy to check if your dm-crypt mapping is correct (i.e. feeded
>>> with the correct key, the correct device offset, etc.) if, like in your
>>> case, there is damage in the beginning of the partition - that decrypts
>> If you know, that there was an fs, it is easy, just run
>> blkid -p /dev/mapper/<cryptdevice>
>> and it should detect fs signature.
> 
> Nope. blkid just probes the primary superblock, which is damaged if the
> beginning of the partition is damaged.

Ah so, I should read it properly.
You can probably use offset option in blkid, so it scans for backup superblock
but that is not so easy.

Milan

  reply	other threads:[~2010-12-02 17:04 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-02 10:28 [dm-crypt] Is partial LUKS recovery possible? Miklos Bagi
2010-12-02 12:15 ` Miklos Bagi
2010-12-02 17:39   ` Arno Wagner
2010-12-02 17:44     ` Nargis Khan
2010-12-02 12:31 ` Mario 'BitKoenig' Holbe
2010-12-02 14:17   ` Miklos Bagi
2010-12-02 15:45     ` Mario 'BitKoenig' Holbe
2010-12-02 16:20       ` Milan Broz
2010-12-02 16:28         ` Mario 'BitKoenig' Holbe
2010-12-02 17:04           ` Milan Broz [this message]
2010-12-02 17:11             ` Mario 'BitKoenig' Holbe
     [not found]       ` <4CF81339.9070004@mbjr.hu>
2010-12-02 22:27         ` Mario 'BitKoenig' Holbe

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=4CF7D181.7020907@redhat.com \
    --to=mbroz@redhat.com \
    --cc=Mario.Holbe@TU-Ilmenau.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