Updating clr-boot-manager failed

Bruno21

Hello,

For each eopkg install, I have an 'Updating clr-boot-manager failed' error
The package seems correctly installed.
Any idea ?

$ sudo eopkg install golang
Mot de passe : 
Taille totale du/des paquets(s) : 100.63 MB
Téléchargement 1 / 1
Paquet golang trouvé dans le dépôt Solus
golang-1.14.3-55-1-x86_64.eopkg (100.6 MB)100%     24.41 MB/s [00:00:00] [fini]
Installation 1 / 1
golang-1.14.3-55-1-x86_64.eopkg [en cache]
Installation de golang, version 1.14.3, millésime 55
Extraction des fichiers de golang
golang installé
 [✓] Syncing filesystems                                                success
 [✓] Updating dynamic library cache                                     success
 [✗] Updating clr-boot-manager                                           failed

A copy of the command output follows:

[FATAL] cbm (../src/bootman/kernel.c:L668): Failed to install initrd /boot/EFI/com.solus-project/initrd-com.solus-project.current.5.6.13-153: No space left on device
[FATAL] cbm (../src/bootman/update.c:L250): Failed to install default-current kernel: ///usr/lib/kernel/com.solus-project.current.5.6.13-153


 [✗] Updating clr-boot-manager                                           failed

A copy of the command output follows:

[FATAL] cbm (../src/bootman/kernel.c:L668): Failed to install initrd /boot/EFI/com.solus-project/initrd-com.solus-project.current.5.6.13-153: No space left on device
[FATAL] cbm (../src/bootman/update.c:L250): Failed to install default-current kernel: ///usr/lib/kernel/com.solus-project.current.5.6.13-153

Solus is on the the same nvme SSD as Windows 10. W10 installed first.

CorvusRuber

Bruno21
Technically yes. I had the same problem not so long ago and tried to fix it in the same way.
Then I discovered that even with an SSD resizing a partition takes a considerably longer time than simply backing up and reinstalling..... so I backed up everything and reinstalled 😅
What troubles me is

Bruno21 Solus is on the the same nvme SSD as Windows 10. W10 installed first.

Playing around with partitions in these situations can become extremely messy extremely quickly, so back up everything (both from Solus and W10) and be prepared to reinstall if something goes wrong.

CorvusRuber

sudo fdisk -l, in the output look for "EFI System" or something like and it's practically certain that its size will be less than 512Mb.
Meaning : you have an EFI partition that is under the minimum recommended size of 512MB that it's now full

Bruno21

Thanks CorvusRuber,

Périphérique        Début        Fin  Secteurs Taille Type
/dev/nvme0n1p1       2048     206847    204800   100M Système EFI

Is it possible to expand EFI partition ?

Dentraq

It seems that /boot partition is filled by old kernels. Try to go in /boot and remove old unusable kernels. Leave only a last version and previous version.
For example, my /boot only have 5.6.13-153 (last version) and 5.6.4-152 (previous version, as alternative) at this moment.
After that, update clr-boot-manager manually by sudo clr-boot-manager update

Justin

Dentraq Some users may end up with unbootable systems if they remove the wrong files. It is better imho to recommend users re-install with the recommended settings or if possible resize the EFI partition.

Bruno21

As it was a fresh install, I erase both OS, install Solus as the only OS to create a 512MB EFI partition, then reinstall W10 and Solus.

Dentraq

Justin Resizing a EFI partition may end up with unbootable system too, because reinstalling GRUB may be needed after expanding partition, which is not so trivial.

SOLUSfiddler

Dentraq
Unless you use RESCATUX to repair GRUB.

Justin

Dentraq So, like I said, best option is to backup and re-install, while not fun it's the safest way.