Re: [dm-crypt] can't open luks device after raid 5 rebuild

From: Ingo Schmitt <ingo.schmitt@binarysignals.net>
To: artificial11000 <artificial11000@googlemail.com>
Cc: dm-crypt@saout.de
Subject: Re: [dm-crypt] can't open luks device after raid 5 rebuild
Date: Sun, 08 Apr 2012 18:33:19 +0200	[thread overview]
Message-ID: <4F81BDCF.6090107@binarysignals.net> (raw)
In-Reply-To: <4F81BB7A.7050508@googlemail.com>

Hi Artificial,

On 04/08/12 18:23, artificial11000 wrote:

> as I noticed that I can't access the device, I recreated the raid manually.
>  mdadm --create --level=5 -n 3 /dev/md127 /dev/sdb /dev/sdc /dev/sdd

You created a new raid that way.

> Could this damage the key-slot?

Yes and all the data on the drives too.

> Are the metadata of the RAID relevant to this?
> I read that old versions of mdadm created RAIDs with metadata=0.90 and
> the newer versions with metadata=1.20.
> 
> artificial
> 
> On 04/08/2012 05:47 PM, Arno Wagner wrote:
>> 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
>>>
>>
> _______________________________________________
> dm-crypt mailing list
> dm-crypt@saout.de
> http://www.saout.de/mailman/listinfo/dm-crypt