my 0+1 and 1+0 raid devices are not getting started on system boot. i realize this could be fixed through the sysinit scripts but mdadm -As should be able to handle this. here is my mdadm.conf DEVICE /dev/hdb1 /dev/hdb2 /dev/hdb3 /dev/hda5 /dev/hda6 /dev/hda7 /dev/hdb5 /dev/hdb6 /dev/hdb7 /dev/hda8 /dev/hda9 /dev/hda10 /dev/md3 /dev/md4 /dev/md6 /dev/md7 ARRAY /dev/md3 level=0 num-devices=3 devices=/dev/hdb1,/dev/hdb2,/dev/hdb3 ARRAY /dev/md4 level=0 num-devices=3 devices=/dev/hda5,/dev/hda6,/dev/hda7 ARRAY /dev/md6 level=1 num-devices=2 devices=/dev/hdb5,/dev/hdb6,/dev/hdb7 ARRAY /dev/md7 level=1 num-devices=2 devices=/dev/hda8,/dev/hda9,/dev/hda10 ARRAY /dev/md5 level=1 num-devices=2 devices=/dev/md3,/dev/md4 ARRAY /dev/md8 level=0 num-devices=2 devices=/dev/md6,/dev/md7 as you can see /dev/md5 is built on /dev/md3 and /dev/md4 and /dev/md8 is built on /dev/md6 and md7. when I run "mdadm -As" i get the following output: mdadm: /dev/md3 has been started with 3 drives. mdadm: /dev/md4 has been started with 3 drives. mdadm: /dev/md6 has been started with 2 drives and 1 spare. mdadm: /dev/md7 has been started with 2 drives and 1 spare. mdadm: no devices found for /dev/md5 mdadm: no devices found for /dev/md8 if i then immediately run "mdadm -As" again it starts /dev/md5 and /dev/md8. why do i have to run it twice and why does it not start all devices the first time? - To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
