unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Duncan Keall <duncan@duncankeall.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 19190@debbugs.gnu.org
Subject: bug#19190: Cannot boot with encrypted root
Date: Thu, 27 Nov 2014 01:05:17 +1300	[thread overview]
Message-ID: <1417003517.3640091.195610409.39CCFAAC@webmail.messagingengine.com> (raw)
In-Reply-To: <8761e2wsjp.fsf@karetnikov.org>

Here's what I've found using a very similar setup to Nikita and after
receiving the same error messages.

> Any message after entering the password prompt?

GRUB prints a single message "Slot 0 opened" and then it's into the
kernel boot logs. The first related message appears to be the
"ext2fs_check_if_mount..." one.

> Perhaps you could try running ‘cryptsetup’ by hand from the REPL.

I needed to replace "/bin/cryptsetup" with "/sbin/cryptsetup". After
that, cryptsetup accepted a password and printed these errors:

  device-mapper: table 253:0: crypt: Error allocating crypto tfm
  device-mapper: ioctl: error adding target to table
  device-mapper: reload ioctl on  failed: No such file or directory
  Failed to open temporary keystore device.
  device-mapper: remove ioctl on temporary-cryptsetup-149 failed: No
  such device or address

The return value was 256, and afterwards /dev/mapper/main still did not
exist.

  parent reply	other threads:[~2014-11-26 16:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-26  3:26 bug#19190: Cannot boot with encrypted root Nikita Karetnikov
2014-11-26  9:55 ` Ludovic Courtès
2014-11-26 12:41   ` Ludovic Courtès
2014-11-26 12:05 ` Duncan Keall [this message]
2014-11-26 16:04   ` Ludovic Courtès
2014-11-27  2:06     ` Duncan Keall
2014-11-27 10:12       ` Ludovic Courtès
2014-12-13 22:01         ` Ludovic Courtès
2014-12-15 10:49           ` Duncan Keall
2015-09-20 20:14             ` Ludovic Courtès

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1417003517.3640091.195610409.39CCFAAC@webmail.messagingengine.com \
    --to=duncan@duncankeall.com \
    --cc=19190@debbugs.gnu.org \
    --cc=ludo@gnu.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).