On Sat, 19 Mar 2011 14:44:40 +0100 Xavier Brochard <xavier@xxxxxxxxxxxxxx> wrote: > Le samedi 19 mars 2011 02:42:47 NeilBrown, vous avez écrit : > > I suggest you: > > > > mdadm --zero /dev/sdb1 > > > > having first double-checked that sdb1 is the devices with Events of 154, > > > > then > > > > mdadm -S /dev/md0 > > mdadm -As /dev/md0 > > > > > > and let the array rebuild the spare. > > Then check the data and make sure it is all good. > > Then add /dev/sdb1 back in as the spare > > mdadm /dev/md0 --add /dev/sdb1 > > > > and everything should be fine - providing you don't hit any hardware errors > > etc. > > It didnt work, until I've stopped the raid array: > mdadm --zero /dev/sdg1 > mdadm: Couldn't open /dev/sdg1 for write - not zeroing > > is that normal, can I continue? > Yes, you are right. You need to stop the array before you zero things. So: mdadm -S /dev/md0 mdadm --zero /dev/the-device-which-thinks-most-of-the-other-devices-have-failed mdadm -As /dev/md0 That last command might need to be mdadm -As /dev/md0 /dev/sdc1 /dev/sdd1 ..... list of all member devices. NeilBrown -- 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
