Bootloader installation error

Windcuttery

Hello,

I tried to install Solus 4.5 on a SSD with a UEFI Windows 10 Dual Boot but am getting a “ The bootloader could not be installed. The installation command ‹pre›cr-boot-manager update</pre> returned error code 1.” error. I am not very knowledgeable about its intricacies. How should i proceed and what other information should i provide?

I have two 16gb sandisk flash drives and prepared one Solus 4.5 Budgie.iso on Windows with Balena Etcher and other one on Fedora(Another computer) with Fedora Media Writer but i believe issue is something else.
I was able to install it selecting CSM but i dont wish to use it like that as it requires me to change it on Bios on which OS to boot. Tried with Secure boot enabled/disabled to no avail. I used to have EndeavourOS installed on it but Brute force deleted it from Windows side. Maybe it messed something up?

Thanks in advance

[deleted]

Windcuttery The Windows EFI partition is most likely too small. You need to expand the EFI partition.

Windcuttery

Using Solus Installation Thumb drive i managed to increase EFI Partition from 100mb to 500mb however even though it shows like that i still get the same error. There is a Used, Unused and Unallocated sections in the efi partition.

Axios

Windcuttery the thread (distrowatch review) in off-topic has some talk about installing both
which may help scroll towards the bottom.
If not may bring light what your doing wrong.

[deleted]

Windcuttery The recommended size is 1GB.

Axios

I understand everybodies different needs but I prefer to keep windows off my linux machines.
and then If I would do it would install two seperate drives and just use in my case f12 and select
what one wanted to use. (the ole single disk unplug install method)
I dont think the culprit is so much linux or solus as it is windows in all these issues.
(Just thinkin)

TraceyC

Axios
While I respect your preferences, that's not helpful to solving Windcuttery's problem. They need to install Solus on one drive, and this should be possible. Windows is not at fault here.

The error seen is indeed due to the Solus installer expecting a 1G EFI partition. It will be necessary to expand the EFI partition to this size for the installer to be successful.

Unfortunately, from my research, all other OSs create the EFI partition with less than 1G, anywhere from 100MiB to 500MiB. I have created a bug report so we can enable users to successfully install Solus alongside another OS using just the Calamares installer.

brent

TraceyC Unfortunately, from my research, all other OSs create the EFI partition with less than 1G, anywhere from 100MiB to 500MiB. I have created a bug report so we can enable users to successfully install Solus alongside another OS using just the Calamares installer.

I don't remember why Solus grew from needing 512MB for boot to 1GB but I will ask another time.
this is solus Alongside of endeavour a few days ago.

calmares had trouble shrinking endeavour.
so I split it 50/50 in Gparted.
all I did was format the shrinkage to GPT. the end.
solus/calmares put in the 1GB boot and took over the sda4 for ext4.

as far was what you are saying here, I split duties with Calmares to make this successful.
I was reminded by @WetGeek (and @[deleted] if I remember right) that quitting Calmares after 20 minutes may have been premature because I had tasked it with something VERY heavy duty in Calmares: cutting Endeavour in half...
..they were perhaps right since it took longer than that in Gparted.
--playing to what you are saying....for me maybe Calmares could have done it all without my intervention had I been patient? I don't know.
Food for thought as far as this issue; just trying to help.

SethStorm666

I had the same error until I resized the /boot to 1 GB. Then everything went fine.

TraceyC

You may be interested to know that we are planning to reduce the minimum EFI partition size to 512MB with Solus 4.6.

If your EFI partition is already / still 512MB, and you don't want to increase its size, you can wait for 4.6.