Is my HDD dying?

Status
Not open for further replies.

wille1101

Dabbler
Joined
Oct 20, 2018
Messages
16
I'm pretty sure it is, but why is a brand new disk dying after a month of use?
Code:
=== START OF INFORMATION SECTION ===
Model Family:     Seagate IronWolf
Device Model:     ST4000VN008-2DR166
Serial Number:    ZDH466SW
LU WWN Device Id: 5 000c50 0b1639b23
Firmware Version: SC60
User Capacity:    4,000,787,030,016 bytes [4.00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    5980 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: 3.0 Gb/s)
Local Time is:    Tue Dec  4 16:54:45 2018 CET
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: FAILED!
Drive failure expected in less than 24 hours. SAVE ALL DATA.
See vendor-specific Attribute list for failed Attributes.

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:                (  591) 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:        ( 628) 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   081   044   044    Pre-fail  Always   In_the_past 140027536
  3 Spin_Up_Time            0x0003   093   093   000    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   100   100   020    Old_age   Always       -       21
 5 Reallocated_Sector_Ct   0x0033   001   001   010    Pre-fail  Always   FAILING_NOW 632
  7 Seek_Error_Rate         0x000f   087   060   045    Pre-fail  Always       -       478204775
  9 Power_On_Hours          0x0032   099   099   000    Old_age   Always       -       962 (167 15 0)
10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0
12 Power_Cycle_Count       0x0032   100   100   020    Old_age   Always       -       21
184 End-to-End_Error        0x0032   100   100   099    Old_age   Always       -       0
187 Reported_Uncorrect      0x0032   001   001   000    Old_age   Always       -       3768
188 Command_Timeout         0x0032   100   098   000    Old_age   Always       -       4295032837
189 High_Fly_Writes         0x003a   100   100   000    Old_age   Always       -       0
190 Airflow_Temperature_Cel 0x0022   072   071   040    Old_age   Always       -       28 (Min/Max 23/29)
191 G-Sense_Error_Rate      0x0032   100   100   000    Old_age   Always       -       0
192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -       3
193 Load_Cycle_Count        0x0032   100   100   000    Old_age   Always       -       50
194 Temperature_Celsius     0x0022   028   040   000    Old_age   Always       -       28 (0 19 0 0 0)
197 Current_Pending_Sector  0x0012   001   001   000    Old_age   Always       -       12144
198 Offline_Uncorrectable   0x0010   001   001   000    Old_age   Offline      -       12144
199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       0
240 Head_Flying_Hours       0x0000   100   253   000    Old_age   Offline      -       959 (104 178 0)
241 Total_LBAs_Written      0x0000   100   253   000    Old_age   Offline      -       3959572807
242 Total_LBAs_Read         0x0000   100   253   000    Old_age   Offline      -       1570783817

SMART Error Log Version: 1
ATA Error Count: 3763 (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 3763 occurred at disk power-on lifetime: 902 hours (37 days + 14 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 00 ff ff ff 4f 00  37d+09:51:22.624  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00  37d+09:51:22.624  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00  37d+09:51:22.624  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00  37d+09:51:22.623  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00  37d+09:51:22.623  READ FPDMA QUEUED

Error 3762 occurred at disk power-on lifetime: 902 hours (37 days + 14 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 00 ff ff ff 4f 00  37d+09:51:19.411  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00  37d+09:51:19.411  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00  37d+09:51:19.411  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00  37d+09:51:19.411  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00  37d+09:51:19.411  READ FPDMA QUEUED

Error 3761 occurred at disk power-on lifetime: 902 hours (37 days + 14 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 00 ff ff ff 4f 00  37d+09:51:16.091  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00  37d+09:51:16.091  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00  37d+09:51:16.091  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00  37d+09:51:16.091  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00  37d+09:51:16.091  READ FPDMA QUEUED

Error 3760 occurred at disk power-on lifetime: 902 hours (37 days + 14 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 00 ff ff ff 4f 00  37d+09:51:12.768  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00  37d+09:51:12.768  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00  37d+09:51:12.768  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00  37d+09:51:12.768  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00  37d+09:51:12.768  READ FPDMA QUEUED

Error 3759 occurred at disk power-on lifetime: 902 hours (37 days + 14 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 00 ff ff ff 4f 00  37d+09:51:09.371  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00  37d+09:51:09.371  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00  37d+09:51:09.371  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00  37d+09:51:09.371  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00  37d+09:51:09.371  READ FPDMA QUEUED

SMART Self-test log structure revision number 1
No self-tests have been logged.  [To run self-tests, use: smartctl -t]

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.
 
Last edited by a moderator:

danb35

Hall of Famer
Joined
Aug 16, 2011
Messages
15,504
why is a brand new disk dying after a month of use?
Because the occasional disk is defective out of the box. Shouldn't be much of a surprise, really. That's why (as @Johnnie Black notes) we recommend you thoroughly burn in and test your disks before putting them into production.
 

pro lamer

Guru
Joined
Feb 16, 2018
Messages
626
a brand new disk dying after a
Mind the bathtub curve - a disk doesn't need to die on the first day. It can die a little bit later. Or maybe I am wrong and burn in tests should cover all the infant time of a disk? How long does the infant Kerri's like period last for a HDD/SSD? (My quick Google foo failed to answer this)

Sent from my mobile phone
 
Joined
Jan 18, 2017
Messages
525
I don't remember seeing any article state a set time frame, personally I keep the shipping package until 9000 hours if it makes it to 9k I should be good to 40k.
 
Status
Not open for further replies.
Top