Blank screen at startup after after update week17-18

Gregre

Dear all,
After updating solus last week, I had a blank screen after restart. I just rolled back to before the update and tried again to update today, hoping that maybe m'y problem would be solved. This time however I upgraded via terminal and so copied the error message I got...

FATAL] cbm (../src/bootman/bootman.c:L996): Failed to install initrd ///usr/lib64/kernel/initrd.d/com.solus-project.nvidia-firmware -> /boot/EFI/com.solus-project/freestanding-com.solus-project.nvidia-firmware: No space left on device
[ERROR] cbm (../src/bootman/update.c:L210): Failed to copying freestanding initrd

And so at restart blank screen again...
I use budgie desktop.
I guess the error message références the booting partition?
Any help would be appreciated to restore the situation !
Best,
Guillaume

SethStorm666

You properly need to remove old kernel versions.

https://help.getsol.us/docs/user/troubleshooting/#boot-into-previous-kernel

Gregre

SethStorm666
Apologies, but I can't find how to remove previous kernel versions properly.
I ran command : sudo CBM_DEBUG=1 clr-boot-manager update, which is stated in the link you shared and it confirmed that there is "no space left on device" (same error message than the one I initially shared)
But i'm at loss of what to do next...
Many thanks

alfisya

Try running sudo usysconf run -f. If it failed, then you have to manually remove old kernel (to which I forgot how, I will look into it).

Btw how big is your /boot partition? Is this an old install, so under 1GB?

Gregre

Thank you all for taking the time,
Thanks to stocc, I was able to recover the desktop manager (exact command being clr-boot-manager).
I had 4 kernel versions (ending with 315, 316, 317 and 318) and the command was telling me I was on 316.
I deleted first the 315 and rebooted, it failed again but when I re-run the listing command, I was on 318 this time and 317 had disappeared without me doing anything. So I deleted 316 and this time reboot was successful :-)

To answer alfisya , the '-f' was not considered a valid command for usysconf.
Indeed it is an old install, at least 6 years (before COVID for sure, but can't remember how long I have been running Solus). My boot partition is 500Mb.
Should I increase the size of it to avoid such problems in the future?
Cheers

stocc

sudo clr-boot-mgr list-kernels sudo clr-boot-mgr remove-kernel <kernel name from above list>
should help I believe.

SethStorm666

Gregre Boot partitition should be at least 1024 MB.

alfisya

Gregre Oops, I meant sudo usysconf run -f.

Glad you managed to solve it. We are still investigating the root cause, you are not the first user that CBM didn't cleanup old kernel properly. Hopefully we can solve it. Cheers

silke

It would help us greatly if people that run into CBM giving a 'no space left on device' could give the output of the following commands, when that happens:

sudo clr-boot-manager mount-boot
sudo clr-boot-manager list-kernels
ls -l /boot/loader/entries/
ls -l /boot/EFI/com.solus-project/
ls -l /usr/lib/kernel/
ls -l /var/lib/kernel/
df -h /boot

And:

sudo env CBM_DEBUG=1 clr-boot-manager update

stocc

silke You'll also need to issue sudo clr-boot-manager mount-boot after the first command