From: Arno Wagner <arno@wagner.name>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] Help! Command failed: /dev/sdd1 is not a LUKS partition
Date: Wed, 10 Feb 2010 18:14:45 +0100 [thread overview]
Message-ID: <20100210171445.GA19887@tansi.org> (raw)
In-Reply-To: <76df45931002100900l57607c1fmb13bcdbcb3def003@mail.gmail.com>
On Wed, Feb 10, 2010 at 12:00:39PM -0500, M Thomas Frederiksen wrote:
> Last issue:
>
> I've got more drives to add to btrfs, but how will it know it needs to
> unlock the other drives to open the root partition? It's only unlocking
> /dev/sda3 during boot, because /dev/sdb2 and /dev/sdc2 aren't being used
> (even tho, I've got them in the crypttab). From the fstab
>
> /dev/mapper/sda3_crypt / btrfs error=remount-ro,compress 0 1
>
> it looks like it just needs the one. Also, they all have the same
> passphrase, so I'd like to unlock them all at once... which mandriva did,
> but kubuntu doesn't. Ideas?
There is no "drive unlocking", what happens is that a new
device is created which just happens to contain a decrypted
version of the encrypted one. They are not associated in any
way (except by an LVM mapping that is typically not understood
by applications).
So either there is a corresponding device in /dev/mapper or
not, btrfs does not care where the device comes from. And
if you have not done the cryptsetup, then there is no device
in /dev/mapper and btrfs cannot use a non-existent device.
Arno
--
Arno Wagner, Dr. sc. techn., Dipl. Inform., CISSP -- Email: arno@wagner.name
GnuPG: ID: 1E25338F FP: 0C30 5782 9D93 F785 E79C 0296 797F 6B50 1E25 338F
----
Cuddly UI's are the manifestation of wishful thinking. -- Dylan Evans
If it's in the news, don't worry about it. The very definition of
"news" is "something that hardly ever happens." -- Bruce Schneier
next prev parent reply other threads:[~2010-02-10 17:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-10 17:00 [dm-crypt] Help! Command failed: /dev/sdd1 is not a LUKS partition M Thomas Frederiksen
2010-02-10 17:14 ` Arno Wagner [this message]
2010-02-10 17:43 ` M Thomas Frederiksen
2010-02-10 18:08 ` Arno Wagner
2010-02-10 22:23 ` M Thomas Frederiksen
2010-02-10 23:09 ` 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=20100210171445.GA19887@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox