From mboxrd@z Thu Jan 1 00:00:00 1970 From: Duncan Keall Subject: bug#19190: Cannot boot with encrypted root Date: Mon, 15 Dec 2014 23:49:39 +1300 Message-ID: <1418640579.2467571.202978541.4A391362@webmail.messagingengine.com> References: <1417003517.3640091.195610409.39CCFAAC@webmail.messagingengine.com> <87ioi2uevw.fsf@gnu.org> <1417053963.3820317.195899889.5AAEB90A@webmail.messagingengine.com> <87tx1lostk.fsf@gnu.org> <877fxvxl8z.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:37134) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Y0TE8-0004JI-BX for bug-guix@gnu.org; Mon, 15 Dec 2014 05:50:12 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Y0TE3-0008De-9F for bug-guix@gnu.org; Mon, 15 Dec 2014 05:50:08 -0500 Received: from debbugs.gnu.org ([140.186.70.43]:37123) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Y0TE3-0008D8-6v for bug-guix@gnu.org; Mon, 15 Dec 2014 05:50:03 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.80) (envelope-from ) id 1Y0TE2-0007pz-NW for bug-guix@gnu.org; Mon, 15 Dec 2014 05:50:02 -0500 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <877fxvxl8z.fsf@gnu.org> 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 Thanks for the update, Ludovic! I've just tested another install with a fresh image from master, using as similar setup as possible to before. The boot process still fails at mounting the root filesystem (as expected): fsck.ext4: No such file or directory while trying to open /dev/mapper/main Possibly non-existent device? However I found that cryptsetup was missing from the store during the early-boot REPL, so I wasn't able to test manually mounting the encrypted filesystem. Nothing in the commit history since v0.8 jumped out as being responsible, so I'm assuming I've missed something obvious during install. I'll have to keep looking!