devstat_7_8 counter is at 118

[cook2000]

Hi,
the value for devstat_7_8 on my SSD changed from one day to the next to 118.
However, this does not match other values—for example, Endurance Remaining is 100.
TBs written is 0.21 TB—which should also continue.
According to the manufacturer, the maximum value for my SSD (Transcend TS240GMTS420S) is 80 TB.
So what does devstat_7_8 failed mean? Should I be concerned?

Thanks and regards
Holger

[Starosdev]

Hi Holger,

What is devstat_7_8?

devstat_7_8 is the Percentage Used Endurance Indicator from ATA Device Statistics (Page 7, offset 8). It is a vendor-specific estimate of the percentage of drive life used. Per the ATA spec, a value of 100 means the estimated endurance has been consumed -- but does not necessarily indicate an actual device failure.

Why does it show as failed?

Scrutiny flags this attribute as failed when the value reaches or exceeds 100 (meaning 100% or more of the manufacturer estimated write endurance has been used).

Your drive reports 118, so Scrutiny correctly marks it as failed per its threshold logic.

Should you be concerned?

Given that your drive has only 0.21 TB written out of an 80 TB rated endurance, and Endurance Remaining shows 100, this is almost certainly a firmware reporting issue on the Transcend TS240GMTS420S. The drive firmware is reporting an incorrect value for this particular statistic. Your drive appears healthy based on all other indicators.

How to suppress this in Scrutiny

You can add an attribute override in your scrutiny.yaml configuration to ignore this false positive:

smart:
  attribute_overrides:
    - protocol: ATA
      attribute_id: "devstat_7_8"
      action: ignore

Or if you would prefer to keep monitoring it but with adjusted thresholds:

smart:
  attribute_overrides:
    - protocol: ATA
      attribute_id: "devstat_7_8"
      warn_above: 80
      fail_above: 95

We have also filed #275 to improve the status messages -- in an upcoming release, the tooltip will show "Percentage Used Endurance Indicator value 118 exceeds threshold 100" instead of the generic "Device statistic exceeds recommended threshold," making it clearer what is happening.