Please do not reply directly to this email. All additional comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=124246
Need Real Name howarth@nitro.med.uc.edu changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |howarth@nitro.med.uc.edu
--- Comment #29 from Need Real Name howarth@nitro.med.uc.edu 2009-02-05 16:00:29 EDT --- I am seeing the same problem after upgrading a system on software RAID-1 from Fedora 8 to 10. The Fedora 10 upgrade went fine except the boot loader upgrade option didn't work (which I have seen on other systems before). I took the usual route of repeating the upgrade but selecting the third option to install a new boot loader. Now the Fedora 10 installation boots fine but when I did the first yum update the rpm failed to install the entry in grub.conf with the error
grubby fatal error unable to find a suitable template
I noticed that I had a grub,conf.rpmsave with...
default=0 timeout=5 splashimage=(hd0,0)/grub/splash.xpm.gz hiddenmenu title Fedora (2.6.27.5-117.fc10.x86_64) root (hd0,0) kernel /vmlinuz-2.6.27.5-117.fc10.x86_64 ro root=/dev/md1 nodmraid rhgb quiet initrd /initrd-2.6.27.5-117.fc10.x86_64.img
but that the current grub.conf has...
default=0 timeout=0 splashimage=(hd0,0)/grub/splash.xpm.gz hiddenmenu title Fedora (2.6.27.5-117.fc10.x86_64) root (hd0,0) kernel /vmlinuz-2.6.27.5-117.fc10.x86_64 ro root=UUID=3adeca51-506e-4b51-aea7-c0ca9525ec36 nodmraid initrd /initrd-2.6.27.5-117.fc10.x86_64.img
I was able to manually add the new kernel to grub.conf using /dev/md1 for root. I am assuming that the new use of the UUID label is screwing up attempt to add the grub entry when the new kernel is installed. I would also note that this machine was originally installed with Windows RAID drivers by the vendor so that I have to use nodmraid to keep dmraid from getting confused by the tattooing on the drive. Perhaps this is related and the wrong labels are being read? Any idea on how to debug this problem further?