Public bug reported:
When trying to configure hibernation on Noble Numbat, systemd-sleep hibernate
complains about
"Failed to find location to hibernate to: Invalid argument" caused by a "0:0"
entry in /sys/power/resume
Current configuration:
1) Legacy boot configuration (non-UEFI!)
2) Dual swap space configuration (/etc/fstab excerpt for swap partition and
file):
UUID=c323a060-1b69-48af-a5bb-395f5d05fb60 none swap sw
0 0
/swap none swap sw,pri=2
0 0
2) resume config in /etc/initramfs-tools/conf.d/resume with the correct
UUID and offset:
RESUME=UUID=7799882e-189c-484b-b9d4-f9e302859b0b resume_offset=39608320
(blkid: /dev/sda1: UUID="7799882e-189c-484b-b9d4-f9e302859b0b"
BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="4f6b947f-01")
3) Correct grub config:
GRUB_CMDLINE_LINUX="resume=UUID=7799882e-189c-484b-b9d4-f9e302859b0b
resume_offset=39608320 acpi_enforce_resources=lax"
Suspect a regression issue with systemd-255 as the issue did *not*
appear with Focal Fossal (system-245) and only surfaced after the
upgrade to 24.04.
Work-around:
Amend /etc/rc.local (if this is enabled via systemd) with:
"lsblk | fgrep <insert device path holding the swap file> | cut -d' '
-f4 >/sys/power/resume"
** Affects: systemd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2061311
Title:
dev's major/minor not captured in /sys/power/resume
Status in systemd package in Ubuntu:
New
Bug description:
When trying to configure hibernation on Noble Numbat, systemd-sleep hibernate
complains about
"Failed to find location to hibernate to: Invalid argument" caused by a "0:0"
entry in /sys/power/resume
Current configuration:
1) Legacy boot configuration (non-UEFI!)
2) Dual swap space configuration (/etc/fstab excerpt for swap partition and
file):
UUID=c323a060-1b69-48af-a5bb-395f5d05fb60 none swap sw
0 0
/swap none swap sw,pri=2
0 0
2) resume config in /etc/initramfs-tools/conf.d/resume with the
correct UUID and offset:
RESUME=UUID=7799882e-189c-484b-b9d4-f9e302859b0b
resume_offset=39608320
(blkid: /dev/sda1: UUID="7799882e-189c-484b-b9d4-f9e302859b0b"
BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="4f6b947f-01")
3) Correct grub config:
GRUB_CMDLINE_LINUX="resume=UUID=7799882e-189c-484b-b9d4-f9e302859b0b
resume_offset=39608320 acpi_enforce_resources=lax"
Suspect a regression issue with systemd-255 as the issue did *not*
appear with Focal Fossal (system-245) and only surfaced after the
upgrade to 24.04.
Work-around:
Amend /etc/rc.local (if this is enabled via systemd) with:
"lsblk | fgrep <insert device path holding the swap file> | cut -d' '
-f4 >/sys/power/resume"
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2061311/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
