Unexpected Smart fail

Don't Lose Your Data Forever!

DIY data recovery has risks. You could lose your data forever! Don't want to risk it? Talk to a professional now.

empatik

New member
Hi.
TLDR: Is it possible for a disk to fail its smart self-health test for software issues. The disk in question is a 4TB Wd external hard drive (my book 25ee). The smart fail started right after i mistakenly tried to rebuild the MBR using Testdisk (i know now that MBR cant handle more than 2tb and i should have gone for GPT).
I know it is kind of a far fetch but i feel like the timing of the error to be at least suspicious.

So now for the long story.
I recently had to reinstall windows on my main computer so i used my external hard drive to store the data meanwhile. Up to this point the external hard drive had been used to a normal level for a external storage device and was clocking in about 3.9k hours online. Once the backup was complete i created a instalation disk for windows but i mistakenly selected the external hard drive instead of the usb key i just connected to the computer.

Yeah, i know, rookie mistake.

Anyways, once i realised the mistake i started looking for solutions. I first tried disk drill, it was working fine and detecting every file with no issue but i found out about the 500mb limit for the free version. So i decided to go for Testdisk, the software detected the ntfs partition but could not rebuild the filesystem. I read somewhere that trying to use Testdisk's mbr rebuild could help you in that case so i went for it. Once the process returned testdisk could not detect the ntfs partition anymore. At that point i realised i was in way over my head with that and choose to go back to diskdrill, save whatever most important data and wipe the rest. That plan would have worked fine from the get go because out of the 3Tb of data i had only a very tiny portion was important. Live and learn.

Once back on disk drill i am getting smart warnings that my drive is failing, read times are abysmall, the whole ordeall. I found out about the MBR vs GPT thing, used windows to convert back to GPT and then tried to format the disk into NTFS. (By that point i gave up saving any data.) The disk would not initialise because of physical failure.

So recap:
4Tb external hard drive used for moderate dudty storage (WD Mybook 24EE, about 3.9k hours use)
One single NTFS partition
- One FAT32 partition of about 40 gig got inserted on the drive
- The FAT32 Partition got unallocated by windows (oops, forgot to mention before)
- Used DiskDrill to detect the files, could not recover because of data limit from the software
- Testdisk detected the NTFS partition but the filesystem was damaged
- Tried the rebuild MBR from testdisk
- Went back to diskdrill, smart errors all over the place and ever since.

Is there a way that what i did to the drive made it declare a false positive to the smart test?
In spoil here is the output of a seft-health test obtained trough GSmartControl.

[spoil]smartctl 7.1 2019-12-30 r5022 [x86_64-linux-5.4.0-65-generic] (local build)
Copyright (C) 2002-19, Bruce Allen, Christian Franke, http://www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family: Western Digital Blue
Device Model: WDC WD40EZRZ-00GXCB0
Serial Number: WD-WCC7K6EV0SCA
LU WWN Device Id: 5 0014ee 263582485
Firmware Version: 80.00A80
User Capacity: 4,000,787,030,016 bytes [4.00 TB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Rotation Rate: 5400 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: Sat Jan 30 13:06:31 2021 EST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
AAM feature is: Unavailable
APM feature is: Unavailable
Rd look-ahead is: Enabled
Write cache is: Enabled
DSN feature is: Unavailable
ATA Security is: Disabled, NOT FROZEN [SEC1]

=== 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: (44520) 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: ( 2) minutes.
Extended self-test routine
recommended polling time: ( 472) minutes.
Conveyance self-test routine
recommended polling time: ( 5) minutes.
SCT capabilities: (0x3035) SCT Status 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 POSR-K 001 001 051 NOW 26995
3 Spin_Up_Time POS--K 186 168 021 - 5666
4 Start_Stop_Count -O--CK 094 094 000 - 6371
5 Reallocated_Sector_Ct PO--CK 194 194 140 - 189
7 Seek_Error_Rate -OSR-K 200 200 000 - 0
9 Power_On_Hours -O--CK 095 095 000 - 3938
10 Spin_Retry_Count -O--CK 100 100 000 - 0
11 Calibration_Retry_Count -O--CK 100 100 000 - 0
12 Power_Cycle_Count -O--CK 094 094 000 - 6306
192 Power-Off_Retract_Count -O--CK 200 200 000 - 15
193 Load_Cycle_Count -O--CK 195 195 000 - 15210
194 Temperature_Celsius -O---K 118 102 000 - 32
196 Reallocated_Event_Count -O--CK 041 041 000 - 159
197 Current_Pending_Sector -O--CK 198 197 000 - 1774
198 Offline_Uncorrectable ----CK 200 200 000 - 0
199 UDMA_CRC_Error_Count -O--CK 200 200 000 - 0
200 Multi_Zone_Error_Rate ---R-- 200 200 000 - 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 5 Comprehensive SMART error log
0x03 GPL R/O 6 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
0x09 SL R/W 1 Selective self-test log
0x10 GPL R/O 1 NCQ Command Error log
0x11 GPL R/O 1 SATA Phy Event Counters log
0x30 GPL,SL R/O 9 IDENTIFY DEVICE data log
0x80-0x9f GPL,SL R/W 16 Host vendor specific log
0xa0-0xa7 GPL,SL VS 16 Device vendor specific log
0xa8-0xb6 GPL,SL VS 1 Device vendor specific log
0xb7 GPL,SL VS 56 Device vendor specific log
0xbd GPL,SL VS 1 Device vendor specific log
0xc0 GPL,SL VS 1 Device vendor specific log
0xc1 GPL VS 93 Device 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 (6 sectors)
Device Error Count: 40578 (device log contains only the most recent 24 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 40578 [17] occurred at disk power-on lifetime: 3937 hours (164 days + 1 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 08 00 01 d1 c0 a7 80 40 00 Error: UNC 8 sectors at LBA = 0x1d1c0a780 = 7814031232

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
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
25 00 00 00 08 00 01 d1 c0 a7 80 40 00 00:09:14.401 READ DMA EXT
25 00 00 00 08 00 00 00 00 7f ea 40 00 00:09:14.401 READ DMA EXT
25 00 00 00 08 00 01 d1 c0 a7 80 40 00 00:09:08.624 READ DMA EXT
25 00 00 00 08 00 00 00 00 7f 22 40 00 00:09:07.942 READ DMA EXT
25 00 00 00 08 00 01 d1 c0 b7 80 40 00 00:09:02.093 READ DMA EXT

Error 40577 [16] occurred at disk power-on lifetime: 3937 hours (164 days + 1 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 08 00 01 d1 c0 a7 80 40 00 Error: UNC 8 sectors at LBA = 0x1d1c0a780 = 7814031232

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
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
25 00 00 00 08 00 01 d1 c0 a7 80 40 00 00:09:08.624 READ DMA EXT
25 00 00 00 08 00 00 00 00 7f 22 40 00 00:09:07.942 READ DMA EXT
25 00 00 00 08 00 01 d1 c0 b7 80 40 00 00:09:02.093 READ DMA EXT
25 00 00 00 08 00 01 d1 c0 b7 80 40 00 00:08:58.073 READ DMA EXT
ec 00 00 00 01 00 00 00 00 00 00 00 00 00:08:56.335 IDENTIFY DEVICE

Error 40576 [15] occurred at disk power-on lifetime: 3937 hours (164 days + 1 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 08 00 01 d1 c0 b7 80 40 00 Error: UNC 8 sectors at LBA = 0x1d1c0b780 = 7814035328

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
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
25 00 00 00 08 00 01 d1 c0 b7 80 40 00 00:09:02.093 READ DMA EXT
25 00 00 00 08 00 01 d1 c0 b7 80 40 00 00:08:58.073 READ DMA EXT
ec 00 00 00 01 00 00 00 00 00 00 00 00 00:08:56.335 IDENTIFY DEVICE
25 00 d5 00 01 00 01 d1 c0 b7 f8 40 00 00:08:52.287 READ DMA EXT
25 00 d5 00 08 00 00 00 00 00 20 40 00 00:08:52.287 READ DMA EXT

Error 40575 [14] occurred at disk power-on lifetime: 3937 hours (164 days + 1 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 08 00 01 d1 c0 b7 80 40 00 Error: UNC 8 sectors at LBA = 0x1d1c0b780 = 7814035328

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
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
25 00 00 00 08 00 01 d1 c0 b7 80 40 00 00:08:58.073 READ DMA EXT
ec 00 00 00 01 00 00 00 00 00 00 00 00 00:08:56.335 IDENTIFY DEVICE
25 00 d5 00 01 00 01 d1 c0 b7 f8 40 00 00:08:52.287 READ DMA EXT
25 00 d5 00 08 00 00 00 00 00 20 40 00 00:08:52.287 READ DMA EXT
25 00 d5 00 08 00 00 00 00 00 18 40 00 00:08:52.287 READ DMA EXT

Error 40574 [13] occurred at disk power-on lifetime: 3937 hours (164 days + 1 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 01 00 01 d1 c0 b7 f8 40 00 Error: UNC 1 sectors at LBA = 0x1d1c0b7f8 = 7814035448

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
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
25 00 d5 00 01 00 01 d1 c0 b7 f8 40 00 00:08:52.287 READ DMA EXT
25 00 d5 00 08 00 00 00 00 00 20 40 00 00:08:52.287 READ DMA EXT
25 00 d5 00 08 00 00 00 00 00 18 40 00 00:08:52.287 READ DMA EXT
25 00 d5 00 08 00 00 00 00 00 10 40 00 00:08:52.286 READ DMA EXT
25 00 d5 00 08 00 00 00 00 00 08 40 00 00:08:52.286 READ DMA EXT

Error 40573 [12] occurred at disk power-on lifetime: 3937 hours (164 days + 1 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 08 00 01 d1 c0 a7 80 40 00 Error: UNC 8 sectors at LBA = 0x1d1c0a780 = 7814031232

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
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
25 00 da 00 08 00 01 d1 c0 a7 80 40 00 00:00:17.977 READ DMA EXT
25 00 da 00 08 00 00 00 00 7f ea 40 00 00:00:17.976 READ DMA EXT
25 00 da 00 08 00 01 d1 c0 a7 80 40 00 00:00:13.899 READ DMA EXT
25 00 da 00 08 00 00 00 00 7f 22 40 00 00:00:13.890 READ DMA EXT
b0 00 da 00 00 00 00 00 c2 4f 00 00 00 00:00:13.718 SMART RETURN STATUS

Error 40572 [11] occurred at disk power-on lifetime: 3937 hours (164 days + 1 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 08 00 01 d1 c0 a7 80 40 00 Error: UNC 8 sectors at LBA = 0x1d1c0a780 = 7814031232

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
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
25 00 da 00 08 00 01 d1 c0 a7 80 40 00 00:00:13.899 READ DMA EXT
25 00 da 00 08 00 00 00 00 7f 22 40 00 00:00:13.890 READ DMA EXT
b0 00 da 00 00 00 00 00 c2 4f 00 00 00 00:00:13.718 SMART RETURN STATUS
25 00 d1 00 08 00 01 d1 c0 b7 80 40 00 00:00:09.618 READ DMA EXT
b0 00 d1 00 01 00 00 00 c2 4f 01 00 00 00:00:09.554 SMART READ ATTRIBUTE THRESHOLDS [OBS-4]

Error 40571 [10] occurred at disk power-on lifetime: 3937 hours (164 days + 1 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 08 00 01 d1 c0 b7 80 40 00 Error: UNC 8 sectors at LBA = 0x1d1c0b780 = 7814035328

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
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
25 00 d1 00 08 00 01 d1 c0 b7 80 40 00 00:00:09.618 READ DMA EXT
b0 00 d1 00 01 00 00 00 c2 4f 01 00 00 00:00:09.554 SMART READ ATTRIBUTE THRESHOLDS [OBS-4]
25 00 d0 00 08 00 01 d1 c0 b7 80 40 00 00:00:05.537 READ DMA EXT
b0 00 d0 00 01 00 00 00 c2 4f 00 00 00 00:00:05.533 SMART READ DATA
ec 00 00 00 01 00 00 00 00 00 00 00 00 00:00:05.420 IDENTIFY DEVICE

Error 40570 [9] occurred at disk power-on lifetime: 3937 hours (164 days + 1 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 08 00 01 d1 c0 b7 80 40 00 Error: UNC 8 sectors at LBA = 0x1d1c0b780 = 7814035328

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
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
25 00 d0 00 08 00 01 d1 c0 b7 80 40 00 00:00:05.537 READ DMA EXT
b0 00 d0 00 01 00 00 00 c2 4f 00 00 00 00:00:05.533 SMART READ DATA
ec 00 00 00 01 00 00 00 00 00 00 00 00 00:00:05.420 IDENTIFY DEVICE
ec 00 00 00 01 00 00 00 00 00 00 00 00 00:00:05.351 IDENTIFY DEVICE
25 00 d5 00 01 00 01 d1 c0 b7 f8 40 00 00:00:01.303 READ DMA EXT

Error 40569 [8] occurred at disk power-on lifetime: 3937 hours (164 days + 1 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 01 00 01 d1 c0 b7 f8 40 00 Error: UNC 1 sectors at LBA = 0x1d1c0b7f8 = 7814035448

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
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
25 00 d5 00 01 00 01 d1 c0 b7 f8 40 00 00:00:01.303 READ DMA EXT
25 00 d5 00 08 00 00 00 00 00 20 40 00 00:00:01.302 READ DMA EXT
25 00 d5 00 08 00 00 00 00 00 18 40 00 00:00:01.302 READ DMA EXT
25 00 d5 00 08 00 00 00 00 00 10 40 00 00:00:01.302 READ DMA EXT
25 00 d5 00 08 00 00 00 00 00 08 40 00 00:00:01.302 READ DMA EXT

Error 40568 [7] occurred at disk power-on lifetime: 3937 hours (164 days + 1 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 01 00 01 d1 c0 b7 f8 40 00 Error: UNC 1 sectors at LBA = 0x1d1c0b7f8 = 7814035448

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
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
25 00 d5 00 01 00 01 d1 c0 b7 f8 40 00 01:48:09.414 READ DMA EXT
25 00 d5 00 08 00 01 d1 c0 b0 78 40 00 01:48:03.619 READ DMA EXT
25 00 d5 00 08 00 01 d1 c0 b0 48 40 00 01:47:58.014 READ DMA EXT
25 00 d5 00 08 00 01 d1 c0 b0 38 40 00 01:47:52.255 READ DMA EXT
25 00 d5 00 08 00 01 d1 c0 b0 08 40 00 01:47:46.636 READ DMA EXT

Error 40567 [6] occurred at disk power-on lifetime: 3937 hours (164 days + 1 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 08 00 01 d1 c0 b0 78 40 00 Error: UNC 8 sectors at LBA = 0x1d1c0b078 = 7814033528

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
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
25 00 d5 00 08 00 01 d1 c0 b0 78 40 00 01:48:03.619 READ DMA EXT
25 00 d5 00 08 00 01 d1 c0 b0 48 40 00 01:47:58.014 READ DMA EXT
25 00 d5 00 08 00 01 d1 c0 b0 38 40 00 01:47:52.255 READ DMA EXT
25 00 d5 00 08 00 01 d1 c0 b0 08 40 00 01:47:46.636 READ DMA EXT
25 00 d5 00 08 00 01 d1 c0 b0 00 40 00 01:47:40.875 READ DMA EXT

Error 40566 [5] occurred at disk power-on lifetime: 3937 hours (164 days + 1 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 08 00 01 d1 c0 b0 48 40 00 Error: UNC 8 sectors at LBA = 0x1d1c0b048 = 7814033480

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
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
25 00 d5 00 08 00 01 d1 c0 b0 48 40 00 01:47:58.014 READ DMA EXT
25 00 d5 00 08 00 01 d1 c0 b0 38 40 00 01:47:52.255 READ DMA EXT
25 00 d5 00 08 00 01 d1 c0 b0 08 40 00 01:47:46.636 READ DMA EXT
25 00 d5 00 08 00 01 d1 c0 b0 00 40 00 01:47:40.875 READ DMA EXT
25 00 d5 00 08 00 01 d1 c0 b0 00 40 00 01:47:35.191 READ DMA EXT

Error 40565 [4] occurred at disk power-on lifetime: 3937 hours (164 days + 1 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 08 00 01 d1 c0 b0 38 40 00 Error: UNC 8 sectors at LBA = 0x1d1c0b038 = 7814033464

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
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
25 00 d5 00 08 00 01 d1 c0 b0 38 40 00 01:47:52.255 READ DMA EXT
25 00 d5 00 08 00 01 d1 c0 b0 08 40 00 01:47:46.636 READ DMA EXT
25 00 d5 00 08 00 01 d1 c0 b0 00 40 00 01:47:40.875 READ DMA EXT
25 00 d5 00 08 00 01 d1 c0 b0 00 40 00 01:47:35.191 READ DMA EXT
25 00 d5 00 08 00 01 d1 c0 af f8 40 00 01:47:29.336 READ DMA EXT

Error 40564 [3] occurred at disk power-on lifetime: 3937 hours (164 days + 1 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 08 00 01 d1 c0 b0 08 40 00 Error: UNC 8 sectors at LBA = 0x1d1c0b008 = 7814033416

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
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
25 00 d5 00 08 00 01 d1 c0 b0 08 40 00 01:47:46.636 READ DMA EXT
25 00 d5 00 08 00 01 d1 c0 b0 00 40 00 01:47:40.875 READ DMA EXT
25 00 d5 00 08 00 01 d1 c0 b0 00 40 00 01:47:35.191 READ DMA EXT
25 00 d5 00 08 00 01 d1 c0 af f8 40 00 01:47:29.336 READ DMA EXT
25 00 d5 00 08 00 01 d1 c0 b2 c0 40 00 01:47:23.729 READ DMA EXT

Error 40563 [2] occurred at disk power-on lifetime: 3937 hours (164 days + 1 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 08 00 01 d1 c0 b0 00 40 00 Error: UNC 8 sectors at LBA = 0x1d1c0b000 = 7814033408

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
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
25 00 d5 00 08 00 01 d1 c0 b0 00 40 00 01:47:40.875 READ DMA EXT
25 00 d5 00 08 00 01 d1 c0 b0 00 40 00 01:47:35.191 READ DMA EXT
25 00 d5 00 08 00 01 d1 c0 af f8 40 00 01:47:29.336 READ DMA EXT
25 00 d5 00 08 00 01 d1 c0 b2 c0 40 00 01:47:23.729 READ DMA EXT
25 00 d5 00 08 00 01 d1 c0 ab 38 40 00 01:47:17.957 READ DMA EXT

Error 40562 [1] occurred at disk power-on lifetime: 3937 hours (164 days + 1 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 08 00 01 d1 c0 b0 00 40 00 Error: UNC 8 sectors at LBA = 0x1d1c0b000 = 7814033408

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
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
25 00 d5 00 08 00 01 d1 c0 b0 00 40 00 01:47:35.191 READ DMA EXT
25 00 d5 00 08 00 01 d1 c0 af f8 40 00 01:47:29.336 READ DMA EXT
25 00 d5 00 08 00 01 d1 c0 b2 c0 40 00 01:47:23.729 READ DMA EXT
25 00 d5 00 08 00 01 d1 c0 ab 38 40 00 01:47:17.957 READ DMA EXT
25 00 d5 00 08 00 01 d1 c0 ab 08 40 00 01:47:12.362 READ DMA EXT

Error 40561 [0] occurred at disk power-on lifetime: 3937 hours (164 days + 1 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 08 00 01 d1 c0 af f8 40 00 Error: UNC 8 sectors at LBA = 0x1d1c0aff8 = 7814033400

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
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
25 00 d5 00 08 00 01 d1 c0 af f8 40 00 01:47:29.336 READ DMA EXT
25 00 d5 00 08 00 01 d1 c0 b2 c0 40 00 01:47:23.729 READ DMA EXT
25 00 d5 00 08 00 01 d1 c0 ab 38 40 00 01:47:17.957 READ DMA EXT
25 00 d5 00 08 00 01 d1 c0 ab 08 40 00 01:47:12.362 READ DMA EXT
25 00 d5 00 08 00 01 d1 c0 aa f8 40 00 01:47:06.601 READ DMA EXT

Error 40560 [23] occurred at disk power-on lifetime: 3937 hours (164 days + 1 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 08 00 01 d1 c0 b2 c0 40 00 Error: UNC 8 sectors at LBA = 0x1d1c0b2c0 = 7814034112

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
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
25 00 d5 00 08 00 01 d1 c0 b2 c0 40 00 01:47:23.729 READ DMA EXT
25 00 d5 00 08 00 01 d1 c0 ab 38 40 00 01:47:17.957 READ DMA EXT
25 00 d5 00 08 00 01 d1 c0 ab 08 40 00 01:47:12.362 READ DMA EXT
25 00 d5 00 08 00 01 d1 c0 aa f8 40 00 01:47:06.601 READ DMA EXT
25 00 d5 00 08 00 01 d1 c0 aa d0 40 00 01:47:01.006 READ DMA EXT

Error 40559 [22] occurred at disk power-on lifetime: 3937 hours (164 days + 1 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 08 00 01 d1 c0 ab 38 40 00 Error: UNC 8 sectors at LBA = 0x1d1c0ab38 = 7814032184

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
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
25 00 d5 00 08 00 01 d1 c0 ab 38 40 00 01:47:17.957 READ DMA EXT
25 00 d5 00 08 00 01 d1 c0 ab 08 40 00 01:47:12.362 READ DMA EXT
25 00 d5 00 08 00 01 d1 c0 aa f8 40 00 01:47:06.601 READ DMA EXT
25 00 d5 00 08 00 01 d1 c0 aa d0 40 00 01:47:01.006 READ DMA EXT
25 00 d5 00 08 00 01 d1 c0 aa c0 40 00 01:46:55.234 READ DMA EXT

Error 40558 [21] occurred at disk power-on lifetime: 3937 hours (164 days + 1 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 08 00 01 d1 c0 ab 08 40 00 Error: UNC 8 sectors at LBA = 0x1d1c0ab08 = 7814032136

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
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
25 00 d5 00 08 00 01 d1 c0 ab 08 40 00 01:47:12.362 READ DMA EXT
25 00 d5 00 08 00 01 d1 c0 aa f8 40 00 01:47:06.601 READ DMA EXT
25 00 d5 00 08 00 01 d1 c0 aa d0 40 00 01:47:01.006 READ DMA EXT
25 00 d5 00 08 00 01 d1 c0 aa c0 40 00 01:46:55.234 READ DMA EXT
25 00 d5 00 08 00 01 d1 c0 aa c0 40 00 01:46:49.663 READ DMA EXT

Error 40557 [20] occurred at disk power-on lifetime: 3937 hours (164 days + 1 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 08 00 01 d1 c0 aa f8 40 00 Error: UNC 8 sectors at LBA = 0x1d1c0aaf8 = 7814032120

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
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
25 00 d5 00 08 00 01 d1 c0 aa f8 40 00 01:47:06.601 READ DMA EXT
25 00 d5 00 08 00 01 d1 c0 aa d0 40 00 01:47:01.006 READ DMA EXT
25 00 d5 00 08 00 01 d1 c0 aa c0 40 00 01:46:55.234 READ DMA EXT
25 00 d5 00 08 00 01 d1 c0 aa c0 40 00 01:46:49.663 READ DMA EXT
25 00 d5 00 08 00 01 d1 c0 aa c0 40 00 01:46:43.873 READ DMA EXT

Error 40556 [19] occurred at disk power-on lifetime: 3937 hours (164 days + 1 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 08 00 01 d1 c0 aa d0 40 00 Error: UNC 8 sectors at LBA = 0x1d1c0aad0 = 7814032080

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
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
25 00 d5 00 08 00 01 d1 c0 aa d0 40 00 01:47:01.006 READ DMA EXT
25 00 d5 00 08 00 01 d1 c0 aa c0 40 00 01:46:55.234 READ DMA EXT
25 00 d5 00 08 00 01 d1 c0 aa c0 40 00 01:46:49.663 READ DMA EXT
25 00 d5 00 08 00 01 d1 c0 aa c0 40 00 01:46:43.873 READ DMA EXT
25 00 d5 00 08 00 01 d1 c0 73 f8 40 00 01:46:38.187 READ DMA EXT

Error 40555 [18] occurred at disk power-on lifetime: 3937 hours (164 days + 1 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 08 00 01 d1 c0 aa c0 40 00 Error: UNC 8 sectors at LBA = 0x1d1c0aac0 = 7814032064

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
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
25 00 d5 00 08 00 01 d1 c0 aa c0 40 00 01:46:55.234 READ DMA EXT
25 00 d5 00 08 00 01 d1 c0 aa c0 40 00 01:46:49.663 READ DMA EXT
25 00 d5 00 08 00 01 d1 c0 aa c0 40 00 01:46:43.873 READ DMA EXT
25 00 d5 00 08 00 01 d1 c0 73 f8 40 00 01:46:38.187 READ DMA EXT
25 00 d5 00 08 00 01 d1 c0 6c 78 40 00 01:46:32.426 READ 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: unknown failure 90% 3937 -
# 2 Short offline Completed: unknown failure 90% 3937 -
# 3 Short offline Completed: unknown failure 90% 3934 -
# 4 Conveyance offline Completed: unknown failure 90% 3933 -
# 5 Short offline Completed: unknown failure 90% 3933 -
# 6 Short offline Completed: unknown failure 90% 3932 -
# 7 Short offline Completed: unknown failure 90% 3932 -
# 8 Conveyance offline Completed: unknown failure 90% 3931 -
# 9 Extended offline Completed: unknown failure 90% 3931 -
#10 Short offline Completed: unknown failure 90% 3931 -

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): 258 (0x0102)
Device State: Active (0)
Current Temperature: 32 Celsius
Power Cycle Min/Max Temperature: 32/32 Celsius
Lifetime Min/Max Temperature: 17/48 Celsius
Under/Over Temperature Limit Count: 0/0
Vendor specific:
01 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 00 00

SCT Temperature History Version: 2
Temperature Sampling Period: 1 minute
Temperature Logging Interval: 1 minute
Min/Max recommended Temperature: 0/60 Celsius
Min/Max Temperature Limit: -41/85 Celsius
Temperature History Size (Index): 478 (288)

Index Estimated Time Temperature Celsius
289 2021-01-30 05:09 40 *********************
... ..( 7 skipped). .. *********************
297 2021-01-30 05:17 40 *********************
298 2021-01-30 05:18 41 **********************
... ..( 97 skipped). .. **********************
396 2021-01-30 06:56 41 **********************
397 2021-01-30 06:57 ? -
398 2021-01-30 06:58 23 ****
399 2021-01-30 06:59 23 ****
400 2021-01-30 07:00 24 *****
401 2021-01-30 07:01 24 *****
402 2021-01-30 07:02 25 ******
403 2021-01-30 07:03 25 ******
404 2021-01-30 07:04 25 ******
405 2021-01-30 07:05 26 *******
406 2021-01-30 07:06 26 *******
407 2021-01-30 07:07 27 ********
408 2021-01-30 07:08 27 ********
409 2021-01-30 07:09 27 ********
410 2021-01-30 07:10 28 *********
411 2021-01-30 07:11 28 *********
412 2021-01-30 07:12 29 **********
413 2021-01-30 07:13 29 **********
414 2021-01-30 07:14 29 **********
415 2021-01-30 07:15 30 ***********
416 2021-01-30 07:16 30 ***********
417 2021-01-30 07:17 30 ***********
418 2021-01-30 07:18 31 ************
... ..( 2 skipped). .. ************
421 2021-01-30 07:21 31 ************
422 2021-01-30 07:22 32 *************
... ..( 2 skipped). .. *************
425 2021-01-30 07:25 32 *************
426 2021-01-30 07:26 33 **************
... ..( 2 skipped). .. **************
429 2021-01-30 07:29 33 **************
430 2021-01-30 07:30 34 ***************
... ..( 3 skipped). .. ***************
434 2021-01-30 07:34 34 ***************
435 2021-01-30 07:35 35 ****************
436 2021-01-30 07:36 35 ****************
437 2021-01-30 07:37 ? -
438 2021-01-30 07:38 32 *************
439 2021-01-30 07:39 41 **********************
... ..( 38 skipped). .. **********************
0 2021-01-30 08:18 41 **********************
1 2021-01-30 08:19 42 ***********************
... ..( 83 skipped). .. ***********************
85 2021-01-30 09:43 42 ***********************
86 2021-01-30 09:44 ? -
87 2021-01-30 09:45 42 ***********************
88 2021-01-30 09:46 ? -
89 2021-01-30 09:47 42 ***********************
... ..( 14 skipped). .. ***********************
104 2021-01-30 10:02 42 ***********************
105 2021-01-30 10:03 ? -
106 2021-01-30 10:04 41 **********************
... ..( 16 skipped). .. **********************
123 2021-01-30 10:21 41 **********************
124 2021-01-30 10:22 42 ***********************
... ..( 7 skipped). .. ***********************
132 2021-01-30 10:30 42 ***********************
133 2021-01-30 10:31 ? -
134 2021-01-30 10:32 43 ************************
135 2021-01-30 10:33 42 ***********************
... ..( 2 skipped). .. ***********************
138 2021-01-30 10:36 42 ***********************
139 2021-01-30 10:37 ? -
140 2021-01-30 10:38 44 *************************
... ..( 3 skipped). .. *************************
144 2021-01-30 10:42 44 *************************
145 2021-01-30 10:43 ? -
146 2021-01-30 10:44 43 ************************
... ..(110 skipped). .. ************************
257 2021-01-30 12:35 43 ************************
258 2021-01-30 12:36 ? -
259 2021-01-30 12:37 37 ******************
... ..( 3 skipped). .. ******************
263 2021-01-30 12:41 37 ******************
264 2021-01-30 12:42 38 *******************
... ..( 7 skipped). .. *******************
272 2021-01-30 12:50 38 *******************
273 2021-01-30 12:51 39 ********************
... ..( 9 skipped). .. ********************
283 2021-01-30 13:01 39 ********************
284 2021-01-30 13:02 40 *********************
... ..( 3 skipped). .. *********************
288 2021-01-30 13:06 40 *********************

SCT Error Recovery Control command not supported

Device Statistics (GP Log 0x04)
Page Offset Size Value Flags Description
0x01 ===== = = === == General Statistics (rev 1) ==
0x01 0x008 4 6306 --- Lifetime Power-On Resets
0x01 0x010 4 3938 --- Power-on Hours
0x01 0x018 6 15108842897 --- Logical Sectors Written
0x01 0x020 6 106771228 --- Number of Write Commands
0x01 0x028 6 8538541868 --- Logical Sectors Read
0x01 0x030 6 345220683 --- Number of Read Commands
0x01 0x038 6 1291898112 --- Date and Time TimeStamp
0x03 ===== = = === == Rotating Media Statistics (rev 1) ==
0x03 0x008 4 3930 --- Spindle Motor Power-on Hours
0x03 0x010 4 810 --- Head Flying Hours
0x03 0x018 4 15226 --- Head Load Events
0x03 0x020 4 1512 --- Number of Reallocated Logical Sectors
0x03 0x028 4 36377 --- Read Recovery Attempts
0x03 0x030 4 0 --- Number of Mechanical Start Failures
0x03 0x038 4 14192 --- Number of Realloc. Candidate Logical Sectors
0x03 0x040 4 15 --- Number of High Priority Unload Events
0x04 ===== = = === == General Errors Statistics (rev 1) ==
0x04 0x008 4 27032 --- Number of Reported Uncorrectable Errors
0x04 0x010 4 27 --- Resets Between Cmd Acceptance and Completion
0x05 ===== = = === == Temperature Statistics (rev 1) ==
0x05 0x008 1 32 --- Current Temperature
0x05 0x010 1 43 --- Average Short Term Temperature
0x05 0x018 1 34 --- Average Long Term Temperature
0x05 0x020 1 48 --- Highest Temperature
0x05 0x028 1 20 --- Lowest Temperature
0x05 0x030 1 45 --- Highest Average Short Term Temperature
0x05 0x038 1 26 --- Lowest Average Short Term Temperature
0x05 0x040 1 34 --- Highest Average Long Term Temperature
0x05 0x048 1 29 --- Lowest Average Long Term Temperature
0x05 0x050 4 0 --- Time in Over-Temperature
0x05 0x058 1 60 --- Specified Maximum Operating Temperature
0x05 0x060 4 0 --- Time in Under-Temperature
0x05 0x068 1 0 --- Specified Minimum Operating Temperature
0x06 ===== = = === == Transport Statistics (rev 1) ==
0x06 0x008 4 8586 --- Number of Hardware Resets
0x06 0x010 4 2309 --- Number of ASR Events
0x06 0x018 4 0 --- Number of Interface CRC Errors
|||_ C monitored condition met
||__ D supports DSN
|___ N normalized value

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

pclab

Moderator
Probably your drive was already with some problems, but you still didn't hit on them.
The first thing you should have done, was to image your drive to another and then start working with recovery software to try to get the data out.
Now you have a can of worms on it.
I would recommend you to use some paid recovery software, like Reclaime or DMDE which are pretty cheap and would allow you to get your data.
 
Top