New kernel not installed because no enough room in /boot

Should I manually delete old kernels?

kernel-devel-2.6.32-504.8.1.el6.x86_64
libreport-plugin-kerneloops-2.0.9-21.el6.centos.x86_64
kernel-2.6.32-504.3.3.el6.x86_64
kernel-firmware-2.6.32-504.8.1.el6.noarch
dracut-kernel-004-356.el6.noarch
kernel-2.6.32-504.el6.x86_64
kernel-devel-2.6.32-504.el6.x86_64
kernel-devel-2.6.32-504.1.3.el6.x86_64
abrt-addon-kerneloops-2.0.8-26.el6.centos.x86_64
kernel-devel-2.6.32-504.3.3.el6.x86_64
kernel-headers-2.6.32-504.8.1.el6.x86_64
kernel-2.6.32-504.1.3.el6.x86_64

Howdy,

Yeah you may want to delete some older kernels – but make sure you’re deleting ones that aren’t currently in use :slight_smile:

-Eric

#yum erase kernel ?

Hi,

Check out this article which should help you accomplish what you’re looking to do in an simple straight forward manner.

http://www.if-not-true-then-false.com/2012/delete-remove-old-kernels-on-fedora-centos-red-hat-rhel/

Cheers!

Best Regards, Peter Knowles TPN Solutions

Email: pknowles@tpnsolutions.com
Phone: 604-782-9342
Skype: tpnsupport
Website: http://www.tpnsolutions.com


Ask me about my new support plans which include a FREE copy of Virtualmin Pro!!!

This is what I do …

#rpm -qa | grep kernel

A list like this should show up e.g.:

kernel…

kernel-old…

kernel-older…

You can remove the old kernels with e.g.:

rpm -e kernel-old

rpm -e kernel-older

Depends on your Distro.

dpkg --list | grep linux-image

apt-get remove linux-image-*********-generic

Always leave 2 on the server.

Don’t delete the one your currently using :slight_smile:

Thank you all.

It is easy to make a mistake erasing them manually so I prefer IF !1 0 solution.
yum.conf had installonly_limit=5 by default
Now, after #yum -y update
#rpm -q kernel
kernel-2.6.32-504.1.3.el6.x86_64
kernel-2.6.32-504.3.3.el6.x86_64
kernel-2.6.32-504.8.1.el6.x86_64

Was this a test or for educational purposes :wink:

Also, with debian based sytems you have apt-get autoremove, providing the new kernel had space to install in the first place, always follow with apt-get autoclean and reboot, checking first that grub.cfg time out is not set to -1 for Ubuntu, it’s a bug that they don’t want to fix for some reason, set it to 5 or 10 and your server will come back up after reboot.

That was a test, kernel now is up-to-date, Webmin does not show it anymore as an available update… and educational purpose too :wink:

Okay, I am on Centos 6, no problems at all with that fix

You rebooted yeah? If you don’t all is vanity.

Cannot reboot now. Not in a hurry.
Thks

Pointless updating the kernel then :slight_smile: Hope it was not a security issue.

I know.
Not a security issue at all, just cannot reboot at this time, some working VS