[SOLVED] Error on "Unable to resume from device" but hibernation works

Hacksaurus_Babu · 2026-05-07 00:12:39

Hello,

I have noticed that no matter if I normally boot my computer or resume from a hibernation I get an error(?) when I boot that of the effect of:

Unable to resume from device '/dev/disk/by-uuid/258bf2b2-ec08-4aaf-99c2-be15c61f 174f' (259:5) offset 241371136, continuing boot process. /dev/nume1n1p2: clean, 1554636/61022208 files, 52359796/244058368 blocks

My hibernation works perfectly fine, so I am not sure what is causing this. This is what I have for my grub config:

# GRUB boot loader configuration

GRUB_DEFAULT="saved"
GRUB_TIMEOUT="5"
GRUB_DISTRIBUTOR="Arch"
GRUB_CMDLINE_LINUX_DEFAULT="loglevel=3 quiet resume=UUID=258bf2b2-ec08-4aaf-99c2-be15c61f174f resume_offset=241371136"
GRUB_CMDLINE_LINUX=""
...SNIP...

I've made sure that sudo filefrag -v /swapfile | awk '$1=="0:" {print substr($4, 1, length($4)-2)}' is the same offset of 241371136. So I'm not sure what its complaining about!

These are the hooks I have in my mkinitcpio.conf

HOOKS=(base udev resume autodetect modconf kms keyboard keymap consolefont block filesystems fsck)

This is what journalctl -b -e | grep -i "hiber" out gave me, if this is helpful at all

May 06 08:02:23 Ariq-PC systemd[1]: Clear Stale Hibernate Storage Info skipped, unmet condition check ConditionPathExists=/sys/firmware/efi/efivars/HibernateLocation-8cf2644b-4b0b-428f-9387-6d876050dc67
May 06 08:02:24 Ariq-PC systemd[1]: Clear Stale Hibernate Storage Info skipped, unmet condition check ConditionPathExists=/sys/firmware/efi/efivars/HibernateLocation-8cf2644b-4b0b-428f-9387-6d876050dc67
May 06 08:02:24 Ariq-PC systemd[1]: Clear Stale Hibernate Storage Info skipped, unmet condition check ConditionPathExists=/sys/firmware/efi/efivars/HibernateLocation-8cf2644b-4b0b-428f-9387-6d876050dc67
May 06 08:02:24 Ariq-PC systemd[1]: Clear Stale Hibernate Storage Info skipped, unmet condition check ConditionPathExists=/sys/firmware/efi/efivars/HibernateLocation-8cf2644b-4b0b-428f-9387-6d876050dc67
May 06 08:36:42 Ariq-PC systemd-logind[546]: The system will hibernate now!
May 06 08:36:42 Ariq-PC systemd[1]: Starting System Hibernate...
May 06 08:36:42 Ariq-PC systemd-sleep[136695]: in suspend-then-hibernate operations or setups with encrypted home directories.
May 06 08:36:42 Ariq-PC systemd-sleep[136695]: Performing sleep operation 'hibernate'...
May 06 08:36:42 Ariq-PC kernel: PM: hibernation: hibernation entry
May 06 17:53:17 Ariq-PC kernel: PM: hibernation: Marking nosave pages: [mem 0x00000000-0x00000fff]
May 06 17:53:17 Ariq-PC kernel: PM: hibernation: Marking nosave pages: [mem 0x0009e000-0x0009efff]
May 06 17:53:17 Ariq-PC kernel: PM: hibernation: Marking nosave pages: [mem 0x000a0000-0x000fffff]
May 06 17:53:17 Ariq-PC kernel: PM: hibernation: Marking nosave pages: [mem 0x40000000-0x403fffff]
May 06 17:53:17 Ariq-PC kernel: PM: hibernation: Marking nosave pages: [mem 0x7747e000-0x774dafff]
May 06 17:53:17 Ariq-PC kernel: PM: hibernation: Marking nosave pages: [mem 0x78165000-0x78165fff]
May 06 17:53:17 Ariq-PC kernel: PM: hibernation: Marking nosave pages: [mem 0x78c71000-0x78c71fff]
May 06 17:53:17 Ariq-PC kernel: PM: hibernation: Marking nosave pages: [mem 0x78c93000-0x78c93fff]
May 06 17:53:17 Ariq-PC kernel: PM: hibernation: Marking nosave pages: [mem 0x7d08a000-0x7effdfff]
May 06 17:53:17 Ariq-PC kernel: PM: hibernation: Marking nosave pages: [mem 0x7efff000-0xffffffff]
May 06 17:53:17 Ariq-PC kernel: PM: hibernation: Basic memory bitmaps created
May 06 17:53:17 Ariq-PC kernel: PM: hibernation: Preallocating image memory
May 06 17:53:17 Ariq-PC kernel: PM: hibernation: Allocated 2009412 pages for snapshot
May 06 17:53:17 Ariq-PC kernel: PM: hibernation: Allocated 8037648 kbytes in 0.76 seconds (10575.85 MB/s)
May 06 17:53:17 Ariq-PC kernel: PM: hibernation: Normal pages needed: 1927139 + 1024, available pages: 6438596
May 06 17:53:17 Ariq-PC kernel: PM: hibernation: Basic memory bitmaps freed
May 06 17:53:17 Ariq-PC kernel: efivarfs: removing variable HibernateLocation-8cf2644b-4b0b-428f-9387-6d876050dc67
May 06 17:53:22 Ariq-PC kernel: PM: hibernation: hibernation exit
May 06 17:53:22 Ariq-PC systemd-sleep[136695]: System returned from sleep operation 'hibernate'.
May 06 17:53:22 Ariq-PC systemd[1]: systemd-hibernate.service: Deactivated successfully.
May 06 17:53:22 Ariq-PC systemd[1]: Finished System Hibernate.
May 06 17:53:22 Ariq-PC systemd[1]: systemd-hibernate.service: Consumed 2.226s CPU time over 16.010s wall clock time, 315.4M memory peak.
May 06 17:53:22 Ariq-PC systemd[1]: Reached target System Hibernation.
May 06 17:53:22 Ariq-PC systemd-logind[546]: Operation 'hibernate' finished.
May 06 17:53:22 Ariq-PC systemd[1]: Stopped target System Hibernation.

Any help would be appreciated!

Last edited by Hacksaurus_Babu (2026-05-12 14:48:25)

5hridhyan · 2026-05-07 02:01:06

Well, you have the `resume` hook in mkinitcpio and the `resume=` kernel param, both of which will try to locate a hibernation image on every boot, not just after hibernating.

on a normal cold boot there is no valid image present, so the kernel prints that message, it's generally harmless as long as actual hibernation/resume works correctly, which it sounds like it does in your case
and when a valid hibernation image *is* present, the resume hook finds it and restores the saved session instead of continuing w/ a normal boot

I see the same message on my machine; I never bothered playing w/ the ordering of the hooks because everything works fine, and I'm not even sure if ordering alone would silence the message, it's just the kernel being vocal about its search!

Last edited by 5hridhyan (2026-05-07 02:09:04)

Hacksaurus_Babu · 2026-05-07 04:53:47

See that would make sense, but even if I do come out of a hibernation state it will state "resuming from hibernation state" but STILL print out that error message which is confusing!

I guess I'm glad that this isn't an issue? But is there a more correct way of handling hibernation is maybe what I'm asking?

seth · 2026-05-07 07:44:38

Please post your complete system journal for the boot:

sudo journalctl -b | curl -s -H "Accept: application/json, */*" --upload-file - 'https://paste.c-net.org/'

Hacksaurus_Babu · 2026-05-10 05:33:22

https://paste.c-net.org/UnityBecker

This is my complete system journal for the boot.

seth · 2026-05-10 06:51:18

That boot ran for almost 11 hours but there's no trace of either entering nor leaving nor aborting hibernation - not even STR?

Hacksaurus_Babu · 2026-05-12 04:41:48

https://paste.c-net.org/HumanlyBehaving

Sorry I forgot I didn't hibernate this boot. Here is a link that hopefully should have that hibernation.

seth · 2026-05-12 06:11:45

May 09 12:46:46 Ariq-PC kernel: Command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=258bf2b2-ec08-4aaf-99c2-be15c61f174f rw loglevel=3 quiet resume=UUID=258bf2b2-ec08-4aaf-99c2-be15c61f174f resume_offset=241371136
May 09 12:46:46 Ariq-PC systemd[1]: Activating swap /swapfile...
May 09 12:46:46 Ariq-PC kernel: Adding 50331644k swap on /swapfile.  Priority:-1 extents:205 across:967286784k SS
May 11 21:01:32 Ariq-PC kernel: efivarfs: removing variable HibernateLocation-8cf2644b-4b0b-428f-9387-6d876050dc67

What happens if you remove the "resume=UUID=258bf2b2-ec08-4aaf-99c2-be15c61f174f resume_offset=241371136" parameters?

Hacksaurus_Babu · 2026-05-12 14:46:44

Oh huh that seemed to fix my issue. When I normally boot it just says "No resume device found, exiting". And when I booted from hibernation it stated that it found a hibernation image and it correctly went into hibernation.

Did something change to GRUB/ the kernel so that I don't need those flags?

journalctl -b

output for reference
https://termbin.com/wtt6

Marked as solved. Thank you so much!

Last edited by Hacksaurus_Babu (2026-05-12 14:48:45)

seth · 2026-05-12 17:51:12

Did something change to GRUB/ the kernel so that I don't need those flags?

Probably the switch fom busybox to systemd as default mkinitcpio.conf hooks.

Arch Linux

#1 2026-05-07 00:12:39

[SOLVED] Error on "Unable to resume from device" but hibernation works

#2 2026-05-07 02:01:06

Re: [SOLVED] Error on "Unable to resume from device" but hibernation works

#3 2026-05-07 04:53:47

Re: [SOLVED] Error on "Unable to resume from device" but hibernation works

#4 2026-05-07 07:44:38

Re: [SOLVED] Error on "Unable to resume from device" but hibernation works

#5 2026-05-10 05:33:22

Re: [SOLVED] Error on "Unable to resume from device" but hibernation works

#6 2026-05-10 06:51:18

Re: [SOLVED] Error on "Unable to resume from device" but hibernation works

#7 2026-05-12 04:41:48

Re: [SOLVED] Error on "Unable to resume from device" but hibernation works

#8 2026-05-12 06:11:45

Re: [SOLVED] Error on "Unable to resume from device" but hibernation works

#9 2026-05-12 14:46:44

Re: [SOLVED] Error on "Unable to resume from device" but hibernation works

#10 2026-05-12 17:51:12

Re: [SOLVED] Error on "Unable to resume from device" but hibernation works

Board footer