Description of problem: After upgrading F16 to F17 Beta (and hitting #810346), every time I boot I get the message "error: file not found" 3 times. Then I get asked to hit a key, and after that booting continues as expected. Version-Release number of selected component (if applicable): GRUB2 1.99-19 How reproducible: always Steps to Reproduce: 1. boot 2. 3. Actual results: The following error is produced: ---- error: file not found error: file not found error: file not found Hit a key to continue ... ---- (Wording might not be totally correct here.) Expected results: No error is produced. Additional info: Recreating grub2 configuration via "grub2-mkconfig -o /boot/grub2/grub.conf" does not help.
Same here. When I first upgraded to F17 I did not have this problem, so this must be a recent regression. It seems to start occurring around the time Grub2 starts displaying only one Linux entry (and hiding the other kernels under "Advanced Linux configuration")
Problem is still present with the latest grub2-2.0-0.22.fc17.x86_64 from Koji.
Have you tried running grub2-install /dev/sda (or wherever your boot loader is installed)? Try to run find /boot/grub2 | sort > before and compare that with the content after. I guess the problem is that grub2-mkconfig references the new all_video module that won't be available before it has been installed.
This is NOTABUG, because you chose 'skip bootloader configuration' at upgrade time (see 810346). -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
Running "grub2-install /dev/sda" solves the problem, thank you! The main difference in "find /boot/grub2 | sort" is that after grub2-install the .mod files are installed in a subdirectory "i386-pc" instead of straight in the grub2 directory.
(In reply to comment #4) > This is NOTABUG, because you chose 'skip bootloader configuration' at > upgrade time I also ran into bug 810346 doing a preupgrade from 16 -> 17, and after fixing it with 'sudo grub2-mkconfig -o /boot/grub2/grub.cfg' I also ran into this bug. I'm not sure why this is NOTABUG, since I for one did not do anything other than accept the preupgrade defaults. If 'skip bootloader configuration' is a default, than that itself would seem to be a bug.
(In reply to comment #6) > (In reply to comment #4) > > This is NOTABUG, because you chose 'skip bootloader configuration' at > > upgrade time For the record: that choice is unfortunately done automatically by upgrade - see 827987. > I also ran into bug 810346 doing a preupgrade from 16 -> 17, No; bug 810346 was for usb install - not for preupgrade. > and after > fixing it with 'sudo grub2-mkconfig -o /boot/grub2/grub.cfg' I also ran into > this bug. You got the same symptoms - not necessarily the same problem. This report is a bit unclear and doesn't mention the installation method. It is probably not preupgrade and your problem is probably different. > I'm not sure why this is NOTABUG, since I for one did not do > anything other than accept the preupgrade defaults. If 'skip bootloader > configuration' is a default, than that itself would seem to be a bug. Other installation methods has the option of choosing to not install a bootloader - something a power user might need. Choosing that option and not handling it is not a bug.
I see. Thanks for clarifying Mads.