From: david larsson <david.larsson@selfhosted.xyz>
To: 35875@debbugs.gnu.org
Subject: bug#35875: Guix won't boot after installation with fully encrypted disk
Date: Sat, 29 Oct 2022 20:28:03 +0200 [thread overview]
Message-ID: <125f409c5b5d92bed3bc2c7d270f2c9e@selfhosted.xyz> (raw)
In-Reply-To: <138779ab-830b-32a9-e64a-e1fccabf90ab@disroot.org>
Hi,
Im having this exact same issue: I can enter the password once to unlock
the disk, then after selecting the grub entry I am stuck at the Guix
grub screen.
I have used terminal based "manual" install, graphical guided install
for full disk - all on one partition - and graphical guided install with
manually created separate /boot partition.
Only non-encrypted disk works to boot install. Also, btrfs fails, ext4
works.
This is using the current 1.3 installer image.
The reason I attempted this installation is because my
full-disk-encryption installation that's a couple years old or so failed
to boot upon reboot, and I did not have any previous generation that I
could select from the grub menu that would boot either - i.e. my Guix
system broke.
I'm considering using an old 1.2 installer image, but Im not sure
whether I should just wait for a 1.4 release, or if there are other
suggestions?
And, I can't ping or ssh to the machine, after Im stuck at the Guix grub
boot screen.
If this is just me and Reg - it's weird. I mean I suppose the full disk
encryption option has been tested by someone before releasing the
installer?
What should I try next?
Best regards,
David
next prev parent reply other threads:[~2022-10-29 18:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-23 21:41 bug#35875: Guix won't boot after installation with fully encrypted disk Reg
2019-05-24 17:00 ` Ludovic Courtès
2019-05-25 8:37 ` Giovanni Biscuolo
2019-05-25 12:53 ` Reg
2019-05-29 16:24 ` Giovanni Biscuolo
2019-05-29 20:52 ` Reg
2019-05-30 12:10 ` Giovanni Biscuolo
2019-05-30 13:40 ` Reg
2019-05-31 22:01 ` Ludovic Courtès
2019-06-01 7:19 ` Reg
2020-03-28 12:42 ` pelzflorian (Florian Pelz)
2020-03-28 21:39 ` Reg
2020-03-29 11:55 ` pelzflorian (Florian Pelz)
2022-10-29 18:28 ` david larsson [this message]
2022-10-30 9:05 ` Josselin Poiret via Bug reports for GNU Guix
2022-10-30 12:27 ` david larsson
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=125f409c5b5d92bed3bc2c7d270f2c9e@selfhosted.xyz \
--to=david.larsson@selfhosted.xyz \
--cc=35875@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).