1

Topic: SOLVED - [ Current NTFS volume size is bigger than the device size! ]

Here are the specifics on another one -- Fedora 11 distribution.
Just 1 windows partition on hard drive. Tried to open it up for a nix dual boot install.
Didn't work out like I expected.

Please help. Thanks.

[ 20091114.145259 ] AVILA { /root }

++ ntfsresize --info --force /dev/sda1

ntfsresize v2.0.0 (libntfs 10:0:0)
Device name        : /dev/sda1
NTFS volume version: 3.1
Cluster size       : 4096 bytes
Current volume size: 160029995520 bytes (160030 MB)
Current device size: 125788158464 bytes (125789 MB)
ERROR: Current NTFS volume size is bigger than the device size!
Corrupt partition table or incorrect device partitioning?

++ fdisk -l -u

Disk /dev/sda: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders, total 312581808 sectors
Units = sectors of 1 * 512 = 512 bytes
Disk identifier: 0x27002700

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *        2048   245682044   122839998+   7  HPFS/NTFS

Disk /dev/sdb: 16.0 GB, 16039018496 bytes
255 heads, 63 sectors/track, 1949 cylinders, total 31326208 sectors
Units = sectors of 1 * 512 = 512 bytes
Disk identifier: 0x000c07ab

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1   *          63      524350      262144   83  Linux
Partition 1 does not end on cylinder boundary.
/dev/sdb2          524351    27214684    13345167   83  Linux
/dev/sdb3        27214685    31310684     2048000   83  Linux

++ parted /dev/sda unit s print

Model: ATA TOSHIBA MK1655GS (scsi)
Disk /dev/sda: 312581808s
Sector size (logical/physical): 512B/512B
Partition Table: msdos

Number  Start  End         Size        Type     File system  Flags
1      2048s  245682044s  245679997s  primary  ntfs         boot

++ uname -a

Linux AVILA 2.6.30.9-96.fc11.i586 #1 SMP Tue Nov 3 23:33:04 EST 2009 i686 i686 i386 GNU/Linux

[ 20091114.145313 ] AVILA { /root }
#

2

Re: SOLVED - [ Current NTFS volume size is bigger than the device size! ]

Thank you namrokretep for creating a new post for your situation.  I have deleted the other posts.

To solve the problem we will also need a copy of the Master Boot Record, and the NTFS Partition Boot Record.


You can capture the Master Boot Record in a file with the following command:

NOTE:  Be extra careful to type this command in properly, otherwise loss of data could result.

dd if=/dev/sda of=sda-namrokretep.mbr bs=512 count=1

where sda-namrokretep.mbr is the name of the file that will need to be uploaded.


You can capture the NTFS Partition Boot Record in a file with the following command:

NOTE:  Be extra careful to type this command in properly, otherwise loss of data could result.

dd if=/dev/sda of=sda1-namrokretep.pbr bs=512 count=1 skip=2048

where sda1-namrokretep.pbr is the name of the file that will need to be uploaded.


Then upload these files to a media sharing site, such as mediafire, and post the link to these files in this forum post.

3

Re: SOLVED - [ Current NTFS volume size is bigger than the device size! ]

gedakc wrote:

mediafire

http://www.mediafire.com/file/krglzmaok … kretep.pbr
http://www.mediafire.com/file/n0tc4oe1m … kretep.mbr

Thanks.

4

Re: SOLVED - [ Current NTFS volume size is bigger than the device size! ]

BTW I did not even try to type the dd line. Cut/Paste is only game in town.

5

Re: SOLVED - [ Current NTFS volume size is bigger than the device size! ]

In this situation I think the best option is to increase the partition size to encompass the whole NTFS file system.

The change I have made to the file is from a length of 245,679,997 sectors:
000001C0   21 00 07 FE  FF FF 00 08  00 00 7D C7  A4 0E 00 00
To a new length of 312,558,585 sectors:
000001C0   21 00 07 FE  FF FF 00 08  00 00 F9 43  A1 12 00 00

Note:  The NTFS volume size is always 1 sector less than the total number of sectors in the partition table entry because the NTFS backup sector is not considered part of the NTFS volume.

To apply this change:

1) Download the new MBR: sda-namrokretep_new.mbr

2) Load the new MBR on your hard disk.
NOTE:  Be extra careful when entering the commands.  Data loss could result otherwise.

dd if=sda-namrokretep_new.mbr of=/dev/sda bs=512 count=1

3) Reboot the computer

4) Check that the file system is recognized in GParted

5) If all seems fine then I would advise booting into Windows and running "chkdsk /f /r" multiple times, until there are no more faults.


NOTE:  We are tracking a problem with GParted resizing file systems.  See post:
WARNING! Problem Resizing File Systems with GParted

6

Re: SOLVED - [ Current NTFS volume size is bigger than the device size! ]

gedakc wrote:

In this situation I think the best option is to increase the partition size to encompass the whole NTFS file system.

The change I have made to the file is from a length of 245,679,997 sectors:
000001C0   21 00 07 FE  FF FF 00 08  00 00 7D C7  A4 0E 00 00
To a new length of 312,558,585 sectors:
000001C0   21 00 07 FE  FF FF 00 08  00 00 F9 43  A1 12 00 00

Note:  The NTFS volume size is always 1 sector less than the total number of sectors in the partition table entry because the NTFS backup sector is not considered part of the NTFS volume.

To apply this change:

1) Download the new MBR: sda-namrokretep_new.mbr

2) Load the new MBR on your hard disk.
NOTE:  Be extra careful when entering the commands.  Data loss could result otherwise.

dd if=sda-namrokretep_new.mbr of=/dev/sda bs=512 count=1

3) Reboot the computer

4) Check that the file system is recognized in GParted

5) If all seems fine then I would advise booting into Windows and running "chkdsk /f /r" multiple times, until there are no more faults.


NOTE:  We are tracking a problem with GParted resizing file systems.  See post:
WARNING! Problem Resizing File Systems with GParted
In the meantime we recommend using GParted Live 0.4.6-1.



I love it when a plan comes together. <PROBLEM SOLVED>

Thank you.

7

Re: SOLVED - [ Current NTFS volume size is bigger than the device size! ]

I am glad to hear the that the problem is solved.

I have taken the liberty of editing your initial post and prefixing the title with "SOLVED"