View Full Version : [all variants] Using gparted
June 1st, 2009, 08:33 PM
I have a 20gb hard drive. I wanted to increase the size of my swap partition, so I shrank the main partition by 1gb using gparted off my system rescue cd. All went well, and I now have about 1gb of unallocated space between my main partition and the swap partition (which is the last partition on the disk. I thought I could just resize the swap partition to to fill to the left and use the unallocated space. Can't figure out how to do that, as space preceding and following the swap partition are zero, and I can't seem to change that. What am I not understanding?
June 1st, 2009, 08:38 PM
I usually just delete the original swap area and then select the unallocated area(which will include the new part you created by shrinking the other partition) and make it a swap partition again. hope that helps!
June 1st, 2009, 09:21 PM
That seemed to work, but I notice after removing the old swap I had to delete an extended partition in order to free space behind the new swap area before expanding it. That seemed to work okay. Now I have two partitions, sda1 and sda3. I took a look at fstab and it shows the swap area as sda5 (the old number system before deleting the extended partition). Should I edit fstab and change the swap area to sda3?
June 1st, 2009, 09:29 PM
I suspect the swap area was mounted and being by the System Rescue CD. Right click on it in gparted and choose unmount (or swapoff, I can't remember the way it is done at the moment) and see if that helps you move/enlarge it.
EDIT: Sorry I was called away half way through writing this post and didn't see the last poster's entry.
June 1st, 2009, 10:12 PM
Post a screen-shot of gparted.
Let us see the actual partition lay-out.
June 2nd, 2009, 12:57 AM
Should I edit fstab and change the swap area to sda3?
to list the swap partitions UUID. Change /etc/fstab entry for swap to match.
June 2nd, 2009, 06:58 AM
I edited fstab, and changed the uuid to match that shown by blkid. Then changed the designation sda5 to sda3. All looks okay, but when I rerun blkid the old sda5 partition shows up in the output of blkid. Looks like this:
mike@mike-desktop:~$ sudo blkid
[sudo] password for mike:
/dev/sda1: UUID="c3dc2164-0e80-4dd7-908e-390eb3733b6f" TYPE="ext3"
/dev/sda5: TYPE="swap" UUID="a798242f-7e2-44f8-9c63-720967a73cee"
/dev/sdb1: UUID="954c5b76-5f4b-4205-aabc-048fc7f4a6a0" SEC_TYPE="ext2" TYPE="ext3"
/dev/sda3: TYPE="swap" UUID="917260b7-9ce3-4038-ad3e-338bcabc0062"
Why does sda5 show up? It shouldn't exist. Also, what is /dev/ramzswap0?
I have a second hard drive sdb1 which is in the list.
June 2nd, 2009, 07:14 AM
One more question. As a result of this exercise, my swap partition is no longer part of an extended partition, but is now a partition in its own right. My extended partition is gone and now I have a primary linux partition and a separate swap partition. I assume that is okay, but something weird happened: my xubuntu boot splash screen lights up, moves the progress bar back and forth, then drops into a text screen titled something like "Reading files necessary to boot...". Have I broken something? System does boot and works okay.
June 2nd, 2009, 09:03 AM
Update: I found and fixed the problem of dropping out of the boot splash screen. Googled it and found a fix:
Still can't explain the invalid swap file listed by blkid, but the incorrect swap file appears in blkid.tab. Shouldn't running blkid update the tab file? Can the tab file be edited, e.g. just delete the invalid entry?
June 2nd, 2009, 10:10 AM
but when I rerun blkid the old sda5 partition shows up.
Haven't seen a non-existent partition show up before. Can't help but just out curiosity what does
ls -l /dev/disk/by-uuid/ show?
June 2nd, 2009, 04:35 PM
Looks like this:
mike@mike-desktop:~$ ls -l /dev/disk/by-uuid/
lrwxrwxrwx 1 root root 10 2009-06-02 08:25 917260b7-9ce3-4038-ad3e-338bcabc0062 -> ../../sda3
lrwxrwxrwx 1 root root 10 2009-06-02 08:25 954c5b76-5f4b-4205-aabc-048fc7f4a6a0 -> ../../sdb1
lrwxrwxrwx 1 root root 10 2009-06-02 08:25 c3dc2164-0e80-4dd7-908e-390eb3733b6f -> ../../sda1
Some googling shows that there are bugs associated with blkid regarding its cache file blkid.tab, with some fixes. Haven't picked one yet, but safest seems to be a rename of blkid.tab and blkid.old, then a rerun of blkid which rebuilds the cache. Will post if it works.
June 4th, 2009, 06:37 AM
Some Googling reveals that blkid does not automatically purge old partitions, and the garbage removal option is spotty, so just screwed up my courage and edited out the offending bad line in the blkid.tab cache. Everything seems to work okay.
Powered by vBulletin® Version 4.2.2 Copyright © 2017 vBulletin Solutions, Inc. All rights reserved.