From: Milan Broz <mbroz@redhat.com>
To: Panagiotis Malakoudis <malakudi@gmail.com>
Cc: dm-crypt@saout.de
Subject: Re: [dm-crypt] Corrupted luks partition, help needed
Date: Thu, 03 Jun 2010 17:51:04 +0200 [thread overview]
Message-ID: <4C07CF68.7090708@redhat.com> (raw)
In-Reply-To: <AANLkTinjoL2jxJxH6KZip99GSIxSxqR3njVxboCqEgO_@mail.gmail.com>
On 06/03/2010 05:32 PM, Panagiotis Malakoudis wrote:
> I have a luks partition which was corrupted by failed disk i/o.
> Examining the partition, the first 512 bytes of the LUKS header is
> correct, then there is a corruption which I am not really sure how many
> sectors affected. Giving the correct key always returns: "No key
> available with this passphrase.". Since the first 512 bytes are correct,
> I guess all key information is unharmed. Is there a way to decrypt the
> partition, even loosing some sectors of data?
If any part of the used keyslot (which is located after visible header,
- in you case starting at sector 8 to sector 264 (hope I calculated it properly),
is modified or lost, you lost that keyslot completely.
Because you have only one active keyslot, you probably lost the whole disk:-(
(Only backup of this keyslot area can help here.)
Milan
next prev parent reply other threads:[~2010-06-03 15:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-03 15:32 [dm-crypt] Corrupted luks partition, help needed Panagiotis Malakoudis
2010-06-03 15:51 ` Milan Broz [this message]
2010-06-03 16:16 ` Panagiotis Malakoudis
2010-06-03 18:12 ` Milan Broz
2010-06-03 18:05 ` Panagiotis Malakoudis
2010-06-03 20:14 ` Arno Wagner
2010-06-03 20:48 ` Luca Berra
2010-06-03 20:56 ` Christoph Anton Mitterer
2010-06-03 22:07 ` Arno Wagner
2010-06-04 6:05 ` Panagiotis Malakoudis
2010-06-04 8:54 ` Roscoe
2010-06-06 19:57 ` [dm-crypt] cryptsetup administration tool Ali Reza Sajedi
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=4C07CF68.7090708@redhat.com \
--to=mbroz@redhat.com \
--cc=dm-crypt@saout.de \
--cc=malakudi@gmail.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 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.