Re: MD device not found on boot

[Tom H <tomh0665@gmail.com>]

On Fri, Mar 2, 2012 at 2:36 PM, Daniel Bareiro <daniel-listas@gmx.net> wrote:
>
> Doing a test on 2.6.32-bpo.5-amd64, the /etc/mdadm/mdadm.conf seems to
> be consistent:
>
> # cat /etc/mdadm/mdadm.conf
> ARRAY /dev/md0 level=raid1 num-devices=2 metadata=0.90 UUID=e94e767e:1183e8a6:67791052:2affdb87
> ARRAY /dev/md1 level=raid1 num-devices=2 metadata=0.90 UUID=0492f0eb:9f649719:24a66d4c:4b61d9a6
> ARRAY /dev/md2 level=raid1 num-devices=2 metadata=0.90 UUID=da5a0c19:c38ccc6d:325196eb:eb163021
> ARRAY /dev/md3 level=raid1 num-devices=2 metadata=0.90 UUID=552e20c1:b4272c8d:b7f9e5fe:737c9276
> ARRAY /dev/md5 level=raid1 num-devices=2 metadata=0.90 UUID=80619797:1712d4dd:64a19d1d:8273eab2
>
> # mdadm --detail --scan
> ARRAY /dev/md0 level=raid1 num-devices=2 metadata=00.90 UUID=e94e767e:1183e8a6:67791052:2affdb87
> ARRAY /dev/md1 level=raid1 num-devices=2 metadata=00.90 UUID=0492f0eb:9f649719:24a66d4c:4b61d9a6
> ARRAY /dev/md2 level=raid1 num-devices=2 metadata=00.90 UUID=da5a0c19:c38ccc6d:325196eb:eb163021
> ARRAY /dev/md3 level=raid1 num-devices=2 metadata=00.90 UUID=552e20c1:b4272c8d:b7f9e5fe:737c9276
> ARRAY /dev/md5 level=raid1 num-devices=2 metadata=00.90 UUID=80619797:1712d4dd:64a19d1d:8273eab2
>
> In any case, given that 2.6.32-bpo.5-amd64 boots without problems
> with same configuration and mdadm metadata, I am inclined to think
> that the problem is some of the kernel. Maybe inirtd...

Did you recreate your initrd after changing your mdadm.conf?