Help debugging critical drive alerts and smartctl data

jasn

Dabbler
Joined
Dec 19, 2014
Messages
32
I've recently received 3 alert notices for one drive in my FreeNAS-11.3-U5, encrypted RAIDZ2 volume, as part of the regular volume scrubs. They are;

Currently unreadable (pending) sectors.​
Offline uncorrectable sectors.​
and Self-Test Log error count increased from 0 to 1​

I'm confused because of the different messages for the same drive, as well as a zpool status -v shows no errors;
Code:
  pool: freenas-boot
state: ONLINE
  scan: scrub repaired 0 in 0 days 00:00:26 with 0 errors on Sun Mar 21 03:45:26 2021
config:

    NAME        STATE     READ WRITE CKSUM
    freenas-boot  ONLINE       0     0     0
      ada10p2   ONLINE       0     0     0

errors: No known data errors

  pool: vol
state: ONLINE
  scan: scrub repaired 0 in 0 days 07:37:49 with 0 errors on Sun Mar 21 07:37:50 2021
config:

    NAME                                                STATE     READ WRITE CKSUM
    vol                                                 ONLINE       0     0     0
      raidz2-0                                          ONLINE       0     0     0
        gptid/797012c3-1eeb-11ea-b9af-ac1f6b412b68.eli  ONLINE       0     0     0
        gptid/7a3293f8-1eeb-11ea-b9af-ac1f6b412b68.eli  ONLINE       0     0     0
        gptid/7aed11bd-1eeb-11ea-b9af-ac1f6b412b68.eli  ONLINE       0     0     0
        gptid/7bb3f2f4-1eeb-11ea-b9af-ac1f6b412b68.eli  ONLINE       0     0     0
        gptid/7c74f38b-1eeb-11ea-b9af-ac1f6b412b68.eli  ONLINE       0     0     0
        gptid/7d3558a2-1eeb-11ea-b9af-ac1f6b412b68.eli  ONLINE       0     0     0
        gptid/7df5f896-1eeb-11ea-b9af-ac1f6b412b68.eli  ONLINE       0     0     0
        gptid/7ece3b0a-1eeb-11ea-b9af-ac1f6b412b68.eli  ONLINE       0     0     0
    logs
      gptid/823a2635-1eeb-11ea-b9af-ac1f6b412b68.eli    ONLINE       0     0     0
    cache
      gptid/810c2dcb-1eeb-11ea-b9af-ac1f6b412b68.eli    ONLINE       0     0     0

errors: No known data errors

Following joeschmuck's Hard Drive Troubleshooting guide, I ran a long smartctl test on the drive, and I believe the data output indicates 5 unrecoverable errors for the same drive location, but I don't know if this means replace the drive or not. I'd appreciate any additional help in parsing the data;
Code:
smartctl 7.0 2018-12-30 r4883 [FreeBSD 11.3-RELEASE-p14 amd64] (local build)
Copyright (C) 2002-18, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Seagate IronWolf
Device Model:     ST10000VN0004-1ZD101
Serial Number:    [removed]
LU WWN Device Id: 5 000c50 0c36cfe30
Firmware Version: SC61
User Capacity:    10,000,831,348,736 bytes [10.0 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    7200 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:    Mon Mar 22 19:07:59 2021 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:      ( 113)    The previous self-test completed having
                    the read element of the test failed.
Total time to complete Offline
data collection:         (  567) 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:      (   1) minutes.
Extended self-test routine
recommended polling time:      ( 943) minutes.
Conveyance self-test routine
recommended polling time:      (   2) minutes.
SCT capabilities:            (0x50bd)    SCT Status supported.
                    SCT Error Recovery Control supported.
                    SCT Feature Control supported.
                    SCT Data Table supported.

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   079   055   044    Pre-fail  Always       -       87176976
  3 Spin_Up_Time            0x0003   096   092   000    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   100   100   020    Old_age   Always       -       48
  5 Reallocated_Sector_Ct   0x0033   100   100   010    Pre-fail  Always       -       3424
  7 Seek_Error_Rate         0x000f   088   060   045    Pre-fail  Always       -       693704362
  9 Power_On_Hours          0x0032   088   088   000    Old_age   Always       -       11132
10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0
12 Power_Cycle_Count       0x0032   100   100   020    Old_age   Always       -       48
184 End-to-End_Error        0x0032   100   100   099    Old_age   Always       -       0
187 Reported_Uncorrect      0x0032   001   001   000    Old_age   Always       -       891
188 Command_Timeout         0x0032   100   100   000    Old_age   Always       -       0
189 High_Fly_Writes         0x003a   086   086   000    Old_age   Always       -       14
190 Airflow_Temperature_Cel 0x0022   061   054   040    Old_age   Always       -       39 (Min/Max 38/41)
191 G-Sense_Error_Rate      0x0032   075   075   000    Old_age   Always       -       50171
192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -       455
193 Load_Cycle_Count        0x0032   100   100   000    Old_age   Always       -       502
194 Temperature_Celsius     0x0022   039   046   000    Old_age   Always       -       39 (0 21 0 0 0)
195 Hardware_ECC_Recovered  0x001a   017   001   000    Old_age   Always       -       87176976
197 Current_Pending_Sector  0x0012   100   098   000    Old_age   Always       -       104
198 Offline_Uncorrectable   0x0010   100   098   000    Old_age   Offline      -       104
199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       0
200 Pressure_Limit          0x0023   100   100   001    Pre-fail  Always       -       0
240 Head_Flying_Hours       0x0000   100   253   000    Old_age   Offline      -       11113 (129 70 0)
241 Total_LBAs_Written      0x0000   100   253   000    Old_age   Offline      -       25654316539
242 Total_LBAs_Read         0x0000   100   253   000    Old_age   Offline      -       88951480773

SMART Error Log Version: 1
ATA Error Count: 891 (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 891 occurred at disk power-on lifetime: 7727 hours (321 days + 23 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 51 00 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455

  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 d8 ff ff ff 4f 00      08:44:59.786  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00      08:44:59.786  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00      08:44:59.786  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00      08:44:59.786  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00      08:44:59.786  READ FPDMA QUEUED

Error 890 occurred at disk power-on lifetime: 7727 hours (321 days + 23 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 51 00 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455

  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 d8 ff ff ff 4f 00      08:44:57.703  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00      08:44:57.703  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00      08:44:57.703  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00      08:44:57.703  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00      08:44:57.703  READ FPDMA QUEUED

Error 889 occurred at disk power-on lifetime: 7727 hours (321 days + 23 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 51 00 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455

  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 d8 ff ff ff 4f 00      08:44:55.537  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00      08:44:55.537  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00      08:44:55.537  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00      08:44:55.537  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00      08:44:55.537  READ FPDMA QUEUED

Error 888 occurred at disk power-on lifetime: 7727 hours (321 days + 23 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 51 00 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455

  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 d8 ff ff ff 4f 00      08:44:53.429  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00      08:44:53.429  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00      08:44:53.429  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00      08:44:53.428  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00      08:44:53.428  READ FPDMA QUEUED

Error 887 occurred at disk power-on lifetime: 7727 hours (321 days + 23 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 51 00 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455

  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 d8 ff ff ff 4f 00      08:44:51.294  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00      08:44:51.294  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00      08:44:51.294  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00      08:44:51.293  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00      08:44:51.293  READ FPDMA QUEUED

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Extended offline    Completed: read failure       10%     11118         -

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.

Lastly, if this drive should be replaced, (I have a spare), I'm anxious to understand the proper procedure to replace a drive in an encrypted volume.

The FreeNAS documentation covers drive replacements here, but there are also separate callouts regarding encrypted volumes. It would have been easier to understand if the documentation simply including the entire process for replacing a drive in an encrypted volume, as well.

So, please feel free to recommend any other guides/videos that can help me understand the proper steps involved.

Thanks..
 
Last edited:

sretalla

Powered by Neutrality
Moderator
Joined
Jan 1, 2016
Messages
9,703
197 Current_Pending_Sector 0x0012 100 098 000 Old_age Always - 104
198 Offline_Uncorrectable 0x0010 100 098 000 Old_age Offline - 104
These are not a good indication.

Error: UNC at LBA = 0x0fffffff = 268435455
Here's the error indicating the block address of at least one problem block.

Usually the way it goes is that this will get worse until it eventually causes the drive to fail completely. You can wait, but it's likely not to be too long, so acting now is prudent.

You will indeed have to follow the process to replace a disk in a GELI encrypted pool.
 

jasn

Dabbler
Joined
Dec 19, 2014
Messages
32
Thank you.

Folks on the FreeNAS subreddit agreed that this drive does indeed need to be replaced.

Rereading the FreeNAS documentation it appears that the steps for replacing a drive in an encrypted pool is;
  1. Place the drive in offline mode
  2. Remove the drive from the server
  3. Install the new drive
  4. Use the replace drive option to select the new drive and add it to the pool
  5. Enter in the encryption key which begins the resilver process
I remember my passphrase, and I did download the geli recovery key when I initially setup the volume. So I believe I have everything I need. If anyone thinks I should do anything else, please feel free to comment.

For example, to be completely sure of no issues, I thought I should use the reset keys to generate a new geli key and add a new passphrase, prior to performing the drive replacement.
 
Top