I was upgrading Fedora Core 1 (with all updates) to Fedora Core 3. My root partition was on LVM. The grub.conf was not updated correctly, leaving machine unbootable. Relevant part of upgrade.log: ... Upgrading mkinitrd-4.1.18-2.i386. Upgrading kernel-2.6.9-1.667.i686. unable to stat /dev/Main/Root: 2 grubby fatal error: unable to find a suitable template grubby fatal error: unable to find a suitable template grubby: doing this would leave no kernel entries. Not writing out new config. Upgrading kernel-smp-2.6.9-1.667.i686. unable to stat /dev/Main/Root: 2 grubby fatal error: unable to find a suitable template ... The /etc/grub.conf after upgrade contained: ----- # grub.conf generated by anaconda # # Note that you do not have to rerun grub after making changes to this file # NOTICE: You have a /boot partition. This means that # all kernel and initrd paths are relative to /boot/, eg. # root (hd0,0) # kernel /vmlinuz-version ro root=/dev/Main/Root # initrd /initrd-version.img #boot=/dev/hda default=0 timeout=10 splashimage=(hd0,0)/grub/splash.xpm.gz title Fedora Core (2.4.22-1.2199.nptlsmp) root (hd0,0) kernel /vmlinuz-2.4.22-1.2199.nptlsmp ro root=/dev/Main/Root rhgb initrd /initrd-2.4.22-1.2199.nptlsmp.img ------------- In order to get the machine to boot again, I had to (manually): - recreate the initrds for 2.6.9-1.667 and 2.6.9-1.667smp (the ones created automatically during the FC1->FC3 upgrade did not have the LVM stuff). - replace the 2.4.22-1.2199.nptlsmp entry in grub.conf with appropriate 2.6.9-1.667smp and 2.6.9-1.667 entries
FC1 -> FC3? Urgh :/ I fixed this for FC2 -> FC3, but I can definitely see how FC1 -> FC3 could be different with the lvm1->lvm2 transition.
Fixed with new udev package.
Any feedback on if this latest udev package resolved the issue?
Since the machine that caused this problem is already upgraded, I do not really have a way to test this.
I'm not seeing other reports with the new udev, so going to close this out. Will reopen if things rear their ugly heads again.