clr-boot-manager generates wrong UUID

inxa

I haven't used Solus on this PC for about two years but the updates went fine without breaking. (Solus is awesome!)
Besides that the Solus-current-6.11.7-308.conf boot file generates the wrong resume=UUID, I guess I changed something back then but don't remember if I only changed the swap partition or something else.
It looks like this:

title Solus 4.6 Convergence
linux /EFI/com.solus-project/kernel-com.solus-project.current.6.11.7-308
initrd /EFI/com.solus-project/initrd-com.solus-project.current.6.11.7-308
options root=UUID=740d882c-aee9-45b3-91aa-3ff2ada33d8b quiet splash rw resume=UUID=c5943a4b-2c46-433e-a222-fddff01947e4

and I can manually edit the resume=UUID to the correct one, but after a sudo clr-boot-manager update or after a linux kernel update it takes the wrong UUID again, which doesn't exist anymore.
I don't know where clr-boot-manager takes the old UUID from, any hints would be appreciated.

brent

inxa
I've never ran this in solus proper, only LIVE iso with Solus proper CHROOTED into, just so I can absolutely be sure,
sudo blkid: whatever # is there for boot drive is the REAL UUID.
then
sudo gedit /etc/fstab
according to you, these should not match. I know for a fact (just did some cloning) that the blkid UUID belongs in /etc/fstab if the fstab UUID is different.

good luck and hope this helps. you could probably check this un-chrooted but I liked to be sure.

I have to EDIT after seeing your EDIT: resume would belong to swap? same principle, maybe. blklid swap # would be the real uuid that belongs in fstab. so if you manually edited in fstab and its still not holding then?? efibootmgr moves always vex me.

second edit: unless zram is a factor?

inxa

alfisya That was it, thanks a lot! Saved me a lot of time, maybe I never would have find that as a normal user.

brent I had to edit it because I screwed up the formatting. Thanks for your input too!

alfisya

/etc/kernel/cmdline.d is where you are looking for. I hit the same problem a few months ago, but I just YOLO'd editing the UUID of the disk instead (not recommended). It is better to edit files in that directory instead. Hope this solves it for you, cheers!

brent

alfisya , but I just YOLO'd editing the UUID of the disk instead (not recommended). It is better to edit files in that directory instead

I wonder if that cmdline UUID is what blkid looks for? and noted.

inxa I had to edit it because I screwed up the formatting. Thanks for your input too!

de nada. glad that's fixed.