RE: UEFI searching for bootx64.efi - but debian has not created this in ESP - help please.
Thank you Pascal
Your final statement in your response answers my question relating to "removable media path"
Ref your questions : <i> What do yo mean exactly ? </i>
As I stated - the /boot directory on the main drive now has new efi files date stamped at the time I ran the reconfigure command
sudo dpkg-reconfigure grub-efi-amd64
>
> : grub-efi-amd64 grub2/force_efi_extra_removable boolean true
Based on responses I think I can now safely move forward with planned deployments
Advisories much appreciated - here is hoping I won't need to ask more questions .
Best
Derrin
-----Original Message-----
From: Pascal Hambourg <pascal@plouf.fr.eu.org>
Sent: 01 December 2022 10:37
To: derrin@usa.net
Cc: debian-efi@lists.debian.org
Subject: Re: UEFI searching for bootx64.efi - but debian has not created this in ESP - help please.
On 30/11/2022 à 11:19, derrin@usa.net wrote:
>
> sudo dpkg-reconfigure grub-efi-amd64
>
> : grub-efi-amd64 grub2/force_efi_extra_removable boolean true
>
> Installing for x86_64-efi platform. Installation finished. No error
> reported.
(...)
> 1) There was a second question in the dialogue relating to NVRAM -
> unsure of response I pressed No.
If you select "no", grub-install will not update the EFI boot entries (default is "yes"). If the UEFI firmware is broken and ignores EFI boot entries, it does not matter. This option is useful when the UEFI firmware is even more broken and hangs when writing the NVRAM.
> Would that be the cause of the message "Warning: os-prober ..."
No, this message is printed by update-grub (grub-mkconfig) and depends on GRUB_DISABLE_OS_PROBER in /etc/default/grub.
> 2) /boot now has a new drop of the related grub-efi-amd64 files - but
> this is not "removable media path"
What do yo mean exactly ?
> Is it a simple case of copying the contents of /boot/grub to the usb
> pen drive that was used to kick start the main install?
>
> (would this over write the removable media /boot/grub?
"Removable media path" has nothing to do with a removable media such as a USB drive. It designates a reserved path /efi/boot/boot{arch}.efi in any EFI system partition which can be booted without an EFI boot entry, so it is used as a workaround when the firmware does not manage EFI boot entries correctly.
Reply to: