grubby fatal error: unable to find a suitable template

[Ex_Soft]

Installing : kernel-PAE-3.1.5-1.fc16.i686 40/105
grubby fatal error: unable to find a suitable template

What should I do to resolve this issue?

[stoggy]

Hey, did you get this fixed? Sounds like the rpm didn't completely install. maybe died in post scripts or something, see the end of message. Do you know the state of the rpm currently? I wouldn't reboot until i got a clean install. No way to test it till you test it and if it tests bad, well then it might suck for awhile. I have never had to many "bad" situations with rpms but there is always a chance.

Check if the rpm is installed or not.

rpm -qa | grep kernel


"im currently in windoze and don't have access to F16. So the grub config file may have changed. I'm not sure. Ill try to check later." Check and see if the kernel you were trying to install added a boot section for you. If the install really screwed up this file might be gone or messed up. Probably not but if this isn't correct don't reboot.


cat /boot/grub/menu.lst



Check to see if the kernel and initrd for your default boot option and for the kernel you were trying to install are there. When you cat the menu.lst file it will show the files you need. This will list them all and you can look for them.

ls /boot/{initrd,vmlinuz}*


next would be to find out why the rpm failed to install. The easiest thing to do is remove the pre and post scripts and find out what it is doing. The file is long but it will be broken up into sections. Then its a matter of walking through the script to figure out why something is failing. Report a bug because this is probably something overlooked in the rpm that is causing it to fail.

rpm -qp --scripts kernel-whatever.rpm > kernel-postscript


if you need help post them.

[fedora16user]

Hi,

this morning I realized the same message while updating my fedora 16 installation via 'yum'.
I normally boot into runlevel 3 for running 'yum check-update' / 'yum update' (if necessary)
every morning.
This morning a bunch of about 300MB of packages were listed. One of them was the above
mentioned kernel, and the same message appeared at my console after the line mentioning
the kernel (3.1.5-1) update.
Because there's always the former kernel available on the boot-menu, I gave the new kernel
a try and rebooted the system - it worked (I'm actually running it at the time of writing).
So, everything I may contribute at this time is to mention the message seemed not to harm
anything - at least on my system.
I also tried some of the commands mentioned above.
The 'post-script' of the kernel package differs only in the kernel release number compared to
the same script of the 3.1.4-1 package.
Under '/boot' there is the kernel (vmlinuz-3.1.5-1.fc16.x86_64) and a related 'initrd' file (which
is called 'initramfs-3.1.5-1.fc16.x86_64.img' on my system).
Also the output of 'lsinitrd /boot/initramfs-3.1.5-1.fc16.x86_64.img' looks OK to me.
If it helps I can give you the output of this command, or maybe some other information - please
let me know.
Nevertheless the behaviour of the system - especially after the upgrade from F14 - is very
awesome this time (I don't remember that much trouble and problems a year ago while upgrading
from F12 to F14).
Hope these comments help a bit...

[AdamW]

This error will usually occur on kernel package-related operations on systems upgraded from F15 to F16, but despite looking scary, does not necessarily indicate anything is terribly wrong. Do you have an actual problem with the newly installed kernel or not?

[fedora16user]

No real problem with running the system here (the kernel-3.1.5-2 update this morning led to
the same message).
What I find strange is the fact that kernel updates up to release 3.1.4-1 did not output this
message (I'm updating and upgrading my system without (major) problems since F10 and
did never realize this message before).
I suspect it's a problem with the 'grubby' package (8.3-2 at the moment). This was updated
between the kernel-3.1.4-1 and kernel-3.1.5-1 updates.

Btw., ignoring a 'fatal error' message is never a good idea...

At a research on the web today I realized that this 'bug' is one that seems to exist since
several YEARS and Fedora releases (e.g., "https://bugzilla.redhat.com/show_bug.cgi?id=124246").
Sometimes there may be fixes, but it seems to reappear all the time...
Maybe some time one will find a 'real fix' to this problem...
In the meantime I will (try to) ignore it - at least, as long my system is working...

[pnelsonsr]

I fixed my grubby problem but mine system was an upgrade of F15 to F16 which changed from grub to grub2.

It seems that grubby has a problem when a /boot/grub/grub.conf file exists and was zero file size or, as was in my case, had a kernel listed that was no longer installed. I simply move the file to grub.conf.old and then removed and re-installed current kernel package (not the one I was booted into) and sure enough the grubby error was no longer there.

If you have /boot/grub dir and a /boot/grub2 dir you may have the same type of issue. As grubby looks at both during its run when installing a new kernel.

[IHeart SymLinks]

I upgraded to F16 via yum as well and get that whenever I update my kernels and have to manually edit grub every time there is a kernel update, before it was automatic.

At first Grub didn't work at all, but my Senior Admin guided me to fixing it by using the grub command line to boot and from there being able to edit menu.lst