Gumpy
Posts: 2
Joined: Wed Dec 13, 2017 7:35 pm

SOLVED: clr-boot-manager can't update the kernel

Wed Dec 13, 2017 7:57 pm

Hello,
after attempting to change the bootloader timeout i noticed upon running "clr-boot-manager update" that it fails to install the kernel with the following error message:

Code: Select all

[FATAL] cbm (src/bootman/kernel.c:L654): Failed to install initrd /boot/EFI/com.solus-project/initrd-com.solus-project.current.4.14.5-39: No space left on device
[FATAL] cbm (src/bootman/update.c:L329): Failed to install default-current kernel: ///usr/lib/kernel/com.solus-project.current.4.14.5-39
I checked the current version and it is indeed stuck at 4.14.4-38.
My EFI partition is 128MB and the root partition 40GB with more than 25GB free. Previous updates worked fine.
Are those sizes too small for new versions could this error be caused by something else?
If I have to resize the partitions what size would be recommended to ensure this wont happen again?
Last edited by Gumpy on Wed Dec 13, 2017 8:49 pm, edited 1 time in total.

User avatar
kyrios
Posts: 1917
Joined: Thu Sep 22, 2016 4:20 pm

Re: clr-boot-manager can't update the kernel

Wed Dec 13, 2017 8:45 pm

Gumpy wrote:
Wed Dec 13, 2017 7:57 pm
Hello,
after attempting to change the bootloader timeout i noticed upon running "clr-boot-manager update" that it fails to install the kernel with the following error message:

Code: Select all

[FATAL] cbm (src/bootman/kernel.c:L654): Failed to install initrd /boot/EFI/com.solus-project/initrd-com.solus-project.current.4.14.5-39: No space left on device
[FATAL] cbm (src/bootman/update.c:L329): Failed to install default-current kernel: ///usr/lib/kernel/com.solus-project.current.4.14.5-39
I checked the current version and it is indeed stuck at 4.14.4-38.
My EFI partition is 128MB and the root partition 40GB with more than 25GB free. Previous updates worked fine.
Are those sizes too small for new versions could this error be caused by something else?
If I have to resize the partitions what size would be recommended to ensure this wont happen again?
Your EFI partition is too small. It should be 512Mb.

Gumpy
Posts: 2
Joined: Wed Dec 13, 2017 7:35 pm

Re: clr-boot-manager can't update the kernel

Wed Dec 13, 2017 8:47 pm

Thanks for the quick reply. I'll fix the size now

Ezibenroc
Posts: 1
Joined: Sat Mar 03, 2018 7:54 pm

Re: SOLVED: clr-boot-manager can't update the kernel

Sat Mar 03, 2018 7:59 pm

Hello,

I get the same problem when I try to run clr-boot-manager. Indeed, my EFI partition is too small.

My partition layout is as follow (dual boot with Windows 10):

Code: Select all

$ fdisk -l
Périphérique       Début        Fin  Secteurs Taille Type
/dev/nvme0n1p1      2048     923647    921600   450M Environnement de récupération Windows
/dev/nvme0n1p2    923648    1128447    204800   100M Système EFI
/dev/nvme0n1p3   1128448    1161215     32768    16M Réservé Microsoft
/dev/nvme0n1p4   1161216  307202047 306040832   146G Données de base Microsoft
/dev/nvme0n1p5 307202048 1000214527 693012480 330,5G Système de fichiers Linux
Do you know how can I increase the size of the EFI partition without having to reinstall the whole system?

chrisoffner3d
Posts: 3
Joined: Sun Mar 25, 2018 12:06 am

Re: SOLVED: clr-boot-manager can't update the kernel

Sun Mar 25, 2018 12:10 am

Ezibenroc wrote:
Sat Mar 03, 2018 7:59 pm
Do you know how can I increase the size of the EFI partition without having to reinstall the whole system?
Did you manage to do it? If so, how exactly?
I seem to be in precisely the same situation as you - with a Win10/Solus dual boot system, and exactly the same partitions and sizes as you (100 MB EFI, surrounded by Microsoft recovery and Microsoft reserve partition).

bolofar
Posts: 6
Joined: Sat Mar 17, 2018 9:40 pm

Re: SOLVED: clr-boot-manager can't update the kernel

Sun Mar 25, 2018 4:45 pm

chrisoffner3d wrote:
Sun Mar 25, 2018 12:10 am
Did you manage to do it? If so, how exactly?

You could use GParted for resizing partitions for example GParted-live https://gparted.sourceforge.io/livecd.php or Solus' live, of course ;) . Note, however that this is a tedious and risky process and may result in an unusable system. Thus backup your HDD first, e.g. using Clonezilla http://clonezilla.org!

chrisoffner3d
Posts: 3
Joined: Sun Mar 25, 2018 12:06 am

Re: SOLVED: clr-boot-manager can't update the kernel

Thu Mar 29, 2018 2:30 pm

Yeah, last time I resized a partition on a dual boot system with Windows, I had to set up everything from scratch again. :/
Resizing this partition would cut into either the Microsoft recovery partition or the Microsoft reserve partition, wouldn't it?

I'm afraid doing this in a manner that doesn't screw up my system, if at all possible, is above my paygrade.

bolofar
Posts: 6
Joined: Sat Mar 17, 2018 9:40 pm

Re: SOLVED: clr-boot-manager can't update the kernel

Sat Mar 31, 2018 1:14 am

chrisoffner3d wrote:
Thu Mar 29, 2018 2:30 pm
Resizing this partition would cut into either the Microsoft recovery partition or the Microsoft reserve partition, wouldn't it?
Well ... this would certainly make either of them unuseable.

The "only" way I would see is to:
  1. shrink the Windows partition /dev/nvme0n1p4, such that there is free space between it and the Reserve partition.
  2. move the Reserve partition /dev/nvme0n1p3 towards the Windows partition. There would then be free space after the efi-partition.
  3. enlarge the efi-partition.
But yes ... this could leave the whole system unuseable if something goes wrong.

Return to “Other Questions”