I have tried out to perform the installation for the current software distribution according to the file “openSUSE-Tumbleweed-NET-x86_64-Snapshot20210202-Media.iso”.
This installation attempt has succeeded almost.
Unfortunately, the following information was displayed at the end.
YaST2
…
Error output: x86_64-efi will be installed for your platform.
/usr/sbin/grub2-install: error: EFI directory could not be found.
I would like to use the following partitions for a corresponding system configuration.
root@Microknoppix:/home/knoppix# parted --list
…
Disk /dev/nvme0n1: 500GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
1 1049kB 5370MB 5369MB fat32 esp boot, esp
4 5370MB 16,1GB 10,7GB ext3 boot
…
I would appreciate further tips so that I can completely activate boot managers for UEFI systems accordingly.
:\ Which settings should I add for such an use case?
Hi
Like I said, reduce the size of the ESP one to 512MB, I normally use 260MB… else it won’t be recognized by the system hardware as an ESP… It’s a defined standard…
Hi
My bad, I stand corrected, minimum size 32MB for 512, 260M for 4K drives… (Might have been stated somewhere long ago when using elilo), anyway seems a pointless size, even when running the shell, BIOS updates, adding boot logos etc, never needed more… <shrug>
FAT32 isn’t a hospitable place for storing isos, which are often larger than the maximum file size for FAT32. Better to make a third partition for those other files, using a native format that features a more hospitable maximum file size, or ExFAT if you need Windows to be able to access those files.
FWIW, my ESP partitions are always 320MB, ample space to host readily accessible backups and test copies of boot files, in addition to the few files that must be there.
An EFI system partition is required according to a current storage standard.
:\ The corresponding storage space expectations can vary considerably, can’t they?
How are the chances to make it easier and safer to resolve such dependencies for the mentioned software installation approach?
Do I need to setup a special environment so that the software “GRUB 2.04” can be finally installed after a “changed root directory”?
Can other boot managers like “rEFInd” (or “Ventoy”) help another bit for the presentation of desirable boot menus?
A message was originally displayed with a German wording at the end of my software installation approach.
YaST2
…
Abbruch-Code: 1
Fehlerausgabe: x86_64-efi wird für Ihre Plattform installiert.
/usr/sbin/grub2-install: Fehler: EFI-Verzeichnis kann nicht gefunden werden.
The previous software installation attempt filled the partitions with some data so that I can edit the file “/mnt/R/etc/fstab” according to my needs at least (for example in a Knoppix session).
:\ I am curious if this adjustment will be picked up by the current network installation software. (I hope that another software update will finally succeed with a few additional system configuration details.)
I have tried out to perform the installation for the current software distribution according to the file “openSUSE-Tumbleweed-NET-x86_64-Snapshot20210203-Media.iso” as an “upgrade” once more.
Unfortunately, the following information was displayed (including a bit of German wording) at the end.
YaST2
…
Fehler beim Ausführen des Befehls ""/usr/sbin/shim-install"","--config-file=/boot/grub2/grub.cfg"]]"
Abbruch-Code: 1
Fehlerausgabe: No valid EFI partition
Can I convince the installation software to accept my storage space selection anyhow?
Hi
The question is does in work if you test with a reduced value, eg 260MB for the efi partition (as in sda1)? Does it work if you move the efi partition to the end of the disk rather than sda1, the esp doesn’t need to be on sda1 and you can have multiple esps…
