Installation Failed: Bootloader could not be installed

General system EndeavourOS installation
41

I wonder why that is?

42

I am thinking, since manjaro also uses calamares as an installer, it grabbed the pre-existing manjaro /boot/efi partition and used that instead of a new one generated by Endeavouros if manually partitioned. @joekamprad how does install alongside work in this case.

43

I also notice the OP has both intel and amd ucode?

1 Like
44

Now that was a novelty! I had never seen that before.

45

Manjaro does something weird with the ucode and places it in the wrong spot when you have EOS installed with Manjaro so i would assume that might be an issue? Even though Manjaro is gone? I’m not the greatest with grub! :wink:

46

Probably the fastest fix @Zinter71 would be try the following:

  1. Boot the EndeavourOS live ISO.
  2. Open gparted.
  3. Nuke the partition you want EndeavourOS on by formatting it EXT4.
  4. Close gparted.
  5. Start the installer.
  6. Select manual partitioning and select the newly nuked partition for installation.
  7. Create a 512 Mib FAT32 partition mounted at /boot/efi and set the boot flag (check the box).
  8. Create a root partition I use 64Gib. If the drive is small 32Gib could work. Create an ext4 partition and mount at /root
  9. Format the rest of the space as an ext4 partition and mount at /home. This is nice because it has a separate home so if something goes really wrong and you need to reinstall you can reuse the /home partition containing all your user files.
1 Like
47

Could it be that the OP checked the boxes for both intel and amd ucode in the installer.
Not being able which one to choose, Grub goes all-in and chooses both?

48

@BONK, you mean formatting the partition as EXT4? (/dev/sda3)
OP has Kubuntu as well in that disk. If you mean creating a new GUID Partition Table, that will nuke Kubuntu as well?

49

Who need Kubunu anyway? :innocent:

1 Like
50

Edited the typo. All my installations are always on separate disks. But the other way would work as well lol.

1 Like
51

@Zinter71

TL;DR
To check:

  • Secure boot disabled?
  • BIOS/Firmware updated? :wink:

Could to post your grub.cfg by

sudo cat /boot/grub/grub.cfg | eos-sendlog

?

52

I have an old Intel laptop, here is where I do my testing and is a full linux system with several partitions (Mainly used for experimentation). My end goal is to get confortable installing and using Arch there, so without any fear I can dual boot it with windows 10 on a disk with two partitions in my AMD laptop.

53

Alright.
In your Intel machine, you don’t need to install amd-ucode.

54

alongside will use existing efi afaik.

1 Like
55

Hello again! sorry for not giving an update earlier. I’ve been trying everything I could think of after reading everything on the Arch wiki related to partitions, BIOS/UEFI stuff, partition tables, GRUB, etc and I still cannot install EndeavourOS. I’m starting to think is probably hardware related, but I’m sure there is something I’m missing. I’ve had problems before installing Manjaro on this computer again with grub/bootloader manager stuff but that was a long time ago. Last week, I installed Manjaro without problems but soon deleted because I wanted to try Arch (too complicated until I found EnOS). I guess I’ll leave it for now, but thank you all for your support. Troubleshooting is still fun despite the lack of success