Need help recovering files from 1TB WD HDD - partition not found

Using PhotoRec to recover lost data
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
Hofi
Posts: 7
Joined: 28 Sep 2020, 19:35

Need help recovering files from 1TB WD HDD - partition not found

#1 Post by Hofi »

Hello everyone, I'd like to ask for help/guidance as I need to recover my data from the external WD 1TB HDD. The issue occurred after I unplugged the USB cable from the PC while uploading some files to the HDD. Below are some screenshots of my initial trouble-shooting. After running TestDisk quick search it seems that it cannot find any partition. I'd like to know if there is any chance of repairing the disk and getting access to the data or whether reformatting is the only option.

This is what happens everyime I plug the WD drive:

https://paste.pics/b4a736266d1537edcb5e8bb61e4a69bd

When I try to open the E: drive:
Location not available.PNG
Location not available.PNG (7.33 KiB) Viewed 1597 times
The HDD is recognized in the device manager:
Device Manager.PNG
Device Manager.PNG (19.28 KiB) Viewed 1597 times
And the disk is format is RAW according to the disk management:
Disk Management.PNG
Disk Management.PNG (63.75 KiB) Viewed 1597 times
After I run TestDisk and select the E: drive

https://paste.pics/1eb5ed707cc71366391c5782238a13bb

After the TestDrive Quick Search finished:

https://paste.pics/35e8ee6d069ceb1ae85f4773a5d50cfe

Logfile is full of "ReadFile The request failed due to a fatal device hardware error." I wanted to attach the log file here but cannot due to the .log being invalid file extension.
Last edited by Hofi on 28 Sep 2020, 21:20, edited 1 time in total.

Sponsored links

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

Re: Need help recovering files from 1TB WD HDD - partition not found

#2 Post by recuperation »

I can't see your pictures. Please upload them using the attachment tab below on the bottom of the page.

Hofi
Posts: 7
Joined: 28 Sep 2020, 19:35

Re: Need help recovering files from 1TB WD HDD - partition not found

#3 Post by Hofi »

recuperation wrote:
28 Sep 2020, 20:53
I can't see your pictures. Please upload them using the attachment tab below on the bottom of the page.
Hello, I was able to upload only 3 attachments. I fixed the URL links for rest of the screenshots in the original post.

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

Re: Need help recovering files from 1TB WD HDD - partition not found

#4 Post by recuperation »

Try renaming the log-extension into txt.


Please attach a logfile from smartmontools or simply post it here.

Use the command

smartctl -a /dev/sdX > C:\mylog.txt

to redirect the output of smartmontools into the file mylog.txt on your C-drive.
Replace X by the disc drive letter in question.
Use administrator rights for this operation.

Hofi
Posts: 7
Joined: 28 Sep 2020, 19:35

Re: Need help recovering files from 1TB WD HDD - partition not found

#5 Post by Hofi »

recuperation wrote:
28 Sep 2020, 21:56
Try renaming the log-extension into txt.


Please attach a logfile from smartmontools or simply post it here.

Use the command

smartctl -a /dev/sdX > C:\mylog.txt

to redirect the output of smartmontools into the file mylog.txt on your C-drive.
Replace X by the disc drive letter in question.
Use administrator rights for this operation.
Logs below:

smartctl 7.1 2019-12-30 r5022 [x86_64-w64-mingw32-w10-1909] (sf-7.1-1)
Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org

/dev/sde: Unable to detect device type
Please specify device type with the -d option.

Use smartctl -h to get a usage summary


still unable to attach the logs from the testdisk. File is now .txt however i receive the "Invalid file extension: testdisk.txt" while trying to upload it here. I just noticed it has 900+ Mb which might be the reason why. Adding the first few lines below. After while it keeps repeating the same error over and over again.


Fri Sep 25 18:03:32 2020
Command line: TestDisk

TestDisk 7.2-WIP, Data Recovery Utility, September 2020
Christophe GRENIER <grenier@cgsecurity.org>
https://www.cgsecurity.org
OS: Windows 8 (9200)
Compiler: GCC 9.3, Cygwin32 3001.4
ext2fs lib: 1.45.3, ntfs lib: 10:0:0, reiserfs lib: none, ewf lib: 20140608, curses lib: ncurses 6.1
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(/dev/sda)=128035676160
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(/dev/sdb)=1000204886016
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(/dev/sdc)=1000170586112
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\PhysicalDrive0)=128035676160
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\PhysicalDrive1)=1000204886016
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\PhysicalDrive2)=1000170586112
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\C:)=112652785664
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\D:)=1000168488960
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\E:)=1000168488960
Hard disk list
Disk /dev/sda - 128 GB / 119 GiB - CHS 15566 255 63, sector size=512 - TOSHIBA THNSNK128GVN8 M.2 2280 128GB, S/N:77DB611LKLMU, FW:K8DC4101
Disk /dev/sdb - 1000 GB / 931 GiB - CHS 121601 255 63, sector size=512 - TOSHIBA MQ01ABD100, S/N:87B3S5XTS, FW:AX0P3D
Disk /dev/sdc - 1000 GB / 931 GiB - CHS 121597 255 63, sector size=512 - WD My Passport 0748, S/N:WXB1E62NRN12, FW:1015

Partition table type defaults to Intel
Disk /dev/sdc - 1000 GB / 931 GiB - WD My Passport 0748
Partition table type: Intel

Analyse Disk /dev/sdc - 1000 GB / 931 GiB - CHS 121597 255 63
Current partition structure:

Partition: Read error

search_part()
Disk /dev/sdc - 1000 GB / 931 GiB - CHS 121597 255 63
file_pread(6,16,buffer,32(0/0/33)) ReadFile The request failed due to a fatal device hardware error.

file_pread(6,3,buffer,48(0/0/49)) ReadFile The request failed due to a fatal device hardware error.

file_pread(6,3,buffer,95(0/1/33)) ReadFile The request failed due to a fatal device hardware error.

file_pread(6,8,buffer,111(0/1/49)) ReadFile The request failed due to a fatal device hardware error.

file_pread(6,11,buffer,158(0/2/33)) ReadFile The request failed due to a fatal device hardware error.

file_pread(6,2,buffer,2080(0/33/2)) ReadFile The request failed due to a fatal device hardware error.

file_pread(6,2,buffer,51(0/0/52)) ReadFile The request failed due to a fatal device hardware error.

file_pread(6,2,buffer,98(0/1/36)) ReadFile The request failed due to a fatal device hardware error.

Hofi
Posts: 7
Joined: 28 Sep 2020, 19:35

Re: Need help recovering files from 1TB WD HDD - partition not found

#6 Post by Hofi »

I realized I did a mistake when running the smartmontools, I specified the disk incorrectly. I tried to run it again but now, for some reason the external HDD started to behave wierdly. When I plug it in, it takes quite some time for it to appear in "This PC", also when I try to right click the drive or run diskmgmt.msc it takes forever to load. When I unplug the HDD suddenly everything loads.

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

Re: Need help recovering files from 1TB WD HDD - partition not found

#7 Post by recuperation »

Please try out the additional -d parameter

smartctl -a -d,sat /dev/sdX > C:\mylog.txt

or the other -d parameter variants mentioned here:

https://www.smartmontools.org/wiki/USB

I suspect a hardware error that would require you contacting a professional recovery company.
But I would like to see the SMART parameters if they can be pulled out of the disc.

Hofi
Posts: 7
Joined: 28 Sep 2020, 19:35

Re: Need help recovering files from 1TB WD HDD - partition not found

#8 Post by Hofi »

Log below:

smartctl 7.1 2019-12-30 r5022 [x86_64-w64-mingw32-w10-1909] (sf-7.1-1)
Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family: Western Digital Elements / My Passport (USB, AF)
Device Model: WDC WD10TMVW-11ZSMS5
Serial Number: WD-WXB1E62NRN12
LU WWN Device Id: 5 0014ee 2074c7c28
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: 5200 rpm
Device is: In smartctl database [for details use: -P show]
ATA Version is: ATA8-ACS (minor revision not indicated)
SATA Version is: SATA 2.6, 3.0 Gb/s
Local Time is: Tue Sep 29 12:36:52 2020 CEDT
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART Status not supported: Incomplete response, ATA output registers missing
SMART overall-health self-assessment test result: PASSED
Warning: This result is based on an Attribute check.

General SMART Values:
Offline data collection status: (0x00) Offline data collection activity
was never started.
Auto Offline Data Collection: Disabled.
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: (25500) 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: ( 247) minutes.
Conveyance self-test routine
recommended polling time: ( 5) minutes.
SCT capabilities: (0x7035) 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 FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x002f 199 199 051 Pre-fail Always - 2492
3 Spin_Up_Time 0x0027 154 137 021 Pre-fail Always - 5266
4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 989
5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0
7 Seek_Error_Rate 0x002e 172 172 000 Old_age Always - 1943
9 Power_On_Hours 0x0032 099 099 000 Old_age Always - 1313
10 Spin_Retry_Count 0x0032 100 100 000 Old_age Always - 0
11 Calibration_Retry_Count 0x0032 100 100 000 Old_age Always - 0
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 661
192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 235
193 Load_Cycle_Count 0x0032 199 199 000 Old_age Always - 4450
194 Temperature_Celsius 0x0022 122 099 000 Old_age Always - 28
196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0
197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 4
198 Offline_Uncorrectable 0x0030 100 253 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0
200 Multi_Zone_Error_Rate 0x0008 100 253 000 Old_age Offline - 0

SMART Error Log Version: 1
ATA Error Count: 256 (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 256 occurred at disk power-on lifetime: 1313 hours (54 days + 17 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 00

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
e1 00 02 00 00 00 00 00 00:07:29.549 IDLE IMMEDIATE
ec 00 01 00 00 00 00 00 00:07:29.542 IDENTIFY DEVICE
e1 00 0f 00 00 00 00 00 00:07:27.542 IDLE IMMEDIATE
e1 00 02 00 00 00 00 00 00:07:26.898 IDLE IMMEDIATE
ec 00 01 00 00 00 00 00 00:07:26.891 IDENTIFY DEVICE

Error 255 occurred at disk power-on lifetime: 1313 hours (54 days + 17 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 0f 00 00 00 00

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
e1 00 0f 00 00 00 00 00 00:07:27.542 IDLE IMMEDIATE
e1 00 02 00 00 00 00 00 00:07:26.898 IDLE IMMEDIATE
ec 00 01 00 00 00 00 00 00:07:26.891 IDENTIFY DEVICE

Error 254 occurred at disk power-on lifetime: 1313 hours (54 days + 17 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 00

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
e1 00 02 00 00 00 00 00 00:07:26.898 IDLE IMMEDIATE
ec 00 01 00 00 00 00 00 00:07:26.891 IDENTIFY DEVICE

Error 253 occurred at disk power-on lifetime: 1313 hours (54 days + 17 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 00

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
e1 00 02 00 00 00 00 00 00:06:19.018 IDLE IMMEDIATE
ec 00 01 00 00 00 00 00 00:06:19.011 IDENTIFY DEVICE
e1 00 0f 00 00 00 00 00 00:06:16.980 IDLE IMMEDIATE
e1 00 02 00 00 00 00 00 00:06:16.311 IDLE IMMEDIATE
ec 00 01 00 00 00 00 00 00:06:16.304 IDENTIFY DEVICE

Error 252 occurred at disk power-on lifetime: 1313 hours (54 days + 17 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 0f 00 00 00 00

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
e1 00 0f 00 00 00 00 00 00:06:16.980 IDLE IMMEDIATE
e1 00 02 00 00 00 00 00 00:06:16.311 IDLE IMMEDIATE
ec 00 01 00 00 00 00 00 00:06:16.304 IDENTIFY DEVICE

SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Short offline Interrupted (host reset) 10% 1300 -
# 2 Short offline Interrupted (host reset) 10% 1300 -
# 3 Conveyance offline Completed: read failure 90% 1256 6266664
# 4 Conveyance offline Completed without error 00% 609 -

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.

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

Re: Need help recovering files from 1TB WD HDD - partition not found

#9 Post by recuperation »

I just see 4 pending sectors and a statement I do not understand:
# 3 Conveyance offline Completed: read failure 90% 1256 6266664
The smart log does not look threatening to me.

Please try to duplicate the drive as described in the testdisk manual

https://www.cgsecurity.org/testdisk.pdf

and see how ddrescue reacts.

Hofi
Posts: 7
Joined: 28 Sep 2020, 19:35

Re: Need help recovering files from 1TB WD HDD - partition not found

#10 Post by Hofi »

So I got Ubuntu live on USB and attempted to create an image from the faulty external HDD. I am creating the .img file on my second internal storage which is freshly formatted 1TB Toshiba HDD.
I kept the ddrescue running for a while and the remaining time grew up to 700+ days. Now is around 1000 days :shock: I don't feel like keeping this running. Is there any way i can make this run faster? use some specific parameters e.g. -n - no-trimming?

ubuntu@ubuntu:/media/WDImage$ sudo ddrescue /dev/sdd wd.img wd.log
GNU ddrescue 1.23
Press Ctrl-C to interrupt
ipos: 750452 kB, non-trimmed: 233472 B, current rate: 0 B/s
opos: 750452 kB, non-scraped: 0 B, average rate: 757 kB/s
non-tried: 999570 MB, bad-sector: 0 B, error rate: 0 B/s
rescued: 599814 kB, bad areas: 0, run time: 13m 11s
pct rescued: 0.05%, read errors: 4, remaining time: 713d 22h
time since last successful read: 0s


**EDIT**
I wasn't sure whether I should create an image from the faulty drive or perform full disk to disk copy. Please let me know what is the case here.

Locked