Hello:
I have a question that arises from my failure to upgrade from F21 to F22. When I installed F21 in my server, I setup 200 mB in my /boot partition, which turned out to be a mistake. Now, /boot lacks space to upgrade to F22 with fedup. I tried to resize the two partitions with gparted, but this package is unable to do so, by what I think is the type of partitions on my drive: the 200 Mb /boot directory is ext3.Linux, the rest (immediately after /boot) is LVM. Here is the Fdisk output:

Disk /dev/sda: 465.8 GiB, 500107862016 bytes, 976773168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x000261fa

Device Boot Start End Sectors Size Id Type
/dev/sda1 * 63 401624 401562 196.1M 83 Linux
/dev/sda2 401625 976768064 976366440 465.6G 8e Linux LVM

Disk /dev/mapper/VolGroup00-LogVol00: 457.6 GiB, 491303993344 bytes, 959578112 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/mapper/VolGroup00-LogVol01: 8 GiB, 8589934592 bytes, 16777216 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Fedup aborts installation of F22, due to lack of space (says I need another 34 Mb). In the /boot directory, the rescue initramsfs is quite large. If I do away with it, or reduce it substantially, I may regain the space I need for the upgrade. Is there any way to do that? I view this as a practical solution, rather than reformatting the disk, with the inherent down time.
I'll be looking forward to your feedback

How are you running gparted ?. If from the installed F21, then the lv's will be mounted - gparted won't touch it.
Try from a current liveCD - the gparted homepage says it can manage LVM2 pvs, so you might be lucky. On a disk that big, make the boot a decent size - say a gig. At least. The updater used to download to there as a temporary work area. I assume fedup does likewise.

Hi syg00.
I ran gparted from an ISO image, in a live CD (booting from the CD). The partitions are recognized, but it cannot resize them. Here is the cfdisk info:

Disk: /dev/sda
Size: 465.8 GiB, 500107862016 bytes, 976773168 sectors
Label: dos, identifier: 0x000261fa

Device Boot Start End Sectors Size Id Type
>> /dev/sda1 * 63 401624 401562 196.1M 83 Linux
/dev/sda2 401625 976768064 976366440 465.6G 8e Linux LVM
Free space 976769024 976773167 4144 2M

My idea was to shrink the LVM, move it towards the end, and give the contiguous space left to the /boot partition. Gparted, running as stated above, could not resize anything. I've done a bit of digging and I've gotten feedback saying Gparted will not resize the LVM in this scenario.
Oh, and yes. Full backups are run routinely to a NAS drive, so I'm covered.