From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jack Hill Subject: Re: grub.cfg does not have luks module for encrypted root Date: Thu, 31 Jan 2019 22:09:10 -0500 (EST) Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; BOUNDARY="925712948-902572640-1548990550=:6623" Return-path: Received: from eggs.gnu.org ([209.51.188.92]:44171) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gpPPt-000192-VD for help-guix@gnu.org; Thu, 31 Jan 2019 22:22:58 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gpPCb-000112-0X for help-guix@gnu.org; Thu, 31 Jan 2019 22:09:13 -0500 Received: from minsky.hcoop.net ([104.248.1.95]:53498) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1gpPCZ-0000yG-3X for help-guix@gnu.org; Thu, 31 Jan 2019 22:09:12 -0500 Received: from marsh.hcoop.net ([45.55.52.66]) by minsky.hcoop.net with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1gpPCY-0007kw-MO for help-guix@gnu.org; Thu, 31 Jan 2019 22:09:10 -0500 In-Reply-To: List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-guix-bounces+gcggh-help-guix=m.gmane.org@gnu.org Sender: "Help-Guix" To: help-guix@gnu.org This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --925712948-902572640-1548990550=:6623 Content-Type: text/plain; format=flowed; charset=UTF-8 Content-Transfer-Encoding: 8BIT I have solved my problem, and now have Grub working with an encrypted /. The config I had before had a gpt partitioned disk, with bios boot. I had an encrypted / and a separate, unencrypted /boot. When I changed the configuration to not use a separate /boot filesystem, and put /boot on the encrypted root, Grub dutifully prompts me for a password, and is then able to boot the system normally. Is it a bug that a separate /boot doesn't work? Is it worth mentioning in the manual that a separate /boot isn't needed? As a side note: I had been expecting 'insmod luks' and 'cryptomount …' lines in the grub.cfg. They don't appear even with the working setup, but we are running grub-install with the GRUB_ENABLE_CRYPTODISK environment variable set. I couldn't find a mention of this variable in the Grub manual. What's going on here/how do all the pieces fit together? Best, Jack --925712948-902572640-1548990550=:6623--