Boot issues encountered with resume= parameter
This document (000020264) is provided subject to the disclaimer at the end of this document.
SUSE Linux Enterprise Server for SAP 15
SUSE Linux Enterprise Server HPC 15
SUSE Linux Enterprise Server 12
SUSE Linux Enterprise Server for SAP 12
SUSE Linux Enterprise Server HPC 12
May 19 19:19:19 geeko kernel: PM: Checking hibernation image partition /dev/mapper/swap May 19 19:19:19 geeko kernel: PM: Hibernation image not present or could not be loaded.
May 20 20:04:09 geeko systemd: Found device /dev/mapper/swap May 20 20:04:09 geeko systemd: Starting Resume from hibernation using device /dev/mapper/swap... May 20 20:04:09 geeko kernel: PM: Starting manual resume from disk May 20 20:04:09 geeko kernel: PM: Hibernation image partition 254:0 present May 20 20:04:09 geeko kernel: PM: Looking for hibernation image. May 20 20:04:09 geeko kernel: PM: Image not found (code -22) May 20 20:04:09 geeko kernel: PM: Hibernation image not present or could not be loaded. May 19 19:04:09 LISSUMAGB2CTST systemd-hibernate-resume: Could not resume from '/dev/mapper/swap' (254:0). May 19 19:04:09 LISSUMAGB2CTST systemd: Started Resume from hibernation using device /dev/mapper/swap. May 19 19:04:09 LISSUMAGB2CTST systemd: Reached target Local File Systems (Pre).Generally speaking, messages related to failing to resume from hibernation image are seen.
A one off solution would be to edit the grub entries in the boot loader.
Follow the product documentation for instructions
You will see an entry like this:
linux /vmlinuz-4.12.14-122.71-default root=UUID=fe845e0b3-abce-46e5-9a65-00b6363e52b9 resume=/dev/mapper/swap splash=silent quiet crashkernel=216M-:108M showopts resume=/dev/mapper/swap splash=silent quiet showopts crashkernel=108M
A cleaned up entry would look like this after removing the duplicate entries and the resume parameters and appending a noresume:
linux /vmlinuz-4.12.14-122.71-default root=UUID=fe845e0b3-abce-46e5-9a65-00b6363e52b9 splash=silent quiet crashkernel=216M-:108M noresume
Or you may attempt to boot selecting "recovery mode" in the boot menu. The recovery mode will make no attempt to resume.
A permanent change would be to change the /etc/default/grub file and remake the grub config file. The steps are as follows.
GRUB_CMDLINE_LINUX_DEFAULT="resume=/dev/mapper/swap splash=silent quiet crashkernel=216M-:108M showopts resume=/dev/mapper/swap splash=silent quiet showopts crashkernel=108M"
GRUB_CMDLINE_LINUX_DEFAULT="splash=silent quiet crashkernel=216M-:108M showopts noresume"
Then it's a simple matter of backing up the /boot/grub2/grub.cfg file, for example by copying that file to /boot/grub2/grub.cfg.backup.
After backing up, remake the grub config file:
grub2-mkconfig -o /boot/grub2/grub.cfg
On the next boot the system will not attempt to resume from the hibernation image.
- Security hardened systems
- Systems in which the swap device, root filesystem or /boot partition was not specified by UUID
- Otherwise improperly configured GRUB, such as duplicate resume= parameters
- Cases where the swap device was unreachable.
This is a desktop feature. On a laptop computer, this helps to reduce the waiting time when work is continued or when the laptop lid is closed.
Linux servers are intended to run with an high uptime, and reboots should happen on purpose and be predictable.
Resuming a server should be considered under very special conditions only. Perhaps certain types of embedded devices might benefit from the feature.
This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.
- Document ID:000020264
- Creation Date: 28-May-2021
- Modified Date:02-Jul-2021
- SUSE Linux Enterprise Server
- SUSE Linux Enterprise Server for SAP Applications
- SUSE Linux Enterprise HPC
For questions or concerns with the SUSE Knowledgebase please contact: firstname.lastname@example.org