Nothing found, now what

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
Locked
Message
Author
Arogen
Posts: 2
Joined: 09 Apr 2021, 13:47

Nothing found, now what

#1 Post by Arogen »

OS: Windows 7
Hard drive: Western Digital 4TB drive, connected by USB dock
How it went bad: Tried to copy a large folder from my PC over onto the drive, after a while it popped up a error saying a sub folder I was trying to copy over was corrupted so I canceled the whole copy operation. Then I got the message that the drive I was copying to needed to be formatted and I see no partition on it. The folder it said was corrupted on the source drive appears to be fine and I was able to copy everything to another internally connected drive without issue.

I assume the partition or file system info is messed up, but the files should still be there.

In testdisk I do a quick scan and no partitions are listed in the results.
The logs has lseek err Invalid arguments in the search. Here is the whole log. Where do I go from here?


Code: Select all

Thu Apr  8 17:57:56 2021
Command line: TestDisk

TestDisk 7.2-WIP, Data Recovery Utility, March 2021
Christophe GRENIER <grenier@cgsecurity.org>
https://www.cgsecurity.org
OS: Windows 7 (7601) SP1
Compiler: GCC 9.3, Cygwin 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)=4000787030016
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(/dev/sdb)=2000398934016
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(/dev/sdc)=3000592982016
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(/dev/sdd)=4000787029504
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(/dev/sde)=15502147584
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\PhysicalDrive0)=4000787030016
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\PhysicalDrive1)=2000398934016
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\PhysicalDrive2)=3000592982016
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\PhysicalDrive3)=4000787029504
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\PhysicalDrive4)=15502147584
filewin32_getfilesize(\\.\PhysicalDrive5) GetFileSize err Incorrect function.

filewin32_setfilepointer(\\.\PhysicalDrive5) SetFilePointer err Incorrect function.

Warning: can't get size for \\.\PhysicalDrive5
filewin32_getfilesize(\\.\PhysicalDrive6) GetFileSize err Incorrect function.

filewin32_setfilepointer(\\.\PhysicalDrive6) SetFilePointer err Incorrect function.

Warning: can't get size for \\.\PhysicalDrive6
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\C:)=1000202377728
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\D:)=1932735283200
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\E:)=2068049821696
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\H:)=3000457232384
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\J:)=15498018816
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\W:)=1000194703360
filewin32_getfilesize(\\.\Z:) GetFileSize err Incorrect function.

filewin32_setfilepointer(\\.\Z:) SetFilePointer err Incorrect function.

Warning: can't get size for \\.\Z:
Hard disk list
Disk /dev/sda - 4000 GB / 3726 GiB - CHS 486401 255 63, sector size=512 - WDC WD40EZRZ-00GXCB0, S/N:2020202057202d4443573743354b4148395a3259, FW:80.00A80
Disk /dev/sdb - 2000 GB / 1863 GiB - CHS 243201 255 63, sector size=512 - WDC WD20EZAZ-00GGJB0, S/N:2020202057202d44585731504341333859584444, FW:80.00A80
Disk /dev/sdc - 3000 GB / 2794 GiB - CHS 364801 255 63, sector size=512 - WDC WD30EZRX-00D8PB0, S/N:2020202057202d444d573443324e393231383530, FW:80.00A80
Disk /dev/sdd - 4000 GB / 3726 GiB - CHS 486401 255 63, sector size=512 - Initio INIC-1610P, S/N:WD-WCC4E1YTRNT1, FW:2.02
Disk /dev/sde - 15 GB / 14 GiB - CHS 1884 255 63, sector size=512 - Kingston DataTraveler 3.0, S/N:6B02A34145C9, FW:PMAP

Partition table type (auto): Intel
Disk /dev/sdd - 4000 GB / 3726 GiB - Initio INIC-1610P
Partition table type: Intel

Analyse Disk /dev/sdd - 4000 GB / 3726 GiB - CHS 486401 255 63
Geometry from i386 MBR: head=256 sector=63
check_part_i386 1 type EE: no test
Current partition structure:
 1 P EFI GPT                  0   0  2 267349  89  4 4294967295

Warning: Bad ending head (CHS and LBA don't match)
No partition is bootable

search_part()
Disk /dev/sdd - 4000 GB / 3726 GiB - CHS 486401 255 63
file_pread(7,2,buffer,7814037503(486401/86/21)) lseek err Invalid argument
file_pread(7,1,buffer,7814037503(486401/86/21)) lseek err Invalid argument
file_pread(7,2,buffer,7814037504(486401/86/22)) lseek err Invalid argument
file_pread(7,14,buffer,7814037506(486401/86/24)) lseek err Invalid argument
file_pread(7,3,buffer,7814037520(486401/86/38)) lseek err Invalid argument
file_pread(7,3,buffer,7814037567(486401/87/22)) lseek err Invalid argument
file_pread(7,8,buffer,7814037583(486401/87/38)) lseek err Invalid argument
file_pread(7,11,buffer,7814037630(486401/88/22)) lseek err Invalid argument
file_pread(7,2,buffer,7814039552(486401/118/54)) lseek err Invalid argument

Results

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

Re: Nothing found, now what

#2 Post by recuperation »

What is the sector size marked on your drive pluggged into the docking station?
If it's 512 byte then your partition tabel style will be GPT, not MBR.

Check health like here:
viewtopic.php?p=33716#p33716
Post the smartmontools log file here. Use the attachment tab on the bottom of the page!

When running Testdisk use GPT, continue using deep search, examine all selected partitions with the p-key for content.

Arogen
Posts: 2
Joined: 09 Apr 2021, 13:47

Re: Nothing found, now what

#3 Post by Arogen »

I started over doing a scan selecting GPT and it is staking 3-4s for one cylinder. At this rate it will take over 22 days to finish. This isn't normal, is it?

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

Re: Nothing found, now what

#4 Post by recuperation »

Arogen wrote: 09 Apr 2021, 18:45 I started over doing a scan selecting GPT and it is staking 3-4s for one cylinder. At this rate it will take over 22 days to finish. This isn't normal, is it?
No, it's not. Stop it. Disconnect it and flush your drive down the toilet or bring it to a professional recovery service.
Honestly, what's the point? What would you do if I said that it's not normal?

9.4.2021 21:10 MESZ added the following:

After thinking about the perfect answer to that repeating question I found the following:

"Normal" is the sustained linear reading rate of the drive assuming there is no further bottleneck.
Please check your drive documentation do learn about normality for your drive.
Many factors could affect transfer speed:
  • possible dammage of your drive
  • interface problems
  • computer (mainboard) problems
  • operating system problems
You can try to eliminate point 2-4 by using a clean install on a healthy machine.
But even then you can suffer from point 1.

It is your decision to decide about continuing the recovery process or not.

Locked