• Support

  • Latest update borked my installation

I would think that maybe your bootloader partition (efi) is full and the file couldn't be copied there.

Precisely what @dbarron has advised. Expand that partition, move it to a new one or remove old kernels (carefully).

    Justin actually I just did some digging and it seems the boot partition is not the problem. Running df -h says the partition is only 17% full. It seems that clr-boot-manager is misbehaving and causing issues.

        otavioschwanck yeah but I'm just using it to try to figure whats going on because I've only got access to a command line through it.

          Justin Nope i'm pretty sure it finished entirely and I finished up some work before rebooting to complete the update.

            So I would try to manually remove the 5.0 kernel (eopkg) and reinstall it. See if it happens again?

              dbarron Sorry if this is a bit of a noob question but I am pretty green when it comes to this stuff. What command should I use to do it? It's not letting me use rm in the boot/efi folder because it's set read-only. Even while in su it won't remove them.

                sudo eopkg it --reinstall linux-current

                  Justin Just did it. While it was updating clr-boot-manager it returned "Child process 'usr/bin/clr-boot-manager' exited abnormally. Do you think I might've fucked up the bootloader or something? It's refusing to recognize 5.0 as the new kernel.

                    Try add CBM_DEBUG=1 before like CBM_DEBUG=1 sudo clr-boot-manager update.

                      Justin This is what I got:

                      [INFO] cbm (..src/bootman/bootman.c:L482): Current running kernel: 4.20.16-112.current
[INFO] cbm (../src/bootman/sysconfig.c:L98): Discovered UEFI ESP : /dev/disk/by-partuuid/e7a5366e-2cf9-4a75-aee6-d71af46e1aB
[INFO] cbm (..src/bootman/sysconfig.c:L123): Fully resolved boot device:/dev/nvme0n1p1
[DEBUG] cbm (..src/lib/probe.c:L261): Root device exists on device-mapper configuration
[DEBUG] cbm (..src/bootman/bootman.c:L130): UEFI boot now selected (systemd)
[INFO] cbm (..src/bootman/bootman.c:L502): path usr/lib/initrd.d does not exist
[INFO] cbm (..src/bootman/update.c:L116): Checking for mounted boot dir
[INFO] cbm (..src/bootman/update.c:L149): Mounting boot device /dev/nvme0n1p1 at /boot
[SUCCESS] cbm(../src/bootman/update.c:L157); /dev/nvme0n1p1 successfully mounted at /boot
[DEBUG] cbm (..src/bootman/update.c:L291): Now beginning update_native
[DEBUG] cbm (..src/bootman/update.c:L300): update_native: 2 available kernels
[DEBUG] cbm (..src/bootman/update.c:L320):
update_native: running kernel is 4.20.16-112
[SUCCESS] cbm (...src/bootman/update.c:L335): update_native: Bootloader updated
[SUCCESS] cbm (..src/bootman/update.c:L349): repaired running kernel 4.20.16-112
[DEBUG] cbm (..src/bootman/update.c:L358): update_native: checking kernels for type current
[INFO] cbm (..src/bootman/update.c:L373): update_native: default kernel for type current is 5.0.5-113
Bus error

                      Mod edit: formatting

                        Hmm yeah, that bus error at the end is the only thing that looks out of place. Hopefully someone with more knowledge of CBM will come along soon to help solve this.

                          Justin Nah it's all good. Just decided to reinstall with the KDE iso. Was lookin for a change of scenery anyways.

                            Suggest after installing kde, install efibootmgr package and do "bootctl install"
                            Note many people here have a 'linux boot manager' or "Systemd Boot Manager" in their efibootmgr entries, meaning they have done 'bootclt install' as well.

                            It will save a lot of hassles later on as you had and easier to fix as well if you have problems.
                            clr-bootmgr is good to 'unify' uefi and bios-legacy boots (grub or systemd-boot) but for uefi, advisable to have this explicitly installed.