From: Jason Dusek <jason.dusek@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Kernel upgrade and now LUKS failure.
Date: Mon, 3 May 2010 09:56:22 -0700 [thread overview]
Message-ID: <i2h42784f261005030956u6b56e7e3qf3416964c2099232@mail.gmail.com> (raw)
I have an encrypted block device, `/dev/sda2', which is
mounted as my root filesystem. I recently installed this
system -- I've been away from Gentoo for awhile -- and used
gentoo sources 2.6.31-r6. When the kernel upgrade rolled
around, to 2.6.32-r7, I installed and rebooted and then my
passphrase didn't work anymore. The error message:
Command failed: No key available with this passphrase.
However, rebooting with my old kernel works fine so I'm not
sure what the problem is. Could it be a different version of
`cryptsetup'? When the device can't be opened on boot, I have
the option to drop to a shell. I try to run `cryptsetup' and I
get the same error -- so maybe that's my problem? Would
different versions of `cryptsetup' be incompatible with
devices encrypted by older versions? That seems brittle and
dangerous to me.
--
Jason Dusek
next reply other threads:[~2010-05-03 16:56 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-03 16:56 Jason Dusek [this message]
2010-05-03 17:31 ` [gentoo-user] Kernel upgrade and now LUKS failure Florian Philipp
2010-05-04 10:06 ` Stefan G. Weichinger
2010-05-04 16:54 ` [gentoo-user] " walt
2010-05-04 17:38 ` Stefan G. Weichinger
2010-05-04 19:28 ` Stefan G. Weichinger
2010-05-04 21:24 ` Daniel Troeder
2010-05-05 4:42 ` Stefan G. Weichinger
2010-05-05 8:00 ` Daniel Troeder
2010-05-05 8:42 ` Stefan G. Weichinger
2010-05-05 19:39 ` Daniel Troeder
2010-05-05 20:17 ` Stefan G. Weichinger
2010-05-05 20:23 ` Stefan G. Weichinger
2010-05-06 16:24 ` Daniel Troeder
2010-05-06 18:38 ` Stefan G. Weichinger
2010-05-07 8:53 ` Stefan G. Weichinger
2010-05-07 14:24 ` Stefan G. Weichinger
2010-05-07 21:14 ` Stefan G. Weichinger
2010-05-10 16:48 ` Daniel Troeder
2010-05-04 23:51 ` walt
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=i2h42784f261005030956u6b56e7e3qf3416964c2099232@mail.gmail.com \
--to=jason.dusek@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/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