I’m trying to install Endeavour on a completely wiped laptop. Both manual partitioning and auto-partitioning result in the following error:
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: Input/output error grub-install: error: efibootmgr failed to register the boot entry: Input/output error.
File "/usr/lib/calamares/modules/bootloader/main.py", line 485, in run
File "/usr/lib/calamares/modules/bootloader/main.py", line 457, in prepare_bootloader
File "/usr/lib/calamares/modules/bootloader/main.py", line 319, in install_grub
File "<string>", line 6, in <module>
I’m using endeavouros-2020.07.15-x86_64 and created the USB drive with dd. Solus OS ran previously on the system (same drive) and booted without problems.
While getting into a partial update mess by installing a wrong version of inxi is unlikely to cause any serious trouble, this is a terrible practice in general. Refreshing the local package database without updating, and then installing a package is just asking for trouble.
I had set both flags when doing it manually before the installation. However, I just retried the installation with doing the partitioning in the installer, and despite setting the boot flag there, afterwards the fat32 partition only has the msftdata flag instead of boot. Any idea what causes this?
I am thinking that since the bootloader gets installed at the end of the installation process could it be possible to chroot and manually install it? In case everything else is already properly installed.
Sometimes i think is worth using live ISO and boot on it and check with gparted and if the flag is not set to boot then try setting it and reboot. As long as the efi partition was created and formatted fat32 it may have just not set the boot flag for whatever reason. Worth a shot trying first before drastic measures.