Am 24.02.2010 18:09, schrieb Robin Hill: > It's degraded because you only have 2 disks in the array, presumably the > event count on the other disks doesn't match up. If you've replaced sdc > and sdd never got rebuilt onto, then you only have the two disks > available for the array anyway. Yep. > If these are the only disks with up-to-date data, and sda4 is still > failing, I can only suggest stopping the array and using dd/dd_rescue to > copy sda4 onto a working disk. You should then be able to reassemble > the array with sdb4 and the new disk, then add in a hot spare to > recover. OK, that's plan B. For now I try to get data aside. md4 is a PV in an LVM-VG ... the main data-LV seems to trigger the errors, but another LV seems more stable (other sectors or something). This other LV contains rsnapshots of the main data-LV ... so if I am lucky I only lose about 2hrs of work if I get the latest snapshot copied. rsync is down to character "s" already ........ For sure there's a third LV as well, containing VMware-VMs ... oh my. Let's pray this one is OK as well, at least while copying stuff. > Alternately, bite the bullet, recreate the array and restore. hmm > Either way, it looks like you ought to be running regular checks on the > array to try to pick up/fix these background failures. smartd lead me to the failing sdc ... no note of sda though ... A bad taste after all. Thanks anyway, Stefan -- 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
