Recently I had a 1.5TB USB 3.0 disk "go bad." It had become a "RAW" disk. I tried TestDisk and it successfully wrote the partition and, after the reboot and chkdsk run, my disk and all of my data was recovered. Great experience!
Now, I've had the same thing happen to another disk, also a 1.5TB USB 3.0 external disk. This time, however, the Write option fails with "Write Error"
Here is the log file:
--> START
Mon Oct 23 08:24:41 2017
Command line: TestDisk
TestDisk 7.1-WIP, Data Recovery Utility, July 2017
Christophe GRENIER <grenier@cgsecurity.org>
http://www.cgsecurity.org
OS: Windows 7 (7601) SP1
Compiler: GCC 5.4, Cygwin 2005.2
ext2fs lib: 1.43.1, 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)=1000204886016
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(/dev/sde)=1500301910016
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\PhysicalDrive0)=1000204886016
filewin32_getfilesize(\\.\PhysicalDrive1) GetFileSize err Incorrect function.
filewin32_setfilepointer(\\.\PhysicalDrive1) SetFilePointer err Incorrect function.
Warning: can't get size for \\.\PhysicalDrive1
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
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\PhysicalDrive4)=1500301910016
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\C:)=322122547200
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\D:)=300647710720
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\E:)=322122547200
filewin32_getfilesize(\\.\F:) GetFileSize err Incorrect function.
filewin32_setfilepointer(\\.\F:) SetFilePointer err Incorrect function.
Warning: can't get size for \\.\F:
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\J:)=0
Warning: can't get size for \\.\J:
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\K:)=0
Warning: can't get size for \\.\K:
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\N:)=0
Warning: can't get size for \\.\N:
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\P:)=1500299395072
Hard disk list
Disk /dev/sda - 1000 GB / 931 GiB - CHS 121601 255 63, sector size=512 - ST1000LM014-1EJ164, S/N:202020202020202020202020335731384a573047, FW:SM16
Disk /dev/sde - 1500 GB / 1397 GiB - CHS 182401 255 63, sector size=512 - TOSHIBA MQ01ABC150, S/N:2020202020202020202059204f32504c51365430, FW:AQF01U
Partition table type (auto): Intel
Disk /dev/sde - 1500 GB / 1397 GiB - TOSHIBA MQ01ABC150
Partition table type: Intel
Analyse Disk /dev/sde - 1500 GB / 1397 GiB - CHS 182401 255 63
Geometry from i386 MBR: head=255 sector=63
NTFS at 0/32/33
Current partition structure:
1 P HPFS - NTFS 0 32 33 182401 35 34 2930272256 [Sony USB]
No partition is bootable
search_part()
Disk /dev/sde - 1500 GB / 1397 GiB - CHS 182401 255 63
NTFS at 0/32/33
filesystem size 2930272256
sectors_per_cluster 8
mft_lcn 786432
mftmirr_lcn 2
clusters_per_mft_record -10
clusters_per_index_record 1
HPFS - NTFS 0 32 33 182401 35 34 2930272256 [Sony USB]
NTFS, blocksize=4096, 1500 GB / 1397 GiB
file_pread(5,2,buffer,2930278399(182401/100/35)) lseek err Invalid argument
file_pread(5,1,buffer,2930278399(182401/100/35)) lseek err Invalid argument
file_pread(5,2,buffer,2930278400(182401/100/36)) lseek err Invalid argument
file_pread(5,8,buffer,2930277248(182401/82/18)) lseek err Invalid argument
file_pread(5,1,buffer,2930277248(182401/82/18)) lseek err Invalid argument
file_pread(5,8,buffer,2930277376(182401/84/20)) lseek err Invalid argument
file_pread(5,8,buffer,2930277504(182401/86/22)) lseek err Invalid argument
file_pread(5,8,buffer,2930277632(182401/88/24)) lseek err Invalid argument
file_pread(5,8,buffer,2930277760(182401/90/26)) lseek err Invalid argument
file_pread(5,8,buffer,2930277888(182401/92/28)) lseek err Invalid argument
file_pread(5,8,buffer,2930278016(182401/94/30)) lseek err Invalid argument
file_pread(5,8,buffer,2930278144(182401/96/32)) lseek err Invalid argument
file_pread(5,8,buffer,2930278272(182401/98/34)) lseek err Invalid argument
file_pread(5,6,buffer,2930278402(182401/100/38)) lseek err Invalid argument
file_pread(5,2,buffer,2930278400(182401/100/36)) lseek err Invalid argument
file_pread(5,8,buffer,2930278408(182401/100/44)) lseek err Invalid argument
file_pread(5,3,buffer,2930278416(182401/100/52)) lseek err Invalid argument
file_pread(5,3,buffer,2930278463(182401/101/36)) lseek err Invalid argument
file_pread(5,8,buffer,2930278479(182401/101/52)) lseek err Invalid argument
file_pread(5,11,buffer,2930278526(182401/102/36)) lseek err Invalid argument
file_pread(5,2,buffer,2930280448(182401/133/5)) lseek err Invalid argument
Results
* HPFS - NTFS 0 32 33 182401 35 34 2930272256 [Sony USB]
NTFS, blocksize=4096, 1500 GB / 1397 GiB
interface_write()
1 * HPFS - NTFS 0 32 33 182401 35 34 2930272256 [Sony USB]
write!
write_mbr_i386: starting...
file_pwrite(5,1,buffer,0(0/0/1)) write err Input/output error
write_all_log_i386: starting...
No extended partition
Partition: Write error
TestDisk exited normally.
--> END
Any ideas?
Thank you for any help you can offer.
Charles.
TestDisk "Write Error"
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
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
- cgrenier
- Site Admin
- Posts: 5432
- Joined: 18 Feb 2012, 15:08
- Location: Le Perreux Sur Marne, France
- Contact:
Re: TestDisk "Write Error"
Can you try TestDisk, Advanced, Boot, RebuildBS, List ? If you can see your files, choose Write, confirm, Quit and restart your computer.
Please post the new log file if it doesn't work.
Please post the new log file if it doesn't work.