On my Desktop computer, Hibernate was running until 3 weeks, maybe after an update.
# journalctl --since 2025-10-13 | grep -i hiber
oct 13 20:36:22 HPI7 systemd-logind[1009]: The system will hibernate now!
oct 13 20:36:23 HPI7 systemd[1]: Starting NVIDIA system hibernate actions...
oct 13 20:36:23 HPI7 hibernate[7960]: nvidia-hibernate.service
oct 13 20:36:23 HPI7 logger[7960]: <13>Oct 13 20:36:23 hibernate: nvidia-hibernate.service
oct 13 20:36:24 HPI7 systemd[1]: nvidia-hibernate.service: Deactivated successfully.
oct 13 20:36:24 HPI7 systemd[1]: Finished NVIDIA system hibernate actions.
oct 13 20:36:24 HPI7 systemd[1]: nvidia-hibernate.service: Consumed 1.119s CPU time, 1.5G memory peak.
oct 13 20:36:24 HPI7 systemd[1]: Starting System Hibernate...
oct 13 20:36:24 HPI7 systemd-sleep[8006]: in suspend-then-hibernate operations or setups with encrypted home directories.
oct 13 20:36:24 HPI7 systemd-sleep[8006]: Performing sleep operation 'hibernate'...
oct 13 20:36:24 HPI7 kernel: PM: hibernation: hibernation entry
when i switch on :
oct 13 20:37:01 HPI7 kernel: PM: hibernation: Registered nosave memory: [mem 0x00000000-0x00000fff]
oct 13 20:37:01 HPI7 kernel: PM: hibernation: Registered nosave memory: [mem 0x00058000-0x00058fff]
oct 13 20:37:01 HPI7 kernel: PM: hibernation: Registered nosave memory: [mem 0x0009e000-0x000fffff]
oct 13 20:37:01 HPI7 kernel: PM: hibernation: Registered nosave memory: [mem 0x82845000-0x82846fff]
oct 13 20:37:01 HPI7 kernel: PM: hibernation: Registered nosave memory: [mem 0x8932c000-0x8935efff]
oct 13 20:37:01 HPI7 kernel: PM: hibernation: Registered nosave memory: [mem 0x8aeae000-0x8aeaefff]
oct 13 20:37:01 HPI7 kernel: PM: hibernation: Registered nosave memory: [mem 0x8c51e000-0x8dffdfff]
oct 13 20:37:01 HPI7 kernel: PM: hibernation: Registered nosave memory: [mem 0x8dfff000-0xffffffff]
oct 13 20:37:01 HPI7 systemd-hibernate-resume-generator[169]: Reported hibernation image: ID=endeavouros kernel=6.17.1-arch1-1 UUID=95c77143-2d6d-46d7-92d9-d4611396edde offset=0
oct 13 20:37:02 HPI7 systemd[1]: Starting Resume from hibernationā¦
oct 13 20:37:02 HPI7 systemd-hibernate-resume[479]: Reported hibernation image: ID=endeavouros kernel=6.17.1-arch1-1 UUID=95c77143-2d6d-46d7-92d9-d4611396edde offset=0
oct 13 20:37:02 HPI7 kernel: PM: hibernation: resume from hibernation
oct 13 20:37:08 HPI7 systemd-hibernate-resume[479]: Unable to resume from device ā/dev/disk/by-uuid/95c77143-2d6d-46d7-92d9-d4611396eddeā (259:6) offset 0, continuing boot process.
oct 13 20:37:08 HPI7 systemd[1]: systemd-hibernate-resume.service: Deactivated successfully.
oct 13 20:37:08 HPI7 systemd[1]: Finished Resume from hibernation.
oct 13 20:37:08 HPI7 systemd[1]: systemd-hibernate-resume.service: Consumed 2.706s CPU time, 2M memory peak.
systemd-hibernate-resume[479]: Unable to resume from device ā/dev/disk/by-uuid/95c77143-2d6d-46d7-92d9-d4611396eddeā (259:6) offset 0, continuing boot process.
If it worked some weeks before: Can you compare your journal from this time vs. now?
I think, you should see some differences?
(Check both, hibernate & resumeā¦)
Thatās the complaint from systemd in your last log, referring to Hibernate Storage Info.
Could you check if this path exists?
In general, hibernation still works as expected here. Resumed E-OS just 5 minutes ago.
Also, is your swap partition big enough? With modern RAM compression, you would need at least three quarters of your RAM.
If you didnāt use much RAM, you could work with a lot less.
If this is not insightful, I would advise you tear the hibernate settings you have down and start over with setting hibernate up.
Current hibernate process is quite impressive imho.
I have a dual-boot Ubuntu/E-OS, and can hibernate both to the same swap partition (if the amount of RAM needed for both is not too high). It gets sorted out at boot.
I discovered that purely by accident when I forgot that I already hibernated one system.
During boot, the system looks for a matching hibernation image somewhere in the swap partition, and if it finds one, it starts it. Foreign images are skipped with an info line on screen. Really neat.
How were your results? I am curious. Hibernation stopped for me unfortunately on one PC, I think it was the Nvidia driver update. Need to investigate why the computer wonāt want to sleep or hibernate now.
oct 30 23:07:13 HPI7 systemd-logind[949]: The system will hibernate now!
oct 30 23:07:13 HPI7 systemd[1]: Starting NVIDIA system hibernate actionsā¦
oct 30 23:07:13 HPI7 hibernate[6779]: nvidia-hibernate.service
oct 30 23:07:13 HPI7 logger[6779]: <13>Oct 30 23:07:13 hibernate: nvidia-hibernate.service
oct 30 23:07:14 HPI7 systemd[1]: nvidia-hibernate.service: Deactivated successfully.
oct 30 23:07:14 HPI7 systemd[1]: Finished NVIDIA system hibernate actions.
oct 30 23:07:14 HPI7 systemd[1]: nvidia-hibernate.service: Consumed 532ms CPU time, 339.5M memory peak.
oct 30 23:07:14 HPI7 systemd[1]: Starting System Hibernateā¦
oct 30 23:07:14 HPI7 systemd-sleep[6819]: in suspend-then-hibernate operations or setups with encrypted home directories.
oct 30 23:07:14 HPI7 systemd-sleep[6819]: Performing sleep operation āhibernateāā¦
oct 30 23:07:14 HPI7 kernel: PM: hibernation: hibernation entry
oct 30 23:09:30 HPI7 kernel: PM: hibernation: Registered nosave memory: [mem 0x00000000-0x00000fff]
oct 30 23:09:30 HPI7 kernel: PM: hibernation: Registered nosave memory: [mem 0x00058000-0x00058fff]
oct 30 23:09:30 HPI7 kernel: PM: hibernation: Registered nosave memory: [mem 0x0009e000-0x000fffff]
oct 30 23:09:30 HPI7 kernel: PM: hibernation: Registered nosave memory: [mem 0x82845000-0x82846fff]
oct 30 23:09:30 HPI7 kernel: PM: hibernation: Registered nosave memory: [mem 0x8932c000-0x8935efff]
oct 30 23:09:30 HPI7 kernel: PM: hibernation: Registered nosave memory: [mem 0x8aeae000-0x8aeaefff]
oct 30 23:09:30 HPI7 kernel: PM: hibernation: Registered nosave memory: [mem 0x8c51e000-0x8dffdfff]
oct 30 23:09:30 HPI7 kernel: PM: hibernation: Registered nosave memory: [mem 0x8dfff000-0xffffffff]
oct 30 23:09:30 HPI7 systemd-hibernate-resume-generator[169]: Reported hibernation image: ID=endeavouros kernel=6.17.1-arch1-1 UUID=d2c8fa71-5b1c-4a37-8db7-ac30555f66b8 offset=0
oct 30 23:09:31 HPI7 systemd[1]: Starting Resume from hibernationā¦
oct 30 23:09:31 HPI7 systemd-hibernate-resume[479]: Reported hibernation image: ID=endeavouros kernel=6.17.1-arch1-1 UUID=d2c8fa71-5b1c-4a37-8db7-ac30555f66b8 offset=0
oct 30 23:09:31 HPI7 kernel: PM: hibernation: resume from hibernation
oct 30 23:09:35 HPI7 systemd-hibernate-resume[479]: Unable to resume from device ā/dev/disk/by-uuid/d2c8fa71-5b1c-4a37-8db7-ac30555f66b8ā (259:6) offset 0, continuing boot process.
oct 30 23:09:35 HPI7 systemd[1]: systemd-hibernate-resume.service: Deactivated successfully.
oct 30 23:09:35 HPI7 systemd[1]: Finished Resume from hibernation.
oct 30 23:09:35 HPI7 systemd[1]: systemd-hibernate-resume.service: Consumed 1.508s CPU time, 1.7M memory peak.
oct 30 23:09:35 HPI7 kernel: PM: hibernation: Marking nosave pages: [mem 0x00000000-0x00000fff]
oct 30 23:09:35 HPI7 kernel: PM: hibernation: Marking nosave pages: [mem 0x00058000-0x00058fff]
oct 30 23:09:35 HPI7 kernel: PM: hibernation: Marking nosave pages: [mem 0x0009e000-0x000fffff]
oct 30 23:09:35 HPI7 kernel: PM: hibernation: Marking nosave pages: [mem 0x82845000-0x82846fff]
oct 30 23:09:35 HPI7 kernel: PM: hibernation: Marking nosave pages: [mem 0x8932c000-0x8935efff]
oct 30 23:09:35 HPI7 kernel: PM: hibernation: Marking nosave pages: [mem 0x8aeae000-0x8aeaefff]
oct 30 23:09:35 HPI7 kernel: PM: hibernation: Marking nosave pages: [mem 0x8c51e000-0x8dffdfff]
oct 30 23:09:35 HPI7 kernel: PM: hibernation: Marking nosave pages: [mem 0x8dfff000-0xffffffff]
oct 30 23:09:35 HPI7 kernel: PM: hibernation: Basic memory bitmaps created
oct 30 23:09:35 HPI7 kernel: PM: hibernation: Read 4763264 kbytes in 2.45 seconds (1944.18 MB/s)
oct 30 23:09:35 HPI7 kernel: PM: hibernation: Failed to load image, recovering.
oct 30 23:09:35 HPI7 kernel: PM: hibernation: Basic memory bitmaps freed
oct 30 23:09:35 HPI7 kernel: PM: hibernation: resume failed (-5)
oct 30 23:09:37 HPI7 systemd[1]: Clear Stale Hibernate Storage Info was skipped because of an unmet condition check (ConditionPathExists=/sys/firmware/efi/efivars/HibernateLocation-8cf2644b-4b0b-428f-9387-6d876050dc67).
oct 30 23:09:38 HPI7 systemd[1]: Clear Stale Hibernate Storage Info was skipped because of an unmet condition check (ConditionPathExists=/sys/firmware/efi/efivars/HibernateLocation-8cf2644b-4b0b-428f-9387-6d876050dc67).
oct 30 23:09:38 HPI7 systemd[1]: Clear Stale Hibernate Storage Info was skipped because of an unmet condition check (ConditionPathExists=/sys/firmware/efi/efivars/HibernateLocation-8cf2644b-4b0b-428f-9387-6d876050dc67).
oct 30 23:09:38 HPI7 systemd[1]: Clear Stale Hibernate Storage Info was skipped because of an unmet condition check (ConditionPathExists=/sys/firmware/efi/efivars/HibernateLocation-8cf2644b-4b0b-428f-9387-6d876050dc67).
I donāt understand this line !
Clear Stale Hibernate Storage Info was skipped because of an unmet condition check (ConditionPathExists=/sys/firmware/efi/efivars/HibernateLocation-8cf2644b-4b0b-428f-9387-6d876050dc67).
Hibernation is not functional :
oct 30 23:52:56 HPI7 systemd-hibernate-resume[481]: Unable to resume from device ā/dev/disk/by-uuid/d2c8fa71-5b1c-4a37-8db7-ac30555f66b8ā (259:6) offset 0, continuing boot process.
oct 30 23:52:56 HPI7 systemd[1]: systemd-hibernate-resume.service: Deactivated successfully.
and it seem that this line appear when i donāt ask an " hibernate"
thus like that the system check if a Image exist on the swap !
If not, the boot continue !
Iām newbies on ālike arch linuxā thus ilf you have a link with doc about thisā¦
oct 31 19:45:22 HPI7 systemd-hibernate-resume[478]: Unable to resume from device '/dev/disk/by-uuid/d2c8fa71-5b1c-4a37-8db7-ac30555f66b8' (259:6) offset 0, continuing boot process.
oct 31 19:45:22 HPI7 systemd[1]: systemd-hibernate-resume.service: Deactivated successfully.
and what abut this line ?
oct 31 19:45:25 HPI7 systemd[1]: Clear Stale Hibernate Storage Info was skipped because of an unmet condition check (ConditionPathExists=/sys/firmware/efi/efivars/HibernateLocation-8cf2644b-4b0b-428f-9387-6d876050dc67).
This has nothing to do with the swap size. Something on the latest (or next-to-latest Nvidia driver update borked the hibernation. I can confirm that I have āthis lineā as well, and I donāt understand it either. The UUID is that of the swap partition. But then, Iām lost. Seems to refer to some of the inner workings of the hibernation file (?).
I guess we have to wait for an update to the Nvidia driver to fix this.
mai 21 17:48:47 HPI7 kernel: efivarfs: removing variable HibernateLocation-8cf2644b-4b0b-428f-9387-6d876050dc67
and so, this one :
mai 21 23:59:41 HPI7 systemd[1]: Clear Stale Hibernate Storage Info was skipped because of an unmet condition check (ConditionPathExists=/sys/firmware/efi/efivars/HibernateLocation-8cf2644b-4b0b-428f-9387-6d876050dc67).