ATA Error Count Increase during scrubs

shakezilla

Cadet
Joined
Mar 1, 2016
Messages
8
Alright I have a 6 drive pool in RAIDZ2 and recently one of my disks started throwing ATA errors during pool scrubs. It only throws a few per scrub (1-3 errors per scrub) but it's fairly consistent for the past few weeks now. The scrubs consistently show no errors.

I'm very confused by what is happening because all of the typical SMART entries that I would use to determine drive failure (5, 197-198) are reporting as 0. Even 199 is reporting as 0. I replaced the SATA cable for the drive a few weeks back after the scrub revealed another 2 errors. But the scrub that went again last night still triggered another 3 errors despite the new SATA cable. SMART tests all show no issues.

I'm very confused and not really sure what to check at this point. Output and hardware below.

zpool status output:
Code:
freenas% zpool status
  pool: MasterPool
 state: ONLINE
status: Some supported features are not enabled on the pool. The pool can
        still be used, but some features are unavailable.
action: Enable all features using 'zpool upgrade'. Once this is done,
        the pool may no longer be accessible by software that does not support
        the features. See zpool-features(5) for details.
  scan: scrub repaired 0B in 12:28:32 with 0 errors on Fri Apr  1 14:28:33 2022
config:

        NAME                                            STATE     READ WRITE CKSUM
        MasterPool                                      ONLINE       0     0     0
          raidz2-0                                      ONLINE       0     0     0
            gptid/db2afdf9-6b06-11ea-a1c9-d050998a98fb  ONLINE       0     0     0
            gptid/6d76e2a1-6df7-11ea-b668-d050998a98fb  ONLINE       0     0     0
            gptid/9e3d3991-6f09-11ea-970a-d050998a98fb  ONLINE       0     0     0
            gptid/6ded85ae-6a0a-11ea-b05b-d050998a98fb  ONLINE       0     0     0
            gptid/ffbf5129-6cbd-11ea-85c1-d050998a98fb  ONLINE       0     0     0
            gptid/68860885-68c9-11ea-8174-d050998a98fb  ONLINE       0     0     0

errors: No known data errors

  pool: freenas-boot
 state: ONLINE
status: Some supported features are not enabled on the pool. The pool can
        still be used, but some features are unavailable.
action: Enable all features using 'zpool upgrade'. Once this is done,
        the pool may no longer be accessible by software that does not support
        the features. See zpool-features(5) for details.
  scan: scrub repaired 0B in 00:00:04 with 0 errors on Tue Mar 29 03:45:04 2022
config:

        NAME          STATE     READ WRITE CKSUM
        freenas-boot  ONLINE       0     0     0
          mirror-0    ONLINE       0     0     0
            nvd0p2    ONLINE       0     0     0
            ada0p2    ONLINE       0     0     0

errors: No known data errors


Here's a copy of the SMART output from the drive in question:
Code:
freenas% sudo smartctl -a /dev/ada2
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 WD100EFAX-68LHPN0
Serial Number:    1EHKPLGZ
LU WWN Device Id: 5 000cca 27ed622e1
Firmware Version: 83.H0A83
User Capacity:    10,000,831,348,736 bytes [10.0 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-2, ATA8-ACS T13/1699-D revision 4
SATA Version is:  SATA 3.2, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Fri Apr  1 11:17:58 2022 EDT
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

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

General SMART Values:
Offline data collection status:  (0x82) Offline data collection activity
                                        was completed without error.
                                        Auto Offline Data Collection: Enabled.
Self-test execution status:      (   0) The previous self-test routine completed
                                        without error or no self-test has ever
                                        been run.
Total time to complete Offline
data collection:                (   93) seconds.
Offline data collection
capabilities:                    (0x5b) SMART execute Offline immediate.
                                        Auto Offline data collection on/off support.
                                        Suspend Offline collection upon new
                                        command.
                                        Offline surface scan supported.
                                        Self-test supported.
                                        No 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:        (1160) minutes.
SCT capabilities:              (0x003d) 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          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x000b   100   100   016    Pre-fail  Always       -       0
  2 Throughput_Performance  0x0004   130   130   054    Old_age   Offline      -       108
  3 Spin_Up_Time            0x0007   221   221   024    Pre-fail  Always       -       263 (Average 332)
  4 Start_Stop_Count        0x0012   100   100   000    Old_age   Always       -       93
  5 Reallocated_Sector_Ct   0x0033   100   100   005    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000a   100   100   067    Old_age   Always       -       0
  8 Seek_Time_Performance   0x0004   128   128   020    Old_age   Offline      -       18
  9 Power_On_Hours          0x0012   098   098   000    Old_age   Always       -       17281
 10 Spin_Retry_Count        0x0012   100   100   060    Old_age   Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       93
 22 Helium_Level            0x0023   100   100   025    Pre-fail  Always       -       100
192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -       806
193 Load_Cycle_Count        0x0012   100   100   000    Old_age   Always       -       806
194 Temperature_Celsius     0x0002   185   185   000    Old_age   Always       -       35 (Min/Max 24/52)
196 Reallocated_Event_Count 0x0032   100   100   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0022   100   100   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0008   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x000a   200   200   000    Old_age   Always       -       0

SMART Error Log Version: 1
ATA Error Count: 12 (device log contains only the most recent five errors)
        CR = Command Register [HEX]
        FR = Features Register [HEX]
        SC = Sector Count Register [HEX]
        SN = Sector Number Register [HEX]
        CL = Cylinder Low Register [HEX]
        CH = Cylinder High Register [HEX]
        DH = Device/Head Register [HEX]
        DC = Device Command Register [HEX]
        ER = Error register [HEX]
        ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.

Error 12 occurred at disk power-on lifetime: 17273 hours (719 days + 17 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 41 00 00 00 00 00  Error: UNC at LBA = 0x00000000 = 0

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 c8 68 d8 a9 95 40 08  12d+04:18:24.458  READ FPDMA QUEUED
  2f 00 01 10 00 00 00 08  12d+04:18:17.541  READ LOG EXT
  2f 00 01 10 00 00 00 08  12d+04:18:17.541  READ LOG EXT
  60 c8 58 d8 a9 95 40 08  12d+04:18:03.705  READ FPDMA QUEUED
  60 00 50 d8 a1 95 40 08  12d+04:18:03.705  READ FPDMA QUEUED

Error 11 occurred at disk power-on lifetime: 17273 hours (719 days + 17 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 41 00 00 00 00 00  Error: UNC at LBA = 0x00000000 = 0

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 c8 58 d8 a9 95 40 08  12d+04:18:17.541  READ FPDMA QUEUED
  60 00 50 d8 a1 95 40 08  12d+04:18:03.705  READ FPDMA QUEUED
  60 00 48 d8 99 95 40 08  12d+04:18:03.705  READ FPDMA QUEUED
  60 00 40 d8 91 95 40 08  12d+04:18:02.548  READ FPDMA QUEUED
  60 00 38 d8 89 95 40 08  12d+04:17:59.445  READ FPDMA QUEUED

Error 10 occurred at disk power-on lifetime: 17272 hours (719 days + 16 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 41 00 00 00 00 00  Error: UNC at LBA = 0x00000000 = 0

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 90 d0 78 e5 83 40 08  12d+04:06:42.936  READ FPDMA QUEUED
  60 08 e0 30 f0 83 40 08  12d+04:06:36.016  READ FPDMA QUEUED
  60 08 d8 d0 e7 83 40 08  12d+04:06:35.637  READ FPDMA QUEUED
  60 10 c8 80 de 83 40 08  12d+04:06:35.166  READ FPDMA QUEUED
  60 10 c0 78 d7 83 40 08  12d+04:06:34.981  READ FPDMA QUEUED

Error 9 occurred at disk power-on lifetime: 16874 hours (703 days + 2 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 41 00 00 00 00 00  Error: UNC at LBA = 0x00000000 = 0

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 00 a0 40 37 eb 40 08   1d+21:14:55.610  READ FPDMA QUEUED
  60 00 a8 40 3f eb 40 08   1d+21:14:48.690  READ FPDMA QUEUED
  60 d8 98 68 2f eb 40 08   1d+21:14:48.690  READ FPDMA QUEUED
  2f 00 01 10 00 00 00 08   1d+21:14:48.689  READ LOG EXT
  2f 00 01 10 00 00 00 08   1d+21:14:48.689  READ LOG EXT

Error 8 occurred at disk power-on lifetime: 16874 hours (703 days + 2 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 41 00 00 00 00 00  Error: UNC at LBA = 0x00000000 = 0

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 d8 68 68 2f eb 40 08   1d+21:14:48.689  READ FPDMA QUEUED
  61 18 88 90 c0 d5 40 08   1d+21:14:46.783  WRITE FPDMA QUEUED
  61 08 80 78 84 b8 40 08   1d+21:14:46.782  WRITE FPDMA QUEUED
  60 00 78 40 3f eb 40 08   1d+21:14:41.655  READ FPDMA QUEUED
  60 00 70 40 37 eb 40 08   1d+21:14:41.655  READ FPDMA QUEUED

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline       Completed without error       00%     17223         -
# 2  Short offline       Completed without error       00%     17175         -
# 3  Short offline       Completed without error       00%     17127         -
# 4  Short offline       Completed without error       00%     17079         -
# 5  Extended offline    Completed without error       00%     17052         -
# 6  Short offline       Completed without error       00%     17031         -
# 7  Short offline       Completed without error       00%     16983         -
# 8  Short offline       Completed without error       00%     16936         -
# 9  Short offline       Completed without error       00%     16888         -
#10  Short offline       Completed without error       00%     16840         -
#11  Short offline       Completed without error       00%     16795         -
#12  Short offline       Completed without error       00%     16747         -
#13  Extended offline    Completed without error       00%     16718         -
#14  Short offline       Completed without error       00%     16699         -
#15  Short offline       Completed without error       00%     16651         -
#16  Short offline       Completed without error       00%     16603         -
#17  Short offline       Completed without error       00%     16555         -
#18  Short offline       Completed without error       00%     16507         -
#19  Short offline       Completed without error       00%     16459         -
#20  Short offline       Completed without error       00%     16411         -
#21  Extended offline    Completed without error       00%     16383         -

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.


Hardware list:
Intel Xeon E-1220 V3 3.1GHz w/ Stock Fan
ASRock Z97 Extreme6 ATX LGA1150 Motherboard
2 x G.Skill Ripjaws X Series 8GB DDR3-1866 CL9 RAM
WD Black 250GB M.2-2280 NVME SSD
Silicon Power A55 256GB SSD
6 X WD Red 10TB 5400RPM (WD100EFAX) HDDs
EVGA GeForce 210 1GB DDR3 Video Card
Intel EXPI9301CT PCIe x1 1 Gbit/s Network Adapter
EVGA Supernova 750W P5 80+ Platinum Certified PSU
Fractal Design Define R5 ATX Mid Tower Case
 

NugentS

MVP
Joined
Apr 16, 2020
Messages
2,947
Thats a WDC WD100EFAX-68LHPN0. The EFAX can (but not always - thanks WD) indicate that the drive is SMR

Can you confirm wether the drive is SMR or CMR? I really hope its a CMR.

Other than that nothing else jumps out at me as being faulty other than the errors obviously
[What is slightly worrying is that the LBA is 00000000 rather than somewhere else]

Do you have a spare drive? Do you have backups?
The drive seems to be having issues reading some sectors. Can you take the drive offline and run a surface test on it (badblocks or similar - warning will take 3-4 days) and see what happens. It also might be worth contacting WD and see if the warranty is good - the drive has <2 years power up
 

shakezilla

Cadet
Joined
Mar 1, 2016
Messages
8
Thats a WDC WD100EFAX-68LHPN0. The EFAX can (but not always - thanks WD) indicate that the drive is SMR

Can you confirm wether the drive is SMR or CMR? I really hope its a CMR.

Other than that nothing else jumps out at me as being faulty other than the errors obviously
[What is slightly worrying is that the LBA is 00000000 rather than somewhere else]

Do you have a spare drive? Do you have backups?
The drive seems to be having issues reading some sectors. Can you take the drive offline and run a surface test on it (badblocks or similar - warning will take 3-4 days) and see what happens. It also might be worth contacting WD and see if the warranty is good - the drive has <2 years power up

It is a CMR drive.

I do not have any spare drives on hand and it would be a huge pain to take the drive offline, wipe it, run a bunch of tests, and then resilver it back into the pool. I could get a spare drive to replace it and run those steps later on I suppose. I'd hate to replace it and have the drive turn out fine because that leaves me with a spare working drive with 17000 hours of wear on it.
 

NugentS

MVP
Joined
Apr 16, 2020
Messages
2,947
Well its always worth having a spare drive anyway - for just this sort of problem
 

Redcoat

MVP
Joined
Feb 18, 2014
Messages
2,925
Well its always worth having a spare drive anyway - for just this sort of problem
Agreed! After 76 years of experience with Murphy's Law I cannot imagine running without one spare drive per server...
 

shakezilla

Cadet
Joined
Mar 1, 2016
Messages
8
I'll order a new drive now in that case but I'll have to run burn in tests on it before I can swap out the problem drive for isolated testing. The current drive has been running like this for several weeks now and only throws errors during scrubs so I assume it will be safe to leave it as is while I burn in the new drive.

If I can run a surface test on the current drive and it reveals no errors/issues, then where does that leave me?
 

NugentS

MVP
Joined
Apr 16, 2020
Messages
2,947
I'll order a new drive now in that case but I'll have to run burn in tests on it before I can swap out the problem drive for isolated testing. The current drive has been running like this for several weeks now and only throws errors during scrubs so I assume it will be safe to leave it as is while I burn in the new drive.

If I can run a surface test on the current drive and it reveals no errors/issues, then where does that leave me?
I think thats a question you answer after running the test.
However, before running any week long burn in / stress test - the first thing to do is run WD's diagnostic tools over the drive. If they fail then warranty the drive (assuming its still got warranty)
 
Top