You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I installed in a VM with a pre-mounted partition layout, in which the EFI system partition is mounted at /efi, rather than at /boot. Using EFISTUB as boot option, not using a UKI.
No error appears in the log, but after the installation completes "without any errors", I reboot and no EFI boot menu option is available. If the installation ISO is left enabled, it boots back into that, otherwise I end up in an EFI shell. If I try the same installation with the EFI partition mounted at /boot, the boot menu option is installed correctly.
While I'm not well versed in how archinstall works internally, what I found (archinstall/lib/installer.py:1324) seemed like it assumes that the EFI partition is mounted at /boot, so that the kernel is automatically placed in the EFI partition root. But if it's not mounted to /boot, the kernel would need to be copied there first?
Which ISO version are you using?
2024-09-01
The installation log
https://0x0.st/Xx5T.log
describe the problem
Description of the issue
I installed in a VM with a pre-mounted partition layout, in which the EFI system partition is mounted at /efi, rather than at /boot. Using EFISTUB as boot option, not using a UKI.
No error appears in the log, but after the installation completes "without any errors", I reboot and no EFI boot menu option is available. If the installation ISO is left enabled, it boots back into that, otherwise I end up in an EFI shell. If I try the same installation with the EFI partition mounted at /boot, the boot menu option is installed correctly.
While I'm not well versed in how
archinstall
works internally, what I found (archinstall/lib/installer.py:1324) seemed like it assumes that the EFI partition is mounted at /boot, so that the kernel is automatically placed in the EFI partition root. But if it's not mounted to /boot, the kernel would need to be copied there first?Virtual machine config:
The text was updated successfully, but these errors were encountered: