Suspend to disk/resume does not work

I had not used suspend to disk/resume since some time ago, but I did yesterday and it didn’t work. When suspending it seem to work fine but the PC didn’t shut down, so I had to turn it of after some minutes.
Then this morning booting it dind’t resume but did a fresh boot.

2019-01-17T00:30:01.675148+01:00 andromeda systemd[1]: Stopped User Manager for UID 0.
2019-01-17T00:30:01.678153+01:00 andromeda systemd[1]: Removed slice User Slice of root.
2019-01-17T00:31:53.755449+01:00 andromeda systemd[1]: Reached target Sleep.
2019-01-17T00:31:53.778682+01:00 andromeda systemd[1]: Starting Hibernate...
2019-01-17T00:31:53.797646+01:00 andromeda kernel: [59919.958099] PM: Hibernation mode set to 'platform'
2019-01-17T00:31:53.842719+01:00 andromeda systemd-sleep[18461]: INFO: running /usr/lib/systemd/system-sleep/grub2.sleep for hibernate
2019-01-17T00:31:53.843048+01:00 andromeda systemd-sleep[18461]: INFO: Running prepare-grub ..
2019-01-17T00:31:56.195946+01:00 andromeda systemd-sleep[18461]:   Skipping grub entry #, because its root= parameter (/dev/mapper/system-root)
2019-01-17T00:31:56.281668+01:00 andromeda systemd-sleep[18461]:     does not match the current root device (/dev/sda6).
2019-01-17T00:31:56.281948+01:00 andromeda systemd-sleep[18461]:   Skipping grub entry #, because its root= parameter (/dev/mapper/system-root)
2019-01-17T00:31:56.282077+01:00 andromeda systemd-sleep[18461]:     does not match the current root device (/dev/sda6).
2019-01-17T00:31:56.282196+01:00 andromeda systemd-sleep[18461]:   Skipping grub entry #, because its root= parameter (/dev/mapper/system-root)
2019-01-17T00:31:56.282315+01:00 andromeda systemd-sleep[18461]:     does not match the current root device (/dev/sda6).
2019-01-17T00:31:56.325094+01:00 andromeda systemd-sleep[18461]:   running kernel is grub menu entry openSUSE Leap 42.3 (vmlinuz-4.4.165-81-default)
2019-01-17T00:31:56.325392+01:00 andromeda systemd-sleep[18461]:   preparing boot-loader: selecting entry openSUSE Leap 42.3, kernel /boot/4.4.165-81-default
2019-01-17T00:31:58.171655+01:00 andromeda systemd-sleep[18461]:   running /usr/sbin/grub2-once "openSUSE Leap 42.3"
2019-01-17T00:31:59.732498+01:00 andromeda systemd-sleep[18461]:     time needed for sync: 1.8 seconds, time needed for grub: 1.5 seconds.
2019-01-17T00:31:59.761781+01:00 andromeda systemd-sleep[18461]: INFO: Done.
2019-01-17T00:31:59.762150+01:00 andromeda systemd-sleep[18461]: Suspending system...
2019-01-17T07:40:33.753168+01:00 andromeda systemd[1]: systemd 228 running in system mode. (+PAM -AUDIT +SELINUX -IMA +APPARMOR -SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT -GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID -ELFUTILS +KMOD -IDN)
2019-01-17T07:40:33.754601+01:00 andromeda systemd[1]: Detected architecture x86-64.
2019-01-17T07:40:33.754639+01:00 andromeda systemd[1]: Set hostname to <andromeda>.
2019-01-17T07:40:33.754651+01:00 andromeda systemd[1]: nss-lookup.target: Dependency Before=nss-lookup.target dropped
2019-01-17T07:40:33.754661+01:00 andromeda systemd[1]: Starting Flush Journal to Persistent Storage...
2019-01-17T07:40:33.754671+01:00 andromeda systemd-sysctl[594]: Couldn't write '0' to 'net/bridge/bridge-nf-call-iptables', ignoring: No such file or directory
2019-01-17T07:40:33.754692+01:00 andromeda systemd-sysctl[594]: Couldn't write '0' to 'net/bridge/bridge-nf-call-ip6tables', ignoring: No such file or directory
2019-01-17T07:40:33.754703+01:00 andromeda systemd[1]: Started Apply Kernel Variables.
2019-01-17T07:40:33.754712+01:00 andromeda systemd[1]: Started Create Static Device Nodes in /dev.
2019-01-17T07:40:33.754722+01:00 andromeda systemd[1]: Starting udev Kernel Device Manager...
2019-01-17T07:40:33.754732+01:00 andromeda systemd[1]: Reached target Local File Systems (Pre).
2019-01-17T07:40:33.754741+01:00 andromeda systemd[1]: Starting RPC Bind...
2019-01-17T07:40:33.754756+01:00 andromeda systemd-udevd[603]: Network interface NamePolicy= disabled by default.
2019-01-17T07:40:33.754767+01:00 andromeda systemd-udevd[603]: invalid TEST operation
2019-01-17T07:40:33.754777+01:00 andromeda systemd-udevd[603]: invalid rule '/usr/lib/udev/rules.d/01-md-raid-creating.rules:7'
2019-01-17T07:40:33.754787+01:00 andromeda systemd[1]: Started RPC Bind.
2019-01-17T07:40:33.754796+01:00 andromeda systemd-udevd[603]: specified group 'plugdev' unknown
2019-01-17T07:40:33.754806+01:00 andromeda systemd-udevd[603]: specified user 'user' unknown
2019-01-17T07:40:33.754821+01:00 andromeda systemd-udevd[603]: invalid KERNEL operation

2019-01-17T07:40:33.754831+01:00 andromeda systemd-udevd[603]: invalid rule '/etc/udev/rules.d/90-extraacl.rules:1'
2019-01-17T07:40:33.754841+01:00 andromeda systemd-udevd[603]: invalid KERNEL operation
2019-01-17T07:40:33.754850+01:00 andromeda systemd-udevd[603]: invalid rule '/etc/udev/rules.d/90-extraacl.rules:2'
2019-01-17T07:40:33.754859+01:00 andromeda systemd[1]: Started udev Kernel Device Manager.
2019-01-17T07:40:33.754869+01:00 andromeda systemd[1]: Started Flush Journal to Persistent Storage.
2019-01-17T07:40:33.754879+01:00 andromeda systemd-udevd[864]: failed to execute '/etc/.mplab_ide/mchplinusbdevice' '/etc/.mplab_ide/mchplinusbdevice remove ': No such file or directory
2019-01-17T07:40:33.754896+01:00 andromeda systemd-udevd[779]: Process '/etc/.mplab_ide/mchplinusbdevice remove ' failed with exit code 2.
2019-01-17T07:40:33.754907+01:00 andromeda systemd-udevd[884]: failed to execute '/etc/.mplab_ide/mchplinusbdevice' '/etc/.mplab_ide/mchplinusbdevice remove ': No such file or directory
2019-01-17T07:40:33.754919+01:00 andromeda systemd-udevd[779]: Process '/etc/.mplab_ide/mchplinusbdevice remove ' failed with exit code 2.
2019-01-17T07:40:33.754929+01:00 andromeda systemd-udevd[891]: failed to execute '/etc/.mplab_ide/mchplinusbdevice' '/etc/.mplab_ide/mchplinusbdevice remove ': No such file or directory
2019-01-17T07:40:33.754940+01:00 andromeda systemd-udevd[779]: Process '/etc/.mplab_ide/mchplinusbdevice remove ' failed with exit code 2.
2019-01-17T07:40:33.754956+01:00 andromeda systemd-udevd[894]: failed to execute '/etc/.mplab_ide/mchplinusbdevice' '/etc/.mplab_ide/mchplinusbdevice remove ': No such file or directory
2019-01-17T07:40:33.754967+01:00 andromeda systemd-udevd[779]: Process '/etc/.mplab_ide/mchplinusbdevice remove ' failed with exit code 2.
2019-01-17T07:40:33.754977+01:00 andromeda systemd-udevd[900]: failed to execute '/etc/.mplab_ide/mchplinusbdevice' '/etc/.mplab_ide/mchplinusbdevice remove ': No such file or directory
2019-01-17T07:40:33.754989+01:00 andromeda systemd-udevd[901]: failed to execute '/etc/.mplab_ide/mchplinusbdevice' '/etc/.mplab_ide/mchplinusbdevice remove ': No such file or directory
2019-01-17T07:40:33.755010+01:00 andromeda systemd-udevd[655]: Process '/etc/.mplab_ide/mchplinusbdevice remove ' failed with exit code 2.
2019-01-17T07:40:33.755026+01:00 andromeda systemd-udevd[710]: Process '/etc/.mplab_ide/mchplinusbdevice remove ' failed with exit code 2.
2019-01-17T07:40:33.755039+01:00 andromeda systemd-udevd[902]: failed to execute '/etc/.mplab_ide/mchplinusbdevice' '/etc/.mplab_ide/mchplinusbdevice remove ': No such file or directory
2019-01-17T07:40:33.755050+01:00 andromeda systemd-udevd[903]: failed to execute '/etc/.mplab_ide/mchplinusbdevice' '/etc/.mplab_ide/mchplinusbdevice remove ': No such file or directory
2019-01-17T07:40:33.755063+01:00 andromeda systemd-udevd[778]: Process '/etc/.mplab_ide/mchplinusbdevice remove ' failed with exit code 2.
2019-01-17T07:40:33.755079+01:00 andromeda systemd-udevd[779]: Process '/etc/.mplab_ide/mchplinusbdevice remove ' failed with exit code 2.
2019-01-17T07:40:33.755091+01:00 andromeda systemd-udevd[904]: failed to execute '/etc/.mplab_ide/mchplinusbdevice' '/etc/.mplab_ide/mchplinusbdevice remove ': No such file or directory
2019-01-17T07:40:33.755102+01:00 andromeda systemd-udevd[655]: Process '/etc/.mplab_ide/mchplinusbdevice remove ' failed with exit code 2.
2019-01-17T07:40:33.755113+01:00 andromeda systemd-udevd[905]: failed to execute '/etc/.mplab_ide/mchplinusbdevice' '/etc/.mplab_ide/mchplinusbdevice remove ': No such file or directory
2019-01-17T07:40:33.755123+01:00 andromeda systemd-udevd[779]: Process '/etc/.mplab_ide/mchplinusbdevice remove ' failed with exit code 2.
2019-01-17T07:40:33.755139+01:00 andromeda mtp-probe: checking bus 1, device 4: "/sys/devices/pci0000:00/0000:00:12.2/usb1/1-4/1-4.4/1-4.4.3"
2019-01-17T07:40:33.755151+01:00 andromeda mtp-probe: bus: 1, device: 4 was not an MTP device
2019-01-17T07:40:33.755161+01:00 andromeda mtp-probe: checking bus 1, device 5: "/sys/devices/pci0000:00/0000:00:12.2/usb1/1-4/1-4.4/1-4.4.4"
2019-01-17T07:40:33.755172+01:00 andromeda mtp-probe: bus: 1, device: 5 was not an MTP device
2019-01-17T07:40:33.755182+01:00 andromeda systemd[1]: Reached target Sound Card.
2019-01-17T07:40:33.755192+01:00 andromeda systemd[1]: Found device WDC_WD5000AADS-0 1.
2019-01-17T07:40:33.755206+01:00 andromeda systemd[1]: Found device WDC_WD5000AADS-0 2.
2019-01-17T07:40:33.755216+01:00 andromeda systemd[1]: Starting File System Check on /dev/sda2...
2019-01-17T07:40:33.755226+01:00 andromeda systemd[1]: Activating swap /dev/disk/by-id/ata-WDC_WD5000AADS-00S9B0_WD-WCAV91599607-part1...
2019-01-17T07:40:33.755236+01:00 andromeda systemd[1]: Created slice system-lvm2\x2dpvscan.slice.
2019-01-17T07:40:33.755245+01:00 andromeda systemd[1]: Listening on LVM2 metadata daemon socket.
2019-01-17T07:40:33.755255+01:00 andromeda systemd[1]: Starting LVM2 PV scan on device 8:17...
2019-01-17T07:40:33.755271+01:00 andromeda systemd[1]: Starting LVM2 PV scan on device 8:19...
2019-01-17T07:40:33.755281+01:00 andromeda systemd[1]: Found device WDC_WD5000AADS-0 3.
2019-01-17T07:40:33.755290+01:00 andromeda systemd[1]: Starting File System Check on /dev/sda3...
2019-01-17T07:40:33.755300+01:00 andromeda systemd[1]: Started LVM2 metadata daemon.
2019-01-17T07:40:33.755310+01:00 andromeda systemd[1]: Activated swap /dev/disk/by-id/ata-WDC_WD5000AADS-00S9B0_WD-WCAV91599607-part1.
2019-01-17T07:40:33.755319+01:00 andromeda systemd[1]: Reached target Swap.
2019-01-17T07:40:33.755329+01:00 andromeda systemd-fsck[1000]: /dev/sda3: recovering journal
2019-01-17T07:40:33.755348+01:00 andromeda systemd-fsck[1000]: /dev/sda3: clean, 383/16392192 files, 34053118/65537167 blocks
2019-01-17T07:40:33.755358+01:00 andromeda systemd[1]: Started File System Check on /dev/sda3.
2019-01-17T07:40:33.755368+01:00 andromeda systemd-fsck[985]: /dev/sda2: recovering journal


In the log it says “suspending system” and then nothing more for yesterday.

Today, the fisrts problem

Skipping grub entry #, because its root= parameter (/dev/mapper/system-root)
 andromeda systemd-sleep[18461]:     does not match the current root device (/dev/sda6).

must come from a time when I dis some test to boot from a lvm partition, but now I’m booting from sda6. I don’t know why it is something still set to the lvm in grub.

what can I change?

best regards

That boot line is set in “/etc/default/grub”. Alternatively, you can set it with Yast bootloader.

Maybe check the “resume=” argument, too. That’s what is used for resume from suspend to disk.

I had taken a look at /etc/default/grub but the contents did not seem very useful


 you can see them in real GRUB with the command `vbeinfo'
GRUB_GFXMODE=auto
# Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux
#GRUB_DISABLE_LINUX_UUID=true
# Uncomment to disable generation of recovery mode menu entries
#GRUB_DISABLE_LINUX_RECOVERY=true
# Uncomment to get a beep at grub start
#GRUB_INIT_TUNE="480 440 1"
# Skip 30_os-prober if you experienced very slow in probing them
# WARNING foregin OS menu entries will be lost if set true here
GRUB_DISABLE_OS_PROBER=false
GRUB_THEME=/boot/grub2/themes/openSUSE/theme.txt
GRUB_BACKGROUND=/boot/grub2/themes/openSUSE/background.png
SUSE_BTRFS_SNAPSHOT_BOOTING=true
GRUB_ENABLE_CRYPTODISK=n
# Xen boot parameters for all Xen boots
GRUB_CMDLINE_XEN=""
# Xen boot parameters for non-recovery Xen boots (in addition to GRUB_CMDLINE_XEN)
GRUB_CMDLINE_XEN_DEFAULT=""


In yast SUSE Paste
SUSE Paste

where the partition is first partition of sda which is a swap one


andromeda:/home/fernando # fdisk -l /dev/sda
Disk /dev/sda: 465.8 GiB, 500107862016 bytes, 976773168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x016eead2

Device     Boot     Start       End   Sectors   Size Id Type
/dev/sda1              63  34056191  34056129  16.2G 82 Linux swap / Solaris
/dev/sda2  *     34058240 222322687 188264448  89.8G 83 Linux
/dev/sda3       222323535 746620874 524297340   250G 83 Linux
/dev/sda4       746620936 976771071 230150136 109.8G  5 Extended
/dev/sda5       746620938 747247409    626472 305.9M 83 Linux
/dev/sda6       747247616 976771071 229523456 109.5G 83 Linux
andromeda:/home/fernando # 



It seems that it is a bit more complicated than I had thought.

Have you recently run (as root):


grub2-mkconfig -o /boot/grub2/grub.cfg

That’s what normally generates the grub boot menu. On my system, that automatically adds the “root=” parameter to the kernel boot line.