cgsecurity.org

I had two internal drives in my Dell XPS 8300 Desktop computer:

C: (my boot drive) 1.5 TB
K: (data storage drive) 1.5 TB

The non-boot drive (K:) experienced a failure of the MBR. It showed up as RAW (and not NTFS). I have since replaced it with a new 1TB internal SATA drive. I connected failed drive to a 3.0 USB port on the PC using an Orico USB3.0 3.5 inch SATA Hard Drive Enclosure. The testdisk.log reports the following:

filewin32_setfilepointer(\\.\PhysicalDrive7) SetFilePointer err Incorrect function.
Warning: can't get size for \\.\PhysicalDrive7

The external drive is 1500 GBytes.
Can testdisk_7.0 (testdisk_win.exe) be made to recognize this drive?
How can the files be restored from this old drive?

Did you use TestDisk 64bit?
TestDisk 7.1WIP is recommended.
Raw means, that a partition exists, but unformatted.
Cause can be either a boot sector problem or faulty file system.
Also you need the correct partition in your partition table.
Can you repeat your diagnose running Analyse, Quick and if nothing would be found Deeper Search also.
You should select your "Disk" instead of of drive?
If any partition is found, can you select ist and press p to have a try to list your files?
Can you copy and paste the content of your testdisk.log into your next post?

Fiona

Thank you for replying to my post. TestDisk 7.1-WIP shows only the following results:

Disk \\.\PhysicalDrive0 - 1500 GB / 1397 GiB - ST1500DM003 - 1CH16G
Disk \\.\PhysicalDrive1 - 1000 GB / 931 GIB - WDC WD10EZEX-00BN5A0
Disk \\.\PhysicalDrive4 - 3000 GB / 2794 GiB - Seagate Backup+ Disk
Drive D: - 555 MB /529 MiB - TSSTcorp DVD+-RW TS-H653J
Drive F: - 2999 GB /2793 GIB - Seagate Backup+ Disk

Physical Drive 0 is my 1.5 TB boot drive C:
Physical Drive 1 is a 1.0 TB secondary internal SATA drive that I added to replace the 1.5 TB drive that failed.
Physical Drive 4 is my external Backup drive
Drive D: is the DVD peripheral
Drive F: seems to be the same as Physical Drive 4 (I am not sure why).

I do not see the failed drive which is in an Orico 3588 Series USB3.0 3.5 inch SATA Hard DRive Enclosure attached to one of four (4) USB 3.0 ports. Note that Physical Drive 4 (Drive F:) is external and on another 3.0 USB port.
At this point the LOG file contains only the following:

Sun Jul 19 15:54:08 2015
Command line: TestDisk

TestDisk 7.1-WIP, Data Recovery Utility, May 2015
Christophe GRENIER <grenier@cgsecurity.org>
http://www.cgsecurity.org
OS: Windows 8 (9200)
Compiler: GCC 4.9, MinGW 3.11
ext2fs lib: none, ntfs lib: 10:0:0, reiserfs lib: none, ewf lib: 20120504, curses lib: pdcurses build 3401

Regards, Chuck (CTDeveloper)

Sry, I forgot to mention, did you use testdisk 7.1WIP 32bit.
Disk selection should look like:

Hard disk list
Disk /dev/sda - 1000 GB / 931 GiB - CHS 121601 255 63, sector size=512
Disk /dev/sdb - 1000 GB / 931 GiB - CHS 121601 255 63, sector size=512
Disk /dev/sdc - 3000 GB / 2794 GiB - CHS 45600 255 63, sector size=4096
Disk \\.\PhysicalDrive2 - 3000 GB / 2794 GiB - CHS 45600 255 63, sector size=4096
Drive C: - 981 GB / 913 GiB - CHS 119300 255 63, sector size=512
Drive E: - 320 GB / 298 GiB - CHS 38913 255 63, sector size=512
Drive F: - 3000 GB / 2794 GiB - CHS 45598 255 63, sector size=4096

TestDisk 64bit is only intended to run on genuine 64bit machines like Itanium with no 32bit emulation like WoW64, as some features are missing.

Note that Physical Drive 4 (Drive F:) is external and on another 3.0 USB port.
At this point the LOG file contains only the following:

Drive is not a disk and displays for example your current partition on your disk.
Can be used for fast boot sector diagnose but it has no partition table.
If you select it, testdisk will recognize partition table type None.

I do not see the failed drive which is in an Orico 3588 Series USB3.0 3.5 inch SATA Hard DRive Enclosure

To recover any data, your disk must be recognized correctly.
How ist your disk listed in your disk management console?

Fiona

Disk Management does not see the corrupted external drive (please see Capture.jpg - attached).

Did you already remove your disk out of its enclosure and test recognition in another enclosure and internally?
Is your disk listed in your device manager under disk drives correctly?
Did you already test another cable?
Does your BIOS/UEFI lists your disk correctly?

Fiona