From: Tommaso <elisapippo@tiscali.it>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] Help: after crypttab modify > begin: waiting for root file system
Date: Tue, 01 Sep 2009 11:17:36 +0200 [thread overview]
Message-ID: <4A9CE6B0.1070702@tiscali.it> (raw)
In-Reply-To: <20090901011335.GC22049@resivo.wgnet.de>
Jonas Meurer wrote:
> hey
Thank you for your reply :) I already managed to rescue my system and
undo my changes using the initrd.imgXXX.bak as you said (phew! :) ),
however I still have a couple of problems, one of which is really WEIRD...
The first problem is that I still can't manage how to use the cleartext
key_temp on /boot to automatically start the system without requesting a
passphrase. However thank you for pointing me at the passdev script, I
didn't know that, suppose it's intended also for this, I'll give a look
at that as soon as possible.
The second, weird problem is the following. Being unable to use the
keyfile for the automount, I temporarily added a second passphrase slot
to the above device. So now, when at boot a passphrase is requested, you
can insert either passphrase1 (the old one) or passphrase2 (the new one,
which is known also by other trusted people who should so be able to
reboot the system in my absence).
The WEIRD problem now is: if I insert passphrase1 the system starts
normally and all is good. If I insert passphrase2... the passphrase is
accepted, the disk is unlocked, the system starts... and all works
EXCEPT for the network card o.O It hangs up on DHCPREQUEST and after a
minute or so it says:
eth1: device is not ready
I'm really unable to understand why the two issues (the different
passphrase and the eth1 not ready) should be related... but I succeeded
in reproducing this behaviour many times and I'm pretty sure it depends
on the passphrase...
next prev parent reply other threads:[~2009-09-01 9:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-30 22:49 [dm-crypt] Help: after crypttab modify > begin: waiting for root file system Tommaso
2009-09-01 1:13 ` Jonas Meurer
2009-09-01 9:17 ` Tommaso [this message]
2009-09-01 9:34 ` Jonas Meurer
2009-09-02 10:43 ` Tommaso
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=4A9CE6B0.1070702@tiscali.it \
--to=elisapippo@tiscali.it \
--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.