unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: "J. Sims" <jtsims@protonmail.com>
Cc: 60104@debbugs.gnu.org
Subject: bug#60104: Hiccups installing GNU Guix 1.4.0rc2 system
Date: Thu, 15 Dec 2022 23:51:28 +0100	[thread overview]
Message-ID: <87ilicl1qn.fsf@gnu.org> (raw)
In-Reply-To: <HYrGixFgcpyQyYQuRS3IY-weWbaouFJZKmx3L8BasxMSfYxrYYxXYZN33pWbnAW_5FTbe8W_XpD4QunmR-56irnpKgqZsYq1s_ZDA7bWzes=@protonmail.com> (J. Sims's message of "Thu, 15 Dec 2022 21:24:19 +0000")

Hi,

"J. Sims" <jtsims@protonmail.com> skribis:

> I managed to successfully install the GNU Guix 1.4.0rc2 system iso on
> an HP Dev One laptop (with help from USB stuff for
> networking). Everything mostly went as expected, except after the
> installation I got a screen saying crypttab couldn't find a specific
> partition.

What’s crypttab?  At which point exactly does this screen appears:
before GRUB, after GRUB, once the Linux kernel has booted?

> I assume this was something left over from a previous OS installation
> since wiping the partitions with cfdisk and then installing worked
> fine. Note that while my initial install attempts did use encryption,
> the final (successful) one did not; I don't think this has any effect
> one way or the other on the viability of installation since I ran into
> the same issue both with and without an encrypted Guix installation
> before wiping the partitions.

OK.

> Hopefully it should be simple enough to just completely rewrite the partition table during installation and sidestep this issue.

Normally the installer will rewrite the partition table, unless (I
think) you choose to keep things unchanged.

Thanks,
Ludo’.




  reply	other threads:[~2022-12-15 22:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-15 21:24 bug#60104: Hiccups installing GNU Guix 1.4.0rc2 system J. Sims via Bug reports for GNU Guix
2022-12-15 22:51 ` Ludovic Courtès [this message]
2022-12-16 19:15   ` J. Sims via Bug reports for GNU Guix
2022-12-17 12:01     ` 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=87ilicl1qn.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=60104@debbugs.gnu.org \
    --cc=jtsims@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).