From: "Ludovic Courtès" <ludo@gnu.org>
To: Kaelyn <kaelyn.alexi@protonmail.com>
Cc: 70897@debbugs.gnu.org
Subject: bug#70897: Guix system hangs on boot with LUKS root partition
Date: Mon, 13 May 2024 12:14:34 +0200 [thread overview]
Message-ID: <87ikzic92t.fsf@gnu.org> (raw)
In-Reply-To: <oG6Z35UECVcm5tFFo502gQx_rdg5xJGWN9uzflvq4rdEPCmZpQvbuJUcOmjtkvhI4iEwqga-wHuZZpgsskyzdJHzEJqDQ1g6AtRmoTMHjQM=@protonmail.com> (Kaelyn's message of "Sun, 12 May 2024 15:26:23 +0000")
Hi Kaelyn,
Kaelyn <kaelyn.alexi@protonmail.com> skribis:
> I recently updated my systems after finally finding https://issues.guix.gnu.org/70051 and seeing the issue I was having with booting with a non-root LUKS partition configured had been fixed. After updating to a commit past these two:
>
> 49f82fca41 mapped-devices: luks: Specify modules needed at the top-level.
> 6062339156 mapped-devices: <mapped-device-type> can specify modules to import.
>
> I am now seeing a different error, which I am pretty sure is related
> to the module import changes in 49f82fca41. The error I get is about
> an unknown symbol "system*/tty" when the initramfs tries to prompt for
> a password to unlock the LUKS partition containing the root
> filesystem.
To be clear, you have both a LUKS-encrypted root and a non-root
LUKS-encrypted partition?
(FWIW I tested (1) with a LUKS-encrypted root, and (2) with a cleartext
root and LUKS-encrypted /home. The bug you mention affected #2.)
Could you share your OS config or a relevant subset thereof?
> I don't know how the module plumbing of Shepherd and the generated
> initramfs work, but I suspect the fix for Shepherd opening LUKS
> partition broke the import of system*/tty in the initramfs (for
> example, at the early REPL that booting my latest system generation
> ends up at, system*/tty is undefined initially, but after evaluating
> "(use-modules (gnu build file-systems))" system*/tty resolves to a
> procedure as exected--so the module is at least present in the
> initramfs). I have encountered this error with two different systems,
> and I believe the reproduction is simply trying to open a LUKS device
> without a keyfile so that a password prompt is necessary.
Hmm. Thanks for investigating!
Ludo’.
next prev parent reply other threads:[~2024-05-13 10:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-12 15:26 bug#70897: Guix system hangs on boot with LUKS root partition Kaelyn via Bug reports for GNU Guix
2024-05-13 10:14 ` Ludovic Courtès [this message]
2024-05-13 19:44 ` Kaelyn via Bug reports for GNU Guix
2024-05-18 17:04 ` Kaelyn via Bug reports for GNU Guix
2024-05-19 14:05 ` 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=87ikzic92t.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=70897@debbugs.gnu.org \
--cc=kaelyn.alexi@protonmail.com \
/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).