Question Is my laptop hard drive failing / failed?

TOMHWHP

Honorable
Jan 21, 2015
5
0
10,510
0
Hi!

I just wondered if anyone could advise me? I had a problem with a file, which I managed to delete, but this made me run a chkdsk. It is a laptop with an internal SSD for Windows and internal HDD for data - and it is the data drive which I am concerned about.

Here is the chkdsk report.




I was searching online, and saw someone say I should also do a GSmartControl report to see what the drive says about itself. This came up with various errors, but I'm not sure how to read the test results. It said 'ATA Error Count: 1334' in the error log, has several lines that say 'pre-failure' and the rest 'old age' in the attributes tab and does have a 'read failure' under self-test logs. However overall it says the drive has passed. Therefore I'm not sure how serious or not these issues are.

I do have backups of my data, but I normally only keep the last couple of full-drive backups, and I'm concerned that if data starts getting corrupted that I'll be backing up corrupt files.

Code:
smartctl 5.43 2012-06-30 r3573 [i686-w64-mingw32-win8(64)] (sf-5.43-1)
Copyright (C) 2002-12 by Bruce Allen, [url=http://smartmontools.sourceforge.net]http://smartmontools.sourceforge.net[/url]

=== START OF INFORMATION SECTION ===
Device Model:     HGST HTS721010A9E630
Serial Number:    JR1000D33AB68E
LU WWN Device Id: 5 000cca 8c8eefc46
Firmware Version: JB0OA3T0
User Capacity:    1,000,204,886,016 bytes [1.00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   8
ATA Standard is:  ATA-8-ACS revision 6
Local Time is:    Thu Sep 10 21:28:33 2020 GMTST
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:  (0x00)    Offline data collection activity
                    was never started.
                    Auto Offline Data Collection: Disabled.
Self-test execution status:      ( 121)    The previous self-test completed having
                    the read element of the test failed.
Total time to complete Offline
data collection:         (   45) seconds.
Offline data collection
capabilities:              (0x51) SMART execute Offline immediate.
                    No Auto Offline data collection support.
                    Suspend Offline collection upon new
                    command.
                    No 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:      ( 173) 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     0x002f   100   086   062    Pre-fail  Always       -       65536
  2 Throughput_Performance  0x0025   100   100   040    Pre-fail  Offline      -       0
  3 Spin_Up_Time            0x0023   253   100   033    Pre-fail  Always       -       1
  4 Start_Stop_Count        0x0032   095   095   000    Old_age   Always       -       9108
  5 Reallocated_Sector_Ct   0x0033   100   100   005    Pre-fail  Always       -       8 (0 1)
  7 Seek_Error_Rate         0x002f   100   100   067    Pre-fail  Always       -       0
  8 Seek_Time_Performance   0x0025   100   100   040    Pre-fail  Offline      -       0
  9 Power_On_Hours          0x0032   080   080   000    Old_age   Always       -       9176
 10 Spin_Retry_Count        0x0033   100   100   060    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   099   099   000    Old_age   Always       -       2862
183 Runtime_Bad_Block       0x0032   100   100   000    Old_age   Always       -       0
184 End-to-End_Error        0x0033   100   100   097    Pre-fail  Always       -       0
187 Reported_Uncorrect      0x0032   100   001   000    Old_age   Always       -       138113263535414
188 Command_Timeout         0x0032   100   100   000    Old_age   Always       -       0
190 Airflow_Temperature_Cel 0x0022   059   049   045    Old_age   Always       -       41 (Min/Max 31/41)
191 G-Sense_Error_Rate      0x0032   095   095   000    Old_age   Always       -       1337
192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -       1441814
193 Load_Cycle_Count        0x0032   039   039   000    Old_age   Always       -       619477
196 Reallocated_Event_Count 0x0032   100   100   000    Old_age   Always       -       1
197 Current_Pending_Sector  0x0032   100   100   000    Old_age   Always       -       40
198 Offline_Uncorrectable   0x0030   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x0036   100   100   000    Old_age   Always       -       0
223 Load_Retry_Count        0x002a   100   100   000    Old_age   Always       -       0

SMART Error Log Version: 1
ATA Error Count: 1334 (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 1334 occurred at disk power-on lifetime: 9162 hours (381 days + 18 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 04 b4 6c dd 04  Error: UNC at LBA = 0x04dd6cb4 = 81620148

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  42 00 04 b4 6c dd 40 00      05:16:12.472  READ VERIFY SECTOR(S) EXT
  b0 d0 00 00 4f c2 40 00      05:16:12.471  SMART READ DATA
  42 00 04 b0 6c dd 40 00      05:16:09.588  READ VERIFY SECTOR(S) EXT
  b0 da 00 00 4f c2 40 00      05:16:09.587  SMART RETURN STATUS
  42 00 08 d8 6c dd 40 00      05:16:06.730  READ VERIFY SECTOR(S) EXT

Error 1333 occurred at disk power-on lifetime: 9162 hours (381 days + 18 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 04 b0 6c dd 04  Error: UNC at LBA = 0x04dd6cb0 = 81620144

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  42 00 04 b0 6c dd 40 00      05:16:09.588  READ VERIFY SECTOR(S) EXT
  b0 da 00 00 4f c2 40 00      05:16:09.587  SMART RETURN STATUS
  42 00 08 d8 6c dd 40 00      05:16:06.730  READ VERIFY SECTOR(S) EXT
  42 00 08 d0 6c dd 40 00      05:16:06.712  READ VERIFY SECTOR(S) EXT
  42 00 08 c8 6c dd 40 00      05:16:03.839  READ VERIFY SECTOR(S) EXT

Error 1332 occurred at disk power-on lifetime: 9162 hours (381 days + 18 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 08 d8 6c dd 04  Error: UNC at LBA = 0x04dd6cd8 = 81620184

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  42 00 08 d8 6c dd 40 00      05:16:06.730  READ VERIFY SECTOR(S) EXT
  42 00 08 d0 6c dd 40 00      05:16:06.712  READ VERIFY SECTOR(S) EXT
  42 00 08 c8 6c dd 40 00      05:16:03.839  READ VERIFY SECTOR(S) EXT
  b0 d0 00 00 4f c2 40 00      05:16:03.837  SMART READ DATA
  42 00 08 c0 6c dd 40 00      05:16:00.963  READ VERIFY SECTOR(S) EXT

Error 1331 occurred at disk power-on lifetime: 9162 hours (381 days + 18 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 08 c8 6c dd 04  Error: UNC at LBA = 0x04dd6cc8 = 81620168

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  42 00 08 c8 6c dd 40 00      05:16:03.839  READ VERIFY SECTOR(S) EXT
  b0 d0 00 00 4f c2 40 00      05:16:03.837  SMART READ DATA
  42 00 08 c0 6c dd 40 00      05:16:00.963  READ VERIFY SECTOR(S) EXT
  b0 da 00 00 4f c2 40 00      05:16:00.962  SMART RETURN STATUS
  42 00 08 b8 6c dd 40 00      05:15:58.096  READ VERIFY SECTOR(S) EXT

Error 1330 occurred at disk power-on lifetime: 9162 hours (381 days + 18 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 08 c0 6c dd 04  Error: UNC at LBA = 0x04dd6cc0 = 81620160

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  42 00 08 c0 6c dd 40 00      05:16:00.963  READ VERIFY SECTOR(S) EXT
  b0 da 00 00 4f c2 40 00      05:16:00.962  SMART RETURN STATUS
  42 00 08 b8 6c dd 40 00      05:15:58.096  READ VERIFY SECTOR(S) EXT
  42 00 08 b0 6c dd 40 00      05:15:55.231  READ VERIFY SECTOR(S) EXT
  42 00 10 e0 6c dd 40 00      05:15:55.189  READ VERIFY SECTOR(S) EXT

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       90%      9176         81620148
# 2  Short offline       Completed: read failure       90%      9176         81620148
# 3  Short offline       Completed without error       00%      8514         -
# 4  Short offline       Completed without error       00%      8513         -
# 5  Short offline       Completed without error       00%      8507         -
# 6  Short offline       Completed without error       00%      8506         -
# 7  Short offline       Completed without error       00%      8505         -
# 8  Short offline       Completed without error       00%      8504         -
# 9  Short offline       Completed without error       00%      8503         -
#10  Short offline       Completed without error       00%      8502         -
#11  Short offline       Completed without error       00%      8497         -
#12  Short offline       Completed without error       00%      8496         -
#13  Short offline       Completed without error       00%      8495         -
#14  Short offline       Completed without error       00%      8494         -
#15  Short offline       Completed without error       00%      8493         -
#16  Short offline       Completed without error       00%      8492         -
#17  Short offline       Completed without error       00%      8491         -
#18  Short offline       Completed without error       00%      8490         -
#19  Short offline       Aborted by host               10%      8490         -
#20  Short offline       Completed without error       00%      8488         -
#21  Short offline       Completed without error       00%      8483         -

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.

Any advice is greatly appreciated. Thanks for your time.
 

USAFRet

Titan
Moderator
Mar 16, 2013
129,176
5,170
165,040
20,013
"20kb in bad sectors"
Yes, the drive has bad sectors. They don't get better, only worse.

But...you should be ready for full data loss ALL the time. Not just from a potentially dying drive, but also malware, ransomware, nasty virus, etc, etc.

If we out here were to say "Naa...thats no problem", and then the drive dies completely next week, what will you do?
It's YOUR data on the line.
OTOH, if we out here were to say "It's going to die tomorrow", what will you do?

You ALWAYS need a backup of any data you care about. Always.
 

TOMHWHP

Honorable
Jan 21, 2015
5
0
10,510
0
Hi!
Thanks for such a quick reply. I do intend to continue backing up regularly - I have this done automatically a NAS system continuously, and also do it manually to an external hdd regularly. I will always do this.

I'm just trying to understand if these backups could end up containing corrupt data if the drive is failing already. Also, are the number of bad clusters and the faults shown on the Smart report standard - or already quite serious?

thanks
 

USAFRet

Titan
Moderator
Mar 16, 2013
129,176
5,170
165,040
20,013
The OS is not saving data to those spaces, so its not porting corrupted data into and through your backup situation.
(and kudos to you for being proactive on this)

Serious? It could go bad at any moment, or last some more years.
There is decay. WE don't know the rate of decay, even if that was really relevant.
I've had an almost brand new drive (5 weeks out of the box) go from seemingly great to dead in 36 hours.
 

TOMHWHP

Honorable
Jan 21, 2015
5
0
10,510
0
Ok thanks so much. If it's not saving in the bad parts, then that's a good thing. I'll keep backups - and maybe keep an older one too just in case. I might investigate replacing the hdd if that is possible sometime too.
 

ASK THE COMMUNITY

Latest posts