From: Marc Ballarin <Ballarin.Marc@gmx.de>
To: Aleksander Swirski <aleksanderswirski@gmail.com>
Cc: dm-crypt@saout.de
Subject: Re: [dm-crypt] please HELP - can't acces encrypted LVM after linux reinstallation.
Date: Fri, 28 Oct 2011 17:53:48 +0200 [thread overview]
Message-ID: <1319817228.19412.36.camel@localhost.localdomain> (raw)
In-Reply-To: <CAP8O3oPrQ69b+p9QeUOgOumL4LSovQJQffWNR_SZskF-UaJ18g@mail.gmail.com>
Am Samstag, den 29.10.2011, 04:23 +1300 schrieb Aleksander Swirski:
...
> I now realize what might have happened. As I explained I set up same
> passphrase again on this crypt disk when installing new system. But I
> suspect, encryption key underneath could be changed and LVM is now
> scrambled?
Yes, if you used LUKS this is exactly what happened. cryptsetup created
a new, random master key and wrote it over your old master key.
Keeping data by using the same password to create a new mapping only
works for plain cryptsetup without any header. With LUKS (and similar
schemes like Truecrypt) passwords are completely unrelated to the master
key which is used for actual data encryption.
> I didn't back up many important files, because my other drive
> failed not long time ago and didn't get new one yet due to cash shortage. Is
> there any hope? PLEASE if anybody can help me. Is it possible to regain
> acces to this LVM?
Unless you have a backup of your old header there really isn't anything
you can do.
Your password unlocks the master key which in turn unlocks the data. But
you have overwritten your old master key :-(
I hope you will find a header backup or someone else has an idea where
the old master key might still be found...
Regards,
Marc
next prev parent reply other threads:[~2011-10-28 15:53 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-28 15:23 [dm-crypt] please HELP - can't acces encrypted LVM after linux reinstallation Aleksander Swirski
2011-10-28 15:37 ` Rick Moritz
2011-10-28 15:48 ` Aleksander Swirski
2011-10-28 15:53 ` Marc Ballarin [this message]
2011-10-28 16:03 ` Arno Wagner
2011-10-28 16:05 ` Aleksander Swirski
2011-10-28 16:24 ` Arno Wagner
2011-10-28 16:38 ` Aleksander Swirski
2011-10-28 17:20 ` Heinz Diehl
2011-10-28 18:14 ` Aleksander Swirski
2011-10-29 7:43 ` Arno Wagner
2011-10-30 16:08 ` Aleksander Swirski
2011-10-30 17:32 ` Arno Wagner
2011-10-30 18:56 ` Aleksander Swirski
2011-10-30 22:25 ` Jonas Meurer
2011-10-31 0:30 ` Aleksander Swirski
2011-10-31 3:30 ` ingo.schmitt
2011-10-31 7:18 ` Arno Wagner
2011-10-31 22:17 ` Jonas Meurer
2011-10-31 22:34 ` Claudio Moretti
2011-10-31 22:48 ` Jonas Meurer
2011-10-31 23:46 ` Claudio Moretti
2011-11-01 5:02 ` Arno Wagner
2011-11-01 4:45 ` Arno Wagner
2011-11-01 4:36 ` Arno Wagner
2011-10-31 8:47 ` Quentin Lefebvre
2011-10-31 22:56 ` Jonas Meurer
2011-10-31 22:40 ` Jonas Meurer
2011-10-29 8:15 ` Yves-Alexis Perez
2011-10-30 19:03 ` Aleksander Swirski
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=1319817228.19412.36.camel@localhost.localdomain \
--to=ballarin.marc@gmx.de \
--cc=aleksanderswirski@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.