mkinitrd unification across distributions
 help / color / mirror / Atom feed
From: "Claudio A. T. Clemens" <asturio-hi6Y0CQ0nG0@public.gmane.org>
To: initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: cryptsetup + lvm order and crypt name
Date: Wed, 06 Aug 2014 00:26:09 +0200	[thread overview]
Message-ID: <53E15A01.9040604@gmx.net> (raw)

[-- Attachment #1: Type: text/plain, Size: 2165 bytes --]

Hi there,

I installed a new Debian (7.6) system, where I have a huge crypted
partition. This crypted partition is used as a lvm VG where the actual
Linux partitions are. Everything worked ok, till I installed dracut
(after installing a newer Kernel, which needed dracut). It was version
020, but now I'm using 038. So the Problem is my partitions setup, which
dracut can't handle (or I can't configure it).

If I boot with rd.auto=1, then after some time I get a prompt, where I
need to enter the password for decrypting the crypted partition. Then
the boot goes on, but after a while I'm asked again for the password for
the same partition (some Debian init-script), and then I'm stuck there,
since the partition is already in use.

If I boot without rd.auto=1, then nothing happens, and after a while I
get a dracut shell. The only way to boot the system is typing the following:

- cryptsetup luksOpen /dev/sda5 sda5_crypt
(sda5_crypt is the name I gave to the crypted volume during
installation) Enter password here
- lvm vgscan
- lvm vgchange -ay
- exit

dracut then can boot successfully.

If I give other name in cryptsetup, instead of sda5_crypt, I end again
in the same boot phase, where the password is asked for a second time.
So I suspect, the the "normal" dracut boot is decrypting my /dev/sda5
with another name. The name is given in the /etc/crypttab, but
rd.luks.crypttab=1 doesn't help. I think the debian script only search
if there is a decrypted partition with the exact name as in the crypttab.

I don't know if this order is supported, first decrypt, than lvm.

What should I do? I'm not a dracut hacker (by now).

Thanks for any idea.

Claudio
-- 
         _
+--- ,--(_) -----------------------------------------------------------+
|  _/ ;-._\    Dipl.-Inf. Univ. Claudio Clemens         saucy          |
| (_)(   ) )   asturio at gmx (.) net           GNU/Linux User #79942  |
|   \ ;-'_/    http://asturio.gmxhome.de/begin.html                    |
|    `--(_)    "YE GODS, I HAVE FEET??!"          <- Userfriendly      |
Chegou a conta telefonicAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA!!!!..


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 263 bytes --]

             reply	other threads:[~2014-08-05 22:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-05 22:26 Claudio A. T. Clemens [this message]
     [not found] ` <53E15A01.9040604-hi6Y0CQ0nG0@public.gmane.org>
2014-08-06  7:11   ` cryptsetup + lvm order and crypt name Amadeusz Żołnowski
     [not found]     ` <871tsuks7j.fsf-txNSArhcdoZACdk+e2mhCEEMvNT87kid@public.gmane.org>
2014-08-07 20:47       ` Claudio Clemens
     [not found]         ` <8761i3pi87.fsf@freja.aidecoe.name>
     [not found]           ` <8761i3pi87.fsf-txNSArhcdoZACdk+e2mhCEEMvNT87kid@public.gmane.org>
2014-08-08  7:16             ` Amadeusz Żołnowski
2014-08-15 11:11             ` Claudio Clemens

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=53E15A01.9040604@gmx.net \
    --to=asturio-hi6y0cq0ng0@public.gmane.org \
    --cc=initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    /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