From: Arno Wagner <arno@wagner.name>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] not a valid LUKS device
Date: Fri, 26 Apr 2013 16:14:05 +0200 [thread overview]
Message-ID: <20130426141405.GA3188@tansi.org> (raw)
In-Reply-To: <51792BC6.7030602@riseup.net>
On Thu, Apr 25, 2013 at 10:12:38AM -0300, Hugo wrote:
> Hi,
>
> Recently, I was installing Ubuntu 13.10 and the installer appears to
> have changed something in the first sector of my home partition as
> described here:
> https://bugs.launchpad.net/bugs/1169611
>
> Now, when I try to open my encrypted partition I get the following error:
>
> # sudo cryptsetup luksOpen /dev/ubuntu/home home_crypt
>
> Device /dev/ubuntu/home is not a valid LUKS device
>
> I don't have a backup of my header and would like to know if I still can
> have hope of recovering the luks partition or if I can re-encrypt it,
> backup the header and start a new life.
>
> What is your opinion on this?
Well, it is difficult to see what this bug really does, but
if it really overwrites the first sector, then the salts
in the LUKS header are gone and there is no way to recover
from that without a header backup.
It seems Ubuntu still does not understand how to keep its
fingers off existing LUKS partitions. I recommend you complain
to them.
Arno
--
Arno Wagner, Dr. sc. techn., Dipl. Inform., Email: arno@wagner.name
GnuPG: ID: CB5D9718 FP: 12D6 C03B 1B30 33BB 13CF B774 E35C 5FA1 CB5D 9718
----
There are two ways of constructing a software design: One way is to make it
so simple that there are obviously no deficiencies, and the other way is to
make it so complicated that there are no obvious deficiencies. The first
method is far more difficult. --Tony Hoare
next prev parent reply other threads:[~2013-04-26 14:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-25 13:12 [dm-crypt] not a valid LUKS device Hugo
2013-04-26 14:14 ` Arno Wagner [this message]
2013-04-26 16:54 ` Hugo
2013-04-26 18:26 ` 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=20130426141405.GA3188@tansi.org \
--to=arno@wagner.name \
--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.