[olug] Insufficient space on /boot to upgrade F13-F14

Rob Townley rob.townley at gmail.com
Sat May 28 06:48:14 UTC 2011

On Sat, May 28, 2011 at 12:55 AM, George De Bruin <sndchaser at gmail.com> wrote:
> Something is definitely not right...  Have you looked at the lost+found
> directory and made sure there isn't anything in it?
> Compressed kernel images should only take 20-25 Meg *total*.  For example:
> -rw-r--r-- 1 root root 104K Mar  7 18:18 config-2.6.32-5-amd64
> drwxr-xr-x 3 root root 4.0K Mar 22 23:49 grub
> -rw-r--r-- 1 root root  16M Mar 22 23:50 initrd.img-2.6.32-5-amd64
> drwx------ 2 root root  16K Mar  5 19:07 lost+found
> -rw-r--r-- 1 root root 1.6M Mar  7 18:18 System.map-2.6.32-5-amd64
> -rw-r--r-- 1 root root 2.4M Mar  7 18:12 vmlinuz-2.6.32-5-amd64
> Do you have un-compressed kernel images?  Is there a bunch of junk in the
> /boot/grub that shouldn't be there?
> Failing those two things - I'd umount /boot and run an fsck on it.  I
> suspect there are a bunch of inodes that need to be freed up or something.
> While gparted might allow you to move the partitions around a bit, it's
> probably going to take a *long* time to do it (each partition in this case
> would need to physically move), and can only be done if the sda2 and sda3
> partitions will end up on a proper cylinder / sector boundary (I forget
> where the boundaries are exactly).
> George

fsck /boot would be a good idea.
However, the fedora preupgrade installer image comes in north of 120MB.
You might run tune2fs -l /boot to see if you reserved a whole bunch of
space you have since forgotten about.

More information about the OLUG mailing list