From: Attila Lendvai <attila@lendvai.name>
To: Maxime Devos <maximedevos@telenet.be>
Cc: 57838@debbugs.gnu.org
Subject: bug#57838: failing to boot, probably due to guix gc
Date: Sun, 25 Sep 2022 16:31:45 +0000 [thread overview]
Message-ID: <1a4KufteLMmEAWtddioo4rdZP8FCVfMEGfnY4pOJzUetKJn3321jlRsaWfsvYGybRG-tbgmewA02PdyTMcyy18SDWFvh2KZexfuvxfFZ918=@lendvai.name> (raw)
In-Reply-To: <f3da0bc1-897a-54ae-4ceb-f4ebb08161bb@telenet.be>
> > on one of my installs i ran the following two commands as root:
> >
> > guix gc --delete-generations=60d
> > guix system delete-generations 60d
> >
> > i think i ran a reboot pretty soon after this, and the machine is failing to boot with the error "no code for module (ice-9 popen)".
>
>
> How did you reboot? Maybe whatever rebooting mechanism you use doesn't
> do 'sync' first or doesn't wait for 'sync' to complete.
i'm pretty sure i have issued a `reboot` in an ssh session.
> To test the hypothesis that there is store corruption, could you do
> "guix gc --verify=contents" (assuming there are some old system
> generations you can boot from)?
as i have explained in an earlier mail, all my old generations (3 remained after the GC) got broken, but they all got repaired by a subsequent reconfigure from a chroot. it has probably installed some files that were missing.
# guix gc --verify=contents
reading the store...
checking path existence...
checking hashes...
#
--
• attila lendvai
• PGP: 963F 5D5F 45C7 DFCD 0A39
--
“Self knowledge is always bad news.”
— John Barth (1930–)
next prev parent reply other threads:[~2022-09-25 16:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-15 19:44 bug#57838: failing to boot, probably due to guix gc Attila Lendvai
2022-09-16 19:44 ` bug#57838: (No Subject) Attila Lendvai
2022-09-19 19:31 ` Josselin Poiret via Bug reports for GNU Guix
2022-09-24 1:43 ` bug#57838: failing to boot, probably due to guix gc Maxime Devos
2022-09-25 16:31 ` Attila Lendvai [this message]
2022-12-18 13:19 ` bug#57838: Attila Lendvai
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='1a4KufteLMmEAWtddioo4rdZP8FCVfMEGfnY4pOJzUetKJn3321jlRsaWfsvYGybRG-tbgmewA02PdyTMcyy18SDWFvh2KZexfuvxfFZ918=@lendvai.name' \
--to=attila@lendvai.name \
--cc=57838@debbugs.gnu.org \
--cc=maximedevos@telenet.be \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.