Your problem is that these extra slots (N:0) are flagged as failed (S:9) and this confuses md.c.
If you get mdadm 1.3.0 and apply the three patches that can be found in http://cgi.cse.unsw.edu.au/~neilb/source/mdadm/patch/applied/
and then stop the array and use: mdadm --assemble --update=summaries /dev/md5 /dev/sda9 /dev/sdc9
then it should fix things up for you. You will need to do a similar thing for all of the arrays. This will be difficult for md2 as it is 'root'. You will need to boot a rescue disc to fix this one.
I have not idea how it got the failed flag.
I didn't read this in time to get this tested - I did a full backup and restore earlier, zeroing all sectors on both drives. All is fine now, however I have no idea how this has happened. I'll set one partition faulty, re-add it and reboot later just to make sure it really works.
2.6 has never been booted on that machine, or disks.
Thanks, I'll keep mdadm in mind next time something like this happens ;-)
-- Cheers, André Tomt andre@tomt.net
- To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
