Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Command Timeout on Seagate Exos 7E8 #687

Open
theAlevan opened this issue Sep 12, 2024 · 1 comment
Open

[BUG] Command Timeout on Seagate Exos 7E8 #687

theAlevan opened this issue Sep 12, 2024 · 1 comment
Labels
bug Something isn't working

Comments

@theAlevan
Copy link

theAlevan commented Sep 12, 2024

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
image

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)
@theAlevan theAlevan added the bug Something isn't working label Sep 12, 2024
@jgwehr
Copy link

jgwehr commented Sep 17, 2024

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants