[BUG] Negative temperature recorded

[abragagn]

Describe the bug
Scrutiny logs a negative temperature for a drive. The drive is not below zero. Truenas scale own reporting tools log correct temp.

Expected behavior
Positive real temperature.

Screenshots
Scrutiny

Truenas

[nesha14586]

I have the same problem. It is also a Patriot SSD, though mine is a bit more cold lol. :D

[kaysond]

This issue is being closed automatically as a part of an effort to streamline and prioritize development effort. If it is still relevant, please reply to this comment and we will convert it to a discussion.

[nesha14586]

Tthis should remain an issue rather than be converted into a discussion, since it describes an actual bug affecting many users.

I thinkeeping it as an issue would make it easier to track, reproduce, and eventually fix.

[kaysond]

See #878

[nesha14586]

Thanks! Hope this will be resolved.
Finish the fight! :D

[abragagn]

Hello, it is still relevant as of today.

[kaysond]

@abragagn - sorry I missed this. Can you try the latest nightly image? And if you still see a negative temp, what do you see for temp if you run smartctl --xall --json?

[pksimeonov]

@kaysond I'm having this issue on a Silicon Power SSD using v0.9.2, below is the requested output.

It appears the SCT is not being properly populated, but SMART ID194 has the correct value (38C):
194 Temperature_Celsius 0x0023 068 068 000 Pre-fail Always - 38

smartctl --xall --json /dev/sda:

{
  "number": 5,
  "name": "Temperature Statistics",
  "revision": 1,
  "table": [
    {
      "offset": 8,
      "name": "Current Temperature",
      "size": 1,
      "value": -88,
      "flags": {
        "value": 192,
        "string": "V--- ",
        "valid": true,
        "normalized": false,
        "supports_dsn": false,
        "monitored_condition_met": false
      }
    },
    {
      "offset": 32,
      "name": "Highest Temperature",
      "size": 1,
      "value": 0,
      "flags": {
        "value": 192,
        "string": "V--- ",
        "valid": true,
        "normalized": false,
        "supports_dsn": false,
        "monitored_condition_met": false
      }
    },
    {
      "offset": 40,
      "name": "Lowest Temperature",
      "size": 1,
      "value": 0,
      "flags": {
        "value": 192,
        "string": "V--- ",
        "valid": true,
        "normalized": false,
        "supports_dsn": false,
        "monitored_condition_met": false
      }
    }
  ]
}

[kaysond]

@kaysond I'm having this issue on a Silicon Power SSD using v0.9.2, below is the requested output.

It appears the SCT is not being properly populated, but SMART ID194 has the correct value (38C): 194 Temperature_Celsius 0x0023 068 068 000 Pre-fail Always - 38

smartctl --xall --json /dev/sda:

{
  "number": 5,
  "name": "Temperature Statistics",
  "revision": 1,
  "table": [
    {
      "offset": 8,
      "name": "Current Temperature",
      "size": 1,
      "value": -88,
      "flags": {
        "value": 192,
        "string": "V--- ",
        "valid": true,
        "normalized": false,
        "supports_dsn": false,
        "monitored_condition_met": false
      }
    },
    {
      "offset": 32,
      "name": "Highest Temperature",
      "size": 1,
      "value": 0,
      "flags": {
        "value": 192,
        "string": "V--- ",
        "valid": true,
        "normalized": false,
        "supports_dsn": false,
        "monitored_condition_met": false
      }
    },
    {
      "offset": 40,
      "name": "Lowest Temperature",
      "size": 1,
      "value": 0,
      "flags": {
        "value": 192,
        "string": "V--- ",
        "valid": true,
        "normalized": false,
        "supports_dsn": false,
        "monitored_condition_met": false
      }
    }
  ]
}

Can you share the full output of the command? There should be a temperature key at the root of the object. I'd also be curious to see all the SCT entries

[pksimeonov]

@kaysond here is the full output
sda-smartctl-xall.json

[kaysond]

@pksimeonov - thanks!

See

  "temperature": {
    "current": -86,
    "lifetime_max": 0,
    "lifetime_min": 0
  },

and

      {
        "number": 5,
        "name": "Temperature Statistics",
        "revision": 1,
        "table": [
          {
            "offset": 8,
            "name": "Current Temperature",
            "size": 1,
            "value": -86,
            "flags": {
              "value": 192,
              "string": "V--- ",
              "valid": true,
              "normalized": false,
              "supports_dsn": false,
              "monitored_condition_met": false
            }
          },

Scrutiny uses the former for temperature data. In the short term, I'd suggest you open an issue with smartmontools: https://github.com/smartmontools/smartmontools

They may be able to give you some smartctl arguments that would fix it, or help us figure out what the underlying issue is. If there's no quick fix, we'll have to add a hook in the collector or backend to let people overwrite the temperature field from smart or sct. This will take longer for me to get to.

[szmarczak]

If it is still relevant

What makes you think it's not relevant?

[chrfranke]

Related: smartmontools issue #609.

[kaysond]

work around tracked in #1058

[Ricky-Bobby510]

Coldest drive here!

"number": 5,
"name": "Temperature Statistics",
"revision": 1,
"table": [
{
"offset": 8,
"name": "Current Temperature",
"size": 1,
"value": -71,
"flags": {
"value": 192,
"string": "V--- ",
"valid": true,
"normalized": false,
"supports_dsn": false,
"monitored_condition_met": false
}
},
{
"offset": 32,
"name": "Highest Temperature",
"size": 1,
"value": 0,
"flags": {
"value": 192,
"string": "V--- ",
"valid": true,
"normalized": false,
"supports_dsn": false,
"monitored_condition_met": false
}
},
{
"offset": 40,
"name": "Lowest Temperature",
"size": 1,
"value": 0,
"flags": {
"value": 192,
"string": "V--- ",
"valid": true,
"normalized": false,
"supports_dsn": false,
"monitored_condition_met": false