On Tuesday January 20, jean@upfrontsystems.co.za wrote: > > 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 Looks like you must have done a hot-add in the mean time.... I would try: mdadm -C /dev/md0 -l 5 -n 3 /dev/hda3 missing /dev/hdc3 and check "fsck -f -n" to check the the filesystem looks OK. This 'mdadm' command will not change any data except the raid superblocks, which are already a mess anyway. If the looks OK, you can then mdadm /dev/md0 --add /dev/hdb3 and see if hdb is working after all. If it didn't look OK, stop the array and try create the array with a different combination of devices. As long as you create a raid5 array with one missing device and only read from the resulting device, no data apart from the superblock will be corrupted. Once you hot-add, or create without a missing device data could get corrupted if the array hasn't been assembled correctly. NeilBrown - 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
