Arch Linux

soravoid

Member

Registered: 2023-07-17

Posts: 7

[SOLVED] Can't get rid of failed hibernation file?

If I start my computer with the "noresume" boot parameter, it will boot fine with no delay. However, when I boot without that parameter, I get a delay followed by a report that something with "Resume from Hibernation" went wrong (a feature I don't really care much about). My journalctl reports the following lines:

Jun 07 06:45:23 archlinux systemd-hibernate-resume-generator[216]: Reported hibernation image: ID=arch kernel=6.4.3-273-tkg-bmq UUID=aba6ed63-55fb-432c-9478-47b1db862333 offset=0
Jun 07 06:45:23 archlinux systemd[1]: Queued start job for default target Initrd Default Target.
Jun 07 06:45:23 archlinux systemd[1]: Created slice Slice /system/systemd-cryptsetup.
Jun 07 06:45:23 archlinux systemd[1]: Started Dispatch Password Requests to Console Directory Watch.
Jun 07 06:45:23 archlinux systemd[1]: Expecting device /dev/disk/by-uuid/aba6ed63-55fb-432c-9478-47b1db862333...
...
Jun 07 06:47:22 archlinux systemd[1]: dev-disk-by\x2duuid-aba6ed63\x2d55fb\x2d432c\x2d9478\x2d47b1db862333.device: Job dev-disk-by\x2duuid-aba6ed63\x2d55fb\x2d432c\x2d9478\x2d47b1db862333.device/start timed out.
Jun 07 06:47:22 archlinux systemd[1]: Timed out waiting for device /dev/disk/by-uuid/aba6ed63-55fb-432c-9478-47b1db862333.
Jun 07 06:47:23 archlinux systemd[1]: Dependency failed for Resume from hibernation.
Jun 07 06:47:23 archlinux systemd[1]: systemd-hibernate-resume.service: Job systemd-hibernate-resume.service/start failed with result 'dependency'.

(Omitted the parts that weren't mentioning the hibernation image, that's what the ellipses are for)

The UUID is the same on every boot, leading me to believe that there is a file (partition? something else indicating hibernation?) somewhere that I need to purge to fix the problem. My system is using BTRFS on LUKS if that matters.

Thanks!

Last edited by soravoid (2024-06-07 17:47:17)

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 25,223

Re: [SOLVED] Can't get rid of failed hibernation file?

Normally your swap partition is where hibernation data is written to.

Check your fstab/cryptsetup file whether it references a partition that doesn't actually exist anymore.

soravoid

Member

Registered: 2023-07-17

Posts: 7

Re: [SOLVED] Can't get rid of failed hibernation file?

Neither fstab nor crypttab have any reference to the partition in the journal. I also tried removing the swap file from the fstab to see whether it'd fix the problem but no dice. Also I noticed that the kernel version for the reported hibernation image seems to be really "old" since I only installed arch on this desktop like a week ago. Also, I did not mention that I'm dual booting with windows 10, which could perhaps cause some issues? I've disabled fast startup and everything, however.

Last edited by soravoid (2024-06-07 17:27:49)

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 25,223

Re: [SOLVED] Can't get rid of failed hibernation file?

Well generally speaking you will have a resume= parameter, no? Where does that point to and does that point to the correct swapfile? This might be not quite trivial with an encrypted partition.

soravoid

Member

Registered: 2023-07-17

Posts: 7

Re: [SOLVED] Can't get rid of failed hibernation file?

I didn't set the resume parameter since I didn't think it was needed cause I didn't want hibernation, but would setting the resume parameter make the system stop looking for that hibernation image?

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 25,223

Re: [SOLVED] Can't get rid of failed hibernation file?

If you haven't enabled it via a resume parameter, you might have an old location in your UEFI variables. HibernateLocation would have to be cleared

efivar -l | grep HibernateLocation

Alternatively just use the noresume param or mask systemd-hibernate-resume-generator

soravoid

Member

Registered: 2023-07-17

Posts: 7

Re: [SOLVED] Can't get rid of failed hibernation file?

Yup! Clearing the EFI var fixed the problem. Thank you!