I think there is something in grub's kernel options that tells it where to look for the location of the hibernate image. So you could simply edit grub during boot and remove that setting.
I don't know Voidlinux but am curious, what GPU are you using? And is your Linux DE using Wayland or X? Nvidia GPU drivers are notorious for having issues with suspend/hibernate/resume. If it's Nvidia you could try tinkering with enabling/disabling the driver options or the suspend/hibernate/resume services.
These should give you some hints:
https://wiki.debian.org/NvidiaGraphicsDrivers#Wayland_configuration
https://gist.github.com/bmcbm/375f14eaa17f88756b4bdbbebbcfd029
Unfortunately I don't know what you'd do exactly to recover from a failed hibernate - the thing with hibernate is that the RAM of the running OS was saved to disk so even turning it off completely isn't going to solve that, the whole point of hibernate is to be able to power off completely after all. When you get your system back up you should do some light testing with standby, not hibernate, just to see if there's issues. Or do what I do and never standby/hibernate :P
I've found similar issues with NVidia cards.
A probable cause is bootloader/initrd issues since these need extra initrd support when booting, and a couple of things can go wrong in updates. You could try to chroot into the system and reinstall the kernel, initrd, and graphics driver.
Oh, and hibernate doesn't work with dual-booting Linux distros (it does not leave file systems unmounted), and although grub was once designed to dual- and multiboot distros, dual-booting is problematic today.... I think some (graphics?) driver stuff can get put into the EFI partition where grub updates can step on other distro's feet.
Oddly, Void has been the first distro for me where it felt like hibernation just worked out of the box. Sorry though, I have no suggestions.
yeah fair enough, thanks anyways.
sudo mkfs.swap /dev/[swap device here>]
oh almost forgot to mention I practically unpluged my pc while it was hibernating so well you know.
If you can access it just pull.your personal files and reinstall. Its not worth the chase unless you have a ton of irreplaceable shit on there.
You can fix these things with Linux. That's the magic of it. While it's not as polished as other OSes (unlike others here keep insisting) you are actually able to fix almost every problem yourself. And while doing it you learn a thing or two.
OP is posting on Lemmy. Idk your workflow but if I've gone from searching to.posting about it I'm already at the bottom of the barrel and its time to cut my loses
What's the point of posting here then if not hoping to find a way to fix it? Me and probably a lot of others here are happy to help. But for that we need some Journal-Output for example.
When I posted no one had liked or commented and it seemed sensible should you just want to get your build going
Backups are needed. But if you want to learn how to solve weird issue like this. This is good practice. But again make sure your files are safe.
imo if OP made it here they have already traveled enough, and I know I didnt know in my comment, but the separate hone partition makes it a lot less painful.
oh lol, no yea i have separate partition for the home directory so it should be easy enough, ty!
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0