On Sat, Oct 3, 2020 at 4:09 AM Marius Schwarz <fedoradev(a)cloud-foo.de> wrote:
Am 03.10.20 um 11:43 schrieb Tomasz Torcz:
If you do not state the devicename, how does grub choose the correct
drive? I don't want to overwrite the bootloader on the ssd.
There is only one correct ESP partition in EFI system to install
bootloader to. You can read the code finding it at
https://github.com/rhboot/grub2/blob/master/util/grub-install.c#L1029
That seems to be commented incorrectly:
L1045:
/*
The EFI System Partition may have been given directly using
--root-directory.
*/
there is no such option according to man and --help .
grub-install [--modules=MODULES] [--install-modules=MODULES]
[--themes=THEMES] [--fonts=FONTS] [--locales=LOCALES]
[--compress[=no,xz,gz,lzo]] [-d | --directory=DIR]
[--grub-mkimage=FILE] [--boot-directory=DIR]
[--target=TARGET] [--grub-setup=FILE]
[--grub-mkrelpath=FILE] [--grub-probe=FILE]
[--allow-floppy] [--recheck] [--force] [--force-file-id]
[--disk-module=MODULE] [--no-nvram] [--removable]
[--bootloader-id=ID] [--efi-directory=DIR] INSTALL_DEVICE
could --efi-directory be meant?
### UPDATE ###
.... after investigating the problem with not finding grub.cfg in the proprosed bootpath
/boot/ .. the solution was simple.
The system died not use secure boot, as secure-boot was disabled for the kernel-surface
kernelseries. They are not signed, so no secure boot possible.
Means: bios is loading "/boot/grub2/grub.cfg" but it can't find it, because
those are symlinks to "/boot/efi/fedora/grub.cfg" but that is not accessible,
because the partition it's linked to, is not mounted there when grub starts.
A grub2-install based grubx64.efi expects to find the grub.cfg in
/boot/grub2/grub.cfg. This OSLoader is not signed.
The grub2-efi-x64-2.04-31.fc33.x86_64 based grubx64.efi expects to
find the grub.cfg on the EFI system partition inside EFI/fedora/ and
this OSLoader is signed.
Basically you've stepped through the Looking Glass by using
grub2-install on a UEFI computer.
--
Chris Murphy