New comment by TeusLollo on void-packages repository

https://github.com/void-linux/void-packages/issues/38533#issuecomment-1222497682

Comment:
> The last step in `post-install` looks suspicious
> 
> ```
> efibootmgr -qo $bootorder
> ```

The step itself looks nominally correct to me, checking the man-page. 

Problem is, we got a fairly complex setup at hand, as evidenced by the "manual" command OP reported working:

`doas efibootmgr --disk /dev/nvme0n1 --part 1 --create --label "Void Linux with test kernel" --loader /vmlinuz-5.18.16_1 --unicode 'loglevel=4 rd.luks.name=809df427-d7d5-408c-a195-3be6e8681333=cryptroot root=/dev/mapper/cryptroot rd.luks.options=discard initrd=\initramfs-5.18.16_1.img' --verbose`

This is utilizing `LUKS`-based filesystem encryption, which can sometimes fail to boot due to seemingly-unrelated issues. 
It would also be necessary to understand what values are being assigned into the `$bootorder` variable. 

1. Are we by chance trying to boot through an `EFISTUB`? Because I don't see any bootloader-specific `.efi` file in the "manual" command the OP has reported to be working. Seemingly, OP is not using `GRUB`, ad example. 
For comparison, a `GRUB`-based non-`LUKS` setup would use the following command: `efibootmgr -c -d /dev/sdx -p 1 -L "<label>" -l "/EFI/<label>/grubx64.efi"`.

2. Has the directory `/dev/nvme0n1` (Which I presume being the `EFI` directory) been marked with the proper `esp` flag? 

3. This may not be particularly useful, but what's the output of `lsblk`, accounting also for the `LUKS` configuration? And what file systems are being utilized into relevant partitions? `Btrfs` with `LUKS `is known to throw seemingly-random errors for unclear reasons.

It's working when issuing a manual command, OP said. 
Why does it not when automated? What's missing, if anything? Is everything that should go into `$bootorder` variable being assigned?