Disk size seems too small; no recoverable partitions

How to use TestDisk to recover lost partition
Post Reply
Message
Author
zachiepie
Posts: 12
Joined: 08 Dec 2015, 04:27

Disk size seems too small; no recoverable partitions

#1 Post by zachiepie » 08 Dec 2015, 04:33

1TB western digital My Disk 3.0 external that displayed as Raw when I plugged it into my windows 7 machine. Worked fine before and no abnormal sounds like clicks. I ran it through test disk, and when I analized the disk it said the size "seemed too small" and it wasn't able to locate any partitions even through a Deep Search. Rewriting a new MBR didn't work either. I suspect I may need to change geometry, but I haven't done that before and need a few extra opinions! I'll attach the log.

If it makes a difference, I'm in the middle of trying to recover two other SATA internal 2.5" drives and this was my backup. 3 hard drive crashes in a year? Thanks, Western Digital.



Mon Dec 7 13:58:41 2015
Command line: TestDisk

TestDisk 7.0, Data Recovery Utility, April 2015
Christophe GRENIER <grenier@cgsecurity.org>
http://www.cgsecurity.org
OS: Windows 7 (7601) SP1
Compiler: GCC 4.8, Cygwin 1007.34
Compilation date: 2015-04-18T13:01:55
ext2fs lib: 1.42.8, ntfs lib: 10:0:0, reiserfs lib: 0.3.1-rc8, ewf lib: 20120504, curses lib: ncurses 5.9
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(/dev/sda)=1000204886016
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(/dev/sdb)=1000202043392
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\PhysicalDrive0)=1000204886016
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\PhysicalDrive1)=1000202043392
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\C:)=1000097185792
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:)=1000200994816
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 121600 255 63, sector size=512
Drive C: - 1000 GB / 931 GiB - CHS 121588 255 63, sector size=512
Drive E: - 1000 GB / 931 GiB - CHS 121600 255 63, sector size=512

Partition table type (auto): None
Drive E: - 1000 GB / 931 GiB
Partition table type: Intel

Analyse Drive E: - 1000 GB / 931 GiB - CHS 121600 255 63
Geometry from i386 MBR: head=102 sector=52
BAD_RS LBA=1920221984 1286028
check_part_i386 1 type 72: no test
BAD_RS LBA=1936028192 5737917
check_part_i386 2 type 6C: no test
Current partition structure:
1 P Sys=72 119528 74 3 232582 38 44 1816210284

Bad relative sector.
2 * Sys=6C 120512 46 15 242121 118 1 1953653108

Bad relative sector.
Space conflict between the following two partitions
1 P Sys=72 119528 74 3 232582 38 44 1816210284
2 * Sys=6C 120512 46 15 242121 118 1 1953653108

search_part()
Drive E: - 1000 GB / 931 GiB - CHS 121600 255 63
BAD_RS LBA=938751927 28956
check_part_i386 failed for partition type 0C
FAT32 LBA 58434 154 16 165423 242 29 1718783843
This partition ends after the disk limits. (start=938751927, size=1718783843, end=2657535769, disk end=1953517568)
NTFS at 121600/215/23
filesystem size 1953517568
sectors_per_cluster 8
mft_lcn 786432
mftmirr_lcn 2
clusters_per_mft_record -10
clusters_per_index_record 1
HPFS - NTFS 0 0 1 121600 215 23 1953517568
NTFS found using backup sector, blocksize=4096, 1000 GB / 931 GiB
Partition not added.
Drive E: - 1000 GB / 931 GiB - CHS 121600 255 63
Check the harddisk size: HD jumpers settings, BIOS detection...
The harddisk (1000 GB / 931 GiB) seems too small! (< 1360 GB / 1267 GiB)
The following partition can't be recovered:
FAT32 LBA 58434 154 16 165423 242 29 1718783843

Results

interface_write()

No partition found or selected for recovery

search_part()
Drive E: - 1000 GB / 931 GiB - CHS 121600 255 63
BAD_RS LBA=938751927 28956
check_part_i386 failed for partition type 0C
FAT32 LBA 58434 154 16 165423 242 29 1718783843
This partition ends after the disk limits. (start=938751927, size=1718783843, end=2657535769, disk end=1953517568)
NTFS at 109851/213/58
filesystem size 1764769792
sectors_per_cluster 8
mft_lcn 786432
mftmirr_lcn 2
clusters_per_mft_record -10
clusters_per_index_record 1
HPFS - NTFS 0 0 1 109851 213 58 1764769792
NTFS found using backup sector, blocksize=4096, 903 GB / 841 GiB
Partition not added.
NTFS at 121600/215/23
filesystem size 1953517568
sectors_per_cluster 8
mft_lcn 786432
mftmirr_lcn 2
clusters_per_mft_record -10
clusters_per_index_record 1
HPFS - NTFS 0 0 1 121600 215 23 1953517568
NTFS found using backup sector, blocksize=4096, 1000 GB / 931 GiB
Partition not added.
Drive E: - 1000 GB / 931 GiB - CHS 121600 255 63
Check the harddisk size: HD jumpers settings, BIOS detection...
The harddisk (1000 GB / 931 GiB) seems too small! (< 1360 GB / 1267 GiB)
The following partition can't be recovered:
FAT32 LBA 58434 154 16 165423 242 29 1718783843

Results

interface_write()

No partition found or selected for recovery
simulate write!

write_mbr_i386: starting...
write_all_log_i386: starting...
No extended partition

Interface Advanced
Geometry from i386 MBR: head=102 sector=52
BAD_RS LBA=1920221984 1286028
check_part_i386 1 type 72: no test
BAD_RS LBA=1936028192 5737917
check_part_i386 2 type 6C: no test
1 P Sys=72 119528 74 3 232582 38 44 1816210284
2 * Sys=6C 120512 46 15 242121 118 1 1953653108
Change partition type:
1 P Sys=72 119528 74 3 232582 38 44 1816210284
New options :
Dump : No
Align partition: Yes
Expert mode : No
A new copy of MBR code has been written.
You have to reboot for the change to take effect.

TestDisk exited normally.

Sponsored links

User avatar
cgrenier
Site Admin
Posts: 3629
Joined: 18 Feb 2012, 15:08
Location: Le Perreux Sur Marne, France
Contact:

Re: Disk size seems too small; no recoverable partitions

#2 Post by cgrenier » 09 Dec 2015, 21:04

Select Disk /dev/sdb, Advanced, Boot, RebuildBS. If you see your files, choose Write, confirm, Quit, restart your computer.

zachiepie
Posts: 12
Joined: 08 Dec 2015, 04:27

Re: Disk size seems too small; no recoverable partitions

#3 Post by zachiepie » 09 Dec 2015, 21:38

And if I can't see my files? (Can't open filesystem, filesystem seems damaged)

Post Reply

Who is online

Users browsing this forum: Google Adsense [Bot] and 3 guests