Hard drives dead on arrival?

tunnel

Cadet
Joined
Apr 15, 2022
Messages
2
Hello - complete newbie here looking for some help confirming my suspicions that I have a dead-on-arrival drive. I've followed this guide so far https://www.truenas.com/community/r...bleshooting-guide-all-versions-of-freenas.17/. I've just converted a desktop to Truenas.

Specs:
CPU: Intel 4790k
MB: asus z97-a
RAM: 32GB DDR3
Boot drive: PNY CS900 Series 2.5" SATA III 6Gb/s - 120GB SSD
HBA: LSI 9240-8i = (9211-8I) IT Mode (new from Ebay for this build)
Pool0: 3x Seagate Exos 7E8 6TB in raid-z1 (new from Amazon for this build)

Shortly after importing new data, I started getting Critical Errors for unreadable and uncorrectable sectors, and the pool is showing as DEGRADED.

I'm running a long SMART test now, however, the short test returns the following results. MSART ID5, 197 and 198 appear "to have failed for RMA purposes" according to the help guide. I'm also confused that the errors have occurred at 'Power-on-lifetime' of 1316hrs. These drives are new and should only have been run for <24hrs in my possession. Is it normal for new drives to have these times, or does this indicate I might have been ripped off with previously RMA'd drives?

Code:
If Selective self-test is pending on power-up, resume after 0 minute delay.

root@truenas[~]# smartctl -a /dev/da1
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 ===
Device Model:     ST6000NM021A-2R7101
Serial Number:    WNB0P40H
LU WWN Device Id: 5 000c50 0cfea6b29
Firmware Version: SN02
User Capacity:    6,001,175,126,016 bytes [6.00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    7200 rpm
Form Factor:      3.5 inches
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   ACS-4 (minor revision not indicated)
SATA Version is:  SATA 3.3, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Fri Apr 15 11:11:41 2022 BST
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:      ( 249) Self-test routine in progress...
                                        90% of test remaining.
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:        ( 567) minutes.
Conveyance self-test routine
recommended polling time:        (   2) minutes.
SCT capabilities:              (0x70bd) 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   068   064   044    Pre-fail  Always       -       181618816
  3 Spin_Up_Time            0x0003   092   092   000    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   099   099   020    Old_age   Always       -       1663
  5 Reallocated_Sector_Ct   0x0033   099   099   010    Pre-fail  Always       -       4720
  7 Seek_Error_Rate         0x000f   083   060   045    Pre-fail  Always       -       219388262
  9 Power_On_Hours          0x0032   099   099   000    Old_age   Always       -       1324
 10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   099   099   020    Old_age   Always       -       1636
 18 Unknown_Attribute       0x000b   100   100   050    Pre-fail  Always       -       0
187 Reported_Uncorrect      0x0032   057   057   000    Old_age   Always       -       43
188 Command_Timeout         0x0032   096   096   000    Old_age   Always       -       4295032836
190 Airflow_Temperature_Cel 0x0022   046   042   040    Old_age   Always       -       54 (Min/Max 25/58)
192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -       1484
193 Load_Cycle_Count        0x0032   099   099   000    Old_age   Always       -       3170
194 Temperature_Celsius     0x0022   054   058   000    Old_age   Always       -       54 (0 21 0 0 0)
195 Hardware_ECC_Recovered  0x001a   027   001   000    Old_age   Always       -       181618816
197 Current_Pending_Sector  0x0012   068   068   000    Old_age   Always       -       15992
198 Offline_Uncorrectable   0x0010   068   068   000    Old_age   Offline      -       15992
199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       0
240 Head_Flying_Hours       0x0000   100   253   000    Old_age   Offline      -       560 (236 72 0)
241 Total_LBAs_Written      0x0000   100   253   000    Old_age   Offline      -       101179533255
242 Total_LBAs_Read         0x0000   100   253   000    Old_age   Offline      -       97273455469

SMART Error Log Version: 1
ATA Error Count: 43 (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 43 occurred at disk power-on lifetime: 1316 hours (54 days + 20 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 78 d2 ea 02  Error: WP at LBA = 0x02ead278 = 48943736

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  61 00 08 ff ff ff 4f 00      06:15:20.762  WRITE FPDMA QUEUED
  60 00 08 ff ff ff 4f 00      06:15:19.750  READ FPDMA QUEUED
  61 00 10 90 02 40 40 00      06:15:19.668  WRITE FPDMA QUEUED
  60 00 10 ff ff ff 4f 00      06:15:19.542  READ FPDMA QUEUED
  60 00 10 ff ff ff 4f 00      06:15:19.542  READ FPDMA QUEUED

Error 42 occurred at disk power-on lifetime: 1316 hours (54 days + 20 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 68 d2 ea 02  Error: UNC at LBA = 0x02ead268 = 48943720

  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 08 ff ff ff 4f 00      06:15:18.892  READ FPDMA QUEUED
  60 00 08 ff ff ff 4f 00      06:15:17.421  READ FPDMA QUEUED
  60 00 08 78 d2 ea 42 00      06:15:17.377  READ FPDMA QUEUED
  60 00 08 68 d2 ea 42 00      06:15:17.377  READ FPDMA QUEUED
  60 00 08 e0 7e 95 43 00      06:15:17.363  READ FPDMA QUEUED

Error 41 occurred at disk power-on lifetime: 1316 hours (54 days + 20 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 78 cd ea 02  Error: WP at LBA = 0x02eacd78 = 48942456

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  61 00 08 50 83 48 44 00      06:13:17.518  WRITE FPDMA QUEUED
  60 00 08 78 cd ea 42 00      06:13:17.224  READ FPDMA QUEUED
  60 00 08 ff ff ff 4f 00      06:13:17.209  READ FPDMA QUEUED
  60 00 08 ff ff ff 4f 00      06:13:17.188  READ FPDMA QUEUED
  60 00 08 ff ff ff 4f 00      06:13:17.188  READ FPDMA QUEUED

Error 40 occurred at disk power-on lifetime: 1316 hours (54 days + 20 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 48 d2 ea 02  Error: UNC at LBA = 0x02ead248 = 48943688

  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 08 ff ff ff 4f 00      06:12:27.197  READ FPDMA QUEUED
  60 00 08 ff ff ff 4f 00      06:12:27.197  READ FPDMA QUEUED
  61 00 00 ff ff ff 4f 00      06:12:26.207  WRITE FPDMA QUEUED
  61 00 00 ff ff ff 4f 00      06:12:26.207  WRITE FPDMA QUEUED
  61 00 00 ff ff ff 4f 00      06:12:26.207  WRITE FPDMA QUEUED

Error 39 occurred at disk power-on lifetime: 1316 hours (54 days + 20 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 98 cd ea 02  Error: WP at LBA = 0x02eacd98 = 48942488

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  61 00 00 ff ff ff 4f 00      06:12:23.710  WRITE FPDMA QUEUED
  61 00 00 ff ff ff 4f 00      06:12:23.710  WRITE FPDMA QUEUED
  61 00 00 ff ff ff 4f 00      06:12:23.710  WRITE FPDMA QUEUED
  61 00 00 ff ff ff 4f 00      06:12:23.710  WRITE FPDMA QUEUED
  61 00 00 ff ff ff 4f 00      06:12:23.710  WRITE FPDMA QUEUED

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Extended offline    Self-test routine in progress 90%      1324         -
# 2  Short offline       Completed without error       00%      1323         -
# 3  Short offline       Completed without error       00%      1322         -
# 4  Short offline       Completed without error       00%      1321         -
# 5  Short offline       Completed without error       00%      1321         -
# 6  Short offline       Completed without error       00%      1319         -
# 7  Short offline       Completed without error       00%      1318         -
# 8  Short offline       Completed without error       00%      1317         -
# 9  Short offline       Completed: read failure       60%      1316         -
#10  Short offline       Completed without error       00%      1315         -
#11  Short offline       Completed without error       00%      1314         -
#12  Short offline       Completed without error       00%      1313         -
#13  Short offline       Completed without error       00%      1312         -
#14  Short offline       Completed without error       00%      1312         -
#15  Extended offline    Completed: read failure       90%      1312         5548648
#16  Short offline       Completed without error       00%      1309         -

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


Code:
zsh: command not found: age
root@truenas[~]#
root@truenas[~]# zpool status -v
  pool: Pool0
 state: DEGRADED
status: One or more devices are faulted in response to persistent errors.
        Sufficient replicas exist for the pool to continue functioning in a
        degraded state.
action: Replace the faulted device, or use 'zpool clear' to mark the device
        repaired.
config:

        NAME                                            STATE     READ WRITE CKSUM
        Pool0                                           DEGRADED     0     0 0
          raidz1-0                                      DEGRADED     0     0 0
            gptid/949d4883-bc29-11ec-a704-ac9e17853029  FAULTED     46     4 0  too many errors
            gptid/94bdef63-bc29-11ec-a704-ac9e17853029  ONLINE       0     0 0
            gptid/94b5eb6e-bc29-11ec-a704-ac9e17853029  ONLINE       0     0 0

errors: No known data errors

  pool: boot-pool
 state: ONLINE
config:
 

NugentS

MVP
Joined
Apr 16, 2020
Messages
2,947
Those power on hours would be a bit of a giveaway.
Return the drive for a refund and then buy one elsewhere
 

jgreco

Resident Grinch
Joined
May 29, 2011
Messages
18,680
I've just converted a desktop to Truenas.
Shortly after importing new data, I started getting Critical Errors for unreadable and uncorrectable sectors, and the pool is showing as DEGRADED.

The burn-in process for a new system really isn't optional, it's where these sorts of issues get shaken out before you start loading data on your NAS.


It is much harder to remediate issues once a system is in use...
 

Jailer

Not strong, but bad
Joined
Sep 12, 2014
Messages
4,977
That is not a new drive. I'd be checking all of the drives and if they show similar power on hours I'd be insisting on a refund and re purchase the drives from a different seller.
 
Last edited:

tunnel

Cadet
Joined
Apr 15, 2022
Messages
2
The burn-in process for a new system really isn't optional, it's where these sorts of issues get shaken out before you start loading data on your NAS.


It is much harder to remediate issues once a system is in use...

Thanks for the guide! my data is still backed up in triplicate elsewhere - but good to have a proper procedure when I get better drives.

I didn't realise I could get stuck with grey market drives on Amazon, but at least I have my facts straight before getting into a shit slinging fight with London-Singapore Computer Corporation!
 

NugentS

MVP
Joined
Apr 16, 2020
Messages
2,947
Its worth, when you buy a drive from Amazon going to the manufacturers web page and typing the serial number into the warranty section, just to check that you are getting a warranty from them as a last resort.

To be fair, its the same buying a new drive from anywhere - always check with the manufacturer. I still have an email from Scan.co.uk agreeing to cover the 3 year (or was it 5) warranty on some Samsung HDD's I bought years ago and after checking discovered they were grey with no warranty from Samsung (and only a year by default from Scan). Must have been 10 years ago (ish). None of the drives went wrong and the ones I haven't discarded (ie can still find) still work and are in use as test drives
 
Last edited:
Top