You are not logged in.
Hi all, this is my first time posting here.
I am struggling to install arch (omarchy really, but posting here because the error likely does not have anything to do with omarchy but rather archinstall)
Here are the logs:
archinstall - https://0x0.st//KS4h.log
output of efibootmgr -v - https://0x0.st//KSJz.log
Please note that efibootmgr output did not look like what you see in the link earlier. Earlier it was
BootCurrent: 0004And it showed 2 "things" there:
1. My USB (0004)
2. Windows Boot Loader (yes, I had windows installed) (0001)
But after some searching online, I gave resetting my bios a try (I have to disconnect the battery from my laptop and drain power)
Post this, I was able to see only 1 entry in `efibootmgr`
But unfortunately, this did not fix my issue. I am unable to find the solution for this and hence asking.
Thanks!
Last edited by ak127a (Yesterday 05:33:50)
Offline
hi. which one is no space left? efipartition or efi-nvmem.
clear it as removing some garbages to save/gain space.
for nvmem delete some garbage efivars.
for efipartition delete some garbage files or shrink initrd etc. or delete partion then recreate it as bigger.
some firmwares allows to add permanent boot entry.
try add it via efishell's "bcfg" builtin.
Offline
The issue was with NVRAM on my motherboard. It looks like Arch was trying to put something there and my motherboard was rejecting it since it was already ~96% full.
What fixed it for me was to use the efi_no_storage_paranoia kernel arguemnt.
Though I'd like to highlight that setting this on vanilla arch was simply not working for me...maybe it was a corrupted usb or something..I did not investigate that.
But this kernel cmdline arg worked with CachyOS. I first tried without it, and it failed with the exact same error.
Then I tried with the kernel arg and worked perfectly fine! yay!
Offline