[smartmontools-support] Time in Over-Temperature seems to be incorrect
Christian Franke
Christian.Franke at t-online.de
Wed Oct 6 17:16:07 CEST 2021
Claudio Kuenzler wrote:
>
> 0x05 ===== = = === == Temperature Statistics (rev 1) ==
> 0x05 0x008 1 30 --- Current Temperature
> 0x05 0x010 1 32 --- Average Short Term Temperature
> 0x05 0x018 1 32 --- Average Long Term Temperature
> 0x05 0x020 1 61 --- Highest Temperature
> 0x05 0x028 1 0 --- Lowest Temperature
> 0x05 0x030 1 41 --- Highest Average Short Term
> Temperature
> 0x05 0x038 1 0 --- Lowest Average Short Term
> Temperature
> 0x05 0x040 1 43 --- Highest Average Long Term
> Temperature
> 0x05 0x048 1 0 --- Lowest Average Long Term
> Temperature
> 0x05 0x050 4 41 --- Time in Over-Temperature
> 0x05 0x058 1 70 --- Specified Maximum Operating
> Temperature
> 0x05 0x060 4 0 --- Time in Under-Temperature
> 0x05 0x068 1 0 --- Specified Minimum Operating
> Temperature
>
>
> OK, I see where you see the 41. I happen to have the same model
> (Crucial MX 500 1TB) laying around here, so I quickly plugged it in to
> see if I see something similar. And indeed:
>
> 0x05 ===== = = === == Temperature Statistics (rev 1) ==
> 0x05 0x008 1 31 --- Current Temperature
> 0x05 0x010 1 50 --- Average Short Term Temperature
> 0x05 0x018 1 50 --- Average Long Term Temperature
> 0x05 0x020 1 60 --- Highest Temperature
> 0x05 0x028 1 0 --- Lowest Temperature
> 0x05 0x030 1 51 --- Highest Average Short Term
> Temperature
> 0x05 0x038 1 0 --- Lowest Average Short Term Temperature
> 0x05 0x040 1 51 --- Highest Average Long Term Temperature
> 0x05 0x048 1 0 --- Lowest Average Long Term Temperature
> 0x05 0x050 4 50 --- Time in Over-Temperature
> 0x05 0x058 1 70 --- Specified Maximum Operating
> Temperature
> 0x05 0x060 4 0 --- Time in Under-Temperature
> 0x05 0x068 1 0 --- Specified Minimum Operating
> Temperature
>
> As in your case, the highest temperature was never above the
> "specified maximum operating temperature". Yet 0x05:0x050 (Time in
> Over-Temperature) shows a value of 50 (41 in your case).
> I suspect this to be a false information from the drive or a false
> interpretation of the drive's data by smartctl. @Christian maybe you
> can spot this immediately?
Unfortunately debug hex dump for device statistics is still missing in
the ATA layer, but under linux SCSI/SAT hex dump should be present.
To check whether smartctl prints the value correctly, please provide the
output of the following command as an attachment:
smartctl -r ioctl,2 -l devstat,5 /dev/...
Only the output after "Device Statistics (GP Log 0x04)" is relevant. You
could discard the dump of the ATA IDENTIFY data block which contains the
serial number.
Thanks,
Christian
More information about the Smartmontools-support
mailing list