On Mon, Jun 01, 2020 at 11:20:31AM +0200, Patrick Dupre wrote:
with the -v option, I have
BootCurrent: 0000
Timeout: 1 seconds
BootOrder: 0000,0002,0001
Boot0000*
fedora HD(3,GPT,a5c3bc11-e83b-48d0-be96-783af37228f1,0x2001800,0xfa000)/File(\EFI\FEDORA\GRUBX64.EFI)
[...]
However, I do not understand how does this work with multi disks.
We have
/boot/efi/EFI/fedora/grubx64.efi
on each disk ?
Which does not seem to be the case.
If you see in the Fedora entry, it has:
HD(3,GPT,a5c3bc11-e83b-48d0-be96-783af37228f1,0x2001800\
,0xfa000)/File(\EFI\FEDORA\GRUBX64.EFI)
That means to look for a volume with the 3rd GPT partition, with the
UUID of a5c3bc11-e83b-48d0-be96-783af37228f1 (and some other data).
On that disk, look for the /EFI/FEDORA/GRUBX64.EFI executable
(remember, this is a DOS filesystem so it's case-insensitive).
Run 'blkid' on a running system, and you'll see that the PARTUUID of
the EFI volume matches the UUID in the above EFI entry.
You can have an EFI volume on multiple disks. EFI also supports
things like network boot, which has a different syntax EFI entry. The
efibootmgr command does a lot of the hard work of figuring that out
for you, so you don't need to manually enter that information.
--
Jonathan Billings <billings(a)negate.org>