BOOT is full

[enlox]

hi
i got this issue with the BOOT being full...
i have no idea how a folder called BOOT can be full so i will try to explain how i figured this out...

i was trying to update from f12 to f14 when the process stopped claiming i hade no diskspace.
i got a 160GB drive for System and this disk has 135GB free space. i have no idea how this can be that the update claims i have no empty disk space...

my server went unresponsive about a month later and i had to force a shutdown. rebooting i got an error message upon logon claiming my BOOT was full. i opened up my drive-page in Amahi and found that all my drives have atleast 100GB free space, each (in total i have like 1TB free space on my 4 drives, including the above mentioned System drive - see attached image). so i found out after some searching on the machine that there is a root-folder called BOOT which when i open it reports there is no free space in there (see attached image). i wonder how that can be? and i also wonder how can i either make this folder bigger or clean some of the content out?

i'd really like to be able to upgrade my system. a complete reinstall is not an option.

[moredruid]

Since /boot is usually a separate filesystem (and not reported in the Amahi storage pool I think) this can happen.
Could you post the results of "df -h" and the contents of your /etc/fstab?

I can then propose a strategy to clean things up properly.

[enlox]

some of it is in swedish but i guess you can figure out what it means anyways

[moredruid]

Hmm seems I've not clearly stated my question.

please post the output of "df -h"

and post the output of "cat /etc/fstab"

you should get separate things.

[enlox]

i thought i did just that... trying again then (yes, i ama complete newb at this)

this was done as SU in root-folder
Filesystem Size Used Available Used% Mounted at
/dev/mapper/vg_osterlunds-lv_root
143G 9,3G 127G 7% /
tmpfs 1000M 436K 1000M 1% /dev/shm
/dev/sda1 194M 194M 0 100% /boot
/dev/sdb1 459G 413G 23G 95% /var/hda/files
/dev/sdc1 688G 68G 586G 11% /var/hda/files/download
/dev/sdd1 917G 658G 213G 76% /var/hda/files/movies


this was also done as SU in root-folder
#
# /etc/fstab
# Created by anaconda on Sun Sep 12 19:22:52 2010
#
# Accessible filesystems, by reference, are maintained under '/dev/disk'
# See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info
#
/dev/mapper/vg_osterlunds-lv_root / ext4 defaults 1 1
UUID=294b73d5-ae0e-46f0-bb67-73cb4c2b2809 /boot ext4 defaults 1 2
/dev/mapper/vg_osterlunds-lv_swap swap swap defaults 0 0
tmpfs /dev/shm tmpfs defaults 0 0
devpts /dev/pts devpts gid=5,mode=620 0 0
sysfs /sys sysfs defaults 0 0
proc /proc proc defaults 0 0
/dev/sdb1 /var/hda/files ext3 defaults 1 2
/dev/sdc1 /var/hda/files/download ext3 defaults 1 2
/dev/sdd1 /var/hda/files/movies ext3 defaults 1 2



i guess this is what you are asking for

[moredruid]

yup, that's what I was looking for.
you have a 200M /boot partition (kinda small).
if your system boots normally you can remove the following files:
initramfs-2.6.32.21-168.fc12.x86_64.img
initramfs-2.6.32.21-170.fc12.x86_64.img
config-2.6.32.21-168.fc12.x86_64.img
config-2.6.32.21-170.fc12.x86_64.img
System.map-2.6.32.21-168.fc12.x86_64.img
System.map-2.6.32.21-170.fc12.x86_64.img
vmlinuz-2.6.32.21-168.fc12.x86_64.img
vmlinuz-2.6.32.21-170.fc12.x86_64.img

and edit /boot/grub/menu.lst: you should remove the following lines to avoid confusion:

Code: Select all

title Fedora (2.6.32.23-170.fc12.x86_64) root (hd0,0) kernel /vmlinuz-2.6.32.23-170.fc12.x86_64 ro root=/dev/mapper/vg00-lvroot LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=us initrd /initramfs-2.6.32.23-170.fc12.x86_64.img title Fedora (2.6.32.21-168.fc12.x86_64) root (hd0,0) kernel /vmlinuz-2.6.32.21-168.fc12.x86_64 ro root=/dev/mapper/vg00-lvroot LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=us initrd /initramfs-2.6.32.21-168.fc12.x86_64.img

and move the folder "upgrade" to somewhere else (out of your /boot partition).
You can then try a yum update again and see what gives.

If that fails you'll need to redefine the current /boot (not a fun chore but possible).

[enlox]

i have done what you told me to do, also moved Upgrade out of boot into root-folder, and now the reports look like this:
(if i still have problems with the upgrade i will get back to you eventually, thanx for now)


Filesystem Size Used Available Used% Mounted on
/dev/mapper/vg_osterlunds-lv_root
143G 77G 60G 57% /
tmpfs 1000M 672K 999M 1% /dev/shm
/dev/sda1 194M 24M 161M 13% /boot
/dev/sdb1 459G 413G 23G 95% /var/hda/files
/dev/sdc1 688G 68G 586G 11% /var/hda/files/download
/dev/sdd1 917G 658G 213G 76% /var/hda/files/movies

#
# /etc/fstab
# Created by anaconda on Sun Sep 12 19:22:52 2010
#
# Accessible filesystems, by reference, are maintained under '/dev/disk'
# See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info
#
/dev/mapper/vg_osterlunds-lv_root / ext4 defaults 1 1
UUID=294b73d5-ae0e-46f0-bb67-73cb4c2b2809 /boot ext4 defaults 1 2
/dev/mapper/vg_osterlunds-lv_swap swap swap defaults 0 0
tmpfs /dev/shm tmpfs defaults 0 0
devpts /dev/pts devpts gid=5,mode=620 0 0
sysfs /sys sysfs defaults 0 0
proc /proc proc defaults 0 0
/dev/sdb1 /var/hda/files ext3 defaults 1 2
/dev/sdc1 /var/hda/files/download ext3 defaults 1 2
/dev/sdd1 /var/hda/files/movies ext3 defaults 1 2

[moredruid]

nice, now only 24M of the 194M is used on /boot

I should hope that 170M is sufficient for a dist-upgrade. You may want to pop by the Fedora IRC to ask, here is a bit on the Fedora Wiki regarding this issue.

[enlox]

i got some tips from that forum, but i would rather have a solution where the system actually moves the Upgrade-folder and use it in another place. is this possible? how do i do that?
just moving the folder will have the upgrade-process create a new folder in /boot and work from there.
i'd like to have the /boot/upgrade folder in say /upgrade.

i googled it and find no answer that i can see

[moredruid]

hmmm
you could try the following:
create a folder on a big disk, e.g. /var/hda/files/myupdate
then create a symlink in /boot to that folder:

Code: Select all

cd /boot ln -s /var/hda/files/myupdate update

You should do everything as root user to be on the safe side.
/boot/upgrade is AFAIK only needed for the new kernel files, not for the installation itself.

In the page I linked there's also an alternative in case you don't have enough space.