Re: can't resume after hibernate
On Tue, Aug 27, 2013 at 01:10:23PM -0700, John Akintayo wrote:
> i am use debian wheezy with kde desktop environment
> i Had a problem hibernating but after installing the hibernation app from repos i was able to hibernate successfully. but now i have problem resuming after hibernation.
> When i bootup after hibernating, i get this=
> resume: libgcrypt version: 1.5.0
> resume: Could not stat the resume device file /dev/dm-3
It looks like you're using encryption. Is this correct?
> Please type in the full path name to try again
> or press ENTER to boot the system.
>
> i end up pressing enter and the system boots up as if i shut it down before.
Seems definitely like your system isn't able to access swap in order
to resume from it.
> i am not sure whether my swap is mounted during boot, when i enter the 'mount' command in CLI i get this=
> root@FireWall:/home/jean# mount
that only shows mounted file systems which aren't swap, but see below.
> this is what is in my fstab
---snip---
> /dev/mapper/FireWall-swap_1 none swap sw 0 0
Ok, so you're using swap which isn't on a standard block device. Do
you have a /etc/crypttab file? If yes, do you have a line in
/etc/crypttab which reads something like:
firewall-swap_1_crypt /dev/mapper/firewall-swap_1 /dev/urandom
cipher=aes-xts-plain64,size=256,swap
If yes, then that's your problem. Your swap partition is being
encrypted with a temporary one-time-only key. When the computer
hibernates, that temporary key is lost, and your swap can't be
accessed when you resume. I don't know how resuming from hibernation
deals with encrypted volumes. If the hibernate scripts can prompt for
a pass phrase, you could place your swap on a volume that is encrypted
with a pass phrase. If the hibernation scripts can't deal with
encryption, then your swap needs to be somewhere which isn't
encrypted. If you're using lvm, and haven't encrypted your entire
drive, put swap on its own unencrypted volume. If your entire disk is
encrypted, and you don't have free unencrypted space besides /boot,
then you're out of luck as far as I can see. Whole disk encryption
sounds neat at first glance, but it does come with pitfalls too. HTH.
Greg
--
web site: http://www.gregn..net
gpg public key: http://www.gregn..net/pubkey.asc
skype: gregn1
(authorization required, add me to your contacts list first)
--
Free domains: http://www.eu.org/ or mail dns-manager@EU.org
Reply to: