Description of problem:
When booting F17 with grub2, I see 3 'File Not Found' errors
but then it loads the kernel and works (when using the standard
linux kernels that come with F17).
I did a preupgrade from F16 in case that matters.
Version-Release number of selected component (if applicable):
Always, at least in this install.
Steps to Reproduce:
preupgrade is apparently broken in several ways and will fail to configure the boot loader properly.
and see if that makes the problem go away.
Remember to take a backup of /boot if you would like to have a backup.
Yes, that makes the errors go away. I still can't boot a custom kernel (hangs before the services start), but at least no grub2 error messages, and the standard F17 kernel boots fine.
That is a strong evidence that whatever it was, it wasn't a grub2 issue. You can try to check the open preupgrade bugs and see if you can add something there or find answers ... or if you should file a preupgrade issue.
(In reply to comment #3)
> That is a strong evidence that whatever it was, it wasn't a grub2 issue. You
> can try to check the open preupgrade bugs and see if you can add something
> there or find answers ... or if you should file a preupgrade issue.
I have the same problem - I still would like to know what went wrong instead of just doing comment 1 to make the problem go away. What can I try before I proceed to get rid of the problem?
preupgrade did not install a new boot loader ... and patching the existing one with grubby also failed.
(In reply to comment #5)
> preupgrade did not install a new boot loader ... and patching the existing
> one with grubby also failed.
But it still 'works' - the new kernel is operational, just with mysterious error messages during grub/dracut?
I think this is a bug with preupgrade - it does not put the latest grub2 under /boot .
"Bug 827987 - preupgrade does not run grub2-install"
and attached my /boot before grub2-install to fix it, and it worked.
Encountered "Bug 817187 - GRUB2 error: file '/boot/grub2/locale/en.mo.gz' not found" after getting rid of the three no-name error lines. That is trivially worked around by copying one file over (https://bugzilla.redhat.com/show_bug.cgi?id=817187#c5).
Turns out that missing any MO file often means that someone forgot to define `LANG` environment variable.
This is rather common when doing a rescue-CD-based bootup sequence where one forgets to execute:
which in turns sources the `/etc/profile.env`, which in turns defines the `LANG=C.UTF8` environment variable.
Without this LANG defined during `grub2-install` (now `grub-install`), this error message will occur during the next reboot.