Cannot boot after 2nd install

[Patrick Dupre]

Hello,

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
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

Also, when booting (before grub), I have
options
/EFI/BOOT/BOOTx64.EFI (this on let be boot on the new install)
/EFI/fedora/grub.cfg
/EFI/fedora/shimx64.efi

Which one should I use preferentially?

Thank

===========================================================================
 Patrick DUPRÉ                                 | | email: [e-mail]
 Laboratoire interdisciplinaire Carnot de Bourgogne
 9 Avenue Alain Savary, BP 47870, 21078 DIJON Cedex FRANCE
 Tel: [phone]
===========================================================================

[Patrick Dupre]

Here is the log

[^[[0;32m  OK  ^[[0m] Mounted ^[[0;1;39m/home^[[0m.
[^[[0;32m  OK  ^[[0m] Started ^[[0;1;39mFile System Check on /dev/disk/by-uuid/B2EF-0CE4^[[0m.
[^[[0;32m  OK  ^[[0m] Mounted ^[[0;1;39m/tmp^[[0m.
[^[[0;32m  OK  ^[[0m] Mounted ^[[0;1;39m/usr/local^[[0m.
[^[[0;32m  OK  ^[[0m] Started ^[[0;1;39mFile System Check on /dev/sda4^[[0m.
         Mounting ^[[0;1;39m/boot/efi^[[0m...
         Mounting ^[[0;1;39m/home/pdupre/archives^[[0m...
[^[[0;1;31mFAILED^[[0m] Failed to mount ^[[0;1;39m/boot/efi^[[0m.
See 'systemctl status boot-efi.mount' for details
[^[[0;1;33mDEPEND^[[0m] Dependency failed for ^[[0;1;39mLocal File Systems^[[0m.
         Starting ^[[0;1;39mRestore /run/initramfs on shutdown^[[0m...

The partition /boot/efi is actually
/dev/disk/by-uuid/B2EF-0CE4

This is bizarre, it mounts perfectly well from the other boot
I cannot run
systemctl status boot-efi.mount

===========================================================================
 Patrick DUPRÉ                                 | | email: [e-mail]
 Laboratoire interdisciplinaire Carnot de Bourgogne
 9 Avenue Alain Savary, BP 47870, 21078 DIJON Cedex FRANCE
 Tel: [phone]
===========================================================================
> Sent: Tuesday, June 25, 2019 at 1:42 PM
> From: "Patrick Dupre" 
> To: fedora 
> Subject: Cannot boot after 2nd install
>
> Hello,
>
> 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
> 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
>
> Also, when booting (before grub), I have
> options
> /EFI/BOOT/BOOTx64.EFI (this on let be boot on the new install)
> /EFI/fedora/grub.cfg
> /EFI/fedora/shimx64.efi
>
> Which one should I use preferentially?
>
> Thank
>
> ===========================================================================
>  Patrick DUPRÉ                                 | | email: [e-mail]
>  Laboratoire interdisciplinaire Carnot de Bourgogne
>  9 Avenue Alain Savary, BP 47870, 21078 DIJON Cedex FRANCE
>  Tel: [phone]
> ===========================================================================
> _______________________________________________
> users mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> 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/[e-mail]

[Patrick Dupre]

Another thing that I do not understand is this
/boot/efi/EFI/fedora/grub.cfg
## BEGIN /etc/grub.d/10_linux ###
insmod part_gpt
insmod ext2
set root='hd0,gpt6'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt6 --hint-efi=hd0,gpt6 --hint-baremetal=ahci0,gpt6  a5b809ae-61c2-4d67-b0f3-109e99faad39
else
  search --no-floppy --fs-uuid --set=root a5b809ae-61c2-4d67-b0f3-109e99faad39
fi
insmod part_gpt
insmod fat
set boot='hd1,gpt1'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=boot --hint-bios=hd1,gpt1 --hint-efi=hd1,gpt1 --hint-baremetal=ahci1,gpt1  B2EF-0CE4
else
  search --no-floppy --fs-uuid --set=boot B2EF-0CE4
fi

Why for the system
set boot='hd1,gpt1'
we have
search --no-floppy --fs-uuid --set=boot B2EF-0CE4
and not
search --no-floppy --fs-uuid --set=root 4f724cae-bdb7-4a76-a1d0-560a78805862
(like search --no-floppy --fs-uuid --set=root a5b809ae-61c2-4d67-b0f3-109e99faad39)
since 4f724cae-bdb7-4a76-a1d0-560a78805862
is the / for the system which does not start

===========================================================================
 Patrick DUPRÉ                                 | | email: [e-mail]
 Laboratoire interdisciplinaire Carnot de Bourgogne
 9 Avenue Alain Savary, BP 47870, 21078 DIJON Cedex FRANCE
 Tel: [phone]
===========================================================================
> Sent: Tuesday, June 25, 2019 at 2:55 PM
> From: "Patrick Dupre" 
> To: [e-mail]
> Cc: fedora 
> Subject: Re: Cannot boot after 2nd install
>
> Here is the log
>
> [^[[0;32m  OK  ^[[0m] Mounted ^[[0;1;39m/home^[[0m.
> [^[[0;32m  OK  ^[[0m] Started ^[[0;1;39mFile System Check on /dev/disk/by-uuid/B2EF-0CE4^[[0m.
> [^[[0;32m  OK  ^[[0m] Mounted ^[[0;1;39m/tmp^[[0m.
> [^[[0;32m  OK  ^[[0m] Mounted ^[[0;1;39m/usr/local^[[0m.
> [^[[0;32m  OK  ^[[0m] Started ^[[0;1;39mFile System Check on /dev/sda4^[[0m.
>          Mounting ^[[0;1;39m/boot/efi^[[0m...
>          Mounting ^[[0;1;39m/home/pdupre/archives^[[0m...
> [^[[0;1;31mFAILED^[[0m] Failed to mount ^[[0;1;39m/boot/efi^[[0m.
> See 'systemctl status boot-efi.mount' for details
> [^[[0;1;33mDEPEND^[[0m] Dependency failed for ^[[0;1;39mLocal File Systems^[[0m.
>          Starting ^[[0;1;39mRestore /run/initramfs on shutdown^[[0m...
>
> The partition /boot/efi is actually
> /dev/disk/by-uuid/B2EF-0CE4
>
> This is bizarre, it mounts perfectly well from the other boot
> I cannot run
> systemctl status boot-efi.mount
>
> ===========================================================================
>  Patrick DUPRÉ                                 | | email: [e-mail]
>  Laboratoire interdisciplinaire Carnot de Bourgogne
>  9 Avenue Alain Savary, BP 47870, 21078 DIJON Cedex FRANCE
>  Tel: [phone]
> ===========================================================================
> > Sent: Tuesday, June 25, 2019 at 1:42 PM
> > From: "Patrick Dupre" 
> > To: fedora 
> > Subject: Cannot boot after 2nd install
> >
> > Hello,
> >
> > 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
> > 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
> >
> > Also, when booting (before grub), I have
> > options
> > /EFI/BOOT/BOOTx64.EFI (this on let be boot on the new install)
> > /EFI/fedora/grub.cfg
> > /EFI/fedora/shimx64.efi
> >
> > Which one should I use preferentially?
> >
> > Thank
> >
> > ===========================================================================
> >  Patrick DUPRÉ                                 | | email: [e-mail]
> >  Laboratoire interdisciplinaire Carnot de Bourgogne
> >  9 Avenue Alain Savary, BP 47870, 21078 DIJON Cedex FRANCE
> >  Tel: [phone]
> > ===========================================================================
> > _______________________________________________
> > users mailing list -- [e-mail]
> > To unsubscribe send an email to [e-mail]
> > 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/[e-mail]
>
> users mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> 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/[e-mail]

[Patrick Dupre]

Hello,

It is still not fixed,
I get a 
Failed to switch root: Specified switch root path '/sysroot' does not seem to be an OS tree. os-release file is missing

It seems that the kernel for the first system are not seen:
grubby --info ALL
index=0
kernel="/boot/boot/vmlinuz-5.1.12-300.fc30.x86_64"
args="ro resume=UUID=23cdaeb2-fca4-4dde-83ed-4fb3235267a0"
root="UUID=a5b809ae-61c2-4d67-b0f3-109e99faad39"
initrd="/boot/boot/initramfs-5.1.12-300.fc30.x86_64.img"
title="Fedora (5.1.12-300.fc30.x86_64) 30 (Thirty)"
id="03f1745f56634738ac83375619d247ec-5.1.12-300.fc30.x86_64"
index=1
kernel="/boot/boot/vmlinuz-5.0.9-301.fc30.x86_64"
args="ro resume=UUID=23cdaeb2-fca4-4dde-83ed-4fb3235267a0"
root="UUID=a5b809ae-61c2-4d67-b0f3-109e99faad39"
initrd="/boot/boot/initramfs-5.0.9-301.fc30.x86_64.img"
title="Fedora (5.0.9-301.fc30.x86_64) 30 (Thirty)"
id="03f1745f56634738ac83375619d247ec-5.0.9-301.fc30.x86_64"
index=2
kernel="/boot/vmlinuz-0-rescue-03f1745f56634738ac83375619d247ec"
args="ro resume=UUID=23cdaeb2-fca4-4dde-83ed-4fb3235267a0"
root="UUID=a5b809ae-61c2-4d67-b0f3-109e99faad39"
initrd="/boot/initramfs-0-rescue-03f1745f56634738ac83375619d247ec.img"
title="Fedora (0-rescue-03f1745f56634738ac83375619d247ec) 30 (Thirty)"
id="03f1745f56634738ac83375619d247ec-0-rescue"

but in
/boot/efi/EFI/fedora/grub.cfg
which I guess is read by both system I have:

menuentry 'Fedora 30 (Workstation Edition) (on /dev/mapper/VolSys_0-root)' --class fedora --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-simple-4f724cae-bdb7-4a76-a1d0-560a78805862' {
        insmod part_gpt
        insmod lvm
        insmod ext2
        set root='lvmid/W6k0N8-5JlY-Xntk-w8Yi-Ss1F-I0IY-VzPRU3/vE133D-nAZ8-ltwF-2o4x-H6Cs-a9l5-19IRw4'
        if [ x$feature_platform_search_hint = xy ]; then
          search --no-floppy --fs-uuid --set=root --hint='lvmid/W6k0N8-5JlY-Xntk-w8Yi-Ss1F-I0IY-VzPRU3/vE133D-nAZ8-ltwF-2o4x-H6Cs-a9l5-19IRw4'  4f724cae-bdb7-4a76-a1d0-560a78805862
        else
          search --no-floppy --fs-uuid --set=root 4f724cae-bdb7-4a76-a1d0-560a78805862
        fi
        linux /boot/vmlinuz-0-rescue-294b6062d63640a59a0bcd0bf1ff6bbd root=/dev/dm-2
        initrd /boot/initramfs-0-rescue-294b6062d63640a59a0bcd0bf1ff6bbd.img
}

which should be boot!
I guess that it has been taken properly

but I get
Failed to switch root: Specified switch root path '/sysroot' does not seem to be an OS tree. os-release file is missing

===========================================================================
 Patrick DUPRÉ                                 | | email: [e-mail]
 Laboratoire interdisciplinaire Carnot de Bourgogne
 9 Avenue Alain Savary, BP 47870, 21078 DIJON Cedex FRANCE
 Tel: [phone]
===========================================================================
> Sent: Tuesday, June 25, 2019 at 3:37 PM
> From: "Patrick Dupre" 
> To: [e-mail]
> Cc: [e-mail]
> Subject: Re: Cannot boot after 2nd install
>
> Another thing that I do not understand is this
> /boot/efi/EFI/fedora/grub.cfg
> ## BEGIN /etc/grub.d/10_linux ###
> insmod part_gpt
> insmod ext2
> set root='hd0,gpt6'
> if [ x$feature_platform_search_hint = xy ]; then
>   search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt6 --hint-efi=hd0,gpt6 --hint-baremetal=ahci0,gpt6  a5b809ae-61c2-4d67-b0f3-109e99faad39
> else
>   search --no-floppy --fs-uuid --set=root a5b809ae-61c2-4d67-b0f3-109e99faad39
> fi
> insmod part_gpt
> insmod fat
> set boot='hd1,gpt1'
> if [ x$feature_platform_search_hint = xy ]; then
>   search --no-floppy --fs-uuid --set=boot --hint-bios=hd1,gpt1 --hint-efi=hd1,gpt1 --hint-baremetal=ahci1,gpt1  B2EF-0CE4
> else
>   search --no-floppy --fs-uuid --set=boot B2EF-0CE4
> fi
>
> Why for the system
> set boot='hd1,gpt1'
> we have
> search --no-floppy --fs-uuid --set=boot B2EF-0CE4
> and not
> search --no-floppy --fs-uuid --set=root 4f724cae-bdb7-4a76-a1d0-560a78805862
> (like search --no-floppy --fs-uuid --set=root a5b809ae-61c2-4d67-b0f3-109e99faad39)
> since 4f724cae-bdb7-4a76-a1d0-560a78805862
> is the / for the system which does not start
>
> ===========================================================================
>  Patrick DUPRÉ                                 | | email: [e-mail]
>  Laboratoire interdisciplinaire Carnot de Bourgogne
>  9 Avenue Alain Savary, BP 47870, 21078 DIJON Cedex FRANCE
>  Tel: [phone]
> ===========================================================================
> > Sent: Tuesday, June 25, 2019 at 2:55 PM
> > From: "Patrick Dupre" 
> > To: [e-mail]
> > Cc: fedora 
> > Subject: Re: Cannot boot after 2nd install
> >
> > Here is the log
> >
> > [^[[0;32m  OK  ^[[0m] Mounted ^[[0;1;39m/home^[[0m.
> > [^[[0;32m  OK  ^[[0m] Started ^[[0;1;39mFile System Check on /dev/disk/by-uuid/B2EF-0CE4^[[0m.
> > [^[[0;32m  OK  ^[[0m] Mounted ^[[0;1;39m/tmp^[[0m.
> > [^[[0;32m  OK  ^[[0m] Mounted ^[[0;1;39m/usr/local^[[0m.
> > [^[[0;32m  OK  ^[[0m] Started ^[[0;1;39mFile System Check on /dev/sda4^[[0m.
> >          Mounting ^[[0;1;39m/boot/efi^[[0m...
> >          Mounting ^[[0;1;39m/home/pdupre/archives^[[0m...
> > [^[[0;1;31mFAILED^[[0m] Failed to mount ^[[0;1;39m/boot/efi^[[0m.
> > See 'systemctl status boot-efi.mount' for details
> > [^[[0;1;33mDEPEND^[[0m] Dependency failed for ^[[0;1;39mLocal File Systems^[[0m.
> >          Starting ^[[0;1;39mRestore /run/initramfs on shutdown^[[0m...
> >
> > The partition /boot/efi is actually
> > /dev/disk/by-uuid/B2EF-0CE4
> >
> > This is bizarre, it mounts perfectly well from the other boot
> > I cannot run
> > systemctl status boot-efi.mount
> >
> > ===========================================================================
> >  Patrick DUPRÉ                                 | | email: [e-mail]
> >  Laboratoire interdisciplinaire Carnot de Bourgogne
> >  9 Avenue Alain Savary, BP 47870, 21078 DIJON Cedex FRANCE
> >  Tel: [phone]
> > ===========================================================================
> > > Sent: Tuesday, June 25, 2019 at 1:42 PM
> > > From: "Patrick Dupre" 
> > > To: fedora 
> > > Subject: Cannot boot after 2nd install
> > >
> > > Hello,
> > >
> > > 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
> > > 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
> > >
> > > Also, when booting (before grub), I have
> > > options
> > > /EFI/BOOT/BOOTx64.EFI (this on let be boot on the new install)
> > > /EFI/fedora/grub.cfg
> > > /EFI/fedora/shimx64.efi
> > >
> > > Which one should I use preferentially?
> > >
> > > Thank
> > >
> > > ===========================================================================
> > >  Patrick DUPRÉ                                 | | email: [e-mail]
> > >  Laboratoire interdisciplinaire Carnot de Bourgogne
> > >  9 Avenue Alain Savary, BP 47870, 21078 DIJON Cedex FRANCE
> > >  Tel: [phone]
> > > ===========================================================================
> > > _______________________________________________
> > > users mailing list -- [e-mail]
> > > To unsubscribe send an email to [e-mail]
> > > 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/[e-mail]
> >
> > users mailing list -- [e-mail]
> > To unsubscribe send an email to [e-mail]
> > 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/[e-mail]
>
> users mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> 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/[e-mail]

[Samuel Sieb]

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!
> 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.

[Patrick Dupre]

> 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 -- [e-mail]
> To unsubscribe send an email to [e-mail]
> 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/[e-mail]