From: Heiko Rosemann <heiko.rosemann@web.de>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] Problem with hibernate on a crypt,lvm-system
Date: Thu, 01 Aug 2013 23:39:21 +0200 [thread overview]
Message-ID: <51FAD589.7010702@web.de> (raw)
In-Reply-To: <OF72C3C5FB.17C762DF-ONC1257BBA.002ACC2C-C1257BBA.002BD2CD@notes.behrgroup.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 08/01/2013 09:58 AM, Andreas Reschke wrote:
> Hi there,
>
> I'm using Fedora 19 on 2 different Laptop with the same
> installation: lvm with crypt (luks). [...] Hibernate is not working
> > Laptop is going to sleep; poweroff; then power on; Laptop is
> normal booting, no resume prior status. On the same Laptop with
> CentOS 6.4 hibernate works perfect.
>
> Any hint?
This is distro-specific stuff, but the problem probably is either that
Fedora like many distros reencrypts swap with a different, random key
at each boot (so the hibernation image will be unreadable) or that the
Fedora initramfs does not luksOpen the partition before it tries to
resume from it, so the resume fails to find the hibernation image. Or
maybe both.
IMHO, you should address this to Fedora to see if the guys there have
a strategy to work for your use case. For my archlinux system I had to
build custom initramfs hooks to luksOpen the swap partitions first.
HTH, Heiko
- --
Mein PGP-Key zur Verifizierung: http://pgp.mit.edu
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.20 (GNU/Linux)
Comment: Using GnuPG with undefined - http://www.enigmail.net/
iEYEARECAAYFAlH61YkACgkQ/Vb5NagElAX7ugCgiws5UC5s2tgbmKhyVvA7oEaA
zTwAmgLOrNsz1RQXzRGpm671eLkcSmh8
=/T2q
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2013-08-01 21:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-01 7:58 [dm-crypt] Problem with hibernate on a crypt,lvm-system Andreas Reschke
2013-08-01 21:39 ` Heiko Rosemann [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=51FAD589.7010702@web.de \
--to=heiko.rosemann@web.de \
--cc=dm-crypt@saout.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox