From: "Michael Kjörling" <michael@kjorling.se>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] Anyone know why I can't access my volumes?
Date: Mon, 21 Oct 2019 07:50:21 +0000 [thread overview]
Message-ID: <n79nhf9zcwbfvj4x3px7xtnr@localhost> (raw)
In-Reply-To: <dSQNvGX80huu7ihdPeNylguMY-SgmnKleKpBEgwGJtOMDzLMPNMl4KN3CQw53EfGHpfsvxwTCjSusU4bcSwH7d88mMUjDJdqbyHF6ukyFyg=@pm.me>
On 20 Oct 2019 21:53 +0000, from philipp@pm.me (Philipp Rösch):
> I installed Arch Linux about a year ago with LUKS on LVM. After an
> update and reboot I can no longer access the volumes: "No key
> available with this passphrase."
That, to me, immediately makes the update suspect. Do you remember
what was updated? The kernel? Keyboard utilities or data? Any
LUKS-related packages? Was a new initramfs generated? Anything else
that might possibly be relevant for the early boot process?
Are you able to download bootable live/rescue media and boot from
that, then try to open the LUKS container from within that
environment? That should allow you to experiment more, since you will
have a fuller environment than the early boot environment. If it works
from within a live environment, then at least you know that it's
something about your installed system, not the data on disk as such.
I strongly recommend that you make at least a header backup, if you
haven't already, just in case something goes further wrong.
--
Michael Kjörling • https://michael.kjorling.se • michael@kjorling.se
“The most dangerous thought that you can have as a creative person
is to think you know what you’re doing.” (Bret Victor)
next prev parent reply other threads:[~2019-10-21 8:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-20 21:53 [dm-crypt] Anyone know why I can't access my volumes? Philipp Rösch
2019-10-21 7:50 ` Michael Kjörling [this message]
2019-10-21 14:33 ` Philipp Rösch
2019-10-21 14:50 ` Arno Wagner
2019-10-21 14:56 ` Philipp Rösch
2019-10-24 7:26 ` Carl-Daniel Hailfinger
2019-10-24 12:34 ` Arno Wagner
2019-10-24 19:35 ` Philipp Rösch
2019-12-10 16:34 ` Philipp Rösch
2019-12-10 17:42 ` Chris Murphy
2019-12-10 20:00 ` Michael Kjörling
2019-12-10 21:18 ` Chris Murphy
2019-12-10 21:51 ` Arno Wagner
-- strict thread matches above, loose matches on Subject: below --
2019-10-21 18:16 Arno Wagner
2019-10-21 18:23 ` Philipp Rösch
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=n79nhf9zcwbfvj4x3px7xtnr@localhost \
--to=michael@kjorling.se \
--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