[SOLVED] smartctl read failure

mfoley · 12-03-2023, 11:57 AM

I have a 4TB WDC WD40EFRX-68WT0N0 SATA drive. Running smartctl -a /dev/sdb after running smartctl -t /dev/sdb (self test) reports:

Code:

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline       Completed: read failure       10%      2203         1173004408
# 2  Short offline       Completed: read failure       10%      2009         1352775304
# 3  Short offline       Completed: read failure       90%     55418         2639450161

Yet that report also says, "SMART overall-health self-assessment test result: PASSED".

So what's up here? Does this drive need to be replaced? If it's having read failures, why would it report "PASSED"?

lvm_ · 12-03-2023, 12:35 PM

Such trifles as bad blocks are not considered a device failure until they exceed the available relocation space, hence PASSED. Attributes are more informative than self-test results

mrmazda · 12-03-2023, 05:35 PM

Reallocated_Sector_Ct, Current_Pending_Sector & Offline_Uncorrectable are much better indicators of badness.

mfoley · 12-04-2023, 01:21 PM

To "fix" this, should I do a format with bad block checking?

michaelk · 12-04-2023, 01:30 PM

As suggested post the drive's attributes.

mrmazda · 12-04-2023, 01:38 PM

I would first use WD's downloadable tool. It may report that its condition is warrantyable. If claimed OK, then consider badblocks and format.

beachboy2 · 12-05-2023, 02:50 AM

mfoley,

Have you tried to run a long SMART test?

Code:

sudo smartctl -t long /dev/sdb

Output:

Code:

sudo smartctl -a /dev/sdb

mfoley · 12-09-2023, 01:53 AM

Quote:

Originally Posted by mrmazda

Reallocated_Sector_Ct, Current_Pending_Sector & Offline_Uncorrectable are much better indicators of badness.

Quote:

Originally Posted by beachboy2

mfoley,

Have you tried to run a long SMART test?

Code:

sudo smartctl -t long /dev/sdb

Output:

Code:

sudo smartctl -a /dev/sdb

Running the long test now and will check Reallocated_Sector_Ct, Current_Pending_Sector & Offline_Uncorrectable per mrmazda.

mfoley · 12-11-2023, 02:59 AM

Results of long test:

Code:

ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  5 Reallocated_Sector_Ct   0x0033   200   200   140    Pre-fail  Always       -       0
197 Current_Pending_Sector  0x0032   200   200   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0030   100   253   000    Old_age   Offline      -       0

Conclusion: I'll monitor these attributes going forward and only get worried if any of these show failures. I may do a badblock reformat some day.