From: Arno Wagner <arno@wagner.name>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] dmsetup or cryptsetup hangs in the initrd
Date: Mon, 19 Oct 2015 09:46:47 +0200 [thread overview]
Message-ID: <20151019074647.GA22388@tansi.org> (raw)
In-Reply-To: <56249687.9060404@gmail.com>
On Mon, Oct 19, 2015 at 09:06:47 CEST, Milan Broz wrote:
> I guess you are missing dmsetup udev rules in initramfs
> or something like that. (Hint: just add --debug to cryptsetup and it will show where is is waiting.)
>
> You should probably use systemd to activate crypt devices in RHEL7 anyway.
>
> On 10/19/2015 08:21 AM, Arno Wagner wrote:
> >> Obviously, this has all been stripped down to make it as simple as
> >> possible. Sorry for the hard coding. If you want to test it, you need to
> >> provide a /dev/sdb1 partition that is at least 2G. If you comment out the
> >> `exit 0' in go.sh it will setup the partition for you.
>
> Using hardcoded sdb1 is wrong, it will overwrite other disk if you e.g. forget
> USB drive plugged in. Use some hw id symlink.
Good point.
Arno
> >> Note that if 95dmcrypt.sh has either the dmsetup or the 2 cryptsetup lines
> >> commented in, it will hang the machine.
>
> Run dracut shell, debug it by hand.
>
> Milan
>
> _______________________________________________
> dm-crypt mailing list
> dm-crypt@saout.de
> http://www.saout.de/mailman/listinfo/dm-crypt
--
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
----
A good decision is based on knowledge and not on numbers. -- Plato
If it's in the news, don't worry about it. The very definition of
"news" is "something that hardly ever happens." -- Bruce Schneier
prev parent reply other threads:[~2015-10-19 7:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-17 14:24 [dm-crypt] dmsetup or cryptsetup hangs in the initrd Sean MacLennan
2015-10-19 6:21 ` Arno Wagner
2015-10-19 7:06 ` Milan Broz
2015-10-19 7:46 ` Arno Wagner [this message]
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=20151019074647.GA22388@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.