unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Steve George <steve@futurile.net>
To: kevinbanjo <kevinbanjo@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: Validating/repairing guix system install
Date: Thu, 10 Oct 2024 09:41:12 +0100	[thread overview]
Message-ID: <h6v52pvcps6oqf3r7ozzrrtpfvtqnu4hgn33nsemz2ytncdyow@cxvjvughgraf> (raw)
In-Reply-To: <CAOHcZqP6s29TD=Ya0z3G7cdTNWKYhf8ycTgxV4bFYuM8muqb=A@mail.gmail.com>

Hi Kevin,

The existing system's configuration is in /run/current-system/configuration.scm. Might be worth inspecting this and seeing if there are obvious mistakes.

The installer places a copy of this in /etc/config.scm. This is the one that users normally start by editing. To validate that it's correct the manual suggests that you do this:

  # creates a vm start-ups script
  guix system vm /etc/config.scm

  # start the vm - login root/no-password - check through
  /gnu/store/...run-vm.sh

If you're able to start the VM correctly then you can apply that configuration.

Normally you'd go back a generation to an earlier 'known good' configuration, but it sounds like you don't have one. Maybe also check that your hard drive is OK and that the Store doesn't have problems:

  guix gc --verify=contents

Bits of the manual that may help:

https://guix.gnu.org/manual/devel/en/html_node/Getting-Started-with-the-System.html
https://guix.gnu.org/manual/devel/en/html_node/Chrooting-into-an-existing-system.html

Good luck,

Futurile / Steve

On  8 Oct, kevinbanjo wrote:
> Hi everyone
> 
> While installing the guix system I had several network errors and now I
> have some pretty serious problems, like for instance the networking process
> dying and herd status just hanging forever.
> 
> Is there a command I can run to validate the whole system and repair it if
> it finds any problems?
> 
> I've messed up the config.scm such that it doesn't want to load so if like
> to just be able to start with a solid foundation with what's supposed to be
> there without trying to reinstall (because that would probably just lead to
> more network induced errors).
> 
> Tia,
> -Kevin


      reply	other threads:[~2024-10-10  8:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-08 21:05 Validating/repairing guix system install kevinbanjo
2024-10-10  8:41 ` Steve George [this message]

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=h6v52pvcps6oqf3r7ozzrrtpfvtqnu4hgn33nsemz2ytncdyow@cxvjvughgraf \
    --to=steve@futurile.net \
    --cc=help-guix@gnu.org \
    --cc=kevinbanjo@gmail.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.
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).