Data Recovery Issues on a 1TB Drive

How to use TestDisk to recover lost partition
Forum rules
When asking for technical support:
- Search for posts on the same topic before posting a new question.
- Give clear, specific information in the title of your post.
- Include as many details as you can, MOST POSTS WILL GET ONLY ONE OR TWO ANSWERS.
- Post a follow up with a "Thank you" or "This worked!"
- When you learn something, use that knowledge to HELP ANOTHER USER LATER.
Before posting, please read https://www.cgsecurity.org/testdisk.pdf
Message
Author
Domenic
Posts: 23
Joined: 13 May 2019, 17:33

Re: Data Recovery Issues on a 1TB Drive

#21 Post by Domenic » 31 May 2019, 20:23

TESTDISK Cylinder Read error:
Attachments
TESTDISK Cylinder Read error:
TESTDISK Cylinder Read error:
TESTDISK Cylinder Read error 2019-05-30 20-09-03 2.png (83.92 KiB) Viewed 2768 times
Last edited by Domenic on 31 May 2019, 20:29, edited 2 times in total.

Sponsored links

Domenic
Posts: 23
Joined: 13 May 2019, 17:33

Re: Data Recovery Issues on a 1TB Drive

#22 Post by Domenic » 31 May 2019, 20:24

TESTDISK "Quick Search":
Attachments
TESTDISK "Quick Search":
TESTDISK "Quick Search":
Screenshot at 2019-05-30 22-19-50 2.png (52.11 KiB) Viewed 2767 times
Last edited by Domenic on 31 May 2019, 20:30, edited 2 times in total.

Domenic
Posts: 23
Joined: 13 May 2019, 17:33

Re: Data Recovery Issues on a 1TB Drive

#23 Post by Domenic » 31 May 2019, 20:24

DDRescue Passive Scan:
Attachments
Screenshot at 2019-05-31 00-26-53 1.png
Screenshot at 2019-05-31 00-26-53 1.png (67.6 KiB) Viewed 2776 times

Domenic
Posts: 23
Joined: 13 May 2019, 17:33

Re: Data Recovery Issues on a 1TB Drive

#24 Post by Domenic » 31 May 2019, 20:25

DDRescue Copy:
Attachments
DDRescue Back to Front2019-05-31 14-46-10 1.png
DDRescue Back to Front2019-05-31 14-46-10 1.png (59.11 KiB) Viewed 2775 times

Domenic
Posts: 23
Joined: 13 May 2019, 17:33

Re: Data Recovery Issues on a 1TB Drive

#25 Post by Domenic » 31 May 2019, 20:27

Complete Error Log:

smartctl 6.6 2017-11-05 r4594 [x86_64-linux-5.0.1-pmagic64] (local build)
Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family: Western Digital Green
Device Model: WDC WD10EZRX-00L4HB0
Serial Number: WD-WCC4J5XDUZLJ
LU WWN Device Id: 5 0014ee 2b6379095
Firmware Version: 01.01A01
User Capacity: 1,000,204,886,016 bytes [1.00 TB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Rotation Rate: 5400 rpm
Device is: In smartctl database [for details use: -P show]
ATA Version is: ATA8-ACS (minor revision not indicated)
SATA Version is: SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is: Thu May 30 14:07:28 2019 EDT
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: 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: ( 0) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: (13920) 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: ( 158) 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 200 200 051 - 0
3 Spin_Up_Time POS--K 140 134 021 - 3983
4 Start_Stop_Count -O--CK 099 099 000 - 1652
5 Reallocated_Sector_Ct PO--CK 200 200 140 - 0
7 Seek_Error_Rate -OSR-K 200 200 000 - 0
9 Power_On_Hours -O--CK 079 079 000 - 15557
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 099 099 000 - 1636
192 Power-Off_Retract_Count -O--CK 200 200 000 - 191
193 Load_Cycle_Count -O--CK 131 131 000 - 208830
194 Temperature_Celsius -O---K 117 105 000 - 26
196 Reallocated_Event_Count -O--CK 200 200 000 - 0
197 Current_Pending_Sector -O--CK 200 200 000 - 0
198 Offline_Uncorrectable ----CK 200 200 000 - 0
199 UDMA_CRC_Error_Count -O--CK 200 200 000 - 1
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
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
0x80-0x9f GPL,SL R/W 16 Host vendor specific log
0xa0-0xa7 GPL,SL VS 16 Device vendor specific log
0xa8-0xb7 GPL,SL VS 1 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: 32207 (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 32207 [14] occurred at disk power-on lifetime: 15557 hours (648 days + 5 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
-- -- -- == -- == == == -- -- -- -- --
04 -- 51 00 02 00 00 00 00 00 00 a0 00 Error: ABRT

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
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
ef 00 10 00 02 00 00 00 00 00 00 a0 00 00:00:02.834 SET FEATURES [Enable SATA feature]
ec 00 00 00 00 00 00 00 00 00 00 a0 00 00:00:02.833 IDENTIFY DEVICE
ef 00 03 00 46 00 00 00 00 00 00 a0 00 00:00:02.833 SET FEATURES [Set transfer mode]
ef 00 10 00 02 00 00 00 00 00 00 a0 00 00:00:02.833 SET FEATURES [Enable SATA feature]
ec 00 00 00 00 00 00 00 00 00 00 a0 00 00:00:02.832 IDENTIFY DEVICE

Error 32206 [13] occurred at disk power-on lifetime: 15557 hours (648 days + 5 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
-- -- -- == -- == == == -- -- -- -- --
04 -- 51 00 46 00 00 00 00 00 00 a0 00 Error: ABRT

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
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
ef 00 03 00 46 00 00 00 00 00 00 a0 00 00:00:02.833 SET FEATURES [Set transfer mode]
ef 00 10 00 02 00 00 00 00 00 00 a0 00 00:00:02.833 SET FEATURES [Enable SATA feature]
ec 00 00 00 00 00 00 00 00 00 00 a0 00 00:00:02.832 IDENTIFY DEVICE
c8 00 00 00 08 00 00 00 00 00 00 e0 00 00:00:02.818 READ DMA
ef 00 10 00 02 00 00 00 00 00 00 a0 00 00:00:02.818 SET FEATURES [Enable SATA feature]

Error 32205 [12] occurred at disk power-on lifetime: 15557 hours (648 days + 5 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
-- -- -- == -- == == == -- -- -- -- --
04 -- 51 00 02 00 00 00 00 00 00 a0 00 Error: ABRT

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
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
ef 00 10 00 02 00 00 00 00 00 00 a0 00 00:00:02.833 SET FEATURES [Enable SATA feature]
ec 00 00 00 00 00 00 00 00 00 00 a0 00 00:00:02.832 IDENTIFY DEVICE
c8 00 00 00 08 00 00 00 00 00 00 e0 00 00:00:02.818 READ DMA
ef 00 10 00 02 00 00 00 00 00 00 a0 00 00:00:02.818 SET FEATURES [Enable SATA feature]
ec 00 00 00 00 00 00 00 00 00 00 a0 00 00:00:02.817 IDENTIFY DEVICE

Error 32204 [11] occurred at disk power-on lifetime: 15557 hours (648 days + 5 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
-- -- -- == -- == == == -- -- -- -- --
04 -- 51 00 08 00 00 00 00 00 00 e0 00 Error: ABRT 8 sectors at LBA = 0x00000000 = 0

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
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
c8 00 00 00 08 00 00 00 00 00 00 e0 00 00:00:02.818 READ DMA
ef 00 10 00 02 00 00 00 00 00 00 a0 00 00:00:02.818 SET FEATURES [Enable SATA feature]
ec 00 00 00 00 00 00 00 00 00 00 a0 00 00:00:02.817 IDENTIFY DEVICE
ef 00 03 00 46 00 00 00 00 00 00 a0 00 00:00:02.817 SET FEATURES [Set transfer mode]
ef 00 10 00 02 00 00 00 00 00 00 a0 00 00:00:02.817 SET FEATURES [Enable SATA feature]

Error 32203 [10] occurred at disk power-on lifetime: 15557 hours (648 days + 5 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
-- -- -- == -- == == == -- -- -- -- --
04 -- 51 00 02 00 00 00 00 00 00 a0 00 Error: ABRT

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
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
ef 00 10 00 02 00 00 00 00 00 00 a0 00 00:00:02.818 SET FEATURES [Enable SATA feature]
ec 00 00 00 00 00 00 00 00 00 00 a0 00 00:00:02.817 IDENTIFY DEVICE
ef 00 03 00 46 00 00 00 00 00 00 a0 00 00:00:02.817 SET FEATURES [Set transfer mode]
ef 00 10 00 02 00 00 00 00 00 00 a0 00 00:00:02.817 SET FEATURES [Enable SATA feature]
ec 00 00 00 00 00 00 00 00 00 00 a0 00 00:00:02.816 IDENTIFY DEVICE

Error 32202 [9] occurred at disk power-on lifetime: 15557 hours (648 days + 5 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
-- -- -- == -- == == == -- -- -- -- --
04 -- 51 00 46 00 00 00 00 00 00 a0 00 Error: ABRT

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
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
ef 00 03 00 46 00 00 00 00 00 00 a0 00 00:00:02.817 SET FEATURES [Set transfer mode]
ef 00 10 00 02 00 00 00 00 00 00 a0 00 00:00:02.817 SET FEATURES [Enable SATA feature]
ec 00 00 00 00 00 00 00 00 00 00 a0 00 00:00:02.816 IDENTIFY DEVICE
c8 00 00 00 08 00 00 00 00 00 00 e0 00 00:00:02.802 READ DMA
ef 00 10 00 02 00 00 00 00 00 00 a0 00 00:00:02.802 SET FEATURES [Enable SATA feature]

Error 32201 [8] occurred at disk power-on lifetime: 15557 hours (648 days + 5 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
-- -- -- == -- == == == -- -- -- -- --
04 -- 51 00 02 00 00 00 00 00 00 a0 00 Error: ABRT

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
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
ef 00 10 00 02 00 00 00 00 00 00 a0 00 00:00:02.817 SET FEATURES [Enable SATA feature]
ec 00 00 00 00 00 00 00 00 00 00 a0 00 00:00:02.816 IDENTIFY DEVICE
c8 00 00 00 08 00 00 00 00 00 00 e0 00 00:00:02.802 READ DMA
ef 00 10 00 02 00 00 00 00 00 00 a0 00 00:00:02.802 SET FEATURES [Enable SATA feature]
ec 00 00 00 00 00 00 00 00 00 00 a0 00 00:00:02.801 IDENTIFY DEVICE

Error 32200 [7] occurred at disk power-on lifetime: 15557 hours (648 days + 5 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
-- -- -- == -- == == == -- -- -- -- --
04 -- 51 00 08 00 00 00 00 00 00 e0 00 Error: ABRT 8 sectors at LBA = 0x00000000 = 0

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
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
c8 00 00 00 08 00 00 00 00 00 00 e0 00 00:00:02.802 READ DMA
ef 00 10 00 02 00 00 00 00 00 00 a0 00 00:00:02.802 SET FEATURES [Enable SATA feature]
ec 00 00 00 00 00 00 00 00 00 00 a0 00 00:00:02.801 IDENTIFY DEVICE
ef 00 03 00 46 00 00 00 00 00 00 a0 00 00:00:02.801 SET FEATURES [Set transfer mode]
ef 00 10 00 02 00 00 00 00 00 00 a0 00 00:00:02.801 SET FEATURES [Enable SATA feature]

Error 32199 [6] occurred at disk power-on lifetime: 15557 hours (648 days + 5 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
-- -- -- == -- == == == -- -- -- -- --
04 -- 51 00 02 00 00 00 00 00 00 a0 00 Error: ABRT

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
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
ef 00 10 00 02 00 00 00 00 00 00 a0 00 00:00:02.802 SET FEATURES [Enable SATA feature]
ec 00 00 00 00 00 00 00 00 00 00 a0 00 00:00:02.801 IDENTIFY DEVICE
ef 00 03 00 46 00 00 00 00 00 00 a0 00 00:00:02.801 SET FEATURES [Set transfer mode]
ef 00 10 00 02 00 00 00 00 00 00 a0 00 00:00:02.801 SET FEATURES [Enable SATA feature]
ec 00 00 00 00 00 00 00 00 00 00 a0 00 00:00:02.800 IDENTIFY DEVICE

Error 32198 [5] occurred at disk power-on lifetime: 15557 hours (648 days + 5 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
-- -- -- == -- == == == -- -- -- -- --
04 -- 51 00 46 00 00 00 00 00 00 a0 00 Error: ABRT

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
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
ef 00 03 00 46 00 00 00 00 00 00 a0 00 00:00:02.801 SET FEATURES [Set transfer mode]
ef 00 10 00 02 00 00 00 00 00 00 a0 00 00:00:02.801 SET FEATURES [Enable SATA feature]
ec 00 00 00 00 00 00 00 00 00 00 a0 00 00:00:02.800 IDENTIFY DEVICE
c8 00 00 00 08 00 00 00 00 00 00 e0 00 00:00:02.786 READ DMA
ef 00 10 00 02 00 00 00 00 00 00 a0 00 00:00:02.786 SET FEATURES [Enable SATA feature]

Error 32197 [4] occurred at disk power-on lifetime: 15557 hours (648 days + 5 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
-- -- -- == -- == == == -- -- -- -- --
04 -- 51 00 02 00 00 00 00 00 00 a0 00 Error: ABRT

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
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
ef 00 10 00 02 00 00 00 00 00 00 a0 00 00:00:02.801 SET FEATURES [Enable SATA feature]
ec 00 00 00 00 00 00 00 00 00 00 a0 00 00:00:02.800 IDENTIFY DEVICE
c8 00 00 00 08 00 00 00 00 00 00 e0 00 00:00:02.786 READ DMA
ef 00 10 00 02 00 00 00 00 00 00 a0 00 00:00:02.786 SET FEATURES [Enable SATA feature]
ec 00 00 00 00 00 00 00 00 00 00 a0 00 00:00:02.785 IDENTIFY DEVICE

Error 32196 [3] occurred at disk power-on lifetime: 15557 hours (648 days + 5 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
-- -- -- == -- == == == -- -- -- -- --
04 -- 51 00 08 00 00 00 00 00 00 e0 00 Error: ABRT 8 sectors at LBA = 0x00000000 = 0

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
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
c8 00 00 00 08 00 00 00 00 00 00 e0 00 00:00:02.786 READ DMA
ef 00 10 00 02 00 00 00 00 00 00 a0 00 00:00:02.786 SET FEATURES [Enable SATA feature]
ec 00 00 00 00 00 00 00 00 00 00 a0 00 00:00:02.785 IDENTIFY DEVICE
ef 00 03 00 46 00 00 00 00 00 00 a0 00 00:00:02.785 SET FEATURES [Set transfer mode]
ef 00 10 00 02 00 00 00 00 00 00 a0 00 00:00:02.785 SET FEATURES [Enable SATA feature]

Error 32195 [2] occurred at disk power-on lifetime: 15557 hours (648 days + 5 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
-- -- -- == -- == == == -- -- -- -- --
04 -- 51 00 02 00 00 00 00 00 00 a0 00 Error: ABRT

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
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
ef 00 10 00 02 00 00 00 00 00 00 a0 00 00:00:02.786 SET FEATURES [Enable SATA feature]
ec 00 00 00 00 00 00 00 00 00 00 a0 00 00:00:02.785 IDENTIFY DEVICE
ef 00 03 00 46 00 00 00 00 00 00 a0 00 00:00:02.785 SET FEATURES [Set transfer mode]
ef 00 10 00 02 00 00 00 00 00 00 a0 00 00:00:02.785 SET FEATURES [Enable SATA feature]
ec 00 00 00 00 00 00 00 00 00 00 a0 00 00:00:02.784 IDENTIFY DEVICE

Error 32194 [1] occurred at disk power-on lifetime: 15557 hours (648 days + 5 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
-- -- -- == -- == == == -- -- -- -- --
04 -- 51 00 46 00 00 00 00 00 00 a0 00 Error: ABRT

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
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
ef 00 03 00 46 00 00 00 00 00 00 a0 00 00:00:02.785 SET FEATURES [Set transfer mode]
ef 00 10 00 02 00 00 00 00 00 00 a0 00 00:00:02.785 SET FEATURES [Enable SATA feature]
ec 00 00 00 00 00 00 00 00 00 00 a0 00 00:00:02.784 IDENTIFY DEVICE
c8 00 00 00 08 00 00 00 00 00 00 e0 00 00:00:02.770 READ DMA
ef 00 10 00 02 00 00 00 00 00 00 a0 00 00:00:02.770 SET FEATURES [Enable SATA feature]

Error 32193 [0] occurred at disk power-on lifetime: 15557 hours (648 days + 5 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
-- -- -- == -- == == == -- -- -- -- --
04 -- 51 00 02 00 00 00 00 00 00 a0 00 Error: ABRT

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
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
ef 00 10 00 02 00 00 00 00 00 00 a0 00 00:00:02.785 SET FEATURES [Enable SATA feature]
ec 00 00 00 00 00 00 00 00 00 00 a0 00 00:00:02.784 IDENTIFY DEVICE
c8 00 00 00 08 00 00 00 00 00 00 e0 00 00:00:02.770 READ DMA
ef 00 10 00 02 00 00 00 00 00 00 a0 00 00:00:02.770 SET FEATURES [Enable SATA feature]
ec 00 00 00 00 00 00 00 00 00 00 a0 00 00:00:02.769 IDENTIFY DEVICE

Error 32192 [23] occurred at disk power-on lifetime: 15557 hours (648 days + 5 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
-- -- -- == -- == == == -- -- -- -- --
04 -- 51 00 08 00 00 00 00 00 00 e0 00 Error: ABRT 8 sectors at LBA = 0x00000000 = 0

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
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
c8 00 00 00 08 00 00 00 00 00 00 e0 00 00:00:02.770 READ DMA
ef 00 10 00 02 00 00 00 00 00 00 a0 00 00:00:02.770 SET FEATURES [Enable SATA feature]
ec 00 00 00 00 00 00 00 00 00 00 a0 00 00:00:02.769 IDENTIFY DEVICE
ef 00 03 00 46 00 00 00 00 00 00 a0 00 00:00:02.769 SET FEATURES [Set transfer mode]
ef 00 10 00 02 00 00 00 00 00 00 a0 00 00:00:02.769 SET FEATURES [Enable SATA feature]

Error 32191 [22] occurred at disk power-on lifetime: 15557 hours (648 days + 5 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
-- -- -- == -- == == == -- -- -- -- --
04 -- 51 00 02 00 00 00 00 00 00 a0 00 Error: ABRT

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
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
ef 00 10 00 02 00 00 00 00 00 00 a0 00 00:00:02.770 SET FEATURES [Enable SATA feature]
ec 00 00 00 00 00 00 00 00 00 00 a0 00 00:00:02.769 IDENTIFY DEVICE
ef 00 03 00 46 00 00 00 00 00 00 a0 00 00:00:02.769 SET FEATURES [Set transfer mode]
ef 00 10 00 02 00 00 00 00 00 00 a0 00 00:00:02.769 SET FEATURES [Enable SATA feature]
ec 00 00 00 00 00 00 00 00 00 00 a0 00 00:00:02.768 IDENTIFY DEVICE

Error 32190 [21] occurred at disk power-on lifetime: 15557 hours (648 days + 5 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
-- -- -- == -- == == == -- -- -- -- --
04 -- 51 00 46 00 00 00 00 00 00 a0 00 Error: ABRT

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
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
ef 00 03 00 46 00 00 00 00 00 00 a0 00 00:00:02.769 SET FEATURES [Set transfer mode]
ef 00 10 00 02 00 00 00 00 00 00 a0 00 00:00:02.769 SET FEATURES [Enable SATA feature]
ec 00 00 00 00 00 00 00 00 00 00 a0 00 00:00:02.768 IDENTIFY DEVICE
c8 00 00 00 08 00 00 00 00 00 00 e0 00 00:00:02.754 READ DMA
ef 00 10 00 02 00 00 00 00 00 00 a0 00 00:00:02.754 SET FEATURES [Enable SATA feature]

Error 32189 [20] occurred at disk power-on lifetime: 15557 hours (648 days + 5 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
-- -- -- == -- == == == -- -- -- -- --
04 -- 51 00 02 00 00 00 00 00 00 a0 00 Error: ABRT

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
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
ef 00 10 00 02 00 00 00 00 00 00 a0 00 00:00:02.769 SET FEATURES [Enable SATA feature]
ec 00 00 00 00 00 00 00 00 00 00 a0 00 00:00:02.768 IDENTIFY DEVICE
c8 00 00 00 08 00 00 00 00 00 00 e0 00 00:00:02.754 READ DMA
ef 00 10 00 02 00 00 00 00 00 00 a0 00 00:00:02.754 SET FEATURES [Enable SATA feature]
ec 00 00 00 00 00 00 00 00 00 00 a0 00 00:00:02.753 IDENTIFY DEVICE

Error 32188 [19] occurred at disk power-on lifetime: 15557 hours (648 days + 5 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
-- -- -- == -- == == == -- -- -- -- --
04 -- 51 00 08 00 00 00 00 00 00 e0 00 Error: ABRT 8 sectors at LBA = 0x00000000 = 0

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
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
c8 00 00 00 08 00 00 00 00 00 00 e0 00 00:00:02.754 READ DMA
ef 00 10 00 02 00 00 00 00 00 00 a0 00 00:00:02.754 SET FEATURES [Enable SATA feature]
ec 00 00 00 00 00 00 00 00 00 00 a0 00 00:00:02.753 IDENTIFY DEVICE
ef 00 03 00 46 00 00 00 00 00 00 a0 00 00:00:02.753 SET FEATURES [Set transfer mode]
ef 00 10 00 02 00 00 00 00 00 00 a0 00 00:00:02.753 SET FEATURES [Enable SATA feature]

Error 32187 [18] occurred at disk power-on lifetime: 15557 hours (648 days + 5 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
-- -- -- == -- == == == -- -- -- -- --
04 -- 51 00 02 00 00 00 00 00 00 a0 00 Error: ABRT

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
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
ef 00 10 00 02 00 00 00 00 00 00 a0 00 00:00:02.754 SET FEATURES [Enable SATA feature]
ec 00 00 00 00 00 00 00 00 00 00 a0 00 00:00:02.753 IDENTIFY DEVICE
ef 00 03 00 46 00 00 00 00 00 00 a0 00 00:00:02.753 SET FEATURES [Set transfer mode]
ef 00 10 00 02 00 00 00 00 00 00 a0 00 00:00:02.753 SET FEATURES [Enable SATA feature]
ec 00 00 00 00 00 00 00 00 00 00 a0 00 00:00:02.752 IDENTIFY DEVICE

Error 32186 [17] occurred at disk power-on lifetime: 15557 hours (648 days + 5 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
-- -- -- == -- == == == -- -- -- -- --
04 -- 51 00 46 00 00 00 00 00 00 a0 00 Error: ABRT

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
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
ef 00 03 00 46 00 00 00 00 00 00 a0 00 00:00:02.753 SET FEATURES [Set transfer mode]
ef 00 10 00 02 00 00 00 00 00 00 a0 00 00:00:02.753 SET FEATURES [Enable SATA feature]
ec 00 00 00 00 00 00 00 00 00 00 a0 00 00:00:02.752 IDENTIFY DEVICE
c8 00 00 00 08 00 00 00 00 00 00 e0 00 00:00:02.726 READ DMA
ef 00 10 00 02 00 00 00 00 00 00 a0 00 00:00:02.726 SET FEATURES [Enable SATA feature]

Error 32185 [16] occurred at disk power-on lifetime: 15557 hours (648 days + 5 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
-- -- -- == -- == == == -- -- -- -- --
04 -- 51 00 02 00 00 00 00 00 00 a0 00 Error: ABRT

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
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
ef 00 10 00 02 00 00 00 00 00 00 a0 00 00:00:02.753 SET FEATURES [Enable SATA feature]
ec 00 00 00 00 00 00 00 00 00 00 a0 00 00:00:02.752 IDENTIFY DEVICE
c8 00 00 00 08 00 00 00 00 00 00 e0 00 00:00:02.726 READ DMA
ef 00 10 00 02 00 00 00 00 00 00 a0 00 00:00:02.726 SET FEATURES [Enable SATA feature]
ec 00 00 00 00 00 00 00 00 00 00 a0 00 00:00:02.725 IDENTIFY DEVICE

Error 32184 [15] occurred at disk power-on lifetime: 15557 hours (648 days + 5 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
-- -- -- == -- == == == -- -- -- -- --
04 -- 51 00 08 00 00 00 00 00 00 e0 00 Error: ABRT 8 sectors at LBA = 0x00000000 = 0

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
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
c8 00 00 00 08 00 00 00 00 00 00 e0 00 00:00:02.726 READ DMA
ef 00 10 00 02 00 00 00 00 00 00 a0 00 00:00:02.726 SET FEATURES [Enable SATA feature]
ec 00 00 00 00 00 00 00 00 00 00 a0 00 00:00:02.725 IDENTIFY DEVICE
ef 00 03 00 46 00 00 00 00 00 00 a0 00 00:00:02.725 SET FEATURES [Set transfer mode]
ef 00 10 00 02 00 00 00 00 00 00 a0 00 00:00:02.725 SET FEATURES [Enable SATA feature]

SMART Error Log Version: 1
Warning: ATA error count 3398 inconsistent with error log pointer 5

ATA Error Count: 3398 (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 3398 occurred at disk power-on lifetime: 15557 hours (648 days + 5 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
-- -- -- -- -- -- --
04 51 02 00 00 00 a0 Error: ABRT

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
ef 10 02 00 00 00 a0 00 00:00:02.834 SET FEATURES [Enable SATA feature]
ec 00 00 00 00 00 a0 00 00:00:02.833 IDENTIFY DEVICE
ef 03 46 00 00 00 a0 00 00:00:02.833 SET FEATURES [Set transfer mode]
ef 10 02 00 00 00 a0 00 00:00:02.833 SET FEATURES [Enable SATA feature]
ec 00 00 00 00 00 a0 00 00:00:02.832 IDENTIFY DEVICE

Error 3397 occurred at disk power-on lifetime: 15557 hours (648 days + 5 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
-- -- -- -- -- -- --
04 51 46 00 00 00 a0 Error: ABRT

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
ef 03 46 00 00 00 a0 00 00:00:02.833 SET FEATURES [Set transfer mode]
ef 10 02 00 00 00 a0 00 00:00:02.833 SET FEATURES [Enable SATA feature]
ec 00 00 00 00 00 a0 00 00:00:02.832 IDENTIFY DEVICE
c8 00 08 00 00 00 e0 00 00:00:02.818 READ DMA
ef 10 02 00 00 00 a0 00 00:00:02.818 SET FEATURES [Enable SATA feature]

Error 3396 occurred at disk power-on lifetime: 15557 hours (648 days + 5 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
-- -- -- -- -- -- --
04 51 02 00 00 00 a0 Error: ABRT

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
ef 10 02 00 00 00 a0 00 00:00:02.833 SET FEATURES [Enable SATA feature]
ec 00 00 00 00 00 a0 00 00:00:02.832 IDENTIFY DEVICE
c8 00 08 00 00 00 e0 00 00:00:02.818 READ DMA
ef 10 02 00 00 00 a0 00 00:00:02.818 SET FEATURES [Enable SATA feature]
ec 00 00 00 00 00 a0 00 00:00:02.817 IDENTIFY DEVICE

Error 3395 occurred at disk power-on lifetime: 15557 hours (648 days + 5 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
-- -- -- -- -- -- --
04 51 08 00 00 00 e0 Error: ABRT 8 sectors at LBA = 0x00000000 = 0

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
c8 00 08 00 00 00 e0 00 00:00:02.818 READ DMA
ef 10 02 00 00 00 a0 00 00:00:02.818 SET FEATURES [Enable SATA feature]
ec 00 00 00 00 00 a0 00 00:00:02.817 IDENTIFY DEVICE
ef 03 46 00 00 00 a0 00 00:00:02.817 SET FEATURES [Set transfer mode]
ef 10 02 00 00 00 a0 00 00:00:02.817 SET FEATURES [Enable SATA feature]

Error 3394 occurred at disk power-on lifetime: 15557 hours (648 days + 5 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
-- -- -- -- -- -- --
04 51 02 00 00 00 a0 Error: ABRT

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
ef 10 02 00 00 00 a0 00 00:00:02.818 SET FEATURES [Enable SATA feature]
ec 00 00 00 00 00 a0 00 00:00:02.817 IDENTIFY DEVICE
ef 03 46 00 00 00 a0 00 00:00:02.817 SET FEATURES [Set transfer mode]
ef 10 02 00 00 00 a0 00 00:00:02.817 SET FEATURES [Enable SATA feature]
ec 00 00 00 00 00 a0 00 00:00:02.816 IDENTIFY DEVICE

SMART Extended Self-test Log Version: 1 (1 sectors)
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Short offline Completed without error 00% 15557 -
# 2 Short offline Completed without error 00% 15554 -
# 3 Extended offline Aborted by host 90% 15554 -
# 4 Short offline Completed without error 00% 15554 -
# 5 Short offline Completed without error 00% 15554 -
# 6 Short offline Completed without error 00% 15553 -
# 7 Short offline Completed without error 00% 10690 -
# 8 Conveyance offline Completed without error 00% 8589 -

SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Short offline Completed without error 00% 15557 -
# 2 Short offline Completed without error 00% 15554 -
# 3 Extended offline Aborted by host 90% 15554 -
# 4 Short offline Completed without error 00% 15554 -
# 5 Short offline Completed without error 00% 15554 -
# 6 Short offline Completed without error 00% 15553 -
# 7 Short offline Completed without error 00% 10690 -
# 8 Conveyance offline Completed without error 00% 8589 -

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)
SCT Support Level: 1
Device State: Active (0)
Current Temperature: 26 Celsius
Power Cycle Min/Max Temperature: 26/26 Celsius
Lifetime Min/Max Temperature: 14/38 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 (90)

Index Estimated Time Temperature Celsius
91 2019-05-30 06:10 23 ****
92 2019-05-30 06:11 23 ****
93 2019-05-30 06:12 23 ****
94 2019-05-30 06:13 ? -
95 2019-05-30 06:14 24 *****
96 2019-05-30 06:15 ? -
97 2019-05-30 06:16 27 ********
98 2019-05-30 06:17 ? -
99 2019-05-30 06:18 27 ********
100 2019-05-30 06:19 ? -
101 2019-05-30 06:20 28 *********
102 2019-05-30 06:21 ? -
103 2019-05-30 06:22 28 *********
104 2019-05-30 06:23 28 *********
105 2019-05-30 06:24 28 *********
106 2019-05-30 06:25 29 **********
107 2019-05-30 06:26 30 ***********
... ..( 2 skipped). .. ***********
110 2019-05-30 06:29 30 ***********
111 2019-05-30 06:30 31 ************
112 2019-05-30 06:31 31 ************
113 2019-05-30 06:32 ? -
114 2019-05-30 06:33 31 ************
... ..( 2 skipped). .. ************
117 2019-05-30 06:36 31 ************
118 2019-05-30 06:37 32 *************
119 2019-05-30 06:38 31 ************
... ..( 2 skipped). .. ************
122 2019-05-30 06:41 31 ************
123 2019-05-30 06:42 32 *************
... ..( 2 skipped). .. *************
126 2019-05-30 06:45 32 *************
127 2019-05-30 06:46 33 **************
... ..( 2 skipped). .. **************
130 2019-05-30 06:49 33 **************
131 2019-05-30 06:50 34 ***************
... ..( 3 skipped). .. ***************
135 2019-05-30 06:54 34 ***************
136 2019-05-30 06:55 35 ****************
... ..( 54 skipped). .. ****************
191 2019-05-30 07:50 35 ****************
192 2019-05-30 07:51 34 ***************
... ..( 4 skipped). .. ***************
197 2019-05-30 07:56 34 ***************
198 2019-05-30 07:57 33 **************
... ..( 18 skipped). .. **************
217 2019-05-30 08:16 33 **************
218 2019-05-30 08:17 32 *************
... ..( 6 skipped). .. *************
225 2019-05-30 08:24 32 *************
226 2019-05-30 08:25 31 ************
... ..( 27 skipped). .. ************
254 2019-05-30 08:53 31 ************
255 2019-05-30 08:54 32 *************
... ..( 3 skipped). .. *************
259 2019-05-30 08:58 32 *************
260 2019-05-30 08:59 33 **************
... ..( 4 skipped). .. **************
265 2019-05-30 09:04 33 **************
266 2019-05-30 09:05 34 ***************
267 2019-05-30 09:06 34 ***************
268 2019-05-30 09:07 35 ****************
269 2019-05-30 09:08 35 ****************
270 2019-05-30 09:09 ? -
271 2019-05-30 09:10 22 ***
272 2019-05-30 09:11 ? -
273 2019-05-30 09:12 24 *****
274 2019-05-30 09:13 25 ******
275 2019-05-30 09:14 26 *******
... ..( 8 skipped). .. *******
284 2019-05-30 09:23 26 *******
285 2019-05-30 09:24 27 ********
... ..( 3 skipped). .. ********
289 2019-05-30 09:28 27 ********
290 2019-05-30 09:29 28 *********
... ..( 7 skipped). .. *********
298 2019-05-30 09:37 28 *********
299 2019-05-30 09:38 ? -
300 2019-05-30 09:39 28 *********
301 2019-05-30 09:40 28 *********
302 2019-05-30 09:41 27 ********
... ..( 2 skipped). .. ********
305 2019-05-30 09:44 27 ********
306 2019-05-30 09:45 ? -
307 2019-05-30 09:46 24 *****
308 2019-05-30 09:47 ? -
309 2019-05-30 09:48 25 ******
310 2019-05-30 09:49 ? -
311 2019-05-30 09:50 26 *******
312 2019-05-30 09:51 26 *******
313 2019-05-30 09:52 30 ***********
... ..( 52 skipped). .. ***********
366 2019-05-30 10:45 30 ***********
367 2019-05-30 10:46 31 ************
... ..( 51 skipped). .. ************
419 2019-05-30 11:38 31 ************
420 2019-05-30 11:39 ? -
421 2019-05-30 11:40 18 -
422 2019-05-30 11:41 19 -
423 2019-05-30 11:42 ? -
424 2019-05-30 11:43 27 ********
425 2019-05-30 11:44 27 ********
426 2019-05-30 11:45 ? -
427 2019-05-30 11:46 28 *********
428 2019-05-30 11:47 ? -
429 2019-05-30 11:48 25 ******
430 2019-05-30 11:49 ? -
431 2019-05-30 11:50 27 ********
432 2019-05-30 11:51 27 ********
433 2019-05-30 11:52 ? -
434 2019-05-30 11:53 26 *******
... ..( 4 skipped). .. *******
439 2019-05-30 11:58 26 *******
440 2019-05-30 11:59 ? -
441 2019-05-30 12:00 29 **********
... ..( 4 skipped). .. **********
446 2019-05-30 12:05 29 **********
447 2019-05-30 12:06 ? -
448 2019-05-30 12:07 30 ***********
449 2019-05-30 12:08 ? -
450 2019-05-30 12:09 28 *********
451 2019-05-30 12:10 28 *********
452 2019-05-30 12:11 28 *********
453 2019-05-30 12:12 ? -
454 2019-05-30 12:13 21 **
455 2019-05-30 12:14 21 **
456 2019-05-30 12:15 21 **
457 2019-05-30 12:16 22 ***
458 2019-05-30 12:17 ? -
459 2019-05-30 12:18 24 *****
460 2019-05-30 12:19 24 *****
461 2019-05-30 12:20 25 ******
462 2019-05-30 12:21 ? -
463 2019-05-30 12:22 28 *********
464 2019-05-30 12:23 28 *********
465 2019-05-30 12:24 ? -
466 2019-05-30 12:25 24 *****
467 2019-05-30 12:26 24 *****
468 2019-05-30 12:27 25 ******
... ..( 2 skipped). .. ******
471 2019-05-30 12:30 25 ******
472 2019-05-30 12:31 26 *******
473 2019-05-30 12:32 26 *******
474 2019-05-30 12:33 26 *******
475 2019-05-30 12:34 27 ********
476 2019-05-30 12:35 27 ********
477 2019-05-30 12:36 27 ********
0 2019-05-30 12:37 ? -
1 2019-05-30 12:38 21 **
... ..( 2 skipped). .. **
4 2019-05-30 12:41 21 **
5 2019-05-30 12:42 22 ***
6 2019-05-30 12:43 ? -
7 2019-05-30 12:44 20 *
8 2019-05-30 12:45 20 *
9 2019-05-30 12:46 21 **
10 2019-05-30 12:47 21 **
11 2019-05-30 12:48 22 ***
12 2019-05-30 12:49 22 ***
13 2019-05-30 12:50 23 ****
... ..( 3 skipped). .. ****
17 2019-05-30 12:54 23 ****
18 2019-05-30 12:55 24 *****
19 2019-05-30 12:56 24 *****
20 2019-05-30 12:57 24 *****
21 2019-05-30 12:58 25 ******
22 2019-05-30 12:59 25 ******
23 2019-05-30 13:00 25 ******
24 2019-05-30 13:01 26 *******
... ..( 7 skipped). .. *******
32 2019-05-30 13:09 26 *******
33 2019-05-30 13:10 27 ********
34 2019-05-30 13:11 27 ********
35 2019-05-30 13:12 27 ********
36 2019-05-30 13:13 28 *********
... ..( 24 skipped). .. *********
61 2019-05-30 13:38 28 *********
62 2019-05-30 13:39 ? -
63 2019-05-30 13:40 21 **
64 2019-05-30 13:41 ? -
65 2019-05-30 13:42 23 ****
66 2019-05-30 13:43 ? -
67 2019-05-30 13:44 23 ****
68 2019-05-30 13:45 23 ****
69 2019-05-30 13:46 23 ****
70 2019-05-30 13:47 24 *****
71 2019-05-30 13:48 ? -
72 2019-05-30 13:49 27 ********
73 2019-05-30 13:50 ? -
74 2019-05-30 13:51 23 ****
75 2019-05-30 13:52 23 ****
76 2019-05-30 13:53 23 ****
77 2019-05-30 13:54 ? -
78 2019-05-30 13:55 24 *****
79 2019-05-30 13:56 24 *****
80 2019-05-30 13:57 24 *****
81 2019-05-30 13:58 25 ******
82 2019-05-30 13:59 25 ******
83 2019-05-30 14:00 25 ******
84 2019-05-30 14:01 26 *******
85 2019-05-30 14:02 26 *******
86 2019-05-30 14:03 26 *******
87 2019-05-30 14:04 ? -
88 2019-05-30 14:05 21 **
89 2019-05-30 14:06 22 ***
90 2019-05-30 14:07 22 ***

SCT Error Recovery Control command not supported

Device Statistics (GP/SMART Log 0x04) not supported

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 1 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
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 87 Vendor specific

Domenic
Posts: 23
Joined: 13 May 2019, 17:33

Re: Data Recovery Issues on a 1TB Drive

#26 Post by Domenic » 31 May 2019, 20:28

DDRescue Log:
# Mapfile. Created by GNU ddrescue version 1.23
# Command line: ddrescue -v -d -f -R -n -r 0 -c 32 -b 4096 /dev/sda /dev/sdc /media/sdb1/trwhywrtywrt/log.log
# Start time: 2019-05-30 23:32:20
# Current time: 2019-05-31 00:27:05
# Copying non-tried blocks... Pass 5 (backwards)
# current_pos current_status current_pass
0xE7F0440000 ? 5
# pos size status
0x00000000 0x00020000 *
0x00020000 0x244860000 ?
0x244880000 0x00020000 *
0x2448A0000 0x2542A0000 ?
0x498B40000 0x00020000 *
0x498B60000 0x2542A0000 ?
0x6ECE00000 0x00020000 *
0x6ECE20000 0x2542A0000 ?
0x9410C0000 0x00020000 *
0x9410E0000 0x2542A0000 ?
0xB95380000 0x00020000 *
0xB953A0000 0x2542A0000 ?
0xDE9640000 0x00020000 *
0xDE9660000 0x2542A0000 ?
0x103D900000 0x00020000 *
0x103D920000 0x2542A0000 ?
0x1291BC0000 0x00020000 *
0x1291BE0000 0x2542A0000 ?
0x14E5E80000 0x00020000 *
0x14E5EA0000 0x2542A0000 ?
0x173A140000 0x00020000 *
0x173A160000 0x2542A0000 ?
0x198E400000 0x00020000 *
0x198E420000 0x2542A0000 ?
0x1BE26C0000 0x00020000 *
0x1BE26E0000 0x2542A0000 ?
0x1E36980000 0x00020000 *
0x1E369A0000 0x2542A0000 ?
0x208AC40000 0x00020000 *
0x208AC60000 0x2542A0000 ?
0x22DEF00000 0x00020000 *
0x22DEF20000 0x2542A0000 ?
0x25331C0000 0x00020000 *
0x25331E0000 0x2542A0000 ?
0x2787480000 0x00020000 *
0x27874A0000 0x2542A0000 ?
0x29DB740000 0x00020000 *
0x29DB760000 0x2542A0000 ?
0x2C2FA00000 0x00020000 *
0x2C2FA20000 0x2542A0000 ?
0x2E83CC0000 0x00020000 *
0x2E83CE0000 0x2542A0000 ?
0x30D7F80000 0x00020000 *
0x30D7FA0000 0x2542A0000 ?
0x332C240000 0x00020000 *
0x332C260000 0x2542A0000 ?
0x3580500000 0x00020000 *
0x3580520000 0x2542A0000 ?
0x37D47C0000 0x00020000 *
0x37D47E0000 0x2542A0000 ?
0x3A28A80000 0x00020000 *
0x3A28AA0000 0x2542A0000 ?
0x3C7CD40000 0x00020000 *
0x3C7CD60000 0x2542A0000 ?
0x3ED1000000 0x00020000 *
0x3ED1020000 0x2542A0000 ?
0x41252C0000 0x00020000 *
0x41252E0000 0x2542A0000 ?
0x4379580000 0x00020000 *
0x43795A0000 0x2542A0000 ?
0x45CD840000 0x00020000 *
0x45CD860000 0x2542A0000 ?
0x4821B00000 0x00020000 *
0x4821B20000 0x2542A0000 ?
0x4A75DC0000 0x00020000 *
0x4A75DE0000 0x2542A0000 ?
0x4CCA080000 0x00020000 *
0x4CCA0A0000 0x2542A0000 ?
0x4F1E340000 0x00020000 *
0x4F1E360000 0x2542A0000 ?
0x5172600000 0x00020000 *
0x5172620000 0x2542A0000 ?
0x53C68C0000 0x00020000 *
0x53C68E0000 0x2542A0000 ?
0x561AB80000 0x00020000 *
0x561ABA0000 0x2542A0000 ?
0x586EE40000 0x00020000 *
0x586EE60000 0x2542A0000 ?
0x5AC3100000 0x00020000 *
0x5AC3120000 0x2542A0000 ?
0x5D173C0000 0x00020000 *
0x5D173E0000 0x2542A0000 ?
0x5F6B680000 0x00020000 *
0x5F6B6A0000 0x2542A0000 ?
0x61BF940000 0x00020000 *
0x61BF960000 0x2542A0000 ?
0x6413C00000 0x00020000 *
0x6413C20000 0x2542A0000 ?
0x6667EC0000 0x00020000 *
0x6667EE0000 0x2542A0000 ?
0x68BC180000 0x00020000 *
0x68BC1A0000 0x2542A0000 ?
0x6B10440000 0x00020000 *
0x6B10460000 0x2542A0000 ?
0x6D64700000 0x00020000 *
0x6D64720000 0x2542A0000 ?
0x6FB89C0000 0x00020000 *
0x6FB89E0000 0x2542A0000 ?
0x720CC80000 0x00020000 *
0x720CCA0000 0x2542A0000 ?
0x7460F40000 0x00020000 *
0x7460F60000 0x2542A0000 ?
0x76B5200000 0x00020000 *
0x76B5220000 0x2542A0000 ?
0x79094C0000 0x00020000 *
0x79094E0000 0x2542A0000 ?
0x7B5D780000 0x00020000 *
0x7B5D7A0000 0x2542A0000 ?
0x7DB1A40000 0x00020000 *
0x7DB1A60000 0x2542A0000 ?
0x8005D00000 0x00020000 *
0x8005D20000 0x2542A0000 ?
0x8259FC0000 0x00020000 *
0x8259FE0000 0x2542A0000 ?
0x84AE280000 0x00020000 *
0x84AE2A0000 0x2542A0000 ?
0x8702540000 0x00020000 *
0x8702560000 0x2542A0000 ?
0x8956800000 0x00020000 *
0x8956820000 0x2542A0000 ?
0x8BAAAC0000 0x00020000 *
0x8BAAAE0000 0x2542A0000 ?
0x8DFED80000 0x00020000 *
0x8DFEDA0000 0x2542A0000 ?
0x9053040000 0x00020000 *
0x9053060000 0x2542A0000 ?
0x92A7300000 0x00020000 *
0x92A7320000 0x2542A0000 ?
0x94FB5C0000 0x00020000 *
0x94FB5E0000 0x2542A0000 ?
0x974F880000 0x00020000 *
0x974F8A0000 0x2542A0000 ?
0x99A3B40000 0x00020000 *
0x99A3B60000 0x2542A0000 ?
0x9BF7E00000 0x00020000 *
0x9BF7E20000 0x2542A0000 ?
0x9E4C0C0000 0x00020000 *
0x9E4C0E0000 0x2542A0000 ?
0xA0A0380000 0x00020000 *
0xA0A03A0000 0x2542A0000 ?
0xA2F4640000 0x00020000 *
0xA2F4660000 0x2542A0000 ?
0xA548900000 0x00020000 *
0xA548920000 0x2542A0000 ?
0xA79CBC0000 0x00020000 *
0xA79CBE0000 0x2542A0000 ?
0xA9F0E80000 0x00020000 *
0xA9F0EA0000 0x2542A0000 ?
0xAC45140000 0x00020000 *
0xAC45160000 0x2542A0000 ?
0xAE99400000 0x00020000 *
0xAE99420000 0x2542A0000 ?
0xB0ED6C0000 0x00020000 *
0xB0ED6E0000 0x2542A0000 ?
0xB341980000 0x00020000 *
0xB3419A0000 0x2542A0000 ?
0xB595C40000 0x00020000 *
0xB595C60000 0x2542A0000 ?
0xB7E9F00000 0x00020000 *
0xB7E9F20000 0x2542A0000 ?
0xBA3E1C0000 0x00020000 *
0xBA3E1E0000 0x2542A0000 ?
0xBC92480000 0x00020000 *
0xBC924A0000 0x2542A0000 ?
0xBEE6740000 0x00020000 *
0xBEE6760000 0x2542A0000 ?
0xC13AA00000 0x00020000 *
0xC13AA20000 0x2542A0000 ?
0xC38ECC0000 0x00020000 *
0xC38ECE0000 0x2542A0000 ?
0xC5E2F80000 0x00020000 *
0xC5E2FA0000 0x2542A0000 ?
0xC837240000 0x00020000 *
0xC837260000 0x2542A0000 ?
0xCA8B500000 0x00020000 *
0xCA8B520000 0x2542A0000 ?
0xCCDF7C0000 0x00020000 *
0xCCDF7E0000 0x2542A0000 ?
0xCF33A80000 0x00020000 *
0xCF33AA0000 0x2542A0000 ?
0xD187D40000 0x00020000 *
0xD187D60000 0x2542A0000 ?
0xD3DC000000 0x00020000 *
0xD3DC020000 0x2542A0000 ?
0xD6302C0000 0x00020000 *
0xD6302E0000 0x2542A0000 ?
0xD884580000 0x00020000 *
0xD8845A0000 0x2542A0000 ?
0xDAD8840000 0x00020000 *
0xDAD8860000 0x2542A0000 ?
0xDD2CB00000 0x00020000 *
0xDD2CB20000 0x2542A0000 ?
0xDF80DC0000 0x00020000 *
0xDF80DE0000 0x2542A0000 ?
0xE1D5080000 0x00020000 *
0xE1D50A0000 0x2542A0000 ?
0xE429340000 0x00020000 *
0xE429360000 0x2542A0000 ?
0xE67D600000 0x00040000 *
0xE67D640000 0x131FE0000 ?
0xE7AF620000 0x00040000 *
0xE7AF660000 0x40DE0000 ?
0xE7F0440000 0xF0976000 *

recuperation
Posts: 300
Joined: 04 Jan 2019, 09:48
Location: Hannover, Deutschland (Germany, Allemagne)

Re: Data Recovery Issues on a 1TB Drive

#27 Post by recuperation » 02 Jun 2019, 12:47

Your ddrescue run has not terminated yet.
The areas marked with a "?" have not yet been examined.
Their big number is caused by read errors which make ddrescue jump to different disk areas hoping to be able to quickly read another portion of the disk without errors.
The read error may show up as pending sectors in the SMART parameters.

The outcome of ddrescue contradicts the "Everything is healthy"-message you have got before.

Domenic
Posts: 23
Joined: 13 May 2019, 17:33

Re: Data Recovery Issues on a 1TB Drive

#28 Post by Domenic » 02 Jun 2019, 16:43

Hi Recuperation,
The outcome of ddrescue contradicts the "Everything is healthy"-message you have got before.
That's why this is so frustrating and why I started to upload the screenshots.
I'm at a total loss and didn't want you to think I was wasting your time.
The fact that the drive isn't clicking or showing obvious signs of failure is confounding as well!
By all accounts I would say there is a mechanical problem but I cant find it.

Do false positives happen a lot or does this tell me something?

Your ddrescue run has not terminated yet.
I was concerned about causing more damage so I aborted the DDRescue.
Are you saying I should let that run it's course and see what happens?

Thank you for all your help as always!

recuperation
Posts: 300
Joined: 04 Jan 2019, 09:48
Location: Hannover, Deutschland (Germany, Allemagne)

Re: Data Recovery Issues on a 1TB Drive

#29 Post by recuperation » 02 Jun 2019, 18:17

Domenic wrote:
02 Jun 2019, 16:43
Do false positives happen a lot or does this tell me something?
I really don't know. I don't look at summaries, I check the SMART parameters for unusual figures.
I can't resolve the issue.
Are you saying I should let that run it's course and see what happens?
Every individual rescue attempt might reduce the rescue probability of a professional recovery service.
I can't take that decision for you.

Domenic
Posts: 23
Joined: 13 May 2019, 17:33

Re: Data Recovery Issues on a 1TB Drive

#30 Post by Domenic » 04 Jun 2019, 23:37

Hi Recuperation,

Update:
I did switch the PCB with a tested donor and its still doing the same thing.
That would have been too easy...

This is a Western Digital 1TB drive with 1 platter.
So switching this to another matching chaise seems doable considering I don't have to worry about platter alignment.
Since there is only 1 platter, I would think it shouldn't be to difficult to pull the platter out of the bad drive and put it into a functional matching drive.
Am I correct in assuming I can just move the platter to another exact same drive with little to no problems?

I don't look at summaries, I check the SMART parameters for unusual figures. I can't resolve the issue.
Is there anything else that I can provide you that might help at this point?

Every individual rescue attempt might reduce the rescue probability of a professional recovery service. I can't take that decision for you.
I totally understand and will probably take another shot at cloning the drive with DDRescue.
I wish I could send it out but cant afford the cost of recovering 300GB of data or afford the chance of putting the sensitive personal and client data in someone else's hands.
The loss hurts a lot but not as much as a data breach.


Also Aleques said:
I managed to do a dd if=/dev/zero bs=512 count=1 of=/dev/affected-device and the read error was gone
Do you have any insight to this command; what is it's purpose, can I run it in Parted Magic or is this only good for a Linux command line?
I think I understand the syntax a little but am still quite confused.

Thank you as always, even if I'm not successful I appreciate your helping me understand all this!

Post Reply

Who is online

Users browsing this forum: Bing [Bot], Google [Bot] and 5 guests