Loader/entries resume=UUID value corrupted on system update

[TheBigStinkyBee]

Every time I do a system update, the OS fails to boot after. It hangs on

running start job for UUID (UUID value that does not exist in fstab or blkid)

I’m using systemd-boot by the way. So I have to get into the machine with an installation media, mount the EFI partition, then I have to edit

/loader/entries/longnumber-6.8.7-arch1-1.conf

and in there I find the problem.

resume=UUID=garbage_UUID_that_doesn't_exist

I change this value to my swap partition UUID and then I can boot properly.

No idea why system updates are suddenly corrupting this value. No idea where it’s getting a random UUID value that doesn’t exist.

How do I fix this so I don’t manually have to update this value to be able to boot after every system update?

[TheBigStinkyBee]

Ok I found on this forum the following suggestion to make the change to resume=UUID permanent

To make the change permanent, edit /etc/kernel/cmdline and rebuild your initramfs: sudo reinstall-kernels

So I did that, did a system update, rebooted, and it booted fine.

Not sure how /etc/kernel/cmdline resume=UUID value got corrupted in the first place but, if you have the same problem at least this is a fix.

For the googlers looking for this solution: EndeavourOS won’t boot, running start job for UUID that does not exist.

[mke]

Seems to be the same error:
https://forum.endeavouros.com/t/update-eos-update-aur-macht-systemd-boot-kaputt/53910
Thank you