I have this recurring issue where Solus is unable to boot after a restart or shutdown. I either get stuck at a blank screen or at my computer manufacturer's splash screen (Lenovo). Doesn't really matter which though, and I can't access a tty from here.
I went through the Solus troubleshooting guide with a live USB, mounting my boot drive, chroot'ing into my install, doing the system update, checking for broken packages and running usysconf run -f etc .. was a fun exercise, but unfortunately the problem still persisted.
What I did notice is that when I compare my partition UUIDs (via sudo blkid) to the 'Solus-current-5.11.16-178.conf' file in "/boot/loader/entries" there is always a discrepancy between the Solus partition UUID and the .conf "resume=UUID". When I update the resume=UUID in the .conf file and reboot, I get in. This is a temp fix until the next reboot lol
This started happening after I installed another OS, but since then I've removed all other Linux distros and started running only Solus + W10 (which will also be going soon). Anyway, obviously the other OS messed with something, and I have an inconvenient temp solution, but wondering if anyone knows how I could go about fixing this more permanently.