Re: [gentoo-user] Failure to start md at boot

[Mick <michaelkintzios@gmail.com>]

[-- Attachment #1: Type: Text/Plain, Size: 1347 bytes --]

On Sunday 31 May 2015 10:01:43 Peter Humphrey wrote:
> I've split this out from the previous thread because it was getting messy.
> I'd followed Rich Freeman's advice to specify arrays by UUID in
> mdadm.conf, and this is what happened:
> 
> On Friday 29 May 2015 01:10:52 I wrote:
> > OK, so this is what I have at present. I haven't booted with it yet to
> > test it - I'll do that in the morning:
> > 
> > DEVICE /dev/sd[abcde][123456789]
> > ARRAY /dev/md1 UUID=ea156c7f:183ca28e:c44c77eb:7ee19756
> > ARRAY /dev/md5 UUID=e7640378:966a5b3a:c44c77eb:7ee19756
> > ARRAY /dev/md7 UUID=c2d056c4:9118021f:ad73c633:b38fa97c
> 
> Specifying the UUIDs hasn't helped. I still get failure to start /dev/md7
> during boot as often as not.

Did you try my suggestion to (also) specify the metadata type to see if it 
makes a difference?

Something else to check:

Make sure that the /etc/fstab name for the RAID device and your 
/etc/mdadm.conf use the same name.

If you have changed the partitions on this RAID, or recreated it, make sure to 
run 'mdadm --zero-superblock', before you delete the partition from the 
partition table, or you could recover it when you recreate a partition if not 
zeroed.

Have a look at smartctl output to see if there is something wrong with any of 
the md7 disks.

-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 473 bytes --]