From: Arno Wagner <arno@wagner.name>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] can't open luks device after raid 5 rebuild
Date: Sun, 8 Apr 2012 17:47:53 +0200 [thread overview]
Message-ID: <20120408154753.GA31917@tansi.org> (raw)
In-Reply-To: <4F818CEF.3030706@googlemail.com>
Hi,
a RAID degradation and successful rebuild does not have this
effect. Did you do something else? Or did you do a manual (forced)
rebuild? What exactly did happen to the RAID and what did you
do to fix it?
The symptoms you see are typical for a damaged key-slot. The
header resides in a single sector and is not affected.
If so, a header backup is possibly the only thing that will
help you, see the FAQ for details.
Arno
On Sun, Apr 08, 2012 at 03:04:47PM +0200, artificial11000 wrote:
> Hi guys,
>
> after my encrypted RAID 5 was degraded and rebuilt, I can't open it anymore.
>
> cryptsetup luksOpen /dev/md127 archiv
> Geben Sie den Passsatz f?r /dev/md127 ein:
> Kein Schl?ssel mit diesem Passsatz verf?gbar.
>
> It says that the provided password doesn't match any of the stored keys.
>
> Here's the output of luksDump:
>
> cryptsetup luksDump /dev/md127
> LUKS header information for /dev/md127
>
> Version: 1
> Cipher name: aes
> Cipher mode: xts-plain
> Hash spec: sha1
> Payload offset: 4040
> MK bits: 512
> MK digest: 53 24 e5 1d 68 3e f1 5f 96 56 06 23 85 4a b6 89
> 07 de 52 1d
> MK salt: 5b 2e 4b 48 d8 2f 91 52 90 79 3b 6e 73 13 52 f1
> 8f 9e 35 50 8e 25 9e 92 22 52 48 26 44 d7 bd 6c
> MK iterations: 10
> UUID: 3fbd3c47-8dc3-4541-8960-00c0a80c8ae9
>
> Key Slot 0: ENABLED
> Iterations: 363564
> Salt: 32 db 41 40 56 fe 6f a9 c7 e4 c4 5f a0 4c 52 db
> 8e df 07 8c 9b 32 86 e6 ac 0c 8a e6 c4
> 69 31 0f
> Key material offset: 8
> AF stripes: 4000
> Key Slot 1: DISABLED
> Key Slot 2: DISABLED
> Key Slot 3: DISABLED
> Key Slot 4: DISABLED
> Key Slot 5: DISABLED
> Key Slot 6: DISABLED
> Key Slot 7: DISABLED
>
>
> Can anyone help me?
>
> Regards
> artificial
> _______________________________________________
> dm-crypt mailing list
> dm-crypt@saout.de
> http://www.saout.de/mailman/listinfo/dm-crypt
>
--
Arno Wagner, Dr. sc. techn., Dipl. Inform., CISSP -- Email: arno@wagner.name
GnuPG: ID: 1E25338F FP: 0C30 5782 9D93 F785 E79C 0296 797F 6B50 1E25 338F
----
One of the painful things about our time is that those who feel certainty
are stupid, and those with any imagination and understanding are filled
with doubt and indecision. -- Bertrand Russell
next prev parent reply other threads:[~2012-04-08 15:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-08 13:04 [dm-crypt] can't open luks device after raid 5 rebuild artificial11000
2012-04-08 15:47 ` Arno Wagner [this message]
2012-04-08 16:23 ` artificial11000
2012-04-08 16:33 ` Ingo Schmitt
2012-04-08 17:09 ` Heinz Diehl
2012-04-08 20:07 ` Salatiel Filho
2012-04-08 20:28 ` Arno Wagner
2012-04-08 20:22 ` Arno Wagner
2012-04-08 20:35 ` Arno Wagner
2012-04-08 20:43 ` artificial11000
2012-04-08 23:22 ` Arno Wagner
-- strict thread matches above, loose matches on Subject: below --
2012-04-07 15:54 artificial11000
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=20120408154753.GA31917@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox