SMART Error, trying to determine issue

LIGISTX

Guru
Joined
Apr 12, 2015
Messages
525
Hi everyone,

Woke up this morning to a email alert of "Device: /dev/da3 [SAT], Self-Test Log error count increased from 0 to 1."

Doing a smartctl -x I get:

Code:
smartctl 7.2 2020-12-30 r5155 [FreeBSD 12.2-RELEASE-p12 amd64] (local build)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Western Digital Red
Device Model:     WDC WD40EFRX-68N32N0
Serial Number:    WD-WCC7XXXXXXXX
LU WWN Device Id: 5 0014ee 20f3c6421
Firmware Version: 82.00A82
User Capacity:    4,000,787,030,016 bytes [4.00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    5400 rpm
Form Factor:      3.5 inches
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ACS-3 T13/2161-D revision 5
SATA Version is:  SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Sun Mar 20 08:22:03 2022 PDT
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
AAM feature is:   Unavailable
APM feature is:   Unavailable
Rd look-ahead is: Enabled
Write cache is:   Enabled
DSN feature is:   Unavailable
ATA Security is:  Disabled, NOT FROZEN [SEC1]
Wt Cache Reorder: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status:  (0x00) Offline data collection activity
                                        was never started.
                                        Auto Offline Data Collection: Disabled.
Self-test execution status:      ( 118) The previous self-test completed having
                                        the read element of the test failed.
Total time to complete Offline
data collection:                (45180) seconds.
Offline data collection
capabilities:                    (0x7b) SMART execute Offline immediate.
                                        Auto Offline data collection on/off support.
                                        Suspend Offline collection upon new
                                        command.
                                        Offline surface scan supported.
                                        Self-test supported.
                                        Conveyance Self-test supported.
                                        Selective Self-test supported.
SMART capabilities:            (0x0003) Saves SMART data before entering
                                        power-saving mode.
                                        Supports SMART auto save timer.
Error logging capability:        (0x01) Error logging supported.
                                        General Purpose Logging supported.
Short self-test routine
recommended polling time:        (   2) minutes.
Extended self-test routine
recommended polling time:        ( 480) minutes.
Conveyance self-test routine
recommended polling time:        (   5) minutes.
SCT capabilities:              (0x303d) SCT Status supported.
                                        SCT Error Recovery Control supported.
                                        SCT Feature Control supported.
                                        SCT Data Table supported.

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAGS    VALUE WORST THRESH FAIL RAW_VALUE
  1 Raw_Read_Error_Rate     POSR-K   200   200   051    -    0
  3 Spin_Up_Time            POS--K   189   157   021    -    5533
  4 Start_Stop_Count        -O--CK   100   100   000    -    180
  5 Reallocated_Sector_Ct   PO--CK   200   200   140    -    0
  7 Seek_Error_Rate         -OSR-K   200   200   000    -    0
  9 Power_On_Hours          -O--CK   049   049   000    -    37554
 10 Spin_Retry_Count        -O--CK   100   100   000    -    0
 11 Calibration_Retry_Count -O--CK   100   100   000    -    0
 12 Power_Cycle_Count       -O--CK   100   100   000    -    173
192 Power-Off_Retract_Count -O--CK   200   200   000    -    167
193 Load_Cycle_Count        -O--CK   200   200   000    -    101
194 Temperature_Celsius     -O---K   119   102   000    -    31
196 Reallocated_Event_Count -O--CK   200   200   000    -    0
197 Current_Pending_Sector  -O--CK   200   200   000    -    0
198 Offline_Uncorrectable   ----CK   100   253   000    -    0
199 UDMA_CRC_Error_Count    -O--CK   200   200   000    -    0
200 Multi_Zone_Error_Rate   ---R--   200   200   000    -    2
                            ||||||_ K auto-keep
                            |||||__ C event count
                            ||||___ R error rate
                            |||____ S speed/performance
                            ||_____ O updated online
                            |______ P prefailure warning

General Purpose Log Directory Version 1
SMART           Log Directory Version 1 [multi-sector log support]
Address    Access  R/W   Size  Description
0x00       GPL,SL  R/O      1  Log Directory
0x01           SL  R/O      1  Summary SMART error log
0x02           SL  R/O      5  Comprehensive SMART error log
0x03       GPL     R/O      6  Ext. Comprehensive SMART error log
0x04       GPL,SL  R/O      8  Device Statistics log
0x06           SL  R/O      1  SMART self-test log
0x07       GPL     R/O      1  Extended self-test log
0x09           SL  R/W      1  Selective self-test log
0x10       GPL     R/O      1  NCQ Command Error log
0x11       GPL     R/O      1  SATA Phy Event Counters log
0x30       GPL,SL  R/O      9  IDENTIFY DEVICE data log
0x80-0x9f  GPL,SL  R/W     16  Host vendor specific log
0xa0-0xa7  GPL,SL  VS      16  Device vendor specific log
0xa8-0xb6  GPL,SL  VS       1  Device vendor specific log
0xb7       GPL,SL  VS      56  Device vendor specific log
0xbd       GPL,SL  VS       1  Device vendor specific log
0xc0       GPL,SL  VS       1  Device vendor specific log
0xc1       GPL     VS      93  Device vendor specific log
0xe0       GPL,SL  R/W      1  SCT Command/Status
0xe1       GPL,SL  R/W      1  SCT Data Transfer

SMART Extended Comprehensive Error Log Version: 1 (6 sectors)
No Errors Logged

SMART Extended Self-test Log Version: 1 (1 sectors)
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Extended offline    Completed: read failure       60%     37549         2088848576
# 2  Short offline       Completed without error       00%     37522         -
# 3  Short offline       Completed without error       00%     37499         -
# 4  Short offline       Completed without error       00%     37475         -
# 5  Extended offline    Completed without error       00%     37459         -
# 6  Short offline       Completed without error       00%     37427         -
# 7  Short offline       Completed without error       00%     37403         -
# 8  Extended offline    Completed without error       00%     37388         -
# 9  Short offline       Completed without error       00%     37356         -
#10  Short offline       Completed without error       00%     37332         -
#11  Short offline       Completed without error       00%     37308         -
#12  Extended offline    Completed without error       00%     37292         -
#13  Short offline       Completed without error       00%     37261         -
#14  Short offline       Completed without error       00%     37236         -
#15  Extended offline    Completed without error       00%     37221         -
#16  Short offline       Completed without error       00%     37188         -
#17  Short offline       Completed without error       00%     37164         -
#18  Short offline       Completed without error       00%     37140         -

SMART Selective self-test log data structure revision number 1
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Not_testing
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing
Selective self-test flags (0x0):
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.

SCT Status Version:                  3
SCT Version (vendor specific):       258 (0x0102)
Device State:                        Active (0)
Current Temperature:                    31 Celsius
Power Cycle Min/Max Temperature:     26/34 Celsius
Lifetime    Min/Max Temperature:     20/48 Celsius
Under/Over Temperature Limit Count:   0/0
Vendor specific:
01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

SCT Temperature History Version:     2
Temperature Sampling Period:         1 minute
Temperature Logging Interval:        1 minute
Min/Max recommended Temperature:      0/65 Celsius
Min/Max Temperature Limit:           -41/85 Celsius
Temperature History Size (Index):    478 (73)

Index    Estimated Time   Temperature Celsius
  74    2022-03-20 00:25    32  *************
 ...    ..(163 skipped).    ..  *************
 238    2022-03-20 03:09    32  *************
 239    2022-03-20 03:10    31  ************
 ...    ..( 99 skipped).    ..  ************
 339    2022-03-20 04:50    31  ************
 340    2022-03-20 04:51    33  **************
 ...    ..( 12 skipped).    ..  **************
 353    2022-03-20 05:04    33  **************
 354    2022-03-20 05:05    34  ***************
 ...    ..(152 skipped).    ..  ***************
  29    2022-03-20 07:38    34  ***************
  30    2022-03-20 07:39    33  **************
 ...    ..( 31 skipped).    ..  **************
  62    2022-03-20 08:11    33  **************
  63    2022-03-20 08:12    32  *************
 ...    ..(  9 skipped).    ..  *************
  73    2022-03-20 08:22    32  *************

SCT Error Recovery Control:
           Read:     70 (7.0 seconds)
          Write:     70 (7.0 seconds)

Device Statistics (GP Log 0x04)
Page  Offset Size        Value Flags Description
0x01  =====  =               =  ===  == General Statistics (rev 1) ==
0x01  0x008  4             173  ---  Lifetime Power-On Resets
0x01  0x010  4           37554  ---  Power-on Hours
0x01  0x018  6     73271643701  ---  Logical Sectors Written
0x01  0x020  6      1905247108  ---  Number of Write Commands
0x01  0x028  6    555319278639  ---  Logical Sectors Read
0x01  0x030  6      3556530456  ---  Number of Read Commands
0x01  0x038  6      2050413824  ---  Date and Time TimeStamp
0x03  =====  =               =  ===  == Rotating Media Statistics (rev 1) ==
0x03  0x008  4           37362  ---  Spindle Motor Power-on Hours
0x03  0x010  4           37260  ---  Head Flying Hours
0x03  0x018  4             269  ---  Head Load Events
0x03  0x020  4               0  ---  Number of Reallocated Logical Sectors
0x03  0x028  4          284578  ---  Read Recovery Attempts
0x03  0x030  4               0  ---  Number of Mechanical Start Failures
0x03  0x038  4               0  ---  Number of Realloc. Candidate Logical Sectors
0x03  0x040  4             167  ---  Number of High Priority Unload Events
0x04  =====  =               =  ===  == General Errors Statistics (rev 1) ==
0x04  0x008  4               0  ---  Number of Reported Uncorrectable Errors
0x04  0x010  4               1  ---  Resets Between Cmd Acceptance and Completion
0x05  =====  =               =  ===  == Temperature Statistics (rev 1) ==
0x05  0x008  1              31  ---  Current Temperature
0x05  0x010  1              32  ---  Average Short Term Temperature
0x05  0x018  1              29  ---  Average Long Term Temperature
0x05  0x020  1              48  ---  Highest Temperature
0x05  0x028  1              20  ---  Lowest Temperature
0x05  0x030  1              44  ---  Highest Average Short Term Temperature
0x05  0x038  1              24  ---  Lowest Average Short Term Temperature
0x05  0x040  1              37  ---  Highest Average Long Term Temperature
0x05  0x048  1              27  ---  Lowest Average Long Term Temperature
0x05  0x050  4               0  ---  Time in Over-Temperature
0x05  0x058  1              65  ---  Specified Maximum Operating Temperature
0x05  0x060  4               0  ---  Time in Under-Temperature
0x05  0x068  1               0  ---  Specified Minimum Operating Temperature
0x06  =====  =               =  ===  == Transport Statistics (rev 1) ==
0x06  0x008  4            1470  ---  Number of Hardware Resets
0x06  0x010  4              31  ---  Number of ASR Events
0x06  0x018  4               0  ---  Number of Interface CRC Errors
                                |||_ C monitored condition met
                                ||__ D supports DSN
                                |___ N normalized value

Pending Defects log (GP Log 0x0c) not supported

SATA Phy Event Counters (GP Log 0x11)
ID      Size     Value  Description
0x0001  2            0  Command failed due to ICRC error
0x0002  2            0  R_ERR response for data FIS
0x0003  2            0  R_ERR response for device-to-host data FIS
0x0004  2            0  R_ERR response for host-to-device data FIS
0x0005  2            0  R_ERR response for non-data FIS
0x0006  2            0  R_ERR response for device-to-host non-data FIS
0x0007  2            0  R_ERR response for host-to-device non-data FIS
0x0008  2            0  Device-to-host non-data FIS retries
0x0009  2            1  Transition from


I think what I am seeing is it had a read failure via "# 1 Extended offline Completed: read failure 60% 37549"

What should next steps be? Try a resilver and long test after that? Just do a long test and see what it tells me? I love the SMART *usually* helps give warning of impending doom, I just wish I better understood what it was telling me...
 

NugentS

MVP
Joined
Apr 16, 2020
Messages
2,947
The smart failure is not good.
I would take the disk offline (swap in a spare) and then do the equivalent of badblocks the entire disk which may map out the dodgy sector. Then re-run the smart long test. If it passes (badblocks and smart) then the disk can be used as a spare for next time.
 

danb35

Hall of Famer
Joined
Aug 16, 2011
Messages
15,504
Try a resilver and long test after that?
No reason at all to do a resilver, and your drive has just failed a long test. I guess you could run another one for the sake of confirmation, but I'd likely be replacing the drive.
 

LIGISTX

Guru
Joined
Apr 12, 2015
Messages
525
The smart failure is not good.
I would take the disk offline (swap in a spare) and then do the equivalent of badblocks the entire disk which may map out the dodgy sector. Then re-run the smart long test. If it passes (badblocks and smart) then the disk can be used as a spare for next time.
Hmm, I do not have any spares, but I guess that is just an amazon order away... You think there is a chance it can be recovered via badblocksing it?

No reason at all to do a resilver, and your drive has just failed a long test. I guess you could run another one for the sake of confirmation, but I'd likely be replacing the drive.
Your opinion is its donezo? I figured as much...
 

danb35

Hall of Famer
Joined
Aug 16, 2011
Messages
15,504
Your opinion is its donezo? I
My opinion is that I don't trust a disk that's failed a long SMART self-test. Now, if it passes a repeat test, that might change things, but I'd still be wary.
 

NugentS

MVP
Joined
Apr 16, 2020
Messages
2,947
Which is why I said keep it as a spare, just in case.
I have some WD Red that fail as your have done, I have then done a full erase after which they pass a smart test. I have one of them in a RAID6 (non ZFS) array and irs working just fine, for now
 

LIGISTX

Guru
Joined
Apr 12, 2015
Messages
525
My opinion is that I don't trust a disk that's failed a long SMART self-test. Now, if it passes a repeat test, that might change things, but I'd still be wary.
Which is why I said keep it as a spare, just in case.
I have some WD Red that fail as your have done, I have then done a full erase after which they pass a smart test. I have one of them in a RAID6 (non ZFS) array and irs working just fine, for now
Thanks for the advice. Replacement will be here this evening… few days it’ll be finished with a bad blocks/smart burn in. Then I’ll see if I can salvage it and retain as a spare.

If I remember right, they say to do a long test, bad blocks, then long test. I don’t quite understand why you need to do a long test first…. Just wastes half a day imo, but what do I know.
 

danb35

Hall of Famer
Joined
Aug 16, 2011
Messages
15,504
Just wastes half a day imo
Because part of the purpose of the process is just to run (and stress) the drive for a while, and make sure it won't die on you. I won't always do SMART tests at beginning and end, depending mainly on how long badblocks takes to run. Last drives I commissioned were 16 TB, and badblocks itself took over a week. The one SMART test was enough for me. But for a 2 TB disk? I'd want to bang on it a bit anyway, so I'd probably do the SMART tests beginning and end.
 

LIGISTX

Guru
Joined
Apr 12, 2015
Messages
525
Because part of the purpose of the process is just to run (and stress) the drive for a while, and make sure it won't die on you. I won't always do SMART tests at beginning and end, depending mainly on how long badblocks takes to run. Last drives I commissioned were 16 TB, and badblocks itself took over a week. The one SMART test was enough for me. But for a 2 TB disk? I'd want to bang on it a bit anyway, so I'd probably do the SMART tests beginning and end.
I guess I don’t fully understand what a long test does. I thought SMART tests don’t actually go and read or write data (writing they obviously don’t do), so how is that even considered “banging on them”? I did a long test last night and it’s now started on badnlocks, but I just don’t fully understand and am trying to get a better grasp on why the first smart test “matters”.
 

NugentS

MVP
Joined
Apr 16, 2020
Messages
2,947
A long test reads all sectors on the drive and reports on errors. To be honest the first test doesn't really matter as you recently ran one (which failed) - so you know your starting position. Just run badblocks (in destructive mode) and then a long test and see if it passes.
 

LIGISTX

Guru
Joined
Apr 12, 2015
Messages
525
A long test reads all sectors on the drive and reports on errors. To be honest the first test doesn't really matter as you recently ran one (which failed) - so you know your starting position. Just run badblocks (in destructive mode) and then a long test and see if it passes.
I’m more talking about a new drive. I already have a replacement being tested, just not sure why the recommendation is long, badblocks, long, when the first long test theoretically is just reporting on a brand new drive… I guess if it is actually reading the sectors it could pop up with an issue.
 

NugentS

MVP
Joined
Apr 16, 2020
Messages
2,947
You don't want to spend a week badblocking a drive when a simple long test could have given you sufficient ammunition to RMA it immediately.
 
Top