On Tue, Dec 16, 2008 at 08:31:08PM +0000, Iain Rauch wrote: > > Hello Iain, > > > > can you please describe what is the *present* status? > > > >> /dev/md0 has been started with 22 drives (out of 24) and 1 spare > > > > So in short, you had failure of 3 drives, reassembled it with 22 drives and > > while you rebuild it again a drive failed? > > > > If so, take this last failed drive, clone it to a new drive (e.g. dd_rescue) > > and continue. > > > > (Sorry, but this is by far too much output below for my tired eyes. > > Sometimes a short description is more helpful). > > > > I'll see if I can do that. > > If I can't get anything useful off sdu (the latest to fail) can I change sdw > from spare to active sync? sds is the spare drive it's trying to recover to > and was the one that became out of sync as it ran in degraded mode. > > I think sdw maybe sdw was only set to faulty because it was the last one to > be recognised and the array got assembled without it. (The system won't boot > with all the drives on together). > > Here is what mdadm -E has to say about each disk: > > http://iain.rauch.co.uk/stuff/skinner-2008-12-16/ > I'm still tired (now even more ;-) ). Just check again if /dev/sdu really was the latest to fail and if so, clone this one. I also suggest to reassemble it without an immediate raid-rebuild. First check your data and only then add a new drives to the raid. Once you start a raid-rebuild. there is no way to go back. We recently also had the problem of three failed disks but we only could get back the data by not assembling the array with the latest failed disk, but with the 2nd latest (don't ask why). So in short 1) clone disk 2) mdadm --assemble --force /dev/mdX /dev/sda1 /dev/sdb1 ... /dev/sdx1 ===> Use only **22** devices here. 3) Mount and check data, maybe even a read-only fsck 4) Add two new disks. Hope it helps, Bernd -- 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
