From: artificial11000 <artificial11000@googlemail.com>
To: dm-crypt@saout.de
Subject: [dm-crypt] can't open luks device after raid 5 rebuild
Date: Sun, 08 Apr 2012 15:04:47 +0200 [thread overview]
Message-ID: <4F818CEF.3030706@googlemail.com> (raw)
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
next reply other threads:[~2012-04-08 13:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-08 13:04 artificial11000 [this message]
2012-04-08 15:47 ` [dm-crypt] can't open luks device after raid 5 rebuild Arno Wagner
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=4F818CEF.3030706@googlemail.com \
--to=artificial11000@googlemail.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 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.