I am looking for guidance on the EFI installation of Obarun. My first assumption, generally, is I am doing something wrong!

I am accepting the default obarun-install values outside of specifying bootloader and using the disk preparation with default values on Virtualbox and Intel hardware. I am using the core media and reproduced the Syslinux error with the JWN media as well. Both were released 9/1/2021.

Using Syslinux, I get the following failure.
Could not prepare Boot variable: No such file or directory
obarun-install: fatal: Create NVRAM entry to point to Syslinux EFI application
Using Grub, I get the following failure.
grub-install: error: failed to get canonical path of `/run/archiso/airootfs'.
obarun-install: fatal: Failed to install GRUB bootloader
Using EFI stub, I get the following failure.
Could not prepare Boot variable: No such file or directory
obarun-install: fatal: Failed to create NVRAM entry.
I am unfamiliar with obarun-install so please share with me if there is a debug mode or a log that would be beneficial. I searched the forum and wiki, but I may have missed it.
To be honest the obarun-install script is not really usefull in case of particular bootloader installation. As i can see you use some Windows partition.
I should advice you to install the system with obarun-install and skip the bootloader installation when the script ask for it. Then chroot the fresh system and install it manually as you do normally.
eric wroteAs i can see you use some Windows partition.
Can you please clarify the quoted statement?

I will follow your guidance and install and configure a bootloader.
Either I have miscommunicated or I am making an erroneous assumption. Help me figure out which. :)

I am not using Windows or attempting to multi-boot with other OSes.

I am assuming in selecting the UEFI installation option on an UEFI virtual machine or physical hardware in obarun-install and accepting the default values will result with a working installation of Obarun.

If my assumption is true, then I believe that I am reporting a bug with obarun-install. I did not want to assume, thus I was asking for guidance. Perhaps in the future, I will be more direct but I was being cautious as I am new to Obarun and to this community.
Sorry for the misunderstanting, however I think that, regardless of how many and which OSes you have, if you are using an UEFI machine the automatic installer would likely always fail :) you should create an ESP partition, make an EFI directory and mount it together with your root partition, then launch the installer, skip the bootloader install and manually install the bootloader as explained by the tutorial.
Fair enough. My assumption was incorrect.

Thank you for you have saved me time! I will install and configure rEFInd, my normal process, instead of working though bootloader.sh which I was doing before seeing your response.

Have a good day!
You are welcome, always glad to help and yes, rEFInd is always a life saver when it comes to UEFI partitions :) Have a nice day too and welcome to the Obarun world ;)
Successfully installed Obarun in Virtualbox with EFI. Moving to a workstation to reproduce my success and document.

Interesting, efibootmgr was puking in the chroot. There was no efivarfs mount. It existed in the live boot environment but not in the chroot.

Could this be why obarun-install errors out during the bootloader install with EFI?
Yes, that's possible. What I realized is that I always have to mount the EFI partition before the install and THEN chrooting into the system it is detected, but it won't happen if I don't make an EFI directory at the very beginning.
@ wastelander, reading my prior post, I realized that I wasn't very clear on the mount. You may have understood me, but..
mount -t efivarfs efivarfs /sys/firmware/efi/efivars
It's all good. I have a path forward and appreciate your insightful guidance.
For reference should others run into the same issue.

https://wiki.archlinux.org/title/Unified_Extensible_Firmware_Interface# Inconsistency_between_efivarfs_and_sysfs-efivars
Mount efivarfs

If efivarfs is not automatically mounted at /sys/firmware/efi/efivars by systemd during boot, then you need to manually mount it to expose UEFI variables to userspace tools like efibootmgr:
# mount -t efivarfs efivarfs /sys/firmware/efi/efivars
Note: The above command should be run both outside (before) and inside the chroot, if any.
It always easier to find pertinent documentation after you struggle and fix the problem, right? :D
techore: Your contribution is noted in the wiki (top) although it was modified in the rare occasions that it applies. https://wiki.obarun.org/doku.php?id=uefi

When booting the obarun live image in an efi capable envrionment/system then the /sys/firmware/efi directory is populated with all the applicable firmware. When using arch-chroot into the target partition (either manual installation or through the installer) the same is founf into /mnt/sys/firmware/efi, arch-chroot does this, mounts the host's /proc /sys /dev ... into the target.
If you boot either obarun or other system in a legacy system this directory doesn't exist, and despite the software that you have installed it will not be populated as it doesn't apply. Because there are systems where you can select bios/legacy or EFI booting. So if it doesn't exist on host it will not mount on target no matter what you do.

At least this is my understanding of the dreaded EFI crap, and based on experimentation with the 072021 image this is what I was able to tell. When booting the image in EFI the directory is populated, when booting legacy you can't populate it no matter what you do. And on target chroot you can only mount what is on host. So this is a very specific situation where this applies.
Nothing to do with systemd doing something more or less in this occasion ;)
Nice wiki update and thank you!

Yeah. Ignoring UEFI imperfections and complexity, another example of the over reliance on systemd.
Typo? :)

"5. efivats and sysfs-efivars" should be "5. efivars and sysfs-efivars" right?
Thank you for updating wiki. It looks good.

Powered by Obarun