If you happen to have some free space on the drive already then this is easy, just create a new partition of at least 100M.
The nice thing about the EFI spec is that it must just be in the first 2.2TB of space so for most users, it means you can simply resize the last partition (downsize it by 100M) and then add an EFI partition at the end.
For example if you had this partition scheme:
/dev/sda1 = /
/dev/sda2 = swap
You could just downsize your swap partition or whatever the last partition is and then create a new partitiion as EFI/FAT32 at the end. UEFI will still find and boot it even if it is not the first partition.
You could use gparted to achieve the above or from any other LiveCD like Ubuntu/Mint you could boot and manipulate the partition table as you need.
Replace the xx with your info eg. if you had /dev/sda3 as your EFI partition then use mkfs.vfat /dev/sda3
apt install grub-efi
Remember the EFI boot loader calls for a partition type of vfat/fat32 and it can be at any location (eg. I have booted from ESP as partition#3).
mkdir -p /boot/efi
mount /dev/sda1 /boot/efi
Note that some platforms/devices/computers/laptops/servers will not boot if you don't use the --bootloader-id option and if you don't use the --no-uefi-secure-boot
Change /dev/sdx to your drive
If you are using secureboot do this:
grub-install --target=x86_64-efi /dev/sdx
Installing for x86_64-efi platform.
grub-install: warning: EFI variables are not supported on this system..
Installation finished. No error reported.
grub-install --target=x86_64-efi /dev/sdx --no-uefi-secure-boot --bootloader-id realtechtalk
The whole issue is that the grub efi binaries are hard coded to find the files in /EFI/debian for Debian for example or for Ubuntu it is /EFI/ubuntu. If you use any bootloader-id other than those things won't work unless they exist.
To have a custom bootloader-id you need the hardcoded/default -bootloader-id in EFI/ and then you can install your customer one. In essence --bootloader-id is broken as users have complained of for years.
This is usually caused by the issues mentioned in #4, especially installing without --bootloader-id a lot of implementations of EFI will not boot if you don't set the --bootloader-id.
If you use a bootloader-id other than the default for the grub built for your OS eg. debian, ubuntu it will probably not work unless you use --no-uefi-secure-boot
If you have EFI/debian or EFI/ubuntu etc.. on your ESP/EFI partition and you are getting this message, it probably means your BIOS is bad/buggy. Some EFI computers will only boot from a file called EFI/boot/bootx64.efi
You can see reports of even Asus computers and chipsets based on Z87 having this issue.
How do you fix the problem?
Create EFI/boot on your ESP/EFI partition.
Then copy grubx64.efi from EFI/debian or EFI/ubuntu (whatever dir your EFI bootloader was installed to) to EFI/boot
Still keep your debian/ubuntu or whatever bootloader dirname you have in EFI. Now your BIOS should pickup the file and then boot from the files it refers to in EFI/debian or EFI/ubuntu and work normally.
This is a bug as some old EFI implemenations will only boot from EFI/boot/bootx64.efi which is why a lot of OS's/distros like Ubuntu and even Microsoft Windows keep this structure.
Yes, in my experience using an MBR partition is not an issue at all.
install, grub, efi, linux, ubuntu, mint, debian, _, loader, apt, chroot, partition, mount, esp, vfat, eg, booted, mkdir, dev, sda, sdx, installing, platform, variables, supported, installation, reported,