Page 1 of 1

TestDisk can't find partitions/Log not opening

Posted: 13 Apr 2020, 21:35
by JamesMaguire
I have been trying to recover data off my external hard drive, but TestDisk cannot find a partition (with both scans) and PhotoRec is not working as well. Because the drive is 1TB, the log file is over 1.65 GB and freezes any document reader. I've been trying anything for about a week now, so any help would be greatly appreciated.

Re: TestDisk can't find partitions/Log not opening

Posted: 14 Apr 2020, 15:09
by cgrenier
Did you get error message while scanning with testdisk or photorec ?

Re: TestDisk can't find partitions/Log not opening

Posted: 15 Apr 2020, 05:12
by JamesMaguire
No errors, just no found partitions (damaged or otherwise).

Re: TestDisk can't find partitions/Log not opening

Posted: 15 Apr 2020, 20:14
by recuperation
I guess your Testdisk log file is full of read errors!
Try to open up your big log file with a hex editor that will only read parts of your file and try to screenshot or write down the asumably repeating messages.
Another way is use any programming language and read the first 10k bytes of the logfile and write them into a new shortened logfile that can be easily opened with a standard editor.

Re: TestDisk can't find partitions/Log not opening

Posted: 15 Apr 2020, 20:37
by JamesMaguire
That was able to read it. Thanks.
It starts with

Code: Select all

Sun Apr 12 12:58:29 2020
Command line: TestDisk

TestDisk 7.2-WIP, Data Recovery Utility, January 2020
Christophe GRENIER <grenier@cgsecurity.org>
https://www.cgsecurity.org
OS: Windows 8 (9200)
Compiler: GCC 7.4, Cygwin32 3000.3
ext2fs lib: 1.45.3, ntfs lib: 10:0:0, reiserfs lib: none, ewf lib: 20140608, curses lib: ncurses 6.0
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(/dev/sda)=500107862016
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(/dev/sdb)=2000365289472
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(/dev/sdg)=1000204886016
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\PhysicalDrive0)=500107862016
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\PhysicalDrive1)=2000365289472
filewin32_getfilesize(\\.\PhysicalDrive2) GetFileSize err Incorrect function.

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

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

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

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

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

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

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

Warning: can't get size for \\.\PhysicalDrive5
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\PhysicalDrive6)=1000204886016
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\C:)=484162142208
filewin32_getfilesize(\\.\D:) GetFileSize err Incorrect function.

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

Warning: can't get size for \\.\D:
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\E:)=0
Warning: can't get size for \\.\E:
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\F:)=0
Warning: can't get size for \\.\F:
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\G:)=0
Warning: can't get size for \\.\G:
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\H:)=0
Warning: can't get size for \\.\H:
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\I:)=2000363192320
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\J:)=15902703616
Hard disk list
Disk /dev/sda - 500 GB / 465 GiB - CHS 60801 255 63, sector size=512 - WDC WD5000AAKX-753CA1, S/N:WD-WCAYUHH35639, FW:19.01H19
Disk /dev/sdb - 2000 GB / 1862 GiB - CHS 243197 255 63, sector size=512 - WD easystore 2625, S/N:WX21E994XE0K, FW:1026
Disk /dev/sdg - 1000 GB / 931 GiB - CHS 121601 255 63, sector size=512 - TOSHIBA External USB 3.0, S/N:C95120062805102

Partition table type defaults to Intel
Disk /dev/sdg - 1000 GB / 931 GiB - TOSHIBA External USB 3.0
Partition table type: Intel

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

Partition: Read error

search_part()
Disk /dev/sdg - 1000 GB / 931 GiB - CHS 121601 255 63Results

interface_write()
 
No partition found or selected for recovery
simulate write!

write_mbr_i386: starting...
Then, it's full of "ReadFile Data error (cyclic redundancy check)" and "ReadFile A device which does not exist was specified" More of the latter.
It ends with:

Code: Select all

Results

interface_write()
 
No partition found or selected for recovery
simulate write!

write_mbr_i386: starting...
file_pread(5,1,buffer,0(0/0/1)) ReadFile A device which does not exist was specified.


Partition: Read error
Store new MBR code
write_all_log_i386: starting...
No extended partition

Interface Advanced

TestDisk exited normally.

Re: TestDisk can't find partitions/Log not opening

Posted: 15 Apr 2020, 20:47
by recuperation
Unfortunately, this is a case for a professional data recovery company.

Re: TestDisk can't find partitions/Log not opening

Posted: 15 Apr 2020, 21:05
by JamesMaguire
I was afraid of that.
Is there any pertinent information I can give them?

Re: TestDisk can't find partitions/Log not opening

Posted: 16 Apr 2020, 06:47
by recuperation
JamesMaguire wrote: 15 Apr 2020, 21:05 I was afraid of that.
Is there any pertinent information I can give them?
A general error description perhaps?
Information about the partition layout and file systems used could be helpful.
I guess they will ask you when they need information.

Re: TestDisk can't find partitions/Log not opening

Posted: 16 Apr 2020, 08:02
by JamesMaguire
recuperation wrote: 16 Apr 2020, 06:47
JamesMaguire wrote: 15 Apr 2020, 21:05 I was afraid of that.
Is there any pertinent information I can give them?
A general error description perhaps?
Information about the partition layout and file systems used could be helpful.
I guess they will ask you when they need information.
Oh, I meant if anything from the log revealed any specific reason for the problem.
Regardless, thank you both for the help.