All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tommaso <elisapippo@tiscali.it>
To: dm-crypt@saout.de
Subject: [dm-crypt] Help: after crypttab modify > begin: waiting for root file system
Date: Mon, 31 Aug 2009 00:49:05 +0200	[thread overview]
Message-ID: <4A9B01E1.5030205@tiscali.it> (raw)

Sorry for my poor english and for the not-so-clear topic, I hope someone
can help me because I'm in serious trouble :(

I run (ehm... I was running :( ) a headless debian lenny server with
encrypted LUKS filesystem. After I made an apparently harmless modify to
the crypttab file I can no longer boot the system. At startup I get the
message:

    Begin: waiting for root file system...


And all is hanged up. I have a plaintext /boot partition with the
bootloader (grub), while everything else is encrypted. My /etc/crypttab
file was something like this:

    lg0-lv0_crypt /dev/mapper/lg0-lv0 none luks


so that at boot time it was necessary to manually insert a passphrase to
unlock the filesystem (lg0-lv0_crypt is mounted as / on fstab). Now, I
must leave the place where the server resides for some weeks, so I
decided to temporarily override this behaviour with a cleartext key file
to avoid problems due to accidental rebooting. So I did:
1) put a random key_temp file in /boot with 600 permission
2) cryptsetup luksAddKey /dev/mapper/lg0-lv0 /boot/key_temp
3) edited /etc/crypttab to look like this:

    lg0-lv0_crypt /dev/mapper/lg0-lv0 /boot/key_temp luks

4) update-initramfs -u ALL

but when I rebooted... all was hanged up as I said before. I can't
manage even how to undo my changes now.

Can you help me please? U_U

             reply	other threads:[~2009-08-30 22:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-30 22:49 Tommaso [this message]
2009-09-01  1:13 ` [dm-crypt] Help: after crypttab modify > begin: waiting for root file system Jonas Meurer
2009-09-01  9:17   ` Tommaso
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=4A9B01E1.5030205@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.