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.

those symlinks where necessary to fix some  other bugs with grubby, which has a slight different imagination where to do updates to grub.cfg, as grub itself has. In other words, one loads from efi path, one not . So symlinks were there to keep them in Sync. ( documented in a grub/grubby br @ bz )

Because it worked before the grub2-install with those symlinks (grub.cfg & grubenv) , there needs to be a different grub-install cmd needed : which could that be?

(for now my system starts again)

best regards,
Marius