From: Jonathan Brielmaier <jonathan.brielmaier@web.de>
To: 50566@debbugs.gnu.org
Subject: bug#50566: [core-updates-frozen] Grub fails to decrypt LUKS partition (cryptomount not found)
Date: Wed, 15 Sep 2021 00:57:54 +0200 [thread overview]
Message-ID: <2462d810-f92a-1a00-c6d6-d44597f51d27@web.de> (raw)
In-Reply-To: <aa357aca-baea-e28f-2dd4-e8516e5c1796@web.de>
I went ahead and did a trick Tobias (nckx) told me in IRC. I booted a
Guix installer from an USB stick and hit 'c' (command line) in its GRUB
menu. Then I gave in the following commands:
```
insmod luks
cryptomount (hd1,gpt2)
Enter passphrase ...:
set root=(crypto0)
configfile /boot/grub/grub.cfg
```
I can then choose between the Guix system generations: 1x
core-updates-frozen and 3x master. The latter did worked before my
reconfigure on c-u-f.
But non of them really worked. I have to enter the LUKS password a
second time and then shepherd fails to start all the services. The cpu
fan blows a bit loud:
```
failed to start service 'file-systems'
failed to start service 'file-system-/boot/efi'
failed to start service 'user-processes'
[...]
```
An Alt+SysReq+E (SIGTERM all apart INIT) gives:
```
shepherd[1]: Service udev has been disabled.
shepherd[1]: Respawning libvirtd.
shepherd[1]: Service libvirtd has been started.
```
And some audit log message. Can audit break the boot?
Has anyone an idea how to find out why those services start to fail? How
to obtain logs?
~Jonathan
next prev parent reply other threads:[~2021-09-14 22:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-13 11:54 bug#50566: [core-updates-frozen] Grub fails to decrypt LUKS partition (cryptomount not found) Jonathan Brielmaier
2021-09-14 22:57 ` Jonathan Brielmaier [this message]
2021-09-17 15:08 ` Jonathan Brielmaier
2021-09-18 15:48 ` Mathieu Othacehe
2021-09-19 15:02 ` Mathieu Othacehe
2021-09-19 21:58 ` Jonathan Brielmaier
2021-09-19 22:47 ` Ludovic Courtès
2021-09-20 8:04 ` Jonathan Brielmaier
2021-09-20 9:19 ` Mathieu Othacehe
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=2462d810-f92a-1a00-c6d6-d44597f51d27@web.de \
--to=jonathan.brielmaier@web.de \
--cc=50566@debbugs.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.
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).