In my opinion, if an HDD has to go into deep recovery mode to try to read a sector correctly, I want to replace that HDD as soon as possible. The deep recovery occurrences are rare enough, in my experience, that I interpret them as an indicator that the HDD is much more likely to fail more seriously (i.e., more than just a bad sector) in the near future, as compared to an HDD that has never gone into deep recovery.
THANK YOU. this is also why I insist that healthy WD drives with zero bad/reallocated sectors that are dropping from arrays within 24 hours aren't doing so because they're going into an error recovery sequence. There is something else going on.
Drives of different makes and models run different firmware. Drives of different makes and models employ different algorithms to correct themselves internally. Therefore demanding that ALL manufacturers provide an end-user tool to adjust the timeout value of a drive's internal operations to an arbitrary value = lunacy. An answer looking for a problem, or just the wrong problem. Not to mention the first people in line for an RMA after a timeout-modified drive incurs data loss will be the same people that demanded a tool in the first place.
Just because the WDTLER tool made certain models of WD drives seem more stable in raid arrays doesn't mean you can extrapolate the phenomenon to the entire industry of desktop class drives, nor that modifying the timeout will be the cure-all for what are more likely case-by-case firmware issues unrelated to error-correction that are causing dropouts from arrays.
Last edited: