Hello,
I'm trying to resize a partition on an IDE hard disk to use the entire disk but can not get more than a 309GB partition. I can get 295, 300, 301, 302GB, etc... fine but start getting problems with anything over 309GB. I get the following error with 310GB or more:

error: block relocator should have relocated 533
Warning: You should reinstall your boot loader before rebooting. Read section 4
of the Parted User documentation for more information.

I am using Slackware 12.1, GNU parted 1.8.8, ext2 filesystem.

Thanks for your help!
chris


Some output that may be of use:
******************************************************************
root@asus:~# parted /dev/hdb print
Model: ST3500630A (ide)
Disk /dev/hdb: 500GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos

Number Start End Size Type File system Flags
1 32.3kB 309GB 309GB primary ext2
******************************************************************
# dumpe2fs /dev/hdb1
Filesystem volume name: seagate
Last mounted on: <not available>
Filesystem UUID: fb4ed7c9-4422-4f43-bb11-2d4d15d0c88e
Filesystem magic number: 0xEF53
Filesystem revision #: 1 (dynamic)
Filesystem features: filetype sparse_super large_file
Default mount options: (none)
Filesystem state: clean
Errors behavior: Continue
Filesystem OS type: Linux
Inode count: 37732352
Block count: 75439224
Reserved block count: 754392
Free blocks: 5652777
Free inodes: 37692827
First block: 0
Block size: 4096
Fragment size: 4096
Blocks per group: 32768
Fragments per group: 32768
Inodes per group: 16384
Inode blocks per group: 512
Last mount time: Wed Jan 7 04:59:49 2009
Last write time: Wed Jan 7 05:26:18 2009
Mount count: 6
Maximum mount count: 30
Last checked: Fri Aug 22 17:23:11 2008
Check interval: 0 (<none>)
Reserved blocks uid: 0 (user root)
Reserved blocks gid: 0 (group root)
First inode: 11
Inode size: 128

don't think anyone needs to see more?

Nobody else responded, so I'll guess.

What happens if you use a live-cd tool like Parted Magic or GParted? What would the command <fdisk-l> using either tell you? Would either parted in a graphic version or fdisk pick up the missing space?

It's not very easy to try a live-CD because the drive is in a server without monitor, keyboard. I appreciate the guess but I don't think I'll go that route at this point.

Does anyone have any thoughts on deleting the partition, then creating a new one beginning on the same cylinder but using the whole 500GB. Then use resize2fs to fill out the file system.

Can ext2 go to 500GB without any special provisions being made?

Is there somethhing I need to be aware of when dealing with file systems this large?

Thanks for any thoughts,
chris

The following worked for me!!

- Using parted, remove partition, noting what cylinders the problem partition is starting and ending on. Use the unit cmd for this.
- Still in parted, mkpart cmd to create a new partition using the entire disk.
- # e2fsck -f /dev/hdb1 -f option forces the check even if the file system seems clean.
- resize2fs /dev/hdb1 to fill out the file system to the full size of the partition.

chris