[olug] Insufficient space on /boot to upgrade F13-F14
George De Bruin
sndchaser at gmail.com
Sat May 28 05:55:31 UTC 2011
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
On Fri, May 27, 2011 at 10:27 PM, Obi-Wan <obiwan at jedi.com> wrote:
> I'm currently running F13 on a Dell XPS 1210 laptop with a ~80GB drive
> partitioned as follows:
>
> Device Boot Start End Blocks Id System
> /dev/sda1 * 1 33 265041 83 Linux (/boot, ext3)
> /dev/sda2 34 9285 74316690 83 Linux (/ - encrypted ext3)
> /dev/sda3 9286 9546 2096482+ 82 Linux swap / Solaris
>
> # df -m
> Filesystem 1M-blocks Used Available Use% Mounted on
> /dev/mapper/luks-1c640d61-ab9a-4fcc-8251-c1c7584f2b11
> 71436 15171 55541 22% /
> /dev/sda1 251 45 193 19% /boot
>
>
> Only the actively running kernel is installed in /boot. When I try to
> upgrade from F13 to F14 using the package update GUI, it complains that
> there is insufficient space in /boot, and refuses to go on. Before the
> attempted upgrade, only 13% was in use. I've since added a kernel
> upgraded within F13. There isn't anything left for me to delete to
> free up more space. It seems silly for the upgrade to require
> dramatically more space in /boot than does general day-to-day
> operation. Isn't there any way I can tell it to use /tmp or /var for
> its scratch space?
>
> Is there any way to get around this using my current partitioning?
>
> If not, is there any way I can steal another 256MB from swap (sda3) and
> add it to /boot (sda1), even though an encrypted partition (/, sda2)
> sits between them on the disk?
>
> --
> Ben "Obi-Wan" Hollingsworth obiwan at jedi.com
> The stuff of earth competes for the allegiance I owe only to the
> Giver of all good things, so if I stand, let me stand on the
> promise that You will pull me through. -- Rich Mullins
> _______________________________________________
> OLUG mailing list
> OLUG at olug.org
> https://lists.olug.org/mailman/listinfo/olug
>
--
---
Faster moments spent spread tales of change within the sound...
More information about the OLUG
mailing list