From mboxrd@z Thu Jan 1 00:00:00 1970 From: Duncan Keall Subject: bug#19190: Cannot boot with encrypted root Date: Thu, 27 Nov 2014 01:05:17 +1300 Message-ID: <1417003517.3640091.195610409.39CCFAAC@webmail.messagingengine.com> References: <8761e2wsjp.fsf@karetnikov.org> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:57558) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XtfeQ-00037I-Ca for bug-guix@gnu.org; Wed, 26 Nov 2014 11:41:14 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XtfeK-0000jX-85 for bug-guix@gnu.org; Wed, 26 Nov 2014 11:41:10 -0500 Received: from debbugs.gnu.org ([140.186.70.43]:49204) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XtfeJ-0000jS-HG for bug-guix@gnu.org; Wed, 26 Nov 2014 11:41:04 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.80) (envelope-from ) id 1XtfeJ-0002W8-9s for bug-guix@gnu.org; Wed, 26 Nov 2014 11:41:03 -0500 In-Reply-To: <8761e2wsjp.fsf@karetnikov.org> Sender: "Debbugs-submit" Resent-Message-ID: List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org To: Ludovic =?UTF-8?Q?Court=C3=A8s?= Cc: 19190@debbugs.gnu.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 =E2=80=98cryptsetup=E2=80=99 by hand from t= he 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.