/boot filling up

melevy · Post by **melevy** » Wed Oct 17, 2012 10:10 am

Hello, I'm new to linux in general, and Ubuntu specifically. My /boot partition has 2.3M available. What can I safely delete?
Thanks!

phoenix · Post by **phoenix** » Wed Oct 17, 2012 11:35 am

[quote user="melevy"]Hello, I'm new to linux in general, and Ubuntu specifically. My /boot partition has 2.3M available. What can I safely delete?![/QUOTE]Nobody here can tell you that, you need to look at what is filling your root partition and you also (I'm guessing) should not have your /opt/zimbra directory structure on the same HD as you root partition.

melevy · Post by **melevy** » Wed Oct 17, 2012 1:59 pm

[quote user="10330phoenix"]Nobody here can tell you that, you need to look at what is filling your root partition and you also (I'm guessing) should not have your /opt/zimbra directory structure on the same HD as you root partition.[/QUOTE]

That's the problem, I can look at what's filling up the partition, but I don't know what I need to keep and what's safe to get rid if. For example:
abi-2.6.32-28-server config-2.6.32-33-server initrd.img-2.6.32-37-server vmcoreinfo-2.6.32-32-server

abi-2.6.32-29-server config-2.6.32-34-server initrd.img-2.6.32-38-server vmcoreinfo-2.6.32-33-server

abi-2.6.32-30-server config-2.6.32-35-server initrd.img-2.6.32-39-server vmcoreinfo-2.6.32-34-server

abi-2.6.32-31-server config-2.6.32-36-server initrd.img-2.6.32-40-server vmcoreinfo-2.6.32-35-server

abi-2.6.32-32-server config-2.6.32-37-server initrd.img-2.6.32-41-server vmcoreinfo-2.6.32-36-server

abi-2.6.32-33-server config-2.6.32-38-server initrd.img-2.6.32-42-server vmcoreinfo-2.6.32-37-server

abi-2.6.32-34-server config-2.6.32-39-server initrd.img-2.6.32-43-server vmcoreinfo-2.6.32-38-server

abi-2.6.32-35-server config-2.6.32-40-server initrd.img-2.6.32-44-server vmcoreinfo-2.6.32-39-server

abi-2.6.32-36-server config-2.6.32-41-server lost+found vmcoreinfo-2.6.32-40-server

abi-2.6.32-37-server config-2.6.32-42-server memtest86+.bin vmcoreinfo-2.6.32-41-server

abi-2.6.32-38-server config-2.6.32-43-server System.map-2.6.32-37-server vmcoreinfo-2.6.32-42-server

abi-2.6.32-39-server config-2.6.32-44-server System.map-2.6.32-38-server vmcoreinfo-2.6.32-43-server

abi-2.6.32-40-server grub System.map-2.6.32-39-server vmcoreinfo-2.6.32-44-server

abi-2.6.32-41-server initrd.img-2.6.32-28-server System.map-2.6.32-40-server vmlinuz-2.6.32-37-server

abi-2.6.32-42-server initrd.img-2.6.32-29-server System.map-2.6.32-41-server vmlinuz-2.6.32-38-server

abi-2.6.32-43-server initrd.img-2.6.32-30-server System.map-2.6.32-42-server vmlinuz-2.6.32-39-server

abi-2.6.32-44-server initrd.img-2.6.32-31-server System.map-2.6.32-43-server vmlinuz-2.6.32-40-server

config-2.6.32-28-server initrd.img-2.6.32-32-server System.map-2.6.32-44-server vmlinuz-2.6.32-41-server

config-2.6.32-29-server initrd.img-2.6.32-33-server vmcoreinfo-2.6.32-28-server vmlinuz-2.6.32-42-server

config-2.6.32-30-server initrd.img-2.6.32-34-server vmcoreinfo-2.6.32-29-server vmlinuz-2.6.32-43-server

config-2.6.32-31-server initrd.img-2.6.32-35-server vmcoreinfo-2.6.32-30-server vmlinuz-2.6.32-44-server

config-2.6.32-32-server initrd.img-2.6.32-36-server vmcoreinfo-2.6.32-31-server
It appears that I only need the latest of these, but before I started deleting, I want to make sure.

soxfan · Post by **soxfan** » Wed Oct 17, 2012 2:11 pm

If you are talking about the /boot directory, and not the root ("/") directory then my guess based on this listing (which doesn't look like it is formatted correctly) is that you have several kernels installed. You probably only need to latest (the one you are mostly likely running) and then maybe the one or two previous kernels. Search the Ubuntu forums for info on limiting the number of kernels that stick around and also on how to get rid of old kernels. I would not simply remove (rm) any of these files.

phoenix · Post by **phoenix** » Wed Oct 17, 2012 2:17 pm

Oops, perhaps I ought to read the posts a bit more closely.

Alupis · Post by **Alupis** » Thu Oct 18, 2012 11:21 am

what linux OS are you running? as in which version -- 10.04, 12.10? etc... 64 bit or 32 bit... is this virtualized or on bare-metal. ...
can you run this command as root while in the boot partition?
sudo du -hc
and also:
sudo df -h
and paste the outputs into this post? This will tell us what files are taking up your space, as well as your volume structure and how much is available, etc...
also... do a this as root and paste the output while in the root "/" of your os partition:
sudo ls -la
want to make sure the permissions are set to not allow anyone but root to write into that mount point...

justdave · Post by **justdave** » Fri Oct 19, 2012 10:49 pm

If you're on Ubuntu, run this:
sudo apt-get autoremove
Old kernels are marked as autoremovable after the new kernel is installed. So running apt-get's autoremove command will remove them.

50asm · Post by **50asm** » Fri Jan 18, 2013 11:13 am

I had this same issue, turned out it was updates filling up my boot partition. See the thread below from the Ubuntu Forums, Herman's post is what took care of the issue for me. Be careful not to remove your current image!
[ubuntu] /boot partition is full - Ubuntu Forums