Am 24.02.2010 19:12, schrieb Robin Hill: >> mdadm --stop /dev/md4 >> >> ddrescue /dev/sda4 /dev/sdd4 >> >> mdadm --assemble --force /dev/md4 /dev/sdb4 /dev/sdd4 >> >> ?? >> > Yes, that'd be what I'd recommend - the ddrescue will only need to make > a single pass across sda4 (except for failed blocks of course), so will > have the lowest risk of exacerbating the disk problems. Of course, the > practicality of doing the assemble will depend on the number of > unreadable blocks found by ddrescue. I decided to somehow roll back. As far as we see we lose 1.5 hrs of work done by some people ... thanks to the rsnapshots ... The LV containing the VM was/is healthy, I was able to copy the vm-directory fine and the VM boots and runs. No work lost here. So far I don't use that flaky md4 for now ... doing the ddrescue would take quite some time and this box has to be UP tomorrow. And additionally I wouldn't know about the result. I'll decide how to proceed tomorrow. For now the data and the function for tomorrow comes first, even without full RAID now. So I restore stuff now ... I am somehow tired and exhausted now and not willing to risk what I have got now. > Good luck! > Robin Thanks a lot ... 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
