• Support

  • Update Error Message: clr-boot-manager failed - But end up update read success.

I Was just running the latest update in the terminal, and towards the end of it i received the error message below. But everything afterwards also seemed to finish updating normally. So I'm Hoping to get some clarification. Given the "FATAL" has me a little spooked lol. My harddrive says i still have space left, over 50GB. So not sure whats up with the

[✓] 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.12.13-184: 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.12.13-184

[✗] 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.12.13-184: 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.12.13-184

The last promt in the update Was this message below.

[✓] Running depmod on kernel 5.12.13-184.current success
[✓] Updating mimetype database success
[✓] Updating manpages database success

Appreciate any help / clarification. Thanks.

    algent Thanks for the response. I'll take a look for that how can I check that? Sorry for the simple question, Im a pretty basic user so my knowledge is limited but always trying to keep learning...I could have sworn the method I used when installing the dual boot initially called for a larger partition size.. but maybe not.

    I'm still able to use my machine, so thats good at least. I just wont power down until I have a solution lined up.

    Thanks again.

      Depends on your desktop environment. There will be something like disks / gnome disks for gnome/budgie and KDE Partition Manager for Plasma. No idea what Mate has. But they should be able to show you all drives and usages.

      Alternatively from the command line, figure out which device and partition is EFI. There should only be 1.
      sudo fdisk -l | grep EFI

      For me:

      /dev/sdc1 2048 1003519 1001472 489M EFI System

      Mount that partition to /boot
      sudo mount /dev/sdc1 /boot

      Get usage:
      df -h | grep /boot

      For me:

      /dev/sdc1 489M 207M 282M 43% /boot

      Thanks for the response Harvey. I just took a look using the KDE partition manager. It is infact a size issue with the EFI system partition. Its only 260 Mib with 223 Mib currently used. Clearly not enough for the upgrade. Bummer.

      Do you have any suggestions for what might be the safest way for me to proceed? Avoiding powering down my machine isnt a great long-term plan lol....Would changing the partition size something a casual user could tackle? Or is it safest just bite the bullet to do a fresh install that totally removes the Windows dual boot?

      Thanks again, really appreciate the info.

        CannonballSoup Would changing the partition size something a casual user could tackle? Or is it safest just bite the bullet to do a fresh install that totally removes the Windows dual boot?

        There are a few options, just make sure you backup your data first.

        Reinstall an do not dual boot.

        This would eliminate the problem and it is the simplest solution. But unless you've been thinking about getting rid of Windows or Linux and just using 1 OS, its a pretty crappy option.

        Reinstall with two separate drives.

        This is what I would do but it requires 2 drives (ideally SSDs).
        Have Windows and Linux on two separate drives so they never need know about each other. This has the added benefit of stopping Windows nuking your Linux boot which has happened in the past, several times.

        The idea is you let your UEFI boot menu toggle between boot drives. Unfortunately the initial setup requires some screwing around disconnecting the other drive while the initial installation of the OS takes place. This is because the operating systems will try use any existing EFI partition on ANY drive defeating the purpose of separating the installs in the first place. To be clear once they're installed you can shut down, connect both drives and never disconnect them again.

        Resizing a partition.

        You can resize the EFI partition but I have never done it so I can not guide you on it, hopefully someone else with experience can help if this is the path you choose.

        Trimming the EFI partition.

        Solus keeps an old kernel image or two around in the EFI partition for recovery purposes. Just in case the latest one has issues with your system. You could try trimming these old kernel images but it is a manual process and requires knowing what to delete. This solution is not ideal as the EFI partition being too small means the issue will return.

            Harvey Lots of great information Harvey....Option 2 sounds like a good long-term plan, i'll look at getting an external ssd and giving that a try....For the time being i'll probably end up just going with option #1...I only dual booted in the first place because Solus is my first Linux experience, and i wasnt sure how it was going to go but it has been months since i even logged into windows, so dual boot was pretty unnecessary in retrospect.

            One more quick question...Do you know happens when i shut down my machine & start it back up again? Thats my biggest concern at this point lol, i dont know what happens when i shut down. I assume the windows boot remains unaffected, but would Solus be able to boot using the most recent version of the Kernal the EFI has stored? Or once I shutdown is this current Solus i have install brick'd?

            cheers!

                CannonballSoup
                I have no idea. My assumption would be that as the kernel install failed due to lack of space it would boot into the old one but I can't promise that will happen.

                  I got a similar error, in other pc, the difference is that my pc don't use uefi, and at the time of installation, I use LLVM on disk partitions and /boot was created with 256mb (by the installer in older iso, newer isos don't have this issue), that's less than 500mb recommended (for the time, it was fine, no errors updating, now it happens every two or three updates).
                  The steps I have made is for my pc with legacy bios and no support for efi, maybe in a pc with efi could be different or similar, I dont know.

                  A workaround is to delete some entries in /boot
                  BE EXTREMELY CAREFUL NOT TO DELETE OTHER THINGS
                  Step 1:
                  In terminal:
                  cd /boot
                  If the directory don't exist, stop here, your case is different to mine, and nothing can be don further this step.

                  Step 2:
                  You can use ls to see what's inside. There are some files called com.solus-project.current.###, com.solus-project.lts.###, initrd-com.solus-project.current.#####, initrd-com.solus-project.lts.#####
                  note that # represent version number of the lts and current kernel.

                  Here you can delete those files, it will free some space
                  sudo rm com.*
                  and
                  sudo rm init*

                  And finaly, step 3:
                  Here you can chose just to update clr-boot-manager or run usysconf, they will work almost the same for the final purpose of updating boot entries but usysconf will do more work.

                  sudo clr-boot-manager update
                  or
                  sudo usysconf run -f

                  It's not a permanent solution but it will work every time the same problem popup.

                  Other form to make a permanent solution is to resize partitions:
                  (DATA COULD BE LOST BY THIS PROCESS, MAKING YOUR INSTALLATION CORRUPTED DOE TO DELETED FILES)
                  So, the permanent solution is to resize the lvm partition to free 200mb, then make boot to the size recommended, I haven't done that jet because of the warning, I don't want to do a re installation (I'll eventually do it anyway)

                    nolan Thanks for the info Nolan, I will look into this & hopefully it can also help anyone else who runs into this issue. I think it may be a little out of my depth though making it a bit risky for my situation. I will likely just be starting fresh and re-installing everything without a dual boot. Thanks again!