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.
