Cannot recover. Used space is more than available space.

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
Khronos
Posts: 1
Joined: 20 Apr 2015, 00:23

Cannot recover. Used space is more than available space.

#1 Post by Khronos »

Hello,

I recently tried to resize an NTFS partition using Paragon Partition Manager but in the end it corrupted the filesystem. Windows now says that it's unformatted.

When I first ran Testdisk, it said there was no partition table and that both boot sectors (backup and main) were bad. I tried to rebuild the MBR however the scan never finished. Once it got to the end it simply started again.

I then tried using the GFT partition table since that's what it should have. However after writing it to the disk, Windows still can't open the partition and still says it's not formatted.

I then tried the Intel partition table without any luck.

I think it may be because Testdisk detects that the amount of used space is more than the amount of space available.

Does anyone have any ideas?

Code: Select all

 

Mon Apr 20 06:45:18 2015
Command line: TestDisk

TestDisk 7.0, Data Recovery Utility, April 2015
Christophe GRENIER <grenier@cgsecurity.org>
http://www.cgsecurity.org
OS: Windows 8 (9200)
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)=128035676160
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(/dev/sdc)=3000592982016
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\PhysicalDrive0)=1000204886016
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\PhysicalDrive1)=128035676160
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\PhysicalDrive2)=3000592982016
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\C:)=128033226752
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\D:)=2916698030080
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\E:)=1000096137216
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\F:)=104857600
Hard disk list
Disk /dev/sda - 1000 GB / 931 GiB - CHS 121601 255 63, sector size=512
Disk /dev/sdb - 128 GB / 119 GiB - CHS 15566 255 63, sector size=512
Disk /dev/sdc - 3000 GB / 2794 GiB - CHS 364801 255 63, sector size=512
Drive C: - 128 GB / 119 GiB - CHS 15565 255 63, sector size=512
Drive D: - 2916 GB / 2716 GiB - CHS 354601 255 63, sector size=512
Drive E: - 1000 GB / 931 GiB - CHS 121588 255 63, sector size=512
Drive F: - 104 MB / 100 MiB - CHS 12 255 63, sector size=512

Partition table type (auto): EFI GPT
Drive D: - 2916 GB / 2716 GiB
Partition table type: Intel

Analyse Drive D: - 2916 GB / 2716 GiB - CHS 354601 255 63
Geometry from i386 MBR: head=255 sector=63
NTFS at 0/32/33
Error: size boot_sector 1401708544 > partition 4294967295
check_part_i386 failed for partition type 07
Current partition structure:
Error: size boot_sector 1401708544 > partition 4294967295
Invalid NTFS or EXFAT boot
 1 * HPFS - NTFS              0  32 33 267349 121 35 4294967295
 1 * HPFS - NTFS              0  32 33 267349 121 35 4294967295

search_part()
Drive D: - 2916 GB / 2716 GiB - CHS 354601 255 63
NTFS at 0/32/33
filesystem size           5696675840
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 354601 203 34 5696675840
     NTFS, blocksize=4096, 2916 GB / 2716 GiB

Results
   * HPFS - NTFS              0  32 33 354601 203 34 5696675840
     NTFS, blocksize=4096, 2916 GB / 2716 GiB

interface_write()
 1 * HPFS - NTFS              0  32 33 354601 203 34 5696675840
write!

write_mbr_i386: starting...
write_all_log_i386: starting...
No extended partition
You will have to reboot for the change to take effect.
A new copy of MBR code has been written.
You have to reboot for the change to take effect.
Partition table type (auto): EFI GPT
Drive D: - 2916 GB / 2716 GiB
Partition table type: EFI GPT
Partition table type (auto): EFI GPT
Drive D: - 2916 GB / 2716 GiB
Partition table type: EFI GPT

Analyse Drive D: - 2916 GB / 2716 GiB - CHS 354601 255 63
hdr_size=92
hdr_lba_self=1
hdr_lba_alt=5696675839 (expected 5696675839)
hdr_lba_start=34
hdr_lba_end=5696675806
hdr_lba_table=2
hdr_entries=128
hdr_entsz=128
Current partition structure:
 1 P MS Data                     2048 5696677887 5696675840

search_part()
Drive D: - 2916 GB / 2716 GiB - CHS 354601 255 63
NTFS at 0/32/33
filesystem size           5696675840
sectors_per_cluster       8
mft_lcn                   786432
mftmirr_lcn               2
clusters_per_mft_record   -10
clusters_per_index_record 1
NTFS part_offset=1048576, part_size=2916698030080, sector_size=512
NTFS partition cannot be added (part_offset<part_size).
NTFS at 0/32/33
filesystem size           5696675840
sectors_per_cluster       8
mft_lcn                   786432
mftmirr_lcn               2
clusters_per_mft_record   -10
clusters_per_index_record 1
     MS Data                     2048 5696677887 5696675840
     NTFS, blocksize=4096, 2916 GB / 2716 GiB

Results
   P MS Data                     2048 5696677887 5696675840
     NTFS, blocksize=4096, 2916 GB / 2716 GiB

interface_write()
 1 P MS Data                     2048 5696677887 5696675840
 

User avatar
Fiona
Posts: 2835
Joined: 18 Feb 2012, 17:19
Location: Ludwigsburg/Stuttgart - Germany

Re: Cannot recover. Used space is more than available space.

#2 Post by Fiona »

Analyse Drive D: - 2916 GB / 2716 GiB - CHS 354601 255 63
Would it be possible to repeat your diagnose and selecting disk instead of your drive?
Drive is only your partition.
MBR is located on your disk and not within a partition.
Practically the first physically executable sector of your disk.
Please let me know if this is working for you?
In case, copy and paste the content of your testdisk.log.

Fiona

Locked