Joined: 19 Apr 2004
|Posted: Sun May 10, 2015 5:43 pm Post subject: Dracut unable to resume from image wrote to swap partition
|I have installed sys-power/suspend-1.0:0. I am able to suspend to ram with s2ram.
When I try s2disk -r /dev/sda2, after a few seconds the computer turns off (no noise, no led).
Then I type space bar, I see the BIOS startup, then I see GRUB, then it boots my grub entry, finally I have got this error message
|dracut: resume: MD5 checksum does not match |
I wonder what is the first step of the process that does not work the way it should.
I see suspend and resume as the following set of steps:
- create swap partition
- create dracut initramfs with resume support
- write image to write partition
- load image from swap partition
My swap partition looks ok:
$ grep sda2 /proc/swaps
/dev/sda2 partition 1048572 0 -1
I create my initramfs with resume support like this:
|$ dracut -v --hostonly --force /boot/initramfs-3.17.7-gentoo.img 3.17.7-gentoo
Image: /boot/initramfs-3.17.7-gentoo.img: 7.8M
with dracut modules:
-rwxr-xr-x 1 root root 1318872 May 10 17:17 usr/sbin/resume
The initramfs shows me that it finds an image and loads it:
[ 2.269721] dracut: resume: libgcrypt version: 1.5.4
[ 2.269978] dracut: resume: MD5 checksum 9f b8 d1 f0 fb 98 04 ec d3 59 ff 09 79 08 6b cc
[ 2.270262] dracut: resume: Compressed image
[ 2.551405] Switched to clocksource tsc
[ 4.904122] dracut: Loading image data pages (107794 pages)... 100% done
[ 4.904503] dracut: resume: MD5 checksum does not match
[ 4.904733] dracut: resume: Computed MD5 checksum 9f b8 d1 f0 fb 98 04 ec d3 59 ff 09 79 08 6b cc
[ 4.904992] dracut:
[ 4.905203] dracut: The system snapshot image could not be read.
[ 4.905394] dracut:
[ 4.905595] dracut: This might be a result of booting a wrong kernel.
The first error message is not very clear, it says the MD5 computed during loading does not match the MD5 found in the image, however the log shows only one MD5 (the same one at 2.269978 and 4.904733])
The second message suggests I am using the wrong kernel, for debug purpose I use entry with advanced options to have option "single", but it is the same kernel.
I have launched s2disk with kernel parameters "init=/bin/bash" to see if s2disk reports an issue, it does not.
My full initramfs log is here
Thanks for help, I have no clue what more to check/change