Failed to install initrd

DankeBrutus

I have been trying to update the clr-boot-manager/kernel and I keep getting this message:

sudo eopkg install --reinstall linux-current Total size of package(s): 83.83 MB Downloading 1 / 1 Package linux-current found in repository Solus linux-current-5.11.6-174-1-x86_64.eopkg [cached] Installing 1 / 1 linux-current-5.11.6-174-1-x86_64.eopkg [cached] Installing linux-current, version 5.11.6, release 174 Extracting the files of linux-current
Installed linux-current [✓] Syncing filesystems 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.11.6-174: 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.11.6-174

[✓] Running depmod on kernel 5.11.6-174.current success

I checked my SSD because I have seen around this forum that sometimes the EFI partition is _100MB but my EFI partition is 522MB, so that doesn't seem to be the issue.
I tried checking the /boot folder and it is empty, so I cannot delete any old kernels in it either.

Does anyone know what's going on?

nathanpainchaud

DankeBrutus The /boot folder is empty because it's automatically unmounted after boot, to prevent users from accidentally messing with it. The instructions on how to mount it are available in this Help Center article, under the Mounting your system section. Given your error message, I don't know what happened to your system, but it's clear that your boot partition somehow became over-encumbered.

Girtablulu

can you run sudo clr-boot-manager list-kernels to see how many kernel packages you have installed?

DankeBrutus

Girtablulu Sorry this is so delayed.

$ sudo clr-boot-manager list-kernels
com.solus-project.current.5.11.6-174
* com.solus-project.current.5.10.15-172 com.solus-project.lts.4.14.225-169 com.solus-project.lts.4.14.221-168

Girtablulu

DankeBrutus you have the lts and current kernel installed, is there a reason why?

DankeBrutus

Girtablulu To be honest I have no clue why both are installed.

How do I remove the LTS? I assume they aren't necessary.

Girtablulu

DankeBrutus please run uname -afirst to see which kernel you are running right now, if it's current you can remove the lts one

DankeBrutus

uname -a Linux desktop-solus 5.10.15-172.current #1 SMP PREEMPT Fri Feb 12 16:35:57 UTC 2021 x86_64 GNU/Linux

So do I have to follow this guide in order to remove LTS or is there a way to do it through my current install?

Girtablulu

DankeBrutus sudo eopkg rm linux-lts should be enough

DankeBrutus

Girtablulu this is what I get when I put that command in:

sudo eopkg rm linux-lts Password: The following list of packages will be removed in the respective order to satisfy dependencies: linux-lts Removing package linux-lts Removed linux-lts [✓] Syncing filesystems success [✗] Updating clr-boot-manager failed

A copy of the command output follows:

[ERROR] cbm (../src/bootman/update.c:L238): Could not find default kernel for type lts, using highest relno [FATAL] cbm (../src/bootman/kernel.c:L668): Failed to install initrd /boot/EFI/com.solus-project/initrd-com.solus-project.current.5.11.6-174: 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.11.6-174

edit: could I not just make the boot/EFI partition larger in gparted, download and install the new kernel update, then remove LTS? How risky, if at all, is resizing the boot partition?

DankeBrutus

Okay, I'm pretty sure I figured it out.

So I tried following this guide and when attempting to chroot the system just wouldn't let me. I figured that something must be up and mounted the boot drive of the SSD that linux lives on and found a bunch of files. At first I thought that maybe the few virtual machines I used caused this but then I figured that didn't make sense because they wouldn't need the boot drive.

Then I went into my BIOS and found that my motherboard was still seeing my old popOS install as a bootable OS. Obviously choosing this would just boot Solus, but I figured that the actual problem may have been that when I installed Solus a couple of months ago it didn't fully override the EFI partition that popOS used. I can't be certain of this, I just don't know, but once I went into Windows and nuked the EFI partition of the SSD my BIOS no longer thought I had popOS on here.

I reinstalled Solus and restored my grsync backup (a lot of my apps didn't play nice with the new install but I expected that) and now everything seems fine, other than having to reinstall some of my stuff.