From: PsiStormYamato <psistormyamato@lavabit.com>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] Bug Report to Ubuntu regarding dangerous installer
Date: Sat, 16 Apr 2011 20:14:26 -0400 [thread overview]
Message-ID: <1302999266.10077.16.camel@desktop-10-10> (raw)
In-Reply-To: <BANLkTinHfujxesXbvHL6vDMPg74NiURueQ@mail.gmail.com>
I've never fooled with encrypted LVMs; I always encrypt separate
partitions. I had a feeling that going the LVM route could lead to
problems, and it looks like you've found one.
I brief search turned up this post from 2009, so it's apparently a known
issue. A workaround is presented, but it's probably not something that
most folks would think to try.
http://ubuntuforums.org/archive/index.php/t-1009031.html
On Sat, 2011-04-16 at 18:18 +0200, Cristian KLEIN wrote:
> Hello,
>
> Let me elaborate a little bit on what happened. I had a computer with
> one ext2 /boot partition and one huge dm-crypt volume, inside which I
> had three logical volumes: root, swap and home. My intend was to
> install Ubuntu Natty on root, without touching home.
>
> LVM and dm-crypt can only be configured using the alternate Installer,
> so I downloaded the daily version of Ubuntu Natty Alternate Installer
> and hoped for the best. When I got to the menu asking me to create
> partitions / file systems, Ubuntu did not automatically activate the
> existing dm-crypt volume. In fact, it didn't even show that the
> partition was of type "crypto". IIRC, the partition was just shown to
> be unknown. Trying to activate the dm-crypt volume, the only option I
> could find was "configure encrypted volumes" [1]. Later I found out
> that it only allows to create a new volume, but not activate an
> existing one.
>
> I understand that the alternate installer is supposed to be for
> experts, but I still think that:
> 1) Ubuntu failed to detect the existing dm-crypt volume, thus
> confusing the user.
> 2) The installer did not provide an easy-to-find command for
> activating the dm-crypt volume.
> 3) Airbags have been turned off, without the user's knowledge.
>
> Please comment and tell me if I am wrong.
>
> Cheers,
> Cristi.
>
> [1] https://help.ubuntu.com/community/Installation/SoftwareRAID?action=AttachFile&do=get&target=ubuntu_raid_06.png
> _______________________________________________
> dm-crypt mailing list
> dm-crypt@saout.de
> http://www.saout.de/mailman/listinfo/dm-crypt
next prev parent reply other threads:[~2011-04-17 0:14 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-12 20:13 [dm-crypt] yet another "lost my partition" message Hugo Melo
2011-04-13 1:10 ` Arno Wagner
2011-04-13 18:06 ` Hugo Melo
2011-04-15 13:52 ` Cristian KLEIN
2011-04-15 14:15 ` Roscoe
2011-04-15 14:21 ` Cristian KLEIN
2011-04-15 16:27 ` Arno Wagner
2011-04-15 16:18 ` Arno Wagner
2011-04-15 16:13 ` Arno Wagner
2011-04-15 19:37 ` Jonas Meurer
2011-04-15 21:58 ` Arno Wagner
2011-04-16 16:37 ` Cristian KLEIN
2011-04-16 17:13 ` Rick Moritz
2011-04-15 16:58 ` [dm-crypt] Bug Report to Ubuntu regarding dangerous installer Arno Wagner
2011-04-15 19:38 ` Claudio Moretti
2011-04-15 22:01 ` Arno Wagner
2011-04-16 11:06 ` Claudio Moretti
2011-04-16 16:18 ` Cristian KLEIN
2011-04-17 0:14 ` PsiStormYamato [this message]
2011-04-17 0:20 ` M Thomas Frederiksen
2011-04-17 1:53 ` Arno Wagner
2011-04-15 20:54 ` PsiStormYamato
-- strict thread matches above, loose matches on Subject: below --
2011-04-17 2:16 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=1302999266.10077.16.camel@desktop-10-10 \
--to=psistormyamato@lavabit.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox