All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arno Wagner <arno@wagner.name>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] LUKS keyslot 4 is invalid
Date: Thu, 20 Nov 2014 20:04:40 +0100	[thread overview]
Message-ID: <20141120190440.GA7061@tansi.org> (raw)
In-Reply-To: <CAKG3i5rcc-cHDvjhagCjyhvzA+bttO3zdka+OHsWkjebZ3svww@mail.gmail.com>

Hi s4per,

this should be caused by something wrinign over the info for
Keyslot 4 (and possibly later) in the header. 

First, before you do anything, make that header backup, as described
in the FAQ, Itmm 6.2.  It will prevent things from getting worse. 
(http://code.google.com/p/cryptsetup/wiki/FrequentlyAskedQuestions)

Usually, you key should be in keyslot 1 and that may still be 
intact. As you can see in FAQ Item 6.12, keyslot infor for 
keyslot 4 is stored at offset 0x190, so anything damaging it 
could also have damaged other fields in the LUKS header.
Still, give this a try:

   cryptsetup repair <device>

It may work, or it may give you another error. If so, please
post that here. (Do NOT do this wiothout header backup!)

Arno





On Wed, Nov 19, 2014 at 23:52:38 CET, Jarosław K wrote:
> Hi all,
> 
> I have an encrypted RAID 1 volume for /home directory. I set it to mount
> automatically after login (based on
> http://nanonanonano.net/linux/debian/enchome). All of it works perfect
> during a few months. Until today ... After login I saw a "clean" user
> profile on my Debian. I know that, my encrypted drive didn't mount
> correctly. Unfortunately, manually mount failed too:
> 
> root@s4per-debian:/home/s4per# cryptsetup luksOpen
> /dev/mapper/isw_echheajchc_Mirror crypt
> Numer klucza LUKS 4 jest nieprawidłowy.   ---> LUKS keyslot 4 is invalid (?)
> 
> I have read something about this issue, and now i think it could be problem
> with LUKS headers. But unfortunatelly i have no any backup of it.
> 
> In Poland we says "Polish wise after the event". Now I know, that I should
> make some backup of headers.
> 
> I kindly request for some help.
> 
> My OS: Debian Sid AMD64
> 
> Regards,
> 
> s4per

> _______________________________________________
> dm-crypt mailing list
> dm-crypt@saout.de
> http://www.saout.de/mailman/listinfo/dm-crypt


-- 
Arno Wagner,     Dr. sc. techn., Dipl. Inform.,    Email: arno@wagner.name
GnuPG: ID: CB5D9718  FP: 12D6 C03B 1B30 33BB 13CF  B774 E35C 5FA1 CB5D 9718
----
A good decision is based on knowledge and not on numbers. -- Plato

If it's in the news, don't worry about it.  The very definition of 
"news" is "something that hardly ever happens." -- Bruce Schneier

  reply	other threads:[~2014-11-20 19:04 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-19 22:52 [dm-crypt] LUKS keyslot 4 is invalid Jarosław K
2014-11-20 19:04 ` Arno Wagner [this message]
2014-11-25 21:50 ` Jarosław K
2014-11-25 23:15   ` Arno Wagner
2014-11-26 17:11   ` Jarosław K
2014-11-26 17:54     ` Arno Wagner
  -- strict thread matches above, loose matches on Subject: below --
2011-11-26 14:19 Mika Kujanpää
2011-11-26 18:45 ` Milan Broz
2011-11-27 11:33   ` Milan Broz
2011-11-27 12:30     ` 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=20141120190440.GA7061@tansi.org \
    --to=arno@wagner.name \
    --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 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.