Hi, people.
I would like to resize a partition but it simply is not working.
Details:
OS:
Ubuntu 12.04 Server with Lubuntu DE, all the latest updates.
Partitions look as thus (in gparted):
/dev/sda1 Unknown 94 MiB bios_grub flag
........2 ext2 572 MiB (boot loader)
........3 linux-swap 1.86 GiB (SWAP)
........4 ext4 13.40 GiB (/)
........5 ext4 216.63 GiB (/home)
unallocated unallocated 698.63GiB
I used advice from a Debian forum to get the above, too long ago to remember which one it was but it's worked very well for me.
My original HD is a 250GiB, but since I'm running out of space, I recently bought a 1TB HD.
(PC hardware: AMD X4 3.2 GHz with 6 GiB RA, asus M4A series motherboard, HD's are all SATA)
Using a live USB (Ubuntu 12.04_64), I commanded "sudo dd if=/dev/sda of=/dev/sdb" plus something about bs=4096k and noerr, I copied it from an ubuntu help site.
Anyway, everything copied perfectly, no problems there.
And now the fun begins.
Time to resize, so I use gparted from the same live USB.
Try as I might, every time I try to resize the partition to take up the rest of the 1TB HD, it simply won't do it.
I commanded "sudo gparted" in terminal and while I'm running the resizing, I get the following error in terminal:
"Unable to satisfy all constraints on the partition.
The backup GPT table is not at the end of the disk, as it should be. This might mean that another operating system believes the disk is smaller. Fix, by moving the backup to the end (and removing the old backup)?
Not all of the space available to /dev/sda appears to be used, you can fix the GPT to use all of the space (an extra 1465128000 blocks) or continue with the current setting?"
and then it stops with the partition going back to it's original size of 216GiB.
I don't know what all that means and searching this error for hours on the internet revealed little other than that nearly all of the solutions involve RAID setups or dual boot systems.
In using fdisk, there was an error about the partition being out of alignment. Further searching lead me to understand that the partition needs to start on a full cylinder instead of writing and reading across two as this would impact drive speed. I haven't found a solution to that yet either.
I must be doing something wrong and I cannot figure out what it is.
Bookmarks