From: Jonas Meurer <jonas@freesources.org>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] how to get a full disk encryption running on Linux Mint 17
Date: Thu, 12 Jun 2014 14:03:47 +0200 [thread overview]
Message-ID: <53999723.50006@freesources.org> (raw)
In-Reply-To: <5399922B.9030403@schmidt9.de>
Am 12.06.2014 13:42, schrieb Andreas:> hello,
>
> having used a Windows-based Truecrypt encryption with
> pre-boot-authentication for some years, I want to do the corresponding
> action under Linux. I am using Linux Mint 17 Cinnamon. The system has
> one harddisk.
Hello Andreas,
first, welcome to the Linux world :)
This list is mainly about dm-crypt kernel implementation, cryptsetup
userspace tool and LUKS. Full disk encryption implementations by Linux
distributions like in Debian, CentOS or Linux Mint are better discussed
on the respective distribution-specific mailinglists or in suitable forums.
I've no experiences with Linux Mint. But as it's a Ubuntu derivate which
itself is a Debian derivate I guess that the disk encryption
implementation is rather similar over there.
At least Debian and Ubuntu Installers do support full disk encrpytion at
installation time. So you don't have to setup it yourself.
Nevertheless I'll give short comments below.
> I got things working so far, using a VirtualBox machine, (so Mint 17 x32
> is used):
>
> - 200 MB primary partition ext3 on /dev/sda1 (unencrypted) as /boot
> - 9,81 GB crypt-luks on /dev/sda2 (as seen from GParted)
>
>
> This configuration boots up GRUB, Mint's green/white dots start flashing.
> Then I think a timeout appears - message reads:
>
> "Gave up waiting for root device ...
> ALERT /dev/mapper/ubuntu-root does not exist - dropping to a shell."
Sounds like the disk (/dev/sda2) unlocking mechanism is missing from
your boot process. Therefore LVM doesn't find the logical volumes,
especially not the logical volume 'root' in volume group 'ubuntu'.
Hence, the script that's responsible to mount your root filesystem fails
with the error.
> When I boot up from CD, start "Preferences - Disks"
> [...]
> So, the partions exist and can be unlocked.
So at least the encryption works. My guess is that either the relevant
line in /etc/crypttab is missing, or the cryptsetup binaries and scripts
aren't included in the initramfs.
I suggest you read /usr/share/doc/cryptsetup/README.Debian.gz and
/usr/share/doc/cryptsetup/README.initramfs.gz.
Kind regards,
jonas
next prev parent reply other threads:[~2014-06-12 12:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-12 11:42 [dm-crypt] how to get a full disk encryption running on Linux Mint 17 Andreas
2014-06-12 12:03 ` Jonas Meurer [this message]
2014-06-12 12:11 ` Benjamin Eberhardt
2014-06-13 6:24 ` Andreas
2014-06-13 21:59 ` 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=53999723.50006@freesources.org \
--to=jonas@freesources.org \
--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.