[BUG] Command Timeout value for Seagate Barracuda is incorrect

[Cyberes]

Describe the bug
There is a discrepancy between what Scrutiny says and what smartctl says:

ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
188 Command_Timeout         0x0032   100   100   000    Old_age   Always       -       0

Drive info:

Model Family:     Seagate Barracuda Pro Compute
Device Model:     ST1000LM049-XXXX
Serial Number:    XXXX
LU WWN Device Id: XXXX
Firmware Version: SDM2
User Capacity:    1,000,204,886,016 bytes [1.00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    7200 rpm
Form Factor:      2.5 inches
TRIM Command:     Available
Device is:        In smartctl database 7.3/5528
ATA Version is:   ACS-3 T13/2161-D revision 3b
SATA Version is:  SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Thu Dec 11 20:41:29 2025
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

Expected behavior
Scrutiny should show 0 for this value.

Screenshots
See above.

Log Files
N/A

[thegranddesign]

Same for other Seagate drives. Command timeout (as far as I'm aware) is vendor specific and can be whatever they want. For example, here's a patch for what's happening to me with smartmontools: smartmontools/smartmontools#301

The value on all of my drives is 4295032834 which scrutiny is stating is bad, but literally all of my pool's drives have this value. There's nothing else about these drives that shows any issues at all.

[FurkanVG]

Got Scrutiny today, literally same thing:

And from the amount of bugs reported, this looks like it wont be fixed, right?

[CoreyJ87]

I have this same issue and its been posted multiple times in here. I'm going look into it and see if I can make a fix in a fork. Theres a couple guys that have been working on forks and the owner of this repo is talking about passing maintainer to them. So we'll see what happens there. Maybe that will get PR's rolling again. If so I'll try to fix this and submit it.

[soleilblanc99]

I have the same issue with a seagate ironwolf 8tb as well

188 Command_Timeout 0x0032 100 099 000 Old_age Always - 1 1 2

Let me know if more information is required

[tobihille]

I have the same issue with a Seagate notebook drive.
The accepted solution here looks like it contains how to interpret these values: https://superuser.com/questions/1747844/interpreting-seagate-smart-value-188-command-timeout-data-format
In the meantime for all that use this tool with a Seagate drive: this is an online calculator to convert the value: https://www.disktuna.com/seagate-raw-smart-attributes-to-error-convertertest/ (picked from the accepted answer, not my own research or work)

[CoreyJ87]

I pushed a PR into starosdev's fork. Used exactly that as the resource to fix it. Its in the forks master branch now.

[Cyberes]

Is your fork the most active? Should I switch to it?

[CoreyJ87]

Its not my fork its @Starosdev's but yes theres a decent amount of work being done on it between him, @venku122 and my tiny PR. I plan to continue to help with it where possible.