> > On 6/25/19 4:42 AM, Patrick Dupre wrote: > > I have a fedora which was running fine fine on /dev/sdb (/boot/efi on /dev/sdb1) > > Then I install a new fedora 30 on /dev/sda6 (also with /boot/efi on /dev/sdb1) > > When I rebooted, the "old" machine did not show up (at grub), then I run > > grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg > > Now "old" machine is recognized at grub, but I get an error at the boot time > > Fedora 30 changed grub to use BLS instead of a monolithic grub.cfg file. > It will be expecting the boot snippets at /boot/loader/entries. I > have no idea what running that command did to your grub config. > > > I cannot even run a command line (like system*) > > Actually, I get > > Failed to mount /boot/efi > > Should I run: > > grub2-install /dev/sda > > or > > grub2-install /dev/sdb > > Never run grub2-install on an EFI system! Maybe, but this fixed the boot systems on another machine 2 weeks ago. My temporary conclusion is that between fedora 28 and fedora 30, the booting has changed. Before, I has some controls that I completely lost. Could you please provide me the complete information. How to install properly a machine with a multi boot. Obviously, my 3 machines had an issue when I moved to fedora 30. For 2 of them grub2-install --recheck --no-floppy /dev/sda fixed the issue (one is efi, the other is not). My understanding is that grub.cfg contains the information for bls in its first part and the information for the old style of booting menuentry ..... How does it coordinate? It seems that for bls the information come from /boot/loader/entries and that for the old style from the old grub.config only? Question, in grub.cfg Before the bls section: I see set root='lvmid/G99jyd-8w45-PWeO-2Oi0-leh4-grNm-RFEyL3/Noro38-PXZz-9l41-B5ZN-JbUZ-SGP3-etdnYp' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint='lvmid/G99jyd-8w45-PWeO-2Oi0-leh4-grNm-RFEyL3/Noro38-PXZz-9l41-B5ZN-JbUZ-SGP3-etdnYp' 3f027e89-8259-4416-906a-9987ca7abdac else search --no-floppy --fs-uuid --set=root 3f027e89-8259-4416-906a-9987ca7abdac fi insmod part_gpt insmod fat set boot='hd0,gpt3' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=boot --hint-bios=hd0,gpt3 --hint-efi=hd0,gpt3 --hint-baremetal=ahci0,gpt3 5612-030F else search --no-floppy --fs-uuid --set=boot 5612-030F fi This tell me about one boot (3f027e89-8259-4416-906a-9987ca7abdac), but not about the other ones? Thank. > > Also, when booting (before grub), I have > > options > > /EFI/BOOT/BOOTx64.EFI (this on let be boot on the new install) > > This will create new EFI boot entry each time you run it. > > > /EFI/fedora/grub.cfg > > This is a config file, you can't boot it. > > > /EFI/fedora/shimx64.efi > > This is the one that should be booted. The install should have created > an EFI boot entry pointing to this. > _______________________________________________ > users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx > Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx > _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
