Install failing... No space left on device grub-install: error:

Hi all,
Asus FX503VD
Installation fails with the following error.
Any help greatly appreciated.
Thanks.

Boost.Python error in job "bootloader".
Command 'grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=EndeavourOS --force' returned non-zero exit status 1.
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.

Traceback:
File "/usr/lib/calamares/modules/bootloader/main.py", line 485, in run
    prepare_bootloader(fw_type)

  File "/usr/lib/calamares/modules/bootloader/main.py", line 457, in prepare_bootloader
    install_grub(efi_directory, fw_type)

  File "/usr/lib/calamares/modules/bootloader/main.py", line 319, in install_grub
    check_target_env_call([libcalamares.job.configuration["grubInstall"],

  File "<string>", line 6, in <module>

please provide full log:
cat ~/endeavour-install.log | curl -F ‘f:1=<-’ ix.io
but could be you are already log off session…

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.

----> No space left on device
----> Input/output error.

i would bet on one of the two things:

  1. legacy boot enabled in BIOS/EFI firmware
  2. reuse partition for /boot/efi and it is already full

Questions:

  • do you try installing dualboot with another OS?
  • do you have Linux OS installed before what you want to overwrite with EndeavourOS?
1 Like

Hi, thanks for the response.

[liveuser@eos-2020.09.20 ~]$ sudo cat ~/endeavour-install.log | curl -F ‘f:1=<-’ ix.io
bash: -’: No such file or directory

Questions:

do you try installing dualboot with another OS?
do you have Linux OS installed before what you want to overwrite with EndeavourOS?

I’ve had several distros installed alongside on another HDD, I suspect the boot manager (rfind) was installed on the SSD.

I overwrote a Manjaro install trying to install EndeavourOS.
I’m typing this in Endeavors live environment as Ive nuked the SSD and have no OS installed.

so it is efi system and configured to boot on efi, i would nuke all petitions you want to use for EndeavourOS as far as i understand you want to use the complete SSD for it?

most easy will be use autopartition (erase disk) make sure choosing the ssd

if you need manually partition you need a fat32 partition with around 250MB make sure choose mounting as /boot/efi and tag boot flag plus root system partition with around minimal 30GB mountpoint / formatting as ext4.
swap as you like with size of your RAM

1 Like

Looking at this its a hot mess!
I will follow your advice and nuke the entire SSD and try again…
I’ll update shortly
thanks

[liveuser@eos-2020.09.20 ~]$ efibootmgr
BootCurrent: 0027
Timeout: 0 seconds
BootOrder: 0013,0020,0023,0024,0025,0026,0027,0028,0007,0006,0018,0004,0000,0011,0009,0003,0005,0001,000D,0019,0010,0017,0014,0015,0012,000F,000E,000C,0016,000B,000A,0008
Boot0000* Windows Boot Manager
Boot0003* rEFInd Boot Manager
Boot0004* rEFInd Boot Manager
Boot0005* ubuntu
Boot0006* rEFInd Boot Manager
Boot0007* rEFInd Boot Manager
Boot0008* rEFInd Boot Manager
Boot0009* rEFInd Boot Manager
Boot000A* rEFInd Boot Manager
Boot000B* rEFInd Boot Manager
Boot000C* rEFInd Boot Manager
Boot000D* rEFInd Boot Manager
Boot000E* rEFInd Boot Manager
Boot000F* rEFInd Boot Manager
Boot0010* rEFInd Boot Manager
Boot0011* rEFInd Boot Manager
Boot0012* rEFInd Boot Manager
Boot0013* kali
Boot0014* rEFInd Boot Manager
Boot0015* Pop!_OS 18.04 LTS
Boot0016* Pop!_OS 19.04
Boot0017* Pop!_OS 18.04 LTS
Boot0018* Pop!_OS 19.04
Boot0019* Pop!_OS 19.04
Boot0020* UEFI OS
Boot0023* debian
Boot0024* UEFI OS
Boot0025* UEFI: KingstonDataTraveler 3.0PMAP
Boot0026* UEFI: KingstonDataTraveler 3.0PMAP, Partition 1
Boot0027* UEFI: KingstonDataTraveler 3.0PMAP
Boot0028* UEFI: KingstonDataTraveler 3.0PMAP, Partition 1
[liveuser@eos-2020.09.20 ~]$ sudoefibootmgr -D
bash: sudoefibootmgr: command not found
[liveuser@eos-2020.09.20 ~]$ sudo efibootmgr -D
Could not set BootOrder: No space left on device

I reformatted both the boot partition and the main partition to fat32 and ext4 respectively using Calamares live copy of gparted.
The disc has 1 more partition,2MiB of unallocated space before the boot partition I have left this alone.
Unfortunately the install failed with the same error.

efibootmgr  

gives the same output as before.

Did you mark the boot partition with the flag?

1 Like

Hi, yes I did, the system is installed fine, its obviously the boot loader I suspect I’m missing something obvious.

Could not set BootOrder: No space left on device

looks like the refind partition is full ?
do you choose manually partition inside calamares?

1 Like

Not sure but perhaps it might help if you cleaned up those efi bootloaders entry you don’t need.

1 Like

Annoyingly this happens when trying to delete the entries

[liveuser@eos-2020.09.20 ~]$ sudo efibootmgr -b 0004 -B
Could not delete variable: No space left on device

Can i delete them any other way?

Don’t know. You might need to look at resetting NVRAM. But this is a bit above my paygrade. You will need to do some research on it and/or get confirmation from other more experienced co-forumers.

1 Like

i do not get why installer is try to use refind partition from another disk. May it is neede dto manually partition to force it to use its own efi fat32 partition.

1 Like

I tried again manually partitioning and the same error.
I am pretty stuck.

If you go into UEFI and disable the boot order for all except one. Most new UEFI have the ability to have multiple entries for boot.Then set the boot to boot on the drive you are installing to. UEFI keeps a running tab of boot entries in NVRAM.

Edit: I would use gparted and set new GPT partition. Then close and run the installer and erase disc and swap with or without hibernate. Or do manual partitioning and use 300M minimum for EFI and set it /boot/efi and flag /boot. Then create you other partitions for root and home and swap if that is what you want and proceed with the installation online.

1 Like

i would try removing old entries from another working OS or simple reinstall refind from scratch

1 Like

When you install rEFInd it adds an entry in the boot order to boot from rEFInd. Were most of these in rEFInd? I suggest on a new install to disable all boot order and set to boot only the drive you are installing to if using the whole ssd.

Edit: Not sure if the user is still going to dualboot with Windows 10?

2 Likes

I have never done it this way but couldn’t they just dd the whole drive and start from scratch?

1 Like

Erasing the drive is only part of the equation. The problem is UEFI keep the entries in NVRAM. On my board in UEFI i can disable all boot devices except the one’s i want. Because UEFI keeps a list and rEFInd installation creates a boot in the boot order to boot from rEFInd. So you need to change that and clear them. User has many many in the list.

Edit:

4 Likes

Hi, yes many!

I deleted what entries I could from the bios, this allowed me to delete more using sudo efibootmanager -b xxxx -B whilst in a live environment.
The result is a fully installed and functional gnome desktop. Yay.
Thanks for the help everyone.

6 Likes