Boot problems after updates

Kenwood

Solus Plasma no longer starts after installing updates.
I have a dual boot with Windows. When I try to start Solus, I get the following error:
“Error preparing initrd: volume corrupt
start_image() returned volume corrupt”
After this error message it boots Windows.
Is there a way to correct this error?

TraceyC

Kenwood

Try reading through Boot Rescue in the Help Center. Hopefully that helps. Good luck.

Vitsteri6

Try asking on Reddit in r/SolusProject, might get some replies there. Hope you fix this issue.

Jinx

Seems like the install broke because of the double boot or some faulty update. This is weird. I can recommend you do a fresh install of Solus

Kenwood

Jinx
Yes probably the best idea. Would be faster and easier. But maybe anyone knows the issue and could help me before I reinstall it or for other users in the future.

Kenwood

TraceyC
I get an error when trying to execute “sudo clr-boot-manager update”:
[ERROR] cbm (../src/bootman/update.c:L189): Cannot determine the currently running kernel

Then I did “sudo clr-boot-manager list-kernels”:

com.solus-project.current.6.12.21-316
com.solus-project.current.6.12.19-315

Followed by “sudo clr-boot-manager set-kernel com.solusproject.current.6.12.21-316” and
“sudo clr-boot-manager list-kernels”:

com.solus-project.current.6.12.21-316
com.solus-project.current.6.12.19-315

And I still get the same error with “sudo clr-boot-manager update”.
I found online the command “sudo CBM_DEBUG=1 clr-boot-manager update”:
[DEBUG] cbm (../src/cli/cli.c:L142): No such file: //etc/kernel/update_efi_vars
[INFO] cbm (../src/bootman/bootman.c:L815): Current running kernel: 6.12.9-312.current
[DEBUG] cbm (../src/bootman/bootman.c:L184): Loading vconsole.conf from //etc/vconsole.conf
[DEBUG] cbm (../src/bootman/bootman.c:L145): shim-systemd caps: 0x26, wanted: 0x02
[DEBUG] cbm (../src/bootman/bootman.c:L160): UEFI boot now selected (shim-systemd)
[INFO] cbm (../src/bootman/bootman.c:L835): path ///etc/kernel/initrd.d does not exist
[DEBUG] cbm (../src/bootman/bootman.c:L856): Non regular file: ///usr/lib64/kernel/initrd.d/.., skipping.
[DEBUG] cbm (../src/bootman/bootman.c:L856): Non regular file: ///usr/lib64/kernel/initrd.d/., skipping.
[INFO] cbm (../src/bootman/bootman.c:L531): Checking for mounted boot dir
[INFO] cbm (../src/bootman/bootman.c:L538): boot_dir is already mounted: /boot
[DEBUG] cbm (../src/bootman/update.c:L164): Now beginning update_native
[DEBUG] cbm (../src/bootman/update.c:L173): update_native: 2 available kernels
[ERROR] cbm (../src/bootman/update.c:L189): Cannot determine the currently running kernel
[SUCCESS] cbm (../src/bootman/update.c:L205): update_native: Bootloader updated
[DEBUG] cbm (../src/bootman/update.c:L230): update_native: Checking kernels for type current
[INFO] cbm (../src/bootman/update.c:L243): update_native: Default kernel for type current is ///usr/lib/kernel
/com.solus-project.current.6.12.21-316
[DEBUG] cbm (../src/bootman/kernel.c:L650): installing extra initrd: /usr/lib64/kernel/initrd-com.solus-projec
t.current.6.12.21-316.nvidia
[DEBUG] cbm (../src/bootloaders/systemd-class.c:L220): adding extra initrd to bootloader: initrd-com.solus-pro
ject.current.6.12.21-316.nvidia
[SUCCESS] cbm (../src/bootman/update.c:L255): update_native: Installed tip for current: ///usr/lib/kernel/com.
solus-project.current.6.12.21-316
[DEBUG] cbm (../src/bootman/kernel.c:L650): installing extra initrd: /usr/lib64/kernel/initrd-com.solus-projec
t.current.6.12.19-315.nvidia
[DEBUG] cbm (../src/bootloaders/systemd-class.c:L220): adding extra initrd to bootloader: initrd-com.solus-pro
ject.current.6.12.19-315.nvidia
[SUCCESS] cbm (../src/bootman/update.c:L269): update_native: Installed last_good kernel (current) (///usr/lib/
kernel/com.solus-project.current.6.12.19-315)
[INFO] cbm (../src/bootman/bootman.c:L531): Checking for mounted boot dir
[INFO] cbm (../src/bootman/bootman.c:L538): boot_dir is already mounted: /boot
[SUCCESS] cbm (../src/bootman/update.c:L338): update_native: Default kernel for current is ///usr/lib/kernel/c
om.solus-project.current.6.12.21-316
[DEBUG] cbm (../src/bootman/update.c:L353): No kernel removals found

At this Point I don’t know what to do with the output.

Kenwood

I found one issue when executing „uname -r“: 6.12.9-312.current

Then is used:
sudo eopkg it --reinstall linux-current
sudo ln -sf /usr/lib/kernel/vmlinuz-6.12.21-316 /usr/lib/kernel/current-kernel
sudo ln -sf /usr/lib/kernel/initrd-6.12.21-316 /usr/lib/kernel/current-initrd

And now it boots again. After booting in Solus, i can now use „sudo clr-boot-manager update“ without an error message.

„unmae -r „ now returns „6.12.21-316.current“
and
„sudo clr-boot-manager list-kernels“ returns „* com.solus-project.current.6.12.21-316“

I dont know why there was an old Kernel entry. Maybe it was updated with the boot rescue procedure.