OK, thank you !

Crossposted to linuxinthewild (https://lemmy.world/c/linuxinthewild)

It’s a marvellous feeling, right?

We thank Dave for his decisive contribution. For future occasions try to backup everything before doing operations of this type. This small script works very well for me:

https://github.com/cleverwise/cya

That allows you to backup even hot systems. Just mount an external disc in /home/cya and run the script with sudo…

The existing file system appears to have been damaged possibly because cfdisk has not adjusted (shrinked) the existing file system before changing the partition settings. In my case, this kind of thing I only dare to do with gparted if partitions contain file systems with data.

I would try the second option I mentioned above, as my last chance: to start a live-rescue and look that allows us to gparted, but I am not very optimistic about it

I always love working with partitions because of the knowledge it gives you, but it is also certainly dangerous and from time to time it is unnevitable to suffer an accident. In any case I always try to do this type of operations with parted and if possible with GUI (gparted).

Being in the photo situation, can’t you make a fsck as the error messages tell you?

fsck /dev/nvme0n1p2

If not, the most practical would be, IMHO, to boot from a rescue live, e.g. https://www.system-rescue.org/Download/ Once booted, you can lift the graphical interface with startx and do with gparted the operations you need on these partitions.