Hi Rodolfo,
Thanks for asking. Surprisingly I launched another trial today. My (not
that expensive) SSD was broken and I had to recover from a former backup
(now on a new SLC ssd).
The problem is solved now. For documention purposes I write my config
down here.
Bascially I followed to wiki under [0]
..which told me to use the device! (not /swap.file) where the swap file
resides. Unfortunately, all my trials were unsuccessful, until I finally
added GRUB_CMDLINE_LINUX_DEFAULT="resume=/dev/mapper/sda2_crypt quiet"
to my grub cfg.
My ssd layout is as follows:
/dev/sda1 -> 512M /boot
/dev/sda2 -> base for a crypt device -> /dev/mapper/sda2_crypt -> rootfs
swap.file is a file on the fs on sda2_crypt
The installation of uswsusp automagically detected the device and the
offset, where the swap file lives. I just never tried to add the above
mentioned kernel option.
># cat /etc/uswsusp.conf
# /etc/uswsusp.conf(5) -- Configuration file for s2disk/s2both
resume device = /dev/mapper/sda2_crypt
#resume device = /swap.file # this does not work (verify [0])
compress = y
image size = 728022466
suspend loglevel = 1
max loglevel = 1
RSA key file = /etc/uswsusp.key
shutdown method = platform
resume offset = 1832960
# offset automagically detected, e.g. dpkg-reconfigure uswsusp
I didn't downgrade to initramfs-tools from wheezy(base), so I can't tell
you if it also works with the wheezy version. Mine is:
initramfs-tools 0.115~bpo70+1 all
The kernel option for GRUB_CMDLINE_LINUX_DEFAULT is documented in the
wiki. Maybe it is possible to add a hint during the configuration
questions. I believe the same applies to swapfiles on non-crypt devices,
too.
Regards,
Marcus
[0] https://wiki.debian.org/Hibernation/Hibernate_Without_Swap_Partition
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org