mdadm --assemble /dev/md0 --force /dev/hd[abc]3
should put it back together for you.
No luck ..
cdimage root # mdadm --verbose --assemble /dev/md0 --force /dev/hda3 /dev/hdb3 /dev/hdc3
mdadm: looking for devices for /dev/md0
mdadm: /dev/hda3 is identified as a member of /dev/md0, slot 3.
mdadm: /dev/hdb3 is identified as a member of /dev/md0, slot 4.
mdadm: /dev/hdc3 is identified as a member of /dev/md0, slot 2.
mdadm: no uptodate device for slot 0 of /dev/md0
mdadm: no uptodate device for slot 1 of /dev/md0
mdadm: added /dev/hda3 to /dev/md0 as 3
mdadm: added /dev/hdb3 to /dev/md0 as 4
mdadm: added /dev/hdc3 to /dev/md0 as 2
mdadm: /dev/md0 assembled from 1 drive - not enough to start it (use --run to insist).
cdimage root # cat /proc/mdstat
Personalities : [raid5]
read_ahead not set
md0 : inactive ide/host0/bus1/target0/lun0/part3[2] ide/host0/bus0/target1/lun0/part3[4] ide/host0/bus0/target0/lun0/part3[3]
0 blocks
unused devices: <none>
cdimage root # mdadm --verbose --examine /dev/hda3
/dev/hda3:
Magic : a92b4efc
Version : 00.90.00
UUID : dd5156aa:9157bc3c:9500db42:445b91fe
Creation Time : Wed Dec 17 11:44:50 2003
Raid Level : raid5
Device Size : 38001664 (36.24 GiB 38.91 GB)
Raid Devices : 3
Total Devices : 4
Preferred Minor : 0
Update Time : Mon Jan 19 07:41:21 2004 State : dirty, no-errors Active Devices : 1 Working Devices : 3 Failed Devices : 1 Spare Devices : 2 Checksum : 736178ae - correct Events : 0.82
Layout : left-symmetric Chunk Size : 64K
Number Major Minor RaidDevice State
this 3 3 3 3 /dev/ide/host0/bus0/target0/lun0/part3
0 0 0 0 0 faulty removed
1 1 0 0 1 faulty removed
2 2 22 3 2 active sync /dev/ide/host0/bus1/target0/lun0/part3
3 3 3 3 3 /dev/ide/host0/bus0/target0/lun0/part3
4 4 3 67 4 /dev/ide/host0/bus0/target1/lun0/part3
I think /dev/hdb3 was the one originally marked faulty, and I wrongly --set-faulty /dev/hda3 ..
-- Jean Jordaan http://www.upfrontsystems.co.za
- 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