[BUG] Command Timeout on Seagate Exos 7E8

[theAlevan]

Describe the bug
On Seagate Exos 7E8 drives, the Command Timeout value is constantly at 100, while the threshold is 0, which is maybe a bug.

Expected behavior
Two 8TB Seagate Exos 7E8 I bought a few months ago, since first spinup, shows the Command Timeout (id: 188 (0xBC) ) SMART value as 100. Since the threshold value is 0, the drive shows up as failed. I ran multiple tests on the drive since then, and have been using it as a raid member, and I had no problems with it.

Now I bought another one, and its Command Timeout value is also 100.

Screenshots

Log Files

[collector.log](https://github.com/user-attachments/files/16982921/collector.log)


# in another terminal trigger the collector
[collector.log](https://github.com/user-attachments/files/16982984/collector.log)

The log files will be available on your host in the `config` directory. Please attach them to this issue. 
[web.log](https://github.com/user-attachments/files/16982922/web.log)

Please also provide the output of `docker info`
[docker info.txt](https://github.com/user-attachments/files/16983135/docker.info.txt)

[jgwehr]

I have had a similar issue with two Seagate drives (one brand new, one refurbed). I haven't experienced any practical issues with near daily use for >6 months. I've recently changed the drivedb file and it's reporting PASS. But, I'm still testing since I may not have an accurate configuration - so no commits, yet.

Seems a duplicate of #522

[tomini]

Hello,
is it normal that from four drives that are the same model (ST16000NM001G-2KK103) two of them passed and the other two did not, because of the 188 (0xBC) Command Timeout?
Thanks

[AnalogJ]

Hi!
I'm going to close this as a dupe of #522
Basically Seagate drives are known to use a custom data format for a number of their SMART attributes. This causes issues with Scrutiny's threshold analysis.

• The workaround is to customize the smartctl command that Scrutiny uses for your drive by creating a collector.yaml file
• The real "fix" here is to make sure your Seagate drive is correctly supported by smartmontools. See this PR

Sorry for the bad news, but this is a known issue and there's just not much we can do on the Scrutiny side.