From: Milan Broz <gmazyland@gmail.com>
To: dm-crypt <dm-crypt@saout.de>
Subject: Re: [dm-crypt] LUKS keyslot invalid
Date: Mon, 31 Dec 2012 12:26:16 +0100 [thread overview]
Message-ID: <50E17658.5020800@gmail.com> (raw)
In-Reply-To: <4FE1ACE321FB45CABE8FE1C09A8D060B@ws1xp>
On 12/29/2012 11:03 PM, wpc95 wrote:
> Running Ubuntu 12.04 (cryptsetup 1.4.0) LUKS claims for 2 of the
> encrypted drives, that 'LUKS keyslot 4 is invalid'. Due to the fact that the
> option 'repair' was launched with cryptsetup 1.4.1, i have started the
> computer with an actual live-linux. But the result with cryptsetup 1.5.0 is
> the same as with 1.4.0: it claims, that 'LUKS keyslot 4 is invalid. Invalid
> offset 1576471435 [first drive] 3746914134 [second drive] in keyslot 4.' The
> repair option says that repair failed with code 22 and a manual repair is
> required.
Just for the archive - the current repair code is able to fix this problem
(it was just simple 4 bytes overwrite, fortunately on unused keyslot metadata).
I was just too cautious and did not enabled repair of 512bit (XTS mode) keys.
That restriction is now removed, so next time repair code should work.
Milan
prev parent reply other threads:[~2012-12-31 11:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-29 22:03 [dm-crypt] LUKS keyslot invalid wpc95
2012-12-30 14:38 ` Milan Broz
2012-12-31 11:26 ` Milan Broz [this message]
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=50E17658.5020800@gmail.com \
--to=gmazyland@gmail.com \
--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