From: Milan Broz <gmazyland@gmail.com>
To: Philipp Durrer <philipp@nexus-informatik.ch>
Cc: dm-crypt@saout.de
Subject: Re: [dm-crypt] Can't mount my LUKS crypted disk after kernel update / reboot
Date: Sun, 16 Dec 2012 19:34:58 +0100 [thread overview]
Message-ID: <50CE1452.20406@gmail.com> (raw)
In-Reply-To: <CALceyLEx70of8AFkKZgGXGQDhmA4VNbvGHkrrFpsiD9_aFkRXQ@mail.gmail.com>
On 12/16/2012 07:11 PM, Philipp Durrer wrote:
> dmsetup table --showkeys
Hm, I should said do compare but do NOT send this to list
(it contains volume key).
You should reencrypt your devices now...
(including truecrypt device you have mapped, because they are no longer
secure)
> unknown partition table doesn't look good to me, but I can see this error for other md drives aswell.
That's fine, it should be LUKS device without partition
(this message is misleading and should be removed from kernel IMO)
I thihk LUKS/dmcrypt works as expected here, something was corrupted in MD or ext4.
> I did check the keyslot with the keyslot_checker in misc, did report that everything looks fine.
> Did aswell check the disk with hd tool and looks fine aswell all random data up to 0x20000 where data begins.
check plain (unlocked) luks device as well, maybe you will see some pattern
which explains that why overwritten (it apparently missing ext4 or any known signature
to blkid)
Milan
next prev parent reply other threads:[~2012-12-16 18:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-13 20:36 [dm-crypt] Can't mount my LUKS crypted disk after kernel update / reboot Philipp Durrer - Nexus Informatik
2012-12-16 9:16 ` Javier Juan Martínez Cabezón
2012-12-16 9:24 ` Javier Juan Martínez Cabezón
2012-12-16 10:49 ` Milan Broz
2012-12-16 18:11 ` Philipp Durrer
2012-12-16 18:34 ` Milan Broz [this message]
2012-12-16 21:27 ` Arno Wagner
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=50CE1452.20406@gmail.com \
--to=gmazyland@gmail.com \
--cc=dm-crypt@saout.de \
--cc=philipp@nexus-informatik.ch \
/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.