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] I bought this Seagate drive like 2 weeks ago, it Fails in Scrutiny #271

Closed
Alfagun74 opened this issue May 29, 2022 · 8 comments
Closed

Comments

@Alfagun74
Copy link

Alfagun74 commented May 29, 2022

I bought this drive like 2 weeks ago, how could this be:
image

I read out the SMART values myself:

SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x000f   083   064   044    Pre-fail  Always       -       192564600
  3 Spin_Up_Time            0x0003   098   098   000    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   100   100   020    Old_age   Always       -       3
  5 Reallocated_Sector_Ct   0x0033   100   100   010    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000f   078   060   045    Pre-fail  Always       -       66939600
  9 Power_On_Hours          0x0032   100   100   000    Old_age   Always       -       263 (114 71 0)
 10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   020    Old_age   Always       -       3
184 End-to-End_Error        0x0032   100   100   099    Old_age   Always       -       0
187 Reported_Uncorrect      0x0032   100   100   000    Old_age   Always       -       0
188 Command_Timeout         0x0032   100   100   000    Old_age   Always       -       0
189 High_Fly_Writes         0x003a   100   100   000    Old_age   Always       -       0
190 Airflow_Temperature_Cel 0x0022   071   069   040    Old_age   Always       -       29 (Min/Max 27/31)
191 G-Sense_Error_Rate      0x0032   100   100   000    Old_age   Always       -       0
192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -       2
193 Load_Cycle_Count        0x0032   100   100   000    Old_age   Always       -       5
194 Temperature_Celsius     0x0022   029   040   000    Old_age   Always       -       29 (0 24 0 0 0)
197 Current_Pending_Sector  0x0012   100   100   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0010   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       0
240 Head_Flying_Hours       0x0000   100   253   000    Old_age   Offline      -       263h+00m+14.192s
241 Total_LBAs_Written      0x0000   100   253   000    Old_age   Offline      -       7914774011
242 Total_LBAs_Read         0x0000   100   253   000    Old_age   Offline      -       15623996987

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)

@mariusberget92
Copy link

mariusberget92 commented May 30, 2022

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.

@Alfagun74
Copy link
Author

@mariusberget92 Absolutely correct. The Bug is that scrutiny flags my drive. Thanks though :)

@Alfagun74 Alfagun74 changed the title [BUG] I bought this drive like 2 weeks ago, it Fails in Scrutiny [BUG] I bought this Seagate drive like 2 weeks ago, it Fails in Scrutiny May 30, 2022
@AnalogJ
Copy link
Owner

AnalogJ commented May 30, 2022

@Alfagun74
Copy link
Author

No. Its detected wrong. There is no problem with this brandnew drive.

@erkston
Copy link

erkston commented May 31, 2022

see #255

@Alfagun74
Copy link
Author

yes this is the same problem. @erkston

@Parlane
Copy link

Parlane commented Jun 14, 2022

This is fixed in latest master :)

@AnalogJ
Copy link
Owner

AnalogJ commented Jun 15, 2022

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!

@AnalogJ AnalogJ closed this as completed Jun 15, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants