I have 2 western digital 2500KS hard disks and noticed already some time ago that the smart implementation is not correct when it comes to temperatures. Afaik, it was something like reporting the temp in \u00c2\u00b0F while they claim to report it in \u00c2\u00b0C. This wouldn’t be a problem if they didn’t also define the thresholds in \u00c2\u00b0C. On an operating system like windows, the user never is bothered by this shortcoming as windows simply has no clue about SMART. On linux however, the user is typically notified by mail or desktop popup when a hard drive exceeds its maximum temp. Which is quite annoying if it is a false alarm. \ud83d\ude09<\/p>\n
A lot of 3rd party tools exist for windows, and that is how I originally encountered the problem<\/a>. So it is really a firmware bug.<\/p>\n So I started looking for a way to either<\/p>\n It seems attribute 190 is the problem. You can always verify this with “smartctl -a” which yields amongst others the vendor specific tags:<\/p>\n Next, we need to adjust the smartd config. sda and sdb need the special ignore for attr 190 (the key option is -i). I also specify for all hard drives that they are actually (S)ATA drives behind the SCSI interface (less warnings in the log ;)).<\/p>\n To make the changes in the config effective, we let smartd reread its config by sending a SIGHUP signal to the process:<\/p>\n done! \ud83d\ude42<\/p>\n","protected":false},"excerpt":{"rendered":" I have 2 western digital 2500KS hard disks and noticed already some time ago that the smart implementation is not correct when it comes to temperatures. Afaik, it was something like reporting the temp in \u00c2\u00b0F while they claim to report it in \u00c2\u00b0C. This wouldn’t be a problem if they didn’t also define the … Continue reading smartd temperature error messages<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[4,20],"tags":[],"class_list":["post-257","post","type-post","status-publish","format-standard","hentry","category-linux","category-suse"],"_links":{"self":[{"href":"https:\/\/mattiesworld.gotdns.org\/weblog\/wp-json\/wp\/v2\/posts\/257","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/mattiesworld.gotdns.org\/weblog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/mattiesworld.gotdns.org\/weblog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/mattiesworld.gotdns.org\/weblog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/mattiesworld.gotdns.org\/weblog\/wp-json\/wp\/v2\/comments?post=257"}],"version-history":[{"count":0,"href":"https:\/\/mattiesworld.gotdns.org\/weblog\/wp-json\/wp\/v2\/posts\/257\/revisions"}],"wp:attachment":[{"href":"https:\/\/mattiesworld.gotdns.org\/weblog\/wp-json\/wp\/v2\/media?parent=257"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/mattiesworld.gotdns.org\/weblog\/wp-json\/wp\/v2\/categories?post=257"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/mattiesworld.gotdns.org\/weblog\/wp-json\/wp\/v2\/tags?post=257"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}\n
\nOption 2 seemed the way to go.
\nFirst you need to know what is failing. Check your \/var\/log\/messages:<\/p>\n\r\nsmartd[3916]: Device: \/dev\/sda, Failed SMART usage Attribute: 190 Temperature_Celsius.\r\nsmartd[3916]: Device: \/dev\/sdb, Failed SMART usage Attribute: 190 Temperature_Celsius.\r\n<\/pre>\n
\r\nVendor Specific SMART Attributes with Thresholds:\r\nID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE\r\n 1 Raw_Read_Error_Rate 0x000f 200 200 051 Pre-fail Always - 0\r\n 3 Spin_Up_Time 0x0003 227 201 021 Pre-fail Always - 3650\r\n 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 487\r\n 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0\r\n 7 Seek_Error_Rate 0x000f 200 200 051 Pre-fail Always - 0\r\n 9 Power_On_Hours 0x0032 098 098 000 Old_age Always - 1683\r\n 10 Spin_Retry_Count 0x0013 100 100 051 Pre-fail Always - 0\r\n 11 Calibration_Retry_Count 0x0012 100 100 051 Old_age Always - 0\r\n 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 487\r\n190 Temperature_Celsius 0x0022 034 021 045 Old_age Always FAILING_NOW 66\r\n194 Temperature_Celsius 0x0022 084 071 000 Old_age Always - 66\r\n196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0\r\n197 Current_Pending_Sector 0x0012 200 200 000 Old_age Always - 0\r\n198 Offline_Uncorrectable 0x0010 200 200 000 Old_age Offline - 0\r\n199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0\r\n200 Multi_Zone_Error_Rate 0x0009 200 200 051 Pre-fail Offline - 0\r\n<\/pre>\n
\nThere is a DEVICESCAN directive which is an easy wizard way to automatically configure all devices found. If you want to configure all your devices the same way anyway, you can simply append all options you want there.
\nIf you, like me, want to give each device its own treat ;), you can add a line per device. As soon as you do that, you can’t use the devicescan wizard anymore. In my case I did something like this:<\/p>\n\r\n\/dev\/sda -a -d sat -i 190 -m root@localhost -M exec \/usr\/lib\/smartmontools\/smart-notify\r\n\/dev\/sdb -a -d sat -i 190 -m root@localhost -M exec \/usr\/lib\/smartmontools\/smart-notify\r\n\/dev\/sdc -a -d sat -m root@localhost -M exec \/usr\/lib\/smartmontools\/smart-notify\r\n\/dev\/sdd -a -d sat -m root@localhost -M exec \/usr\/lib\/smartmontools\/smart-notify\r\n<\/pre>\n
killall -HUP smartd<\/pre>\n