All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oko Hid <randomwalker0201@gmail.com>
To: Milan Broz <gmazyland@gmail.com>
Cc: dm-crypt@saout.de
Subject: Re: [dm-crypt] unlock luks volume using valid keyslot
Date: Tue, 28 Jun 2016 19:27:19 +0900	[thread overview]
Message-ID: <CAEJM0ZOPE+1F=qG+eb9d8bH_q_28xdGThpWBNZMfJF1qSzYLSg@mail.gmail.com> (raw)
In-Reply-To: <d48279f0-180a-763b-043c-09bdcfe98d3a@gmail.com>

Dear Milan,
and dm-crypt members

Thank you for your quick response.
From now, I try to repair my hdd referring your advice, carefully.

Later, I will report the result.

Thank you, again.


2016-06-28 19:11 GMT+09:00 Milan Broz <gmazyland@gmail.com>:
> On 06/28/2016 07:47 AM, Oko Hid wrote:
>> Dear dm-crypt members,
>>
>> Please teach me how to unlock the luks partition using valid keyslot.
>
> ...
>
>
>> # Invalid offset 3012998038 in keyslot 4 (beyond data area offset 4096).
>> LUKS keyslot 4 is invalid.
> ...
>
>> The output message shows the addresses of keyslots, and
>> of keyslot 4 may be invalid.
>> (However, 0 seems ok ... I wish.)
>>
>> So, how can I do for this situation?
>> Is it possible to access the partition and data using Keyslot 0 ?
>
> Backup you header manually (just dd 4MB of the device).
> dd if=<device> of=backupfile.img bs=1M count=4
> (Do not skip this step, really :)
>
> Then run "cryptsetup repair <device>". It should fix slot offsets
> and you should be able to access it again.
>
> Milan
>

  reply	other threads:[~2016-06-28 10:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-28  5:47 [dm-crypt] unlock luks volume using valid keyslot Oko Hid
2016-06-28 10:11 ` Milan Broz
2016-06-28 10:27   ` Oko Hid [this message]
2016-06-28 13:55 ` Arno Wagner
2016-06-28 14:13   ` 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='CAEJM0ZOPE+1F=qG+eb9d8bH_q_28xdGThpWBNZMfJF1qSzYLSg@mail.gmail.com' \
    --to=randomwalker0201@gmail.com \
    --cc=dm-crypt@saout.de \
    --cc=gmazyland@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.