Grub bootloader install fail

Hello, I’ve been tying to install endeavouros on my asus tuf dash f15 laptop, but any time i do i keep getting the same error with the installation of the grub bootloader

"Could not prepare Boot variable: No space left on device
grub-install: error: efibootmgr failed to register the boot entry: Input/output error.
2025-02-03 - 21:04:44 [2]: WARNING: [PYTHON JOB]: "Command 'grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=endeavouros --force' returned non-zero exit status 1." 
2025-02-03 - 21:04:44 [6]: [PYTHON JOB]: "stdout:Installing for x86_64-efi platform.\nCould not prepare Boot variable: No space left on device\ngrub-install: error: efibootmgr failed to register the boot entry: Input/output error."

here is the full install log output: https://termbin.com/yh0f

I’m installing as a dual boot with windows 10 but using a separate ssd for the endeavouros install, i have tried erase disk install and manual partition install but both return the same error. i also tried a systemd-boot install but that seemed to only create a second windows bootloader on my ssd that would not see endeavouros at all. I did find the following thread that seemed to at least get me passed the error: Bootloader Installation Error code 1 but after this if i try to boot into endeavouros it only boots me into the grub shell but from there it looks like it can’t find the bootloader or the disk it’s installed on and i cannot boot into endeavouros at all.

Could not prepare Boot variable: No space left on device

thats the issue… you may need to add a new EFI partition instead of using the one from windows:

here set efi to add new one:

I see you say on another drive so it is this one:

Error could also be that the nvram on the motherboard is full efi implementations are basically really bad in cases …

check:

efibootmgr on livesession to see if you have unused entries in nvram… you can try removing them…

Okay so i checked efibootmgr first and it showed the windows bootloader but also an ubuntu boot partition from an earlier attempt with linux mint to see if it gave the same error, which it did, so i deleted it, but after a restart i saw it was still there somehow. Eventually decided to clean up my drive where the windows install is but that didn’t help either so i did a clean reinstall of windows 10 just on the drive it was already on which also did nothing. Then went into the bios to see if i can delete that ubuntu boot but the same thing happened it just keeps coming back. I tried to delete it through efibootmgr in a live session but that comes back with the following:


tried for a while to fix it within windows using easybcd and bcdedit but to no avail. I did however find that the bios registers it as stored on the drive windows is on but bcdedit and easybcd only see it as being on a partition named \devices\harddiskvolume1

which is seemingly a ghost partition since i can’t find that path anywhere else. i have confirmed that there is more than enough space on the windows drive (about 177GB) and the drive i’m trying to install endeavouros on is completely unallocated space. I will say i’m not entirely sure how to clean out nvram since i could only find how to do that on a router for some reason but as of right now the error is still exactly the same.

you have only 3 entries in your nvram that should not make it full…

yeah that’s what i assumed

2025-02-03 - 21:04:43 [6]: [PYTHON JOB]: "Bootloader: grub (efi)" 
2025-02-03 - 21:04:43 [6]:     .. Running QList("grub-install", "--target=x86_64-efi", "--efi-directory=/boot/efi", "--bootloader-id=endeavouros", "--force") 
2025-02-03 - 21:04:44 [6]:     .. Target cmd: QList("grub-install", "--target=x86_64-efi", "--efi-directory=/boot/efi", "--bootloader-id=endeavouros", "--force") Exit code: 1 output:
 Installing for x86_64-efi platform.
Could not prepare Boot variable: No space left on device
grub-install: error: efibootmgr failed to register the boot entry: Input/output error.
2025-02-03 - 21:04:44 [2]: WARNING: [PYTHON JOB]: "Command 'grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=endeavouros --force' returned non-zero exit status 1." 
2025-02-03 - 21:04:44 [6]: [PYTHON JOB]: "stdout:Installing for x86_64-efi platform.\nCould not prepare Boot variable: No space left on device\ngrub-install: error: efibootmgr failed to register the boot entry: Input/output error."

/dev/nvme1n1p1 4096 2101247 2097152 1G EFI System
this is the partition it tries to add bootloader on … it could be it failes to mount it properly it could be corrupted or something too so no space left could be false error … you may have fast boot not disabled on windows?

And in case the full drive is free for Linux you can try completely erase it … something like secure erase or using partition manager to do that.

but this:


i am not sure but kind of remember to saw such looks like corrupted nvram…
Could be needed to reflash Bios

i’m 100% sure fastboot is disabled in both the bios and windows i even redid the disabling after i reinstalled windows so i can only assume that that partition is corrupt which is odd bc i let the endeavouros installer create that partition from a completely unallocated drive

i’ll see if i can reflash the bios in hopes that might fix it

1 Like

nvram “Non-Volatile Random-Access Memory” in your Motherboard used to save the boot device entries its not created by OS these are two different things… only to ensure about that

error could be both linkling the same issue with nvram also first part is talking about grub-install what writes to efi partition but also triggers to write the entry into the nvram…

All also talking like a pro only … as of no clue what the underlaying issue is.
In case you can also try booting Linux over boot once option… F12 esc or F8 on bootup it should show a menu of devices to boot from that’s independent of nram entries-

well crazy enough the bios reflash worked and endeavouros finally installed thank you so much for your help!

1 Like

that`s nice to read!

And now have fun onto the purple side :enos:

2 Likes

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.