On 18/07/17 18:20, Maarten wrote: > Now from what I've gathered over the years and from earlier incidents, I > have now 1 (one) chance left to rescue data off this array; by hopefully > cloning the bad 3rd-failed drive with the aid of dd_rescue and > re-assembling --force the fully-degraded array. (Only IF that drive is > still responsive and can be cloned) If it clones successfully, great. If it clones, but with badblocks, I keep on asking - is there any way we can work together to turn dd-rescue's log into a utility that will flag failed blocks as "unreadable"? This project is mentioned on the wiki, the idea being that you can tell the hard drive to return a read error if the computer tries to access certain blocks. This "fake" read error means that we can then use a partially copied disk to rebuild an array knowing that we will get an error rather than silent corruption if we try and access the faulty block. At least then, we know what is damaged rather than trying to integrity-check an entire disk in the hope that we'll detect the corruption. Cheers, Wol -- 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
