Failed to boot after reboot

Must I do:
sudo clr-boot-manager set-kernel com.solus-project.current.6.12.17-314 ?

Here are the proposed kernels:

  com.solus-project.current.6.12.17-314
  com.solus-project.current.6.12.12-313
  com.solus-project.lts.6.6.80-265
  com.solus-project.lts.5.15.77-189

The command gives:

Generating grub configuration file ...
Warning: os-prober will be executed to detect other bootable partitions.
Its output will be used to detect bootable binaries on them and create new boot entries.
done

But no kernel is selected.

Is it normal @Harvey please ?

It failed to boot in grub, telling:
‘Error : file « /boot/null » not available ´

In addition, when I go in grub command, it does know sudo command, and I don’t see usual directories in /dev but:

urandom
lp1
lp2
lp3
lp0
null
What must I do to rescue my boot please, usual advices of the help section does not seem applyable.

The only line of the grub menu is
Solus 4.7 Endurance (6.2.17-314.current).
I have 4 com… kernel files in the /boot directory

Thank you.

I followed the guide, but when doing:

sudo clr-boot-manager update

last step to Regenerate UEFI boot entries before rebooting the system

I get:

[FATAL] cbm (../src/bootman/bootman.c:L548): Cannot determine boot device

All steps before seems ok, and /etc/fstab corresponds to the output of ls -lah /dev/disk/by-uuid

At least, now, sudo clr-boot-manager list-kernels lists all my four kernels (but still without star in front of one of them).
Any idea of how to tell to solus what is my boot device?

I apologize not to have seen that, to follow the guide, I needed to have booted on a live solus usb key

stocc

Yes, grub was installed with Solus. There is no other system on it.

The booting partition is a nvme (first partition swap, second ext4 for system, no encryption).
I have 5 other disks for data: 1 nvme, 1 sata3 ssd and 3 harddrives.

I looked at the /etc/kernel directory because of the following issue that shows an error looking like mine: https://github.com/getsolus/packages/issues/3742
and I have only this into, the file /etc/kernel/cmdline.d/10_resume.conf in which it is written:

resume=UUID=uuid_of_my_swap_partition

The command inxi -bz gives me:

System:
  Kernel: 6.12.9-312.current arch: x86_64 bits: 64
  Desktop: Budgie v: 10.9.2 Distro: Solus 4.7 endurance
Machine:
  Type: Desktop Mobo: ASRock model: Z370 Professional Gaming i7
    serial: <filter> UEFI: American Megatrends v: P1.10 date: 09/08/2017
CPU:
  Info: 6-core Intel Core i7-8700K [MT MCP] speed (MHz): avg: 800
    min/max: 800/4700
Graphics:
  Device-1: NVIDIA GP104 [GeForce GTX 1070] driver: N/A
  Device-2: Logitech QuickCam Vision Pro driver: snd-usb-audio,uvcvideo
    type: USB
  Display: server: X.org v: 1.21.1.16 with: Xwayland v: 24.1.6 driver: X:
    loaded: nvidia gpu: N/A
  API: OpenGL v: 4.5 vendor: mesa v: 24.3.4 note: incomplete (EGL sourced)
    renderer: llvmpipe (LLVM 19.1.6 256 bits)
  Info: Tools: api: eglinfo,glxinfo gpu: nvidia-settings,nvidia-smi
    x11: xdpyinfo, xprop, xrandr
Network:
  Device-1: Intel Ethernet I219-V driver: e1000e
  Device-2: Intel Dual Band Wireless-AC 3168NGW [Stone Peak] driver: iwlwifi
  Device-3: Intel I211 Gigabit Network driver: igb
  Device-4: Aquantia AQtion AQC107 NBase-T/IEEE 802.3an Ethernet [Atlantic
    10G] driver: atlantic
Drives:
  Local Storage: total: 13.66 TiB used: 365.05 GiB (2.6%)
Info:
  Memory: total: 64 GiB available: 62.72 GiB used: 1.98 GiB (3.1%)
  Processes: 370 Uptime: 1h 19m Shell: Bash inxi: 3.3.37

Maybe originally, I had either ubuntu or elementaryOS before I discovered Solus, but the computer had always only one linux system

Sorry, I had not seen your answer @stocc .

I realized that my fstab seemed to have been changed by the last upgrade. I had created a long time ago a swap file on one of my device (in addition of the current swap partition). In the new fstab, upgrade seems to have changed the UUID of one of my disk (my second nvme) by the UUID of my (unused) old swap partition (first portion of the first nvme) and my swap partition UUID for the data disk UUID

Edited 2025 03 12: no fstab modification, swap is swap and booting partition is booting partition, just an error from me. The error is still the same.

Therefore, I followed again all the process of boot rescue with my corrected /etc/fstab file

When I run last command sudo clr-boot-manager update, I get the following message:

[FATAL] cbm (../src/bootman/bootman.c:L548): Cannot determine boot device

I was wondering if it was because my partitions were not mounted. Therefore I mounted them, and retry with the same result..
I have the feeling that everything is ok but clr-boot-manager still tells me that it cannot determine booting device.
And when I do fdisk -l, my supposed boot partition is recognized as Linux and as a booting partition (there is a star in the dedicated column). It doesn't seem that I have EFI except on the USB live key.

Maybe rescatux is a good solution, but I had really bad experiences with partitions and repairs already (it was on a mac, but anyway).

I think my original installation was ubuntu with a swap partition. When I installed Solus a long time ago, I did it on the ubuntu Linux partition.