| 1 |
On Sunday 31 May 2015 10:01:43 Peter Humphrey wrote: |
| 2 |
> I've split this out from the previous thread because it was getting messy. |
| 3 |
> I'd followed Rich Freeman's advice to specify arrays by UUID in |
| 4 |
> mdadm.conf, and this is what happened: |
| 5 |
> |
| 6 |
> On Friday 29 May 2015 01:10:52 I wrote: |
| 7 |
> > OK, so this is what I have at present. I haven't booted with it yet to |
| 8 |
> > test it - I'll do that in the morning: |
| 9 |
> > |
| 10 |
> > DEVICE /dev/sd[abcde][123456789] |
| 11 |
> > ARRAY /dev/md1 UUID=ea156c7f:183ca28e:c44c77eb:7ee19756 |
| 12 |
> > ARRAY /dev/md5 UUID=e7640378:966a5b3a:c44c77eb:7ee19756 |
| 13 |
> > ARRAY /dev/md7 UUID=c2d056c4:9118021f:ad73c633:b38fa97c |
| 14 |
> |
| 15 |
> Specifying the UUIDs hasn't helped. I still get failure to start /dev/md7 |
| 16 |
> during boot as often as not. |
| 17 |
|
| 18 |
Did you try my suggestion to (also) specify the metadata type to see if it |
| 19 |
makes a difference? |
| 20 |
|
| 21 |
Something else to check: |
| 22 |
|
| 23 |
Make sure that the /etc/fstab name for the RAID device and your |
| 24 |
/etc/mdadm.conf use the same name. |
| 25 |
|
| 26 |
If you have changed the partitions on this RAID, or recreated it, make sure to |
| 27 |
run 'mdadm --zero-superblock', before you delete the partition from the |
| 28 |
partition table, or you could recover it when you recreate a partition if not |
| 29 |
zeroed. |
| 30 |
|
| 31 |
Have a look at smartctl output to see if there is something wrong with any of |
| 32 |
the md7 disks. |
| 33 |
|
| 34 |
-- |
| 35 |
Regards, |
| 36 |
Mick |
Archives