grub-efi-bootloader doesn't make multiple boot entries with efibootmgr if multiple targets are specified

  • Open
  • quality assurance status badge
Details
2 participants
  • Oleg Pykhalov
  • Nathan Dehnel
Owner
unassigned
Submitted by
Nathan Dehnel
Severity
normal
N
N
Nathan Dehnel wrote on 3 Mar 00:01 +0100
(name . bug-guix)(address . bug-guix@gnu.org)
CAEEhgEvBfvTnH7FsgRozrtErHNiGQv7-GPs_xQJYDHE=Hd0Y1g@mail.gmail.com
(bootloader
(bootloader-configuration
(bootloader grub-efi-bootloader)
(targets '("/boot/efi1" "/boot/efi2"))

This creates multiple boot partitions, but doesn't register all of
them with the BIOS/create multiple boot entries
O
O
Oleg Pykhalov wrote on 3 Mar 08:31 +0100
(name . Nathan Dehnel)(address . ncdehnel@gmail.com)(address . 69515@debbugs.gnu.org)
87jzmjojox.fsf@gmail.com
Hi,

Nathan Dehnel <ncdehnel@gmail.com> writes:

Toggle quote (8 lines)
> (bootloader
> (bootloader-configuration
> (bootloader grub-efi-bootloader)
> (targets '("/boot/efi1" "/boot/efi2"))
>
> This creates multiple boot partitions, but doesn't register all of
> them with the BIOS/create multiple boot entries

It appears that the reason for the issue is that the EFI file is
identical on both targets. Could this behavior actually be considered a
bug? Consider the scenario of a multi-disk system; have you attempted to
remove one of the disks and observe the boot process to determine if the
duplicated EFI file is causing unexpected behavior?

Regards,
Oleg.
-----BEGIN PGP SIGNATURE-----

iQJIBAEBCgAyFiEEcjhxI46s62NFSFhXFn+OpQAa+pwFAmXkJ04UHGdvLndpZ3Vz
dEBnbWFpbC5jb20ACgkQFn+OpQAa+pyh7Q//Wb3dGLcNQRVWDHzcSM44O0IyFS3H
0TdJXJMFVM91WJTjtpCKGHcBT726IC5M8wSmu4IPcYAJ04zyU6knEIJpXgbfxh6M
5k53dj5WFE8Br+5+Kch6c4lRq7XQ7xCOb9AVyxKxufX3mAAfTTmi2KbRxB59muQu
G4AWmt719GC6sa/80RwBpaRBJzDdv57SQfTH+OaJBPfsJETQHlQ79RW7h+mrAF4J
SOapiOkm2+eVGRh89F7VfLXWEzknYR2AG32JC8Giv9V+cMOVnq4bWZglzj36Uy0d
cAC2lrMTB1VL0OC4L3vFydyLWoz+lLBp/zflFadudfD7DAo2YRJdtoBhgMT0ldYv
5sImCZ2hPV5OtCHiS+PMgsK+zW5AuVnVG1lRA0HL0URANmu8jdaMofCw+8q/kb+x
xhctCfQqqBGX6OLUD0yvRtAamvKCT88gOksBWSAjDhGWqPM8FHODSSQaz3deUOeS
JVvRNBDGSpgvSW/xsvEBUCfoHrL7xr5BCYopdisCwvwxfyQ5W+Ukz31ndXpGHBkr
jvZwexJrW55Vnc6hJaFHVLRojq+148zwTUv2hJdp/KLvO0wnRmsuIYwhggZ/C+Lf
gu3wN6ImwuJi0c5MPJfLBeuOW8t6VeAgeBGAzOCSXBE/nbOfD9P3Z8Ju4TQrr/ZE
+fQdqud6jEzIaio=
=SA4H
-----END PGP SIGNATURE-----

N
N
Nathan Dehnel wrote on 3 Mar 23:45 +0100
(name . Oleg Pykhalov)(address . go.wigust@gmail.com)(address . 69515@debbugs.gnu.org)
CAEEhgEt2AyEnF92aMgRhm-XrkTc8RdmQHwa2iKL9qsGhqzHkSQ@mail.gmail.com
The configure makes only one boot entry, and if I remove one of the
disks, it disappears from the BIOS boot options. If I make another
boot entry manually with efibootmgr, it appears as a second boot
option.

On Sun, Mar 3, 2024 at 1:31?AM Oleg Pykhalov <go.wigust@gmail.com> wrote:
Toggle quote (21 lines)
>
> Hi,
>
> Nathan Dehnel <ncdehnel@gmail.com> writes:
>
> > (bootloader
> > (bootloader-configuration
> > (bootloader grub-efi-bootloader)
> > (targets '("/boot/efi1" "/boot/efi2"))
> >
> > This creates multiple boot partitions, but doesn't register all of
> > them with the BIOS/create multiple boot entries
>
> It appears that the reason for the issue is that the EFI file is
> identical on both targets. Could this behavior actually be considered a
> bug? Consider the scenario of a multi-disk system; have you attempted to
> remove one of the disks and observe the boot process to determine if the
> duplicated EFI file is causing unexpected behavior?
>
> Regards,
> Oleg.
?
Your comment

Commenting via the web interface is currently disabled.

To comment on this conversation send an email to 69515@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 69515
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch