Created attachment 1580927 [details] buggy grub.cfg as generated with GRUB_ENABLE_BLSCFG=true quand je démarre, j'arrive sur un grub avec une seule entrée W7 qui n’aboutit à rien. la commande *configfile /grub2/grub.cfg.rpmsave* me permet d'accéder au menu de Grub, et celui ci me donne le grub tel qu'il était en F29, et je peux démarrer La commande *grub2-install /dev/sda* ne retourne pas d'erreur Description of problem: after f29 to f30 upgrade using dnf, grub contains no linux entry The workarount is here: https://fedoraproject.org/wiki/Common_F30_bugs#GRUB_boot_menu_is_not_populated_after_an_upgrade the command `grub> configfile /grub2/grub.cfg.rpmsave` displays the previous grub and I can boot using f29 kernel Version-Release number of selected component (if applicable): Grub 2.03 How reproducible: Always Steps to Reproduce: 1. Setting GRUB_ENABLE_BLSCFG=true 2. sudo grub2-mkconfig -o /boot/grub2/grub.cfg 3. reboot, no linux option will be displayed Actual results: [jean-baptiste@jportable ~]$ sudo grub2-mkconfig -o /boot/grub2/grub.cfg Generating grub configuration file ... Found Windows 7 on /dev/sda1 done Expected results: With *GRUB_ENABLE_BLSCFG=false* [jean-baptiste@jportable ~]$ sudo grub2-mkconfig -o /boot/grub2/grub.cfg Generating grub configuration file ... Found linux image: /boot/vmlinuz-5.1.8-300.fc30.x86_64 Found initrd image: /boot/initramfs-5.1.8-300.fc30.x86_64.img Found linux image: /boot/vmlinuz-5.0.13-300.fc30.x86_64 Found initrd image: /boot/initramfs-5.0.13-300.fc30.x86_64.img Found linux image: /boot/vmlinuz-5.0.13-200.fc29.x86_64 Found initrd image: /boot/initramfs-5.0.13-200.fc29.x86_64.img Found linux image: /boot/vmlinuz-0-rescue-a662f91c1e5341819cc96eabdef3540c Found initrd image: /boot/initramfs-0-rescue-a662f91c1e5341819cc96eabdef3540c.img Additional info: [jean-baptiste@jportable ~]$ cat /etc/default/grub GRUB_TIMEOUT=5 GRUB_DISTRIBUTOR="$(sed 's, release .*$,,g' /etc/system-release)" GRUB_DEFAULT=saved GRUB_DISABLE_SUBMENU=true GRUB_TERMINAL_OUTPUT="console" GRUB_CMDLINE_LINUX="rd.luks.uuid=luks-5bb46ab4-aa47-4af7-82a4-4f2ab9d35549 rd.luks.uuid=luks-7c207cba-1f09-47a4-822e-e64221b474f7 rhgb quiet iomem=relaxed nopat" GRUB_DISABLE_RECOVERY="true" GRUB_ENABLE_BLSCFG=true [jean-baptiste@jportable ~]$ sudo grubby --default-kernel /boot/vmlinuz-5.1.8-300.fc30.x86_64 [jean-baptiste@jportable ~]$ cat /etc/fstab # # /etc/fstab # Created by anaconda on Sun May 31 14:23:42 2015 # # Accessible filesystems, by reference, are maintained under '/dev/disk' # See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info # /dev/mapper/luks-5bb46ab4-aa47-4af7-82a4-4f2ab9d35549 / ext4 defaults,x-systemd.device-timeout=0 1 1 /dev/mapper/luks-58cddefa-1c94-4204-bd50-5446ac69d94a /home ext4 defaults,x-systemd.device-timeout=0 1 1 UUID=eea720b7-01d0-404c-acd5-240a3896c540 /boot ext4 defaults 1 2 /dev/mapper/luks-7c207cba-1f09-47a4-822e-e64221b474f7 swap swap defaults,x-systemd.device-timeout=0 0 0 [jean-baptiste@jportable ~]$ sudo blkid -a blkid : option invalide -- 'a' Exécutez « blkid --help » pour obtenir des renseignements complémentaires. [jean-baptiste@jportable ~]$ sudo blkid /dev/sda1: LABEL="SYSTEM_DRV" UUID="0CFEC97AFEC95C98" TYPE="ntfs" PARTUUID="a205ed9e-01" /dev/sda2: UUID="58cddefa-1c94-4204-bd50-5446ac69d94a" TYPE="crypto_LUKS" PARTUUID="a205ed9e-02" /dev/sda3: UUID="eea720b7-01d0-404c-acd5-240a3896c540" TYPE="ext4" PARTUUID="a205ed9e-03" /dev/sda5: UUID="7c207cba-1f09-47a4-822e-e64221b474f7" TYPE="crypto_LUKS" PARTUUID="a205ed9e-05" /dev/sda6: UUID="5bb46ab4-aa47-4af7-82a4-4f2ab9d35549" TYPE="crypto_LUKS" PARTUUID="a205ed9e-06" /dev/mapper/luks-5bb46ab4-aa47-4af7-82a4-4f2ab9d35549: UUID="22af981a-bf20-4ca6-bf7b-966cc41ef444" TYPE="ext4" /dev/mapper/luks-7c207cba-1f09-47a4-822e-e64221b474f7: UUID="dd9f812f-feeb-406b-8586-5f36f362cefe" TYPE="swap" /dev/mapper/luks-58cddefa-1c94-4204-bd50-5446ac69d94a: LABEL="home" UUID="5a075e2f-2285-46f6-bab5-851684819dea" TYPE="ext4" [jean-baptiste@jportable ~]$ ll /boot/ total 159039 -rw-r--r--. 1 root root 202392 6 mai 03:15 config-5.0.13-200.fc29.x86_64 -rw-r--r--. 1 root root 202395 6 mai 02:58 config-5.0.13-300.fc30.x86_64 -rw-r--r--. 1 root root 204442 9 juin 19:32 config-5.1.8-300.fc30.x86_64 drwx------. 4 root root 1024 12 mai 20:21 efi -rw-r--r--. 1 root root 188476 5 avril 22:24 elf-memtest86+-5.01 drwxr-xr-x. 2 root root 3072 10 mai 2018 extlinux drwx------. 6 root root 1024 20 mai 19:26 grub2 -rw-rw-r--. 1 root root 46568294 31 mai 2015 initramfs-0-rescue-a662f91c1e5341819cc96eabdef3540c.img -rw-------. 1 root root 23100383 12 mai 13:29 initramfs-5.0.13-200.fc29.x86_64.img -rw-------. 1 root root 23158473 12 mai 23:01 initramfs-5.0.13-300.fc30.x86_64.img -rw-------. 1 root root 23170254 15 juin 02:01 initramfs-5.1.8-300.fc30.x86_64.img -rw-r--r--. 1 root root 560539 29 juin 2016 initrd-plymouth.img drwxr-xr-x. 3 root root 1024 10 mai 2018 loader drwx------. 2 root root 12288 31 mai 2015 lost+found -rw-r--r--. 1 root root 186800 5 avril 22:24 memtest86+-5.01 -rw-------. 1 root root 4170938 6 mai 03:14 System.map-5.0.13-200.fc29.x86_64 -rw-------. 1 root root 4173946 6 mai 02:58 System.map-5.0.13-300.fc30.x86_64 -rw-------. 1 root root 4283404 9 juin 19:32 System.map-5.1.8-300.fc30.x86_64 -rwxr-xr-x. 1 root root 5897400 31 mai 2015 vmlinuz-0-rescue-a662f91c1e5341819cc96eabdef3540c -rwxr-xr-x. 1 root root 8872136 6 mai 03:16 vmlinuz-5.0.13-200.fc29.x86_64 -rwxr-xr-x. 1 root root 8872136 6 mai 02:58 vmlinuz-5.0.13-300.fc30.x86_64 -rwxr-xr-x. 1 root root 8991432 9 juin 19:33 vmlinuz-5.1.8-300.fc30.x86_64
Created attachment 1580928 [details] buggy grub.cfg as generated by f29
Created attachment 1580929 [details] correct grub.cfg as generated with GRUB_ENABLE_BLSCFG=false
well, product should be Fedora, version f30, hardware is x86_64, OS is Linux this is a laptop, and I'm using coreboot on it
Changing product and version to Fedora and 30 per Comment 4.
This message is a reminder that Fedora 30 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 30 on 2020-05-26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '30'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 30 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 30 changed to end-of-life (EOL) status on 2020-05-26. Fedora 30 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.