From: Maxime Devos <maximedevos@telenet.be>
To: Attila Lendvai <attila@lendvai.name>, 57838@debbugs.gnu.org
Subject: bug#57838: failing to boot, probably due to guix gc
Date: Sat, 24 Sep 2022 03:43:26 +0200 [thread overview]
Message-ID: <f3da0bc1-897a-54ae-4ceb-f4ebb08161bb@telenet.be> (raw)
In-Reply-To: <pa0uwc_lSNtPiZmfkmBFuzQr106M9dN93EyM5rqWUdNBIWXIrDeZMlJSbWaUlC8KF_I9XyMpqA2SnqFRpfJ-3VWm7sMfYdEWxlL_AujxQ6Q=@lendvai.name>
[-- Attachment #1.1.1: Type: text/plain, Size: 788 bytes --]
For these kind of errors, I think I've an idea what's the cause in
<https://issues.guix.gnu.org/58035>.
On 15-09-2022 21:44, Attila Lendvai wrote:
> dear Guixers,
>
> 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.
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)?
Greetings,
Maxime.
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 929 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]
next prev parent reply other threads:[~2022-09-24 1:44 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 ` Maxime Devos [this message]
2022-09-25 16:31 ` bug#57838: failing to boot, probably due to guix gc Attila Lendvai
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
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=f3da0bc1-897a-54ae-4ceb-f4ebb08161bb@telenet.be \
--to=maximedevos@telenet.be \
--cc=57838@debbugs.gnu.org \
--cc=attila@lendvai.name \
/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).