Re: SAS preventive disk replacement

HÃ¥kon Alstadheim <[email protected]> Mon, 28 Nov 2016 22:15:02 +0100
Newsgroups gmane.linux.utilities.smartmontools
Message-ID <[email protected]>

Den 26. nov. 2016 22:44, skrev L.A. Walsh:
> Gandalf Corvotempesta wrote:
> Should i look for "elements in grown defect list"?
>> Should i look for the uncorrected errors in the below table reporting 
>> writes/reads/verifies?
>>
>> Should i look for something else in the "-x" output?
>>
> ----
>     Dang... that's one thing about smartmon, is that for better
> or worse, it makes the "call" based on its recorded data.  If SAS
> doesn't have similar, someone would have to know how the various
> parameters collected affect failure rate.
>
>     I think I read a report by google that said the single biggest
> correlating factor in failed disks was temperature -- though I don't
> know if it was 'max temperature' or 'daily-max-averaged' or what...
>
If you run your drives within the temperature tolerance, then what
matters most is temperature /variability/ . I have some seagate SAS
drives that have a max temperature gradient (10 deg./ hour ?) specified.
You should be able to keep temperature changes way lower than that.
Other than that, total max-min span in temperature could also be meaningful.

In addition to google, reading the spec.s on your drives could give some
insight.



------------------------------------------------------------------------------