Question

Kernel update

  • Posted on May 31, 2013
  • andre1Asked by andre1

Running a “yum update”, CentOS try to install a new kernel. However, I get this:

Installing : kernel-2.6.32-358.6.2.el6.x86_64 1/1 grubby fatal error: unable to find a suitable template Verifying : kernel-2.6.32-358.6.2.el6.x86_64 1/1

Installed: kernel.x86_64 0:2.6.32-358.6.2.el6

The installation completes, but the system keep booting on old kernel. Maybe it’s related to “grubby fatal error: unable to find a suitable template”. I think the kernel is installed but not added to grub. How can I fix this in a safe way?


Submit an answer

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Want to learn more? Join the DigitalOcean Community!

Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.

Hey there,

Just wanted to step in and offer a quick update here. It’s no longer necessary for us to import new kernels. Instead, if you’re using one of our older images, you can ensure you’re using the newest kernel by switching to our “GrubLoader” kernel in the control panel, and performing a full power off/on.

This will allow your Droplet to boot using your locally installed kernels rather than the ones on our HV that we manually used to import.

Newer images boot like this automatically, but older images need to be switched over manually.

More info here: https://www.digitalocean.com/community/tutorials/how-to-update-a-digitalocean-server-s-kernel

Thanks, Eris Customer Success Engineer

I solved the problem by editing /boot/grub/grub.conf and updating the kernel argument “root=UUID=xxxxxxxxxxx” to use a UUID that actually exists. I found out the UUID of my ‘/’ partition using ‘blkid’. After editing grub.conf, I did a ‘yum reinstall kernel’ and there were no grubby errors anymore.

If you don’t have any luck using a UUID, you could also try using root=LABEL=DOROOT where ‘DOROOT’ is whatever is returned from something like ‘sudo e2label /dev/vda1’

Hope this helps someone :)

The method on http://www.itekhost.net/grubby-fatal-error is really dumb, don’t use it, it doesn’t do anything good.