-
-
Notifications
You must be signed in to change notification settings - Fork 163
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] I bought this Seagate drive like 2 weeks ago, it Fails in Scrutiny #271
Comments
Seagate drive? They use HEX48 values. Try to get the raw hex value (you can use Crystal Disk Info on Windows for example). Then go here: https://yksi.ml/ and paste the HEX48 value there and see the true value. Had the same issue with my seagate drive. Here's my post on SuperUser too: https://superuser.com/questions/1721683/hdd-smart-read-error-rate-is-my-drive-dying Edit: I didn't see you already did the HEX48 stuff. Sorry. I think scrutiny doesn't convert the value to HEX48 though and that's why it marks it as failed maybe. |
@mariusberget92 Absolutely correct. The Bug is that scrutiny flags my drive. Thanks though :) |
No. Its detected wrong. There is no problem with this brandnew drive. |
see #255 |
yes this is the same problem. @erkston |
This is fixed in latest master :) |
As mentioned by @Parlane this issue has been fixed in v0.4.13. Closing this issue for now, but if that doesn't work for you, please reopen or comment! |
I bought this drive like 2 weeks ago, how could this be:
![image](https://user-images.githubusercontent.com/22225051/170888031-f9e6c920-fc79-4b03-8d8c-a6e70258f2c5.png)
I read out the SMART values myself:
I found this: https://forums.unraid.net/topic/111734-raw-read-error-rate-for-seagate-drives/
and according to this page: https://yksi.ml/ my values should be okay.
Why does scrutiny flag it as failed even though its brandnew?
Originally posted by @Alfagun74 in #267 (comment)
The text was updated successfully, but these errors were encountered: