You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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)
The text was updated successfully, but these errors were encountered:
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.
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
The text was updated successfully, but these errors were encountered: