On the topic of hard drive temperature and fail rate, Google has published a paper showing that there's little relation between high temp and fail rate, and Google has wide experience with hard disks (I believe them, hehe)

http://www.tomshardware.com/news/google-hard-drives,4347.html

Javier

On Wed, Sep 23, 2009 at 11:44 PM, Eric Shubert <ejs@shubes.net> wrote:
Good guess Franc.

Manufacturers appear to use different normalized values. I see a few
others now where the normalized and raw values are the same. WD appears
to have some other sort of scheme, as Franc has guessed.

Is there an explaination somewhere of the method(s) to the madness?
I probably don't really want to know, but thought I'd at least ask. :)

Thanks to everyone for enlightening me on this.

Franc Zabkar wrote:
> I suspect that the normalised value of 100 correlates to 50 deg C.
> Your drive's temperature is 37C, which is 13 degrees better than 50C,
> so its normalised value is 113. I expect that a worst case value of
> 93 is indicating that the temperature has at one time reached 57C.
>
> I'm just guessing, though ...
>
> -Franc
>
>
>> I'm seeing this from logwatch:
>> --------------------- Smartd Begin ------------------------
>>   /dev/sda :
>>      Usage: Temperature_Celsius (194) changed to
>>        110, 109, 110, 112, 113, 114, 113, 114,
>>   /dev/sdb :
>>      Usage: Temperature_Celsius (194) changed to
>>        105, 106, 108, 109, 108, 109, 108,
>>   ---------------------- Smartd End -------------------------
>>
>> The actual log message looks like:
>> Sep 23 04:48:05 ness smartd[25173]: Device: /dev/sda, SMART Usage
>> Attribute: 194 Temperature_Celsius changed from 113 to 114
>>
>> Here's what I have in smartd.conf:
>> /dev/sda -d ata -a -m root
>> /dev/sdb -d ata -a -m root
>>
>> When I run "smartctl -a -d ata /dev/sda" I get (among other things):
>> ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE
>> UPDATED  WHEN_FAILED RAW_VALUE
>> 194 Temperature_Celsius     0x0022   113   093   000    Old_age   Always
>>        -       37


--
-Eric 'shubes'


------------------------------------------------------------------------------
Come build with us! The BlackBerry&reg; Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9&#45;12, 2009. Register now&#33;
http://p.sf.net/sfu/devconf
_______________________________________________
Smartmontools-support mailing list
Smartmontools-support@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/smartmontools-support