On Wed, 14 Jul 2010 16:37:09 +0200 Jan Ceuleers <jan.ceuleers@xxxxxxxxxxxx> wrote: > Hi guys. > > I've been having trouble with a four-disk raid5 array, which I now believe were caused by a flaky eSATA cable. The cable has been replaced, and the controller now seems to reliably see all four disks. > > In fact I have five disks, and so a partition on the fifth disk acts as a spare. Over the past several days I've been connecting and disconnecting drives in ways that I didn't realise were unreliable (due to the faulty cable). > > This has resulted in the md metadata being out of sync on the different partitions. Please could someone provide advice as to how to recover this array (which contains an ext3 filesystem)? > > > Many thanks! > > Jan mdadm -A /dev/md2 --force /dev/sd[ade]2 sdc2 this it is a spare, so you don't want it just now. sdb2 and sde2 both think that are 'device 0', but sde2 is clearly newer. So run the above mdadm comment (assuming none of the devices have been renamed again since you created the --examine output), then fsck -n /dev/md2 and make sure it is happy. If it is you can added sdb2 and sde2 as spares. 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
