Description of problem: After "dnf update" having installed new kernels, new installed kernels are not added in grub2 boot menu. Version-Release number of selected component (if applicable): grub2-common-2.02-80.fc30.noarch How reproducible: Always Steps to Reproduce: 1. Booting 2. 3. Actual results: The grub2 menu is not up to date Expected results: Additional info: Coming from bug 1652806
Unfortunately, I'm not able to attached the requested files: Error 500 - Internal Server Error The server encountered an internal error and was unable to complete your request.
I have done, in this order: I have installed the grubby-deprecated package. I have created the attached tar file containing the requested files. I have entered "grub2-mkconfig -o" saving the output in a scratch file. I have entered "grub2-install /dev/sda". I have entered "grub2-mkconfig -o" saving the output in another scratch file. I have compared both output files of grub2-mkconfig and I have found then identical. I have saved such a file as /boot/grub2/tentative.cfg. I have booted and used this /boot/grub2/tentative.cfg as configfile of grub2. The first look is that the boot was successful. I will have to see what will happen at the next kernel installation by dnf. I will try to update the requested files later, when the server will accept them.
Created attachment 1571516 [details] /etc/default/grub
Created attachment 1571525 [details] /boot/grub2/grubenv
Created attachment 1571526 [details] /boot/grub2/grub.cfg
Created attachment 1571527 [details] /boot/loader/entries/72d3a4c728fc44929d30dbf0ee8dc601-0-rescue.conf
Created attachment 1571528 [details] /boot/loader/entries/72d3a4c728fc44929d30dbf0ee8dc601-5.0.11-100.fc28.i686.conf
Created attachment 1571529 [details] /boot/loader/entries/72d3a4c728fc44929d30dbf0ee8dc601-5.0.13-300.fc30.i686.conf
Created attachment 1571530 [details] /boot/loader/entries/72d3a4c728fc44929d30dbf0ee8dc601-5.0.14-300.fc30.i686.conf
Created attachment 1571531 [details] /boot/loader/entries/72d3a4c728fc44929d30dbf0ee8dc601-5.0.16-300.fc30.i686.conf
(In reply to Claude Frantz from comment #5) > Created attachment 1571526 [details] > /boot/grub2/grub.cfg The problem is that you have a non-BLS grub.cfg that contains the menu entries but have GRUB_ENABLE_BLSCFG=true in your /etc/default/grub. You should set it to false if you don't want to use a BLS configuration.
I suspect that the problem started with the upgrade from Fedora 28 to 30. To be honest, I have no problem if BLS configuration is installed and running well. What do you suggest me to return to a clean situation with BLS configuration ? Please remember, that the attached files are in the state before I have run grub2-mkconfig. See comment 2.
(In reply to Claude Frantz from comment #12) > I suspect that the problem started with the upgrade from Fedora 28 to 30. To > be honest, I have no problem if BLS configuration is installed and running > well. > > What do you suggest me to return to a clean situation with BLS configuration > ? Please remember, that the attached files are in the state before I have > run grub2-mkconfig. See comment 2. I would suggest to keep GRUB_ENABLE_BLSCFG=true in your /etc/default/grub, generate a grub.cfg with GRUB_ENABLE_BLSCFG=true and remove the grubby-deprecated package (since it's only needed with a non-BLS config).
OK ! Thanks ! The current grub.cfg has been generated with GRUB_ENABLE_BLSCFG=true, so it needs not to be changed. I have simply removed the grubby-deprecated package.
I have another system running f28 and I have to upgrade it to f30. Exactly the same situation as I had. The grubby-deprecated package doesn't exist in f28. I suspect that the upgrade process will again result in a non bootable system. What can I do in order to try to avoid this situation ? Is it a good idea to simply insert GRUB_ENABLE_BLSCFG="false" in /etc/default/grub ?
(In reply to Claude Frantz from comment #15) > I have another system running f28 and I have to upgrade it to f30. Exactly > the same situation as I had. > > The grubby-deprecated package doesn't exist in f28. I suspect that the > upgrade process will again result in a non bootable system. What can I do in > order to try to avoid this situation ? > > Is it a good idea to simply insert GRUB_ENABLE_BLSCFG="false" in > /etc/default/grub ? Just run grub2-install before doing your upgrade to make sure that you have a recent GRUB core.img as mentioned here: https://fedoraproject.org/wiki/Common_F30_bugs#GRUB_boot_menu_is_not_populated_after_an_upgrade
I have this problem in F29 [1] grub2-common-2.02-62.fc29.noarch grub2-efi-ia32-2.02-62.fc29.x86_64 grub2-pc-2.02-62.fc29.x86_64 grub2-pc-modules-2.02-62.fc29.noarch grub2-tools-2.02-62.fc29.x86_64 grub2-tools-efi-2.02-62.fc29.x86_64 grub2-tools-extra-2.02-62.fc29.x86_64 grub2-tools-minimal-2.02-62.fc29.x86_64 grubby-8.40-18.fc29.x86_64 grubby-bls-8.40-18.fc29.noarch grub-customizer-5.1.0-1.fc29.x86_64
(In reply to Sergio Monteiro Basto from comment #17) > I have this problem in F29 [1] > > > > grub2-common-2.02-62.fc29.noarch > grub2-efi-ia32-2.02-62.fc29.x86_64 > grub2-pc-2.02-62.fc29.x86_64 > grub2-pc-modules-2.02-62.fc29.noarch > grub2-tools-2.02-62.fc29.x86_64 > grub2-tools-efi-2.02-62.fc29.x86_64 > grub2-tools-extra-2.02-62.fc29.x86_64 > grub2-tools-minimal-2.02-62.fc29.x86_64 > grubby-8.40-18.fc29.x86_64 > grubby-bls-8.40-18.fc29.noarch You need to remove grubby-bls. Unless you switched your F29 configuration to BLS.
(In reply to Javier Martinez Canillas from comment #18) > (In reply to Sergio Monteiro Basto from comment #17) > > I have this problem in F29 [1] > > > > > > > > grub2-common-2.02-62.fc29.noarch > > grub2-efi-ia32-2.02-62.fc29.x86_64 > > grub2-pc-2.02-62.fc29.x86_64 > > grub2-pc-modules-2.02-62.fc29.noarch > > grub2-tools-2.02-62.fc29.x86_64 > > grub2-tools-efi-2.02-62.fc29.x86_64 > > grub2-tools-extra-2.02-62.fc29.x86_64 > > grub2-tools-minimal-2.02-62.fc29.x86_64 > > grubby-8.40-18.fc29.x86_64 > > grubby-bls-8.40-18.fc29.noarch > > You need to remove grubby-bls. Unless you switched your F29 configuration to > BLS. yes, it fixes thanks .
According to your recommendation, I have ran grub2-install before doing your upgrade. The upgrade process ended without problem but the system was not able to boot, but the new situation is different now. grub2 booted well and plymouth was started but then stopped with the message "Failed to Start Switch Root". After some investigation, I have found that root= had probably no or a wrong value. Here are the steps which I have ran next: Reboot. In the grub2 menu, I have edited the highlighted entry, adding "root=LABEL=root" at the end of the line beginning with "linux" and I have allowed to boot. The partition which should be mounted at "/" has this label "root". The system booted well. I have entered "dnf update". It ended with just a warning about skipped packages. No critical ones. I have ran "grub2-mkconfig -o /boot/grub2/grub.cfg". It ended without error. Reboot. Stopped again with he message "Failed to Start Switch Root". Reboot with the edited grub2 line as previously. The system started. I have added "root=LABEL=root" at the end of the "GRUB_CMDLINE_LINUX" in /etc/default/grub. Then grub2-mkconfig again, no error message displayed. Reboot without editing the highlighted line in the grub2 menu. Again got the message "Failed to Start Switch Root". I'm suspecting dracut now. What can I do now ?
In addition to the above mentioned procedure, I have tried to run grub2-install and grub2-mkconfig again, on the upgraded system. Now, the system is able to start itself, on power on, as expected.
(In reply to Javier Martinez Canillas from comment #18) > (In reply to Sergio Monteiro Basto from comment #17) > > I have this problem in F29 [1] > > > > > > > > grub2-common-2.02-62.fc29.noarch > > grub2-efi-ia32-2.02-62.fc29.x86_64 > > grub2-pc-2.02-62.fc29.x86_64 > > grub2-pc-modules-2.02-62.fc29.noarch > > grub2-tools-2.02-62.fc29.x86_64 > > grub2-tools-efi-2.02-62.fc29.x86_64 > > grub2-tools-extra-2.02-62.fc29.x86_64 > > grub2-tools-minimal-2.02-62.fc29.x86_64 > > grubby-8.40-18.fc29.x86_64 > > grubby-bls-8.40-18.fc29.noarch > > You need to remove grubby-bls. Unless you switched your F29 configuration to > BLS. Moving to grubby component . Seems to be a grubby fault , shouldn't we force just have one grubby in system ? Thanks
It happens again with me, [1] doesn't add new entry in grub boot menu . and with verbose [2] and with command [3] which a command of grub2-common on 99-grub-mkconfig.install I find out that wan't run in my machine [4] exits with exit 0 . How is suppose have an KERNEL_INSTALL_MACHINE_ID variable ? Thanks [1] /bin/kernel-install add 5.2.13-200.fc30.x86_64 /lib/modules/5.2.13-200.fc30.x86_64/vmlinuz || exit $? [2] /bin/kernel-install --verbose add 5.2.13-200.fc30.x86_64 /lib/modules/5.2.13-200.fc30.x86_64/vmlinuz [3] /usr/lib/kernel/install.d/99-grub-mkconfig.install add 5.2.13-200.fc30.x86_64 /boot/07adf8bb49c3c0cad262e42800000010/5.2.13-200.fc30.x86_64 /lib/modules/5.2.13-200.fc30.x86_64/vmlinuz [4] if ! [[ $KERNEL_INSTALL_MACHINE_ID ]]; then echo exit 0 exit 0 fi
After run "systemd-machine-id-setup", it seems that fix this issue ( new installed kernels are not added in grub2 boot menu ) , after read this commit [1], I guessed that, I needed to run systemd-machine-id-setup , my laptop is an F30 upgraded from F29, F28 etc. [1] https://src.fedoraproject.org/rpms/grub2/c/db5dccf3325bf366642be1556d71e2fabccef496
see also https://bugzilla.redhat.com/show_bug.cgi?id=1713902
(In reply to Sergio Monteiro Basto from comment #24) > After run "systemd-machine-id-setup", it seems that fix this issue ( new > installed kernels are not added in grub2 boot menu ) , after read this > commit [1], I guessed that, I needed to run systemd-machine-id-setup , my > laptop is an F30 upgraded from F29, F28 etc. > > > [1] > https://src.fedoraproject.org/rpms/grub2/c/ > db5dccf3325bf366642be1556d71e2fabccef496 I'm surprised that you didn't have an /etc/machine-id set.
Closing this as NOTABUG since it was caused by a missing /etc/machine-id.