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: 22
Joined: 13 May 2019, 17:33

Re: Data Recovery Issues on a 1TB Drive

#11 Post by Domenic » 16 May 2019, 02:30

Hi recuperation,

So many questions.....

What causes ATA Errors?
Also you said your drive had 42000h running time and mine has 15000h running time, how could I be getting that many ATA errors?


Im not questioning what your saying at all, I'm just super curious because this is knowledge I dont possess.


I am recommending you for saint hood at this point for being so helpful!
Thanks again

Sponsored links

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

Re: Data Recovery Issues on a 1TB Drive

#12 Post by recuperation » 17 May 2019, 14:31

Domenic wrote:
16 May 2019, 02:30
What causes ATA Errors?
Ask the association.
Also you said your drive had 42000h running time and mine has 15000h running time, how could I be getting that many ATA errors?
I can only guess, I really don't know.
If the firmware sees an error and loops endlessly waiting for a successful termination of an operation maybe, who knows?

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

Re: Data Recovery Issues on a 1TB Drive

#13 Post by Domenic » 18 May 2019, 14:09

Hi recuperation,

This stuff is so interesting yet so damn confounding...
The problem is I don't know enough of The taught theory but, for better or worse, that's never stopped me before.


New developments with the drive!
I put it to the side and let it rest since the last go around the other day.
Since then the drive has stopped spinning up correctly.
It doesn't spin up on power up or on attempt to access the files.
It does however spin up slowly when I run the "Basic Health Test" but stops spinning shortly after the test begins.
The weird thing is it is passing the "Basic Health Test" again!
I'm currently running the "Extended Health Test" but it has another 1:38hrs to go.

Could this be a bad control board?

I will post the results when it finishes and maybe you can something I can't.

How do I post pictures on the forum?

I meant when I said last time, you have been extremely helpful and I appreciate it very much!!

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

Re: Data Recovery Issues on a 1TB Drive

#14 Post by recuperation » 18 May 2019, 16:03

Domenic wrote:
18 May 2019, 14:09
It does however spin up slowly when I run the "Basic Health Test" but stops spinning shortly after the test begins.
The weird thing is it is passing the "Basic Health Test" again!
I'm currently running the "Extended Health Test" but it has another 1:38hrs to go.
Be precise. Which tests are you referring to?
Domenic wrote:
18 May 2019, 14:09
Could this be a bad control board?
Yes.
Domenic wrote:
18 May 2019, 14:09
How do I post pictures on the forum?
Use the file extension tab just below the "send" button.
Domenic wrote:
18 May 2019, 14:09
I meant when I said last time, you have been extremely helpful and I appreciate it very much!!
Thank you!

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

Re: Data Recovery Issues on a 1TB Drive

#15 Post by Domenic » 20 May 2019, 19:05

Hi recuperation,

Sorry I didn't post back sooner I had an emergency this weekend.

I'm referring to the GSmartControl Basic Tests, both Short and Extended.
Both Tests say "PASSED" and " Completed Without Error, 100%". (Posted Picture)

After working with you this past week I'm understanding what I'm looking at a little more and the drive is definitely throwing Errors.
I missed it before because the tests keep saying "Passed" and I just don't know enough.
I really don't get it; the drive says "PASSED" every time but throws errors and still wont connect.

Below is the GSmart Log from the last "Extended Test".
I am also attaching screenshots I took of the last round of tests, so you can see what I'm talking about.

Edit: Having trouble with the picture size., will try again later.

As Always, Thanks for everything!!


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: Sat May 18 13:27:03 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 141 134 021 - 3941
4 Start_Stop_Count -O--CK 099 099 000 - 1647
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 - 1631
192 Power-Off_Retract_Count -O--CK 200 200 000 - 186
193 Load_Cycle_Count -O--CK 131 131 000 - 208825
194 Temperature_Celsius -O---K 120 105 000 - 23
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: 57595 (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 57595 [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.964 SET FEATURES [Enable SATA feature]
ec 00 00 00 00 00 00 00 00 00 00 a0 00 00:00:02.964 IDENTIFY DEVICE
ef 00 03 00 46 00 00 00 00 00 00 a0 00 00:00:02.964 SET FEATURES [Set transfer mode]
ef 00 10 00 02 00 00 00 00 00 00 a0 00 00:00:02.963 SET FEATURES [Enable SATA feature]
ec 00 00 00 00 00 00 00 00 00 00 a0 00 00:00:02.963 IDENTIFY DEVICE

Error 57594 [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.964 SET FEATURES [Set transfer mode]
ef 00 10 00 02 00 00 00 00 00 00 a0 00 00:00:02.963 SET FEATURES [Enable SATA feature]
ec 00 00 00 00 00 00 00 00 00 00 a0 00 00:00:02.963 IDENTIFY DEVICE
c8 00 00 00 08 00 00 00 00 00 00 e0 00 00:00:02.949 READ DMA
ef 00 10 00 02 00 00 00 00 00 00 a0 00 00:00:02.948 SET FEATURES [Enable SATA feature]

Error 57593 [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.963 SET FEATURES [Enable SATA feature]
ec 00 00 00 00 00 00 00 00 00 00 a0 00 00:00:02.963 IDENTIFY DEVICE
c8 00 00 00 08 00 00 00 00 00 00 e0 00 00:00:02.949 READ DMA
ef 00 10 00 02 00 00 00 00 00 00 a0 00 00:00:02.948 SET FEATURES [Enable SATA feature]
ec 00 00 00 00 00 00 00 00 00 00 a0 00 00:00:02.948 IDENTIFY DEVICE

Error 57592 [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.949 READ DMA
ef 00 10 00 02 00 00 00 00 00 00 a0 00 00:00:02.948 SET FEATURES [Enable SATA feature]
ec 00 00 00 00 00 00 00 00 00 00 a0 00 00:00:02.948 IDENTIFY DEVICE
ef 00 03 00 46 00 00 00 00 00 00 a0 00 00:00:02.948 SET FEATURES [Set transfer mode]
ef 00 10 00 02 00 00 00 00 00 00 a0 00 00:00:02.947 SET FEATURES [Enable SATA feature]

Error 57591 [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.948 SET FEATURES [Enable SATA feature]
ec 00 00 00 00 00 00 00 00 00 00 a0 00 00:00:02.948 IDENTIFY DEVICE
ef 00 03 00 46 00 00 00 00 00 00 a0 00 00:00:02.948 SET FEATURES [Set transfer mode]
ef 00 10 00 02 00 00 00 00 00 00 a0 00 00:00:02.947 SET FEATURES [Enable SATA feature]
ec 00 00 00 00 00 00 00 00 00 00 a0 00 00:00:02.947 IDENTIFY DEVICE

Error 57590 [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.948 SET FEATURES [Set transfer mode]
ef 00 10 00 02 00 00 00 00 00 00 a0 00 00:00:02.947 SET FEATURES [Enable SATA feature]
ec 00 00 00 00 00 00 00 00 00 00 a0 00 00:00:02.947 IDENTIFY DEVICE
c8 00 00 00 08 00 00 00 00 00 00 e0 00 00:00:02.933 READ DMA
ef 00 10 00 02 00 00 00 00 00 00 a0 00 00:00:02.932 SET FEATURES [Enable SATA feature]

Error 57589 [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.947 SET FEATURES [Enable SATA feature]
ec 00 00 00 00 00 00 00 00 00 00 a0 00 00:00:02.947 IDENTIFY DEVICE
c8 00 00 00 08 00 00 00 00 00 00 e0 00 00:00:02.933 READ DMA
ef 00 10 00 02 00 00 00 00 00 00 a0 00 00:00:02.932 SET FEATURES [Enable SATA feature]
ec 00 00 00 00 00 00 00 00 00 00 a0 00 00:00:02.932 IDENTIFY DEVICE

Error 57588 [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.933 READ DMA
ef 00 10 00 02 00 00 00 00 00 00 a0 00 00:00:02.932 SET FEATURES [Enable SATA feature]
ec 00 00 00 00 00 00 00 00 00 00 a0 00 00:00:02.932 IDENTIFY DEVICE
ef 00 03 00 46 00 00 00 00 00 00 a0 00 00:00:02.932 SET FEATURES [Set transfer mode]
ef 00 10 00 02 00 00 00 00 00 00 a0 00 00:00:02.931 SET FEATURES [Enable SATA feature]

Error 57587 [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.932 SET FEATURES [Enable SATA feature]
ec 00 00 00 00 00 00 00 00 00 00 a0 00 00:00:02.932 IDENTIFY DEVICE
ef 00 03 00 46 00 00 00 00 00 00 a0 00 00:00:02.932 SET FEATURES [Set transfer mode]
ef 00 10 00 02 00 00 00 00 00 00 a0 00 00:00:02.931 SET FEATURES [Enable SATA feature]
ec 00 00 00 00 00 00 00 00 00 00 a0 00 00:00:02.931 IDENTIFY DEVICE

Error 57586 [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.932 SET FEATURES [Set transfer mode]
ef 00 10 00 02 00 00 00 00 00 00 a0 00 00:00:02.931 SET FEATURES [Enable SATA feature]
ec 00 00 00 00 00 00 00 00 00 00 a0 00 00:00:02.931 IDENTIFY DEVICE
c8 00 00 00 08 00 00 00 00 00 00 e0 00 00:00:02.917 READ DMA
ef 00 10 00 02 00 00 00 00 00 00 a0 00 00:00:02.916 SET FEATURES [Enable SATA feature]

Error 57585 [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.931 SET FEATURES [Enable SATA feature]
ec 00 00 00 00 00 00 00 00 00 00 a0 00 00:00:02.931 IDENTIFY DEVICE
c8 00 00 00 08 00 00 00 00 00 00 e0 00 00:00:02.917 READ DMA
ef 00 10 00 02 00 00 00 00 00 00 a0 00 00:00:02.916 SET FEATURES [Enable SATA feature]
ec 00 00 00 00 00 00 00 00 00 00 a0 00 00:00:02.916 IDENTIFY DEVICE

Error 57584 [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.917 READ DMA
ef 00 10 00 02 00 00 00 00 00 00 a0 00 00:00:02.916 SET FEATURES [Enable SATA feature]
ec 00 00 00 00 00 00 00 00 00 00 a0 00 00:00:02.916 IDENTIFY DEVICE
ef 00 03 00 46 00 00 00 00 00 00 a0 00 00:00:02.916 SET FEATURES [Set transfer mode]
ef 00 10 00 02 00 00 00 00 00 00 a0 00 00:00:02.916 SET FEATURES [Enable SATA feature]

Error 57583 [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.916 SET FEATURES [Enable SATA feature]
ec 00 00 00 00 00 00 00 00 00 00 a0 00 00:00:02.916 IDENTIFY DEVICE
ef 00 03 00 46 00 00 00 00 00 00 a0 00 00:00:02.916 SET FEATURES [Set transfer mode]
ef 00 10 00 02 00 00 00 00 00 00 a0 00 00:00:02.916 SET FEATURES [Enable SATA feature]
ec 00 00 00 00 00 00 00 00 00 00 a0 00 00:00:02.915 IDENTIFY DEVICE

Error 57582 [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.916 SET FEATURES [Set transfer mode]
ef 00 10 00 02 00 00 00 00 00 00 a0 00 00:00:02.916 SET FEATURES [Enable SATA feature]
ec 00 00 00 00 00 00 00 00 00 00 a0 00 00:00:02.915 IDENTIFY DEVICE
c8 00 00 00 08 00 00 00 00 00 00 e0 00 00:00:02.901 READ DMA
ef 00 10 00 02 00 00 00 00 00 00 a0 00 00:00:02.900 SET FEATURES [Enable SATA feature]

Error 57581 [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.916 SET FEATURES [Enable SATA feature]
ec 00 00 00 00 00 00 00 00 00 00 a0 00 00:00:02.915 IDENTIFY DEVICE
c8 00 00 00 08 00 00 00 00 00 00 e0 00 00:00:02.901 READ DMA
ef 00 10 00 02 00 00 00 00 00 00 a0 00 00:00:02.900 SET FEATURES [Enable SATA feature]
ec 00 00 00 00 00 00 00 00 00 00 a0 00 00:00:02.900 IDENTIFY DEVICE

Error 57580 [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.901 READ DMA
ef 00 10 00 02 00 00 00 00 00 00 a0 00 00:00:02.900 SET FEATURES [Enable SATA feature]
ec 00 00 00 00 00 00 00 00 00 00 a0 00 00:00:02.900 IDENTIFY DEVICE
ef 00 03 00 46 00 00 00 00 00 00 a0 00 00:00:02.900 SET FEATURES [Set transfer mode]
ef 00 10 00 02 00 00 00 00 00 00 a0 00 00:00:02.900 SET FEATURES [Enable SATA feature]

Error 57579 [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.900 SET FEATURES [Enable SATA feature]
ec 00 00 00 00 00 00 00 00 00 00 a0 00 00:00:02.900 IDENTIFY DEVICE
ef 00 03 00 46 00 00 00 00 00 00 a0 00 00:00:02.900 SET FEATURES [Set transfer mode]
ef 00 10 00 02 00 00 00 00 00 00 a0 00 00:00:02.900 SET FEATURES [Enable SATA feature]
ec 00 00 00 00 00 00 00 00 00 00 a0 00 00:00:02.899 IDENTIFY DEVICE

Error 57578 [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.900 SET FEATURES [Set transfer mode]
ef 00 10 00 02 00 00 00 00 00 00 a0 00 00:00:02.900 SET FEATURES [Enable SATA feature]
ec 00 00 00 00 00 00 00 00 00 00 a0 00 00:00:02.899 IDENTIFY DEVICE
c8 00 00 00 08 00 00 00 00 00 00 e0 00 00:00:02.885 READ DMA
ef 00 10 00 02 00 00 00 00 00 00 a0 00 00:00:02.884 SET FEATURES [Enable SATA feature]

Error 57577 [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.900 SET FEATURES [Enable SATA feature]
ec 00 00 00 00 00 00 00 00 00 00 a0 00 00:00:02.899 IDENTIFY DEVICE
c8 00 00 00 08 00 00 00 00 00 00 e0 00 00:00:02.885 READ DMA
ef 00 10 00 02 00 00 00 00 00 00 a0 00 00:00:02.884 SET FEATURES [Enable SATA feature]
ec 00 00 00 00 00 00 00 00 00 00 a0 00 00:00:02.884 IDENTIFY DEVICE

Error 57576 [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.885 READ DMA
ef 00 10 00 02 00 00 00 00 00 00 a0 00 00:00:02.884 SET FEATURES [Enable SATA feature]
ec 00 00 00 00 00 00 00 00 00 00 a0 00 00:00:02.884 IDENTIFY DEVICE
ef 00 03 00 46 00 00 00 00 00 00 a0 00 00:00:02.884 SET FEATURES [Set transfer mode]
ef 00 10 00 02 00 00 00 00 00 00 a0 00 00:00:02.884 SET FEATURES [Enable SATA feature]

Error 57575 [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.884 SET FEATURES [Enable SATA feature]
ec 00 00 00 00 00 00 00 00 00 00 a0 00 00:00:02.884 IDENTIFY DEVICE
ef 00 03 00 46 00 00 00 00 00 00 a0 00 00:00:02.884 SET FEATURES [Set transfer mode]
ef 00 10 00 02 00 00 00 00 00 00 a0 00 00:00:02.884 SET FEATURES [Enable SATA feature]
ec 00 00 00 00 00 00 00 00 00 00 a0 00 00:00:02.883 IDENTIFY DEVICE

Error 57574 [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.884 SET FEATURES [Set transfer mode]
ef 00 10 00 02 00 00 00 00 00 00 a0 00 00:00:02.884 SET FEATURES [Enable SATA feature]
ec 00 00 00 00 00 00 00 00 00 00 a0 00 00:00:02.883 IDENTIFY DEVICE
c8 00 00 00 08 00 00 00 00 00 00 e0 00 00:00:02.861 READ DMA
ef 00 10 00 02 00 00 00 00 00 00 a0 00 00:00:02.860 SET FEATURES [Enable SATA feature]

Error 57573 [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.884 SET FEATURES [Enable SATA feature]
ec 00 00 00 00 00 00 00 00 00 00 a0 00 00:00:02.883 IDENTIFY DEVICE
c8 00 00 00 08 00 00 00 00 00 00 e0 00 00:00:02.861 READ DMA
ef 00 10 00 02 00 00 00 00 00 00 a0 00 00:00:02.860 SET FEATURES [Enable SATA feature]
ec 00 00 00 00 00 00 00 00 00 00 a0 00 00:00:02.860 IDENTIFY DEVICE

Error 57572 [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.861 READ DMA
ef 00 10 00 02 00 00 00 00 00 00 a0 00 00:00:02.860 SET FEATURES [Enable SATA feature]
ec 00 00 00 00 00 00 00 00 00 00 a0 00 00:00:02.860 IDENTIFY DEVICE
ef 00 03 00 46 00 00 00 00 00 00 a0 00 00:00:02.860 SET FEATURES [Set transfer mode]
ef 00 10 00 02 00 00 00 00 00 00 a0 00 00:00:02.860 SET FEATURES [Enable SATA feature]

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% 15554 -
# 2 Extended offline Aborted by host 90% 15554 -
# 3 Short offline Completed without error 00% 15554 -
# 4 Short offline Completed without error 00% 15554 -
# 5 Short offline Completed without error 00% 15553 -
# 6 Short offline Completed without error 00% 10690 -
# 7 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: 22 Celsius
Power Cycle Min/Max Temperature: 22/22 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 (49)

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

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 45 Vendor specific

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

Re: Data Recovery Issues on a 1TB Drive

#16 Post by Domenic » 22 May 2019, 18:09

Hi recuperation,

I was able to crop the pictures down so they fit...

GSmart Test Images:
GSmart Short 1.png
GSmart Short 1.png (41.29 KiB) Viewed 267 times
GSmart Short 2.png
GSmart Short 2.png (96.43 KiB) Viewed 267 times
GSmart Extended 1.png
GSmart Extended 1.png (79.33 KiB) Viewed 267 times

aleques
Posts: 1
Joined: 28 May 2019, 13:00

Re: Data Recovery Issues on a 1TB Drive

#17 Post by aleques » 28 May 2019, 13:07

Almost every software will start trying to read the device from sector 0 onwards, but some allow you to try the other way around (from end to start). If your damaged sectors are only at the start off the disk, you probably can get away with a dd rescue -R to another drive or file and then do the rest of forensics there,

I found myself there some years ago after a power failure. The interesting thing is that I managed to do a dd if=/dev/zero bs=512 count=1 of=/dev/affected-device and the read error was gone. I had to reconstruct the partition table from scratch and the mbr but the thing worked again (I then moved the data to a newer hd).

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

Re: Data Recovery Issues on a 1TB Drive

#18 Post by recuperation » 29 May 2019, 09:49

Hello Aleques,

this is an interesting finding, thanks for posting it.
I would personnally try out that hint but would not recommend it to others.

The drive in questions seems to fail already when running the IDENTIFY command.
It seems to loop that command, but the following post from Domenic is confusing:
Testdisk shows the drive but cannot analyze it, I get “Partition: Read Error”. I ran a quick scan and got read errors on what seemed like every cylinder.
If Testdisk shows the drive I assume the IDENTIFY command to be succesful.

Checking his log I found

199 UDMA_CRC_Error_Count -O--CK 200 200 000 - 1

which might indicate a cabling issue.

If that error happens repeatedly I expect the count to go up.

Domenic should test/replace the interface cables or try to run the drive from a different motherboard or from a different interface (USB p.e.) trying to exclude the possibility of an interface error.

There is no additional hint I could give now.

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

Re: Data Recovery Issues on a 1TB Drive

#19 Post by Domenic » 31 May 2019, 20:18

Hi everyone,

Thank you for your replies, I really appreciate all the help!

Recuperation,
Yesterday I ran a TESTDISK "Analyze" and got a "Partition: Read error" again.
I then ran the "Quick Search", it ran for 6hrs or so and only got to 3%, it again errored on every cylinder.
I stopped the "Quick Search" because the ATA Error Count jumped from 3,000 to 59,000 and I was concerned about the platter.
Im convinced the data is still there and didnt want to cause further problems.
The drive seems to be spinning up correctly, I had my ear to it for a few min and still shows no signs of physical damage.
I will upload the pictures after this post.

Also I have attempted to connect the drive to a different machine running Windows7, through my USB SATA interface and got the same I/O error.
I currently have the drive connected directly to the motherboard and getting the same results in Windows10 and Parted Magic as before.
I am going to attempt to switch the control board on the drive at some point over the next few days and will let you know how that goes.


Aleques,
I have tried to run DDRescue from both the start and from the end of the drive, both times it faild with the same error.
I will attempt again and upload the screenshot of the error because it does not creat a log.
I ran a passive scan in DDResue from end to start last night as well and it ran for 54min with 0%.
So I again aborted because I dont want to cause damage to the platter.
I will upload the screenshot after this post as well.

Also, I am by no means fully knowledgeable here.
I am not working directly in Linux, I am using Parted Magic with the tools built in.
The interesting thing is that I managed to do a dd if=/dev/zero bs=512 count=1 of=/dev/affected-device and the read error was gone
What does this command attdmpt to do?
Is it something I can do through one of the tools built into Parted Magic?

Thanks again everybody!

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

Re: Data Recovery Issues on a 1TB Drive

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

Partition Read Error:
Attachments
Partition Read error 1.png
Partition Read Error
Partition Read error 1.png (76.67 KiB) Viewed 202 times

Post Reply

Who is online

Users browsing this forum: No registered users and 2 guests