From: Jack Hill <jackhill@jackhill.us>
To: help-guix@gnu.org
Subject: Re: grub.cfg does not have luks module for encrypted root
Date: Thu, 31 Jan 2019 22:09:10 -0500 (EST) [thread overview]
Message-ID: <alpine.DEB.2.20.1901312152080.6623@marsh.hcoop.net> (raw)
In-Reply-To: <alpine.DEB.2.20.1901302159270.6623@marsh.hcoop.net>
[-- Attachment #1: Type: text/plain, Size: 893 bytes --]
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
next prev parent reply other threads:[~2019-02-01 3:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-31 3:13 grub.cfg does not have luks module for encrypted root Jack Hill
2019-02-01 3:09 ` Jack Hill [this message]
2019-02-01 14:03 ` Joshua Branson
2019-02-01 15:29 ` Jack Hill
2019-02-02 13:50 ` Joshua Branson
2019-02-02 19:02 ` swedebugia
2019-02-03 18:16 ` Joshua Branson
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=alpine.DEB.2.20.1901312152080.6623@marsh.hcoop.net \
--to=jackhill@jackhill.us \
--cc=help-guix@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.
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).