This is a relatively fresh CentOS 6 installation with the install script from my VirtualminPro license area.
For some reason, every time there is a new kernel update I am unable to install it, as yum informs me that there is a shortage of space in /boot
I then have to delete the oldest kernel on my system with rpm -e and subsequently do a yum update after which the new kernel is successfully installed. I can then shutdown -r now to boot in to the new kernel.
Just curious to know why I have to do this each time a kernel update is available? Shouldn't the initial installation through your script offer enough space in /boot to take care of this? Just seems odd that I have to intervene each time a kernel update is available. Is this normal with all relatively fresh installs running CentOS 6?
Comments
Submitted by andreychek on Fri, 07/20/2012 - 17:14 Comment #1
Howdy -- the install.sh script only installs Virtualmin, it doesn't install your OS or the kernel that CentOS is running.
It sounds like, during the initial installation of CentOS, that the /boot partition may not have been setup to be large enough.
If you're receiving messages about /boot being out of space, your options would be to either remove some of the older kernel prior to installing new ones, or to perform a new CentOS install, making the /boot partition larger (or not putting it on a separate partition).