On 06/01/2016 11:42 AM, Wols Lists wrote: > Okay - so would this be better (a lot slower, possibly, but safe ...) > > Use dd - so it DOES bomb on error! - and only replace the drive once > you've got a clean read off it. With 2TB drives, that should work so > long as they're not faulty. And if it's - JUST - a timeout issue, > this'll work fine? If there's errors, you'll never get a clean read. (Short of the moon and stars aligning for a near-miracle.) ddrescue and similar replace those errors with zeros to successfully retrieve less than 100% of your data. The whole point of keeping it in the array is to get the correct data from the array's redundancy wherever the disk has unfixed read errors. And with correct timeouts, to *FIX* that read error. Please read *all* of the links I posted on why and how this is. Side note: In these situations, you should *not* use overlays, as that prevents the *FIX* part from happening. Temporarily setting the timeouts for non-raid drives is a one-liner: for x in /sys/block/*/device/timeout ; do echo 180 > $x ; done Phil -- 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
