Bug#574817: libata transition breaks mdadm arrays

[Mathieu Parent (Debian)]

Mathieu Parent



On Mon, Mar 22, 2010 at 2:56 PM, martin f krafft <madduck at debian.org> wrote:
> tags 574817 moreinfo
> thanks
>
> also sprach Mathieu Parent <sathieu at debian.org> [2010.03.21.1250 +0100]:
>> Following an upgrade to the Big bang release (2.6.32-10), my mdadm
>> arrays stopped to work.
>
> I fail to see how this has anything to do with mdadm.
>
>> I have to do the following at EACH boot to solve temporaly the problem:
>>  mdadm --stop /dev/md0
>>  mdadm --assemble /dev/md0 /dev/sd{b,c,d,e}
>>  vgchange -ay
>>  mount -a
>
> Did you change hostnames at some point?

No. How can it be related?

> Compare the output of /usr/share/mdadm/mkconf to
> /etc/mdadm/mdadm.conf and watch out for the UUID especially.
>
> If they differ, recreate the latter. The experimental mdadm package
> should have detected this.

The uuid are the same (see diff in a former mail), but there are two
more parameters that are only in /etc/mdadm/mdadm.conf (level=raid5
num-devices=4). I will try without and see (in a couple of hours).