I finally was able to create a VM in which to load and "play" with CentOS 6, and the first time I went to update the kernel I ran into this:
Downloading Packages: kernel-2.6.32-71.29.1.el6.x86_64.rpm | 22 MB 01:11 Running rpm_check_debug Running Transaction Test Transaction Test Succeeded Running Transaction Installing : kernel-2.6.32-71.29.1.el6.x86_64 1/1 grubby fatal error: unable to find a suitable template
What does that mean and how do I fix it?
On Tue, 2011-07-26 at 08:32 -0700, Mark wrote:
grubby fatal error: unable to find a suitable template
Google first result: https://bugzilla.redhat.com/show_bug.cgi?id=124246#c2 "never ever rpm -U a kernel... really."
Could it be you upgraded instead of installed the new kernel?
Regards, Leonard.
On Jul 26, 2011 9:09 AM, "Leonard den Ottolander" leonard@den.ottolander.nl wrote:
On Tue, 2011-07-26 at 08:32 -0700, Mark wrote:
grubby fatal error: unable to find a suitable template
Google first result: https://bugzilla.redhat.com/show_bug.cgi?id=124246#c2 "never ever rpm -U a kernel... really."
Could it be you upgraded instead of installed the new kernel?
sudo yum update
I never use rpm if I can avoid it.
On Tue, 2011-07-26 at 11:07 -0700, Mark wrote:
On Tue, 2011-07-26 at 08:32 -0700, Mark wrote:
grubby fatal error: unable to find a suitable template
Pasting the above into google renders lots of results that might help you track down your specific problem. Things like duplicate disk labels or missing symlinks to /dev/root or Fedora kernel entries in grub.conf not working correctly as a template for the CentOS kernel entry.
It's hard to tell what exactly your problem is since you do not supply a lot of information. It might be you can just fix your issue by editing grub.conf to add or fix the boot entry for this kernel.
Regards, Leonard.
At Tue, 26 Jul 2011 21:16:54 +0200 CentOS mailing list centos@centos.org wrote:
On Tue, 2011-07-26 at 11:07 -0700, Mark wrote:
On Tue, 2011-07-26 at 08:32 -0700, Mark wrote:
grubby fatal error: unable to find a suitable template
Pasting the above into google renders lots of results that might help you track down your specific problem. Things like duplicate disk labels or missing symlinks to /dev/root or Fedora kernel entries in grub.conf not working correctly as a template for the CentOS kernel entry.
It's hard to tell what exactly your problem is since you do not supply a lot of information. It might be you can just fix your issue by editing grub.conf to add or fix the boot entry for this kernel.
One random thought: On *some* VM setups (and I believe the OP is using a VM), some of the boot infrastructure might be missing or exists only the host system, so it might not be possible to upgrade a VM's kernel while inside of the VM. (I know that is the way it is for the CentOS 4 VPS I rent from Tektonic).
Regards, Leonard.