Smart Readout Question/Unrecoverable error

m_aar_ten · Oct 16, 2023

I recently bought a pretty new drive (under 2000 hours) from a data center near me.
After installing it, TrueNAS wouldnt detect the drive, after trying some things out I found the solution, the drive wanted its own SATA power cable, it wouldnt detect when there was another drive plugged into the cable.

After installing it in my new server I ran a long SMART test.
Halfway through I got an alert for an unrecoverable error, but everything was still functioning(according to the alert) , ZFS Health now show 10 ZFS Error.

After a good 24+ hours the test finally finished, gave me an alert for 202 offline uncorrectable.
My question is: should I be worried about this? This drive has barely been running for 3 days in my system, and is still pretty new all things considered.
Could it be possible that there are problems with the cable SATA or SATA power cable?

Seeing as this drive is not even a year old, would this fall under warranty, seeing as the drive hasnt failed yet.
I am very new to this, I tried searching for answers but it has been hard to find something clear.

Here are the SATA test results.

Code:

sudo smartctl -x /dev/sda
smartctl 7.2 2020-12-30 r5155 [x86_64-linux-5.15.131+truenas] (local build)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Toshiba MG08ACA... Enterprise Capacity HDD
Device Model:     TOSHIBA MG08ACA16TE
Serial Number:    4290A1AFFVGG
LU WWN Device Id: 5 000039 b98cb3e15
Firmware Version: 0102
User Capacity:    16,000,900,661,248 bytes [16.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.3, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Mon Oct 16 22:00:43 2023 CEST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
AAM feature is:   Unavailable
APM feature is:   Disabled
Rd look-ahead is: Enabled
Write cache is:   Enabled
DSN feature is:   Unavailable
ATA Security is:  Disabled, frozen [SEC2]
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:  (0x84) Offline data collection activity
                                        was suspended by an interrupting command from host.
                                        Auto Offline Data Collection: Enabled.
Self-test execution status:      ( 119) The previous self-test completed having
                                        the read element of the test failed.
Total time to complete Offline
data collection:                (  120) 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:        (1418) 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          FLAGS    VALUE WORST THRESH FAIL RAW_VALUE
  1 Raw_Read_Error_Rate     PO-R--   100   085   050    -    0
  2 Throughput_Performance  P-S---   100   100   050    -    0
  3 Spin_Up_Time            POS--K   100   100   001    -    7914
  4 Start_Stop_Count        -O--CK   100   100   000    -    15
  5 Reallocated_Sector_Ct   PO--CK   100   100   010    -    4
  7 Seek_Error_Rate         PO-R--   100   100   050    -    0
  8 Seek_Time_Performance   P-S---   100   100   050    -    0
  9 Power_On_Hours          -O--CK   096   096   000    -    1772
 10 Spin_Retry_Count        PO--CK   100   100   030    -    0
 12 Power_Cycle_Count       -O--CK   100   100   000    -    14
 23 Helium_Condition_Lower  PO---K   100   100   075    -    0
 24 Helium_Condition_Upper  PO---K   100   100   075    -    0
191 G-Sense_Error_Rate      -O--CK   100   100   000    -    1
192 Power-Off_Retract_Count -O--CK   100   100   000    -    12
193 Load_Cycle_Count        -O--CK   100   100   000    -    184
194 Temperature_Celsius     -O---K   100   100   000    -    34 (Min/Max 15/38)
196 Reallocated_Event_Count -O--CK   100   100   000    -    4
197 Current_Pending_Sector  -O--CK   100   100   000    -    201
198 Offline_Uncorrectable   ----CK   100   100   000    -    202
199 UDMA_CRC_Error_Count    -O--CK   200   200   000    -    0
220 Disk_Shift              -O----   100   100   000    -    286392328
222 Loaded_Hours            -O--CK   096   096   000    -    1638
223 Load_Retry_Count        -O--CK   100   100   000    -    0
224 Load_Friction           -O---K   100   100   000    -    0
226 Load-in_Time            -OS--K   100   100   000    -    594
240 Head_Flying_Hours       P-----   100   100   001    -    0
                            ||||||_ 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     51  Comprehensive SMART error log
0x03       GPL     R/O      5  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
0x08       GPL     R/O      2  Power Conditions log
0x09           SL  R/W      1  Selective self-test log
0x0c       GPL     R/O    513  Pending Defects log
0x10       GPL     R/O      1  NCQ Command Error log
0x11       GPL     R/O      1  SATA Phy Event Counters log
0x24       GPL     R/O  53248  Current Device Internal Status Data log
0x25       GPL     R/O  53248  Saved Device Internal Status Data log
0x30       GPL,SL  R/O      9  IDENTIFY DEVICE data log
0x80-0x9f  GPL,SL  R/W     16  Host 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 (5 sectors)
Device Error Count: 117 (device log contains only the most recent 20 errors)
        CR     = Command Register
        FEATR  = Features Register
        COUNT  = Count (was: Sector Count) Register
        LBA_48 = Upper bytes of LBA High/Mid/Low Registers ]  ATA-8
        LH     = LBA High (was: Cylinder High) Register    ]   LBA
        LM     = LBA Mid (was: Cylinder Low) Register      ] Register
        LL     = LBA Low (was: Sector Number) Register     ]
        DV     = Device (was: Device/Head) Register
        DC     = Device Control Register
        ER     = Error register
        ST     = Status register
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 117 [16] occurred at disk power-on lifetime: 1736 hours (72 days + 8 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 43 00 b0 00 01 44 cc 59 60 40 00  Error: UNC at LBA = 0x144cc5960 = 5449210208

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  60 01 00 00 b0 00 01 44 cc 58 a8 40 00     18:08:59.525  READ FPDMA QUEUED
  60 01 00 00 b8 00 01 44 cc 57 a8 40 00     18:08:59.524  READ FPDMA QUEUED
  60 01 00 00 f8 00 01 44 cc 56 a8 40 00     18:08:59.508  READ FPDMA QUEUED
  61 00 10 00 b0 00 07 46 bf fc 90 40 00     18:08:59.487  WRITE FPDMA QUEUED
  60 08 00 00 a8 00 01 44 cc a6 a8 40 00     18:08:59.487  READ FPDMA QUEUED

Error 116 [15] occurred at disk power-on lifetime: 1736 hours (72 days + 8 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 43 00 b8 00 01 44 cc 59 60 40 00  Error: UNC at LBA = 0x144cc5960 = 5449210208

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  60 08 00 00 28 00 01 44 cc 66 a8 40 00     18:08:56.099  READ FPDMA QUEUED
  60 08 00 00 20 00 01 44 cc 5e a8 40 00     18:08:56.095  READ FPDMA QUEUED
  60 08 00 00 b8 00 01 44 cc 56 a8 40 00     18:08:56.091  READ FPDMA QUEUED
  60 08 00 00 f0 00 01 44 cc 4e a8 40 00     18:08:56.087  READ FPDMA QUEUED
  60 08 00 00 b0 00 01 44 cc 46 a8 40 00     18:08:56.083  READ FPDMA QUEUED

Error 115 [14] occurred at disk power-on lifetime: 203 hours (8 days + 11 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 00 00 00 01 b4 48 d7 40 00  Error: UNC at LBA = 0x01b448d7 = 28592343

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  42 00 00 10 00 00 00 01 b4 48 d7 40 00  8d+11:58:05.512  READ VERIFY SECTOR(S) EXT
  42 00 00 00 01 00 07 46 bf b3 77 40 00  8d+11:58:05.484  READ VERIFY SECTOR(S) EXT
  35 00 00 00 01 00 07 46 bf b3 77 40 00  8d+11:58:05.483  WRITE DMA EXT
  42 00 00 00 17 00 07 46 bf b3 b9 40 00  8d+11:58:05.461  READ VERIFY SECTOR(S) EXT
  35 00 00 00 17 00 07 46 bf b3 b9 40 00  8d+11:58:05.461  WRITE DMA EXT

Error 114 [13] occurred at disk power-on lifetime: 203 hours (8 days + 11 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 00 00 00 01 b4 48 d6 40 00  Error: UNC at LBA = 0x01b448d6 = 28592342

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  42 00 00 10 00 00 00 01 b4 48 d6 40 00  8d+11:58:04.487  READ VERIFY SECTOR(S) EXT
  42 00 00 00 01 00 07 46 bf b3 77 40 00  8d+11:58:04.459  READ VERIFY SECTOR(S) EXT
  35 00 00 00 01 00 07 46 bf b3 77 40 00  8d+11:58:04.458  WRITE DMA EXT
  42 00 00 00 17 00 07 46 bf b3 b9 40 00  8d+11:58:04.436  READ VERIFY SECTOR(S) EXT
  35 00 00 00 17 00 07 46 bf b3 b9 40 00  8d+11:58:04.436  WRITE DMA EXT

Error 113 [12] occurred at disk power-on lifetime: 203 hours (8 days + 11 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 00 00 00 01 b4 48 d5 40 00  Error: UNC at LBA = 0x01b448d5 = 28592341

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  42 00 00 10 00 00 00 01 b4 48 d5 40 00  8d+11:58:03.462  READ VERIFY SECTOR(S) EXT
  42 00 00 00 01 00 07 46 bf b3 77 40 00  8d+11:58:03.434  READ VERIFY SECTOR(S) EXT
  35 00 00 00 01 00 07 46 bf b3 77 40 00  8d+11:58:03.433  WRITE DMA EXT
  42 00 00 00 17 00 07 46 bf b3 b9 40 00  8d+11:58:03.412  READ VERIFY SECTOR(S) EXT
  35 00 00 00 17 00 07 46 bf b3 b9 40 00  8d+11:58:03.412  WRITE DMA EXT

Error 112 [11] occurred at disk power-on lifetime: 203 hours (8 days + 11 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 00 00 00 01 b4 48 d4 40 00  Error: UNC at LBA = 0x01b448d4 = 28592340

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  42 00 00 10 00 00 00 01 b4 48 d4 40 00  8d+11:58:02.437  READ VERIFY SECTOR(S) EXT
  42 00 00 00 01 00 07 46 bf b3 77 40 00  8d+11:58:02.409  READ VERIFY SECTOR(S) EXT
  35 00 00 00 01 00 07 46 bf b3 77 40 00  8d+11:58:02.408  WRITE DMA EXT
  42 00 00 00 17 00 07 46 bf b3 b9 40 00  8d+11:58:02.386  READ VERIFY SECTOR(S) EXT
  35 00 00 00 17 00 07 46 bf b3 b9 40 00  8d+11:58:02.386  WRITE DMA EXT

Error 111 [10] occurred at disk power-on lifetime: 203 hours (8 days + 11 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 00 00 00 01 b4 48 d3 40 00  Error: UNC at LBA = 0x01b448d3 = 28592339

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  42 00 00 10 00 00 00 01 b4 48 d3 40 00  8d+11:58:01.295  READ VERIFY SECTOR(S) EXT
  42 00 00 00 01 00 07 46 bf b3 77 40 00  8d+11:58:01.267  READ VERIFY SECTOR(S) EXT
  35 00 00 00 01 00 07 46 bf b3 77 40 00  8d+11:58:01.267  WRITE DMA EXT
  42 00 00 00 17 00 07 46 bf b3 b9 40 00  8d+11:58:01.242  READ VERIFY SECTOR(S) EXT
  35 00 00 00 17 00 07 46 bf b3 b9 40 00  8d+11:58:01.242  WRITE DMA EXT

Error 110 [9] occurred at disk power-on lifetime: 203 hours (8 days + 11 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 00 00 00 01 b4 48 d2 40 00  Error: UNC at LBA = 0x01b448d2 = 28592338

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  42 00 00 10 00 00 00 01 b4 48 d2 40 00  8d+11:58:00.187  READ VERIFY SECTOR(S) EXT
  42 00 00 00 01 00 07 46 bf b3 77 40 00  8d+11:58:00.159  READ VERIFY SECTOR(S) EXT
  35 00 00 00 01 00 07 46 bf b3 77 40 00  8d+11:58:00.159  WRITE DMA EXT
  42 00 00 00 17 00 07 46 bf b3 b9 40 00  8d+11:58:00.136  READ VERIFY SECTOR(S) EXT
  35 00 00 00 17 00 07 46 bf b3 b9 40 00  8d+11:58:00.136  WRITE DMA EXT

SMART Extended Self-test Log Version: 1 (1 sectors)
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline       Completed: read failure       70%      1752         28660728
# 2  Extended offline    Completed: read failure       10%      1751         28611177

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):       1 (0x0001)
Device State:                        SMART Off-line Data Collection executing in background (4)
Current Temperature:                    34 Celsius
Power Cycle Min/Max Temperature:     33/38 Celsius
Lifetime    Min/Max Temperature:     15/38 Celsius
Specified Max Operating Temperature:    55 Celsius
Under/Over Temperature Limit Count:   0/0
Vendor specific:
00 00 02 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:      5/55 Celsius
Min/Max Temperature Limit:           -40/70 Celsius
Temperature History Size (Index):    478 (277)

Index    Estimated Time   Temperature Celsius
 278    2023-10-16 14:03    34  ***************
 ...    ..(476 skipped).    ..  ***************
 277    2023-10-16 22:00    34  ***************

SCT Error Recovery Control:
           Read: Disabled
          Write: Disabled

Device Statistics (GP Log 0x04)
Page  Offset Size        Value Flags Description
0x01  =====  =               =  ===  == General Statistics (rev 3) ==
0x01  0x008  4              14  ---  Lifetime Power-On Resets
0x01  0x010  4            1772  ---  Power-on Hours
0x01  0x018  6     31949266826  ---  Logical Sectors Written
0x01  0x020  6        64544047  ---  Number of Write Commands
0x01  0x028  6      2549519605  ---  Logical Sectors Read
0x01  0x030  6         3178963  ---  Number of Read Commands
0x01  0x038  6      6379200000  ---  Date and Time TimeStamp
0x02  =====  =               =  ===  == Free-Fall Statistics (rev 1) ==
0x02  0x010  4               1  ---  Overlimit Shock Events
0x03  =====  =               =  ===  == Rotating Media Statistics (rev 1) ==
0x03  0x008  4             564  ---  Spindle Motor Power-on Hours
0x03  0x010  4             445  ---  Head Flying Hours
0x03  0x018  4             184  ---  Head Load Events
0x03  0x020  4              32  ---  Number of Reallocated Logical Sectors
0x03  0x028  4            1801  ---  Read Recovery Attempts
0x03  0x030  4               0  ---  Number of Mechanical Start Failures
0x03  0x038  4            1608  ---  Number of Realloc. Candidate Logical Sectors
0x03  0x040  4              12  ---  Number of High Priority Unload Events
0x04  =====  =               =  ===  == General Errors Statistics (rev 1) ==
0x04  0x008  4             117  ---  Number of Reported Uncorrectable Errors
0x04  0x010  4               5  ---  Resets Between Cmd Acceptance and Completion
0x05  =====  =               =  ===  == Temperature Statistics (rev 1) ==
0x05  0x008  1              34  ---  Current Temperature
0x05  0x010  1              33  N--  Average Short Term Temperature
0x05  0x018  1              24  N--  Average Long Term Temperature
0x05  0x020  1              38  ---  Highest Temperature
0x05  0x028  1              15  ---  Lowest Temperature
0x05  0x030  1              36  N--  Highest Average Short Term Temperature
0x05  0x038  1              22  N--  Lowest Average Short Term Temperature
0x05  0x040  1              24  N--  Highest Average Long Term Temperature
0x05  0x048  1              24  N--  Lowest Average Long Term Temperature
0x05  0x050  4               0  ---  Time in Over-Temperature
0x05  0x058  1              55  ---  Specified Maximum Operating Temperature
0x05  0x060  4               0  ---  Time in Under-Temperature
0x05  0x068  1               5  ---  Specified Minimum Operating Temperature
0x06  =====  =               =  ===  == Transport Statistics (rev 1) ==
0x06  0x008  4              16  ---  Number of Hardware Resets
0x06  0x010  4               9  ---  Number of ASR Events
0x06  0x018  4               0  ---  Number of Interface CRC Errors
0x07  =====  =               =  ===  == Solid State Device Statistics (rev 1) ==
                                |||_ C monitored condition met
                                ||__ D supports DSN
                                |___ N normalized value

Pending Defects log (GP Log 0x0c)
Index                LBA    Hours
    0           28611264      535
    1           28611265      535
    2           28611266      535
    3           28611267      535
    4           28611268      535
    5           28611269      535
    6           28611270      535
    7           28611271      535
    8           28611296      535
    9           28611297      535
   10           28611298      535
   11           28611299      535
   12           28611300      535
   13           28611301      535
   14           28611302      535
   15           28611303      535
   16           28611384      535
   17           28611385      535
   18           28611386      535
   19           28611387      535
   20           28611388      535
   21           28611389      535
   22           28611390      535
   23           28611391      535
   24           28613416      535
   25           28613417      535
   26           28613418      535
   27           28613419      535
   28           28613420      535
   29           28613421      535
   30           28613422      535
... (1577 entries not shown)

SATA Phy Event Counters (GP Log 0x11)
ID      Size     Value  Description
0x0001  4            0  Command failed due to ICRC error
0x0002  4            0  R_ERR response for data FIS
0x0003  4            0  R_ERR response for device-to-host data FIS
0x0004  4            0  R_ERR response for host-to-device data FIS
0x0005  4            0  R_ERR response for non-data FIS
0x0006  4            0  R_ERR response for device-to-host non-data FIS
0x0007  4            0  R_ERR response for host-to-device non-data FIS
0x0008  4            0  Device-to-host non-data FIS retries
0x0009  4            3  Transition from drive PhyRdy to drive PhyNRdy
0x000a  4            3  Device-to-host register FISes sent due to a COMRESET
0x000b  4            0  CRC errors within host-to-device FIS
0x000d  4            0  Non-CRC errors within host-to-device FIS
0x000f  4            0  R_ERR response for host-to-device data FIS, CRC
0x0010  4            0  R_ERR response for host-to-device data FIS, non-CRC
0x0012  4            0  R_ERR response for host-to-device non-data FIS, CRC
0x0013  4            0  R_ERR response for host-to-device non-data FIS, non-CRC

sfatula · Oct 16, 2023

201 pending sectors is bad! And 202 offline uncorrectable. While cables and such can cause zfs errors, they should not cause those 2 errors. I would not use that drive.

It might fall under warranty, I don't know Toshibas policy. Might be only the original owner can get it replaced for example. I'd definitely return it to whomever sold it to you.

A good place for quality recertified enterprise drives is serverpartsdeal. And they would replace it.

danb35 · Oct 16, 2023

In addition to over 200 bad sectors, that disk has also failed every SMART self-test it's had. You got a bad disk. You're supposed to test them before adding them to a pool.

sfatula · Oct 16, 2023

Yeah, saw that too. In this case, could probably have even looked at smart data before running a test, I don't care if a test passes or not, that's too many! Definitely always do tests and review smart data before putting one into production.

I would even consider using this drive. I am not quite as paranoid as some who replace with 1 bad sector, I can take a few without worrying about it, but 200, no way.

joeschmuck · Oct 16, 2023

m_aar_ten said:
I recently bought a pretty new drive (under 2000 hours) from a data center near me.

There was a reason they were getting rid of it. I would demand my money back, they sold you a failing drive and it is abundantly clear, they knew what they were doing, screwing you over. Under 2000 hours and all those failures, they knew. Hopefully it is under warranty.

m_aar_ten · Oct 16, 2023

Thanks for the replies.

I am not sure he knew, he asked me for the smart results when he sold it to me because he had more of them laying around.
I am in contact with him and will be trying to go through warranty first, and ask for a new replacement if that doesn't work out.

danb35 said:
In addition to over 200 bad sectors, that disk has also failed every SMART self-test it's had. You got a bad disk. You're supposed to test them before adding them to a pool.

Where could I see this? So I know what to look for in the future.

danb35 · Oct 17, 2023

m_aar_ten said:
Where could I see this?

It's in the SMART output you posted:

Code:

SMART Extended Self-test Log Version: 1 (1 sectors)
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline       Completed: read failure       70%      1752         28660728
# 2  Extended offline    Completed: read failure       10%      1751         28611177

m_aar_ten · Oct 17, 2023

danb35 said:

Interesting, those are the 2 tests I ran since receiving the drive.

Would running BadBlocks be a possible solution to see if things change? Or is it recommended to just RMA it since it is this new and already showing signs like this?

I also mailed TOSHIBA to ask if this is valid for RMA.

danb35 · Oct 17, 2023

m_aar_ten said:
Would running BadBlocks be a possible solution to see if things change?

I'd be interested to see the results from badblocks, but I wouldn't expect things to improve.

Ericloewe · Oct 17, 2023

Yeah, if a drive can't even finish a short test, it is irredeemably inoperative for all intents and purposes (unless you specifically need a failing drive to test things with).

Etorix · Oct 17, 2023

m_aar_ten said:
Would running BadBlocks be a possible solution to see if things change? Or is it recommended to just RMA it since it is this new and already showing signs like this?

Badblocks will NEVER correct bad hardware. And uncorrectable sectors are a definitive cause for RMA.
Have Toshiba replace the drive (possibly shipping the replacement in advance) or send it back to the seller, get your refund and let them deal with RMA.

sfatula · Oct 17, 2023

The bad sectors are found here:


SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAGS    VALUE WORST THRESH FAIL RAW_VALUE
197 Current_Pending_Sector  -O--CK   100   100   000    -    201
198 Offline_Uncorrectable   ----CK   100   100   000    -    202

The attribute name tells you the type, and the raw value tells you the number of them. This needs to be returned, it's a bad drive.

joeschmuck · Oct 17, 2023

Bad Blocks "may" force the drive to map out the current bad media surface locations (sectors) however the fact that this drive has this many failures at such a young age is troublesome. Bad Blocks on a 12TB drive will take several days (almost a week?) if my memory serves me correctly to complete all four test patterns.

Honestly, you should either RMA the drive or have the place which sold it to you replace it.

To point out a few little things:

m_aar_ten said:
220 Disk_Shift -O---- 100 100 000 - 286392328

This value (which I don't see often) indicates the platters have moved from the center of the spindle. But I have no idea what the number magnitude means. The fact that the Thresh value is 000, and your Worst and Value = 100, tells me it didn't move enough to count it as a real problem. To me this is conflicting information. And this isn't a Seagate drive where you might need to subtract FFFFFFFF from the value to get the real value.

m_aar_ten said:
191 G-Sense_Error_Rate -O--CK 100 100 000 - 1

And this error says someone probably dropped it. Although what I've read says this on it's own is not always credible because some drive sensors are very sensitive and some are not. I don't believe there is a standard shock force for this value.

But in your case, with the Disk Shift and G-Sense indicating errors, I'd say someone dropped it. That is what I'd think at least until someone schools me on these values.

Replace the drive by any means, it will only give you trouble.

m_aar_ten · Oct 17, 2023

joeschmuck said:
Bad Blocks "may" force the drive to map out the current bad media surface locations (sectors) however the fact that this drive has this many failures at such a young age is troublesome. Bad Blocks on a 12TB drive will take several days (almost a week?) if my memory serves me correctly to complete all four test patterns.

Honestly, you should either RMA the drive or have the place which sold it to you replace it.

To point out a few little things:

This value (which I don't see often) indicates the platters have moved from the center of the spindle. But I have no idea what the number magnitude means. The fact that the Thresh value is 000, and your Worst and Value = 100, tells me it didn't move enough to count it as a real problem. To me this is conflicting information. And this isn't a Seagate drive where you might need to subtract FFFFFFFF from the value to get the real value.

And this error says someone probably dropped it. Although what I've read says this on it's own is not always credible because some drive sensors are very sensitive and some are not. I don't believe there is a standard shock force for this value.

But in your case, with the Disk Shift and G-Sense indicating errors, I'd say someone dropped it. That is what I'd think at least until someone schools me on these values.

Replace the drive by any means, it will only give you trouble.

That is very strange indeed!
I already contacted the seller, and he said he would replace the drive if the RMA process doesn't work out.
I will test drives before using them in the future, thanks again for the explanation!

Important Announcement for the TrueNAS Community.

Smart Readout Question/Unrecoverable error

m_aar_ten

Cadet

sfatula

Guru

danb35

Hall of Famer

sfatula

Guru

joeschmuck

Old Man

m_aar_ten

Cadet

danb35

Hall of Famer

m_aar_ten

Cadet

danb35

Hall of Famer

Ericloewe

Server Wrangler

Etorix

Wizard

sfatula

Guru

joeschmuck

Old Man

m_aar_ten

Cadet

Similar threads

Important Announcement for the TrueNAS Community.

Smart Readout Question/Unrecoverable error

Cadet

Guru

Hall of Famer

Guru

Old Man

Cadet

Hall of Famer

Cadet

Hall of Famer

Server Wrangler

Wizard

Guru

Old Man

Cadet

Important Announcement for the TrueNAS Community.

Related topics on forums.truenas.com for thread: "Smart Readout Question/Unrecoverable error"

Similar threads