constantly shows wrong temperature (99°C )

[brian]

Hello, here's my system info

~$ lsb_release -rd
Description: Ubuntu 16.04 LTS
Release: 16.04

~$ apt-cache policy udisks2
udisks2:
  Installed: 2.1.7-1ubuntu1
  Candidate: 2.1.7-1ubuntu1
  Version table:
 *** 2.1.7-1ubuntu1 500
        500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
        100 /var/lib/dpkg/status

Here's the problem: udisks2 constantly shows that my ssd temperature is 99°C (210°F), but in reality it's 30°C

~$ sudo smartctl -A /dev/sda
smartctl 6.5 2016-01-24 r4214 [x86_64-linux-4.4.0-22-generic] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF READ SMART DATA SECTION ===
SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate 0x000b 100 100 050 Pre-fail Always - 0
  9 Power_On_Hours 0x0012 100 100 000 Old_age Always - 24
 12 Power_Cycle_Count 0x0012 100 100 000 Old_age Always - 51
168 Unknown_Attribute 0x0012 100 100 000 Old_age Always - 0
170 Unknown_Attribute 0x0003 100 100 010 Pre-fail Always - 231
173 Unknown_Attribute 0x0012 100 100 000 Old_age Always - 65539
192 Power-Off_Retract_Count 0x0012 100 100 000 Old_age Always - 23
194 Temperature_Celsius 0x0023 070 070 030 Pre-fail Always - 30 (Min/Max 30/30)
218 Unknown_Attribute 0x000b 100 100 050 Pre-fail Always - 0
231 Temperature_Celsius 0x0013 100 100 000 Pre-fail Always - 99
241 Total_LBAs_Written 0x0012 100 100 000 Old_age Always - 337

in the GUI app ("Disks") it shows the wrong temperature too. hddtemp works well though:

~$ sudo hddtemp /dev/sda
/dev/sda: PNY EU SSD CS1311 240GB: 30°C

[Phillip Susi (psusi)]

It seems that this extra attribute needs to not be treated as temperature. I have patched libatasmart to do this. Please try the version in my ppa and see if it resolves it for you. You can add my ppa by running sudo add-apt-repository ppa:psusi/ppa, then an apt-get update and upgrade should install the new version of libatasmart.

[brian (blec78)]

It works great now. Thank you :)

[Phillip Susi (psusi)]

Martin, could you please review and apply the attached patch?

[Ubuntu Foundations Team Bug Bot (crichton)]

The attachment "0001-Fix-incorrect-temperature-reporting.patch" seems to be a debdiff. The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. If the attachment isn't a patch, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issue please contact him.]

[Martin Pitt (pitti)]

@Phillip, thanks for working on this! https://en.wikipedia.org/wiki/S.M.A.R.T. mentions both possibilities for attribute 231. Do you happen to have a more direct reference? Also, can you please create an upstream bug for this as well? Thanks!

[Phillip Susi (psusi)]

Sorry for the late reply Martin... my bugs mailbox has gotten quite backed up. I emailed smartmontols-devel about the issue and their response was:

There likely was some historic HDD which used attribute 231 for temperature (same for 9 and 220).

And yes, there are devices which report temperature in more than one attribute.

They went on to say they would probably change smartmontools to prefer the more common attribute and I thought that libatasmart should follow suit.

Will create the upstream bug report, though the last one or two I have created with patches attached have gone ignored there for years so...

[Thomas Mayer (thomas303)]

Confirming this issue:

Using Ubuntu 16.04, Kernel 4.4.0-57-generic wrong temperatures also make it into syslog:

Jan 2 20:22:27 server smartd[876]: Device: /dev/sda [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 110 to 112
Jan 2 20:22:27 server smartd[876]: Device: /dev/sdb [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 111 to 113

Not only is that wrong, it also tells admins that there was need to take action. Eventually, it makes it into some monitoring tool, which thereby abstracts the RAW_VALUE even further.

Note that in reality my drives have <40°C, just by reading SMART's RAW_VALUE (and touching the drive with my finger).

Also note that the device model is "In smartctl database", according to smartctl's output. That said, I'd expect smartctl to somehow "know" all variables of my drive, including their meaning.

smartctl 6.5 2016-01-24 r4214 [x86_64-linux-4.4.0-57-generic] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family: Western Digital AV-GP (AF)
Device Model: WDC WD30EURS-63SPKY0
[...]
Firmware Version: 80.00A80
User Capacity: 3.000.592.982.016 bytes [3,00 TB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Device is: In smartctl database [for details use: -P show]
ATA Version is: ACS-2 (minor revision not indicated)
SATA Version is: SATA 3.0, 3.0 Gb/s (current: 3.0 Gb/s)
Local Time is: Mon Jan 2 23:27:25 2017 CET
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 0
  3 Spin_Up_Time 0x0027 177 176 021 Pre-fail Always - 6133
  4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 98
  5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0
  7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0
  9 Power_On_Hours 0x0032 072 072 000 Old_age Always - 20909
 10 Spin_Retry_Count 0x0032 100 253 000 Old_age Always - 0
 11 Calibration_Retry_Count 0x0032 100 253 000 Old_age Always - 0
 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 98
192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 55
193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 42
194 Temperature_Celsius 0x0022 112 101 000 Old_age Always - 38
196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0
197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 0
198 Offline_Uncorrectable 0x0030 100 253 000 Old_age Offline - 0
199 UDMA_C...

[Thomas Mayer (thomas303)]

I think my case is different: It's not about variable 231/duplicate entries for temperature.

Instead, smartctl does something with the temperature's RAW_VALUE and thereby falsifies it.

For my case, I filed a new bug report #1653560, respectively.

[Yury (drvlas)]

Hi,

I'm in too. But my case is a little bit different and I don't see how can I apply any patch.
I try to install Linux Mint 18.1 with my brand new Kingston 256GB SSD. When I check the SSD with Disks it's OK, but the utility shows 100 Celsius temperature.
Then I begin the installation, choose partitions and try to move on. The Installer crashes with Error 5.
Is it possible to apply the patch in such a case? How am I to do it? I use USB live cd.

[Yury (drvlas)]

Sorry guys,

My case is different indeed. But in a sense it may be caused by other error.
I've made integrity check of the USB stick with a system - and it showed an error in one file.
After rewriting the system on a USD everything became fine.

[Phillip Susi (psusi)]

Yes, that is unrelated to this bug, which is simply a display issue.

[Łukasz Zemczak (sil2100)]

I could sponsor this change for you as it looks sane in this case, but I'm a bit concerned that it's not the right way to go. I think the right way is per what smartmontols-devel reply was, i.e. that we should actually, in case of multiple temperature readings, should prefer the one that's more common - and in that case treat the other attribute as another value. I'm simply worried that this change could affect some of those older HDDs that actually used 231 only to denote temperature. Do we know if those won't get affected?

[Phillip Susi (psusi)]

I'm not sure that there are any drives that used only 231. This whole thing seems to be very black magic / ad hoc.

It might be worth checking how the latest upstream release of smartmontools handles this.

[Robie Basak (racb)]

I have similar feelings to sil2100. I don't think it makes sense for Ubuntu to do something special here. Until someone figures out what upstream is doing I don't think it's appropriate to add a delta to Ubuntu for this. So unsubscribing ~ubuntu-sponsors for now. Please resubscribe ~ubuntu-sponsors when the upstream situation is determined.

[Trent Nelson (trent-a-b-nelson)]

I've added support for SSD Life Left via the quirks infrastructure. The two devices I have access to, that abuse attribute 231, store the value differently, so I had to use separate quirks.

The attached patch adds support for Kingston A400 and V300 series SSDs. Side-effect, correct temperature reporting!

Let me know if the diff needs any tweaks to make it more, Ubuntu-y.

[Trent Nelson (trent-a-b-nelson)]

Sorry, I missed Robie's comment yesterday. Upstream seems inactive/dead. Nothing from Lennart on https://bugs.freedesktop.org/buglist.cgi?product=libatasmart since 2011. No commits to http://git.0pointer.net/libatasmart.git since 2012. I didn't see any indication the development had been picked up anywhere else.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Natetronn (natetronn)]

Not sure I should chime in, since it's already been confirmed but, I'm seeing this as well.

Says it's 100c in Disks and in Freon too.

$ sudo hddtemp /dev/sdb
/dev/sdb: KINGSTON SA400S37240G: 26°C

I'm a bit too tired at this point to try and figure out how to address the issue. I'll read the thread again in the morning.

[Refrain (c384mb)]

https://bugs.launchpad.net/psensor/+bug/1842525

[Michael Speth (conzar)]

I just want to add my comment as well.

With hddtemp I get the following:
/dev/sdc: KINGSTON SA400S37240G: 33°C

With smartctl I get the following:
194 Temperature_Celsius 0x0023 067 054 000 Pre-fail Always - 33 (Min/Max 20/46)
231 Temperature_Celsius 0x0013 100 100 000 Pre-fail Always - 97

[Sebastien Bacher (seb128)]

The issue is being reported on https://github.com/storaged-project/udisks/issues/568

[Humphrey van Polanen Petel (hpvpp)]

bug 1912873 was marked as duplicate, but might have extra information

[Humphrey van Polanen Petel (hpvpp)]

I have copied below the information from bug 1912873 for convenience
--
SMART attribute 231 of the KINGSTON SA400S37480G (SBFKK1B3) is defined as "SSD_Life_Left" (see https://media.kingston.com/support/downloads/MKP_521_Phison_SMART_attribute.pdf).

The drive is correctly specified in the smartmontools, smartctl/smartd database (see attached).

disks (gnome-disk-utility 3.36.1 = UDisks 2.8.4 (built against 2.8.4)) reports attribute 231 as "temperature".

Possibly relevant is that "smartctl -t short" reports an error (see attached)

Bug 1878509 probably refers to the same problem.

[Juha Niiranen (juha-niiranen)]

I also have the Disk display incorrectly Kingston disk temperature (98°C). And also the Psensor shows the wrong temperature.

Device Model: KINGSTON SKC600512G
SSD Disk

Attached (smartctl -a /dev/sdc) smartctl_sdc.txt and (udisksctl dump) udisk_dump.txt.

[Juha Niiranen (juha-niiranen)]

Attached udisksctl dump

[Juha Niiranen (juha-niiranen)]

hhdtemp show correct temperature.
hddtemp /dev/sdc
/dev/sdc: KINGSTON SKC600512G: 28°C

[Juha Niiranen (juha-niiranen)]

my system info:
lsb_release -rd
Description: Ubuntu 20.04.3 LTS
Release: 20.04

[Juha Niiranen (juha-niiranen)]

Kingston KC600 SMART attribute https://media.kingston.com/support/downloads/KC600-SMART-attribute.pdf

[mrvst (maravento)]

Affect ubuntu mate 22.04.1
Gnome Disks reports 100 °C on brand new Kingston A400 SATA3. Psensor too. Hardware sensor (udisk2) too
Crystal disk info report 26 °C

I can't understand how it is possible that this bug was detected in 2016 and in 2022 (almost 2023) it still hasn't been fixed. what do you need to do it?

Related link:
https://github.com/mate-desktop/mate-sensors-applet/issues/129
https://github.com/HarlemSquirrel/gnome-shell-extension-sensory-perception/issues/26
https://www.reddit.com/r/debian/comments/p93k4v/gnome_disks_reports_100_c_on_brand_new_kingston/

[Julian Andres Klode (juliank)]

Unsubscribing Ubuntu Sponsors, as this issue seems to be fairly complex and the patch seems controversial and incomplete.

[mrvst (maravento)]

8 years have passed since this issue was reported and there is no solution