unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 59784@debbugs.gnu.org
Subject: bug#59784: [version 1.4.0rc1] Retrying a failed install fails
Date: Sat, 10 Dec 2022 09:39:54 +0100	[thread overview]
Message-ID: <87y1rf649x.fsf@pelzflorian.de> (raw)
In-Reply-To: <87mt7wap6v.fsf@gnu.org> ("Ludovic Courtès"'s message of "Fri, 09 Dec 2022 10:42:16 +0100")

Ludovic Courtès <ludo@gnu.org> writes:
> I tried to reproduce it:
>
>   0. I chose a basic installation to a fully-encrypted disk with a
>      single partition.
>
>   1. I hit Ctrl-C while ‘guix system init’ was downloading substitutes.
>
>   2. That led me to a confusing error screen says “Command cryptsetup
>      failed” with Ignore/Abort/Retry buttons.  This should have been
>      “Command guix system init” failed no?
>
>   3. I resumed starting with the “Configuration File” step, and there
>      ‘guix system init’ ran to completion just fine.

Yes, these were the steps, except I did not do encryption.  But I had
not told the whole story …  Sorry!

So what was missing is that the reason I pressed Ctrl-C was a rare
dropout by my Ethernet controller.  Because it is so rare and has not
happened anymore since, as a substitute, for reproducing, I did as
follows:

 0. Use Ethernet for the installation.

 1. During substitute downloading, pull the Ethernet plug.

 2. Get lucky so the installation will crash with an error and not just
    pause.  Otherwise, if no crash, repeat.

 3. Press Ctrl-C.

 4. Resume the installation from the last step.

 5. It will fail now.

I now uploaded an installer-dump-bade9971 of me reproducing the issue.

> Maybe the difference is that you hit Ctrl-C when ‘guix system init’ had
> already started copying stuff to /mnt?

No, like you, I was in the substitute downloading step.

This issue is much rarer than I thought.

Thank you for investigating.

Regards,
Florian




  parent reply	other threads:[~2022-12-10  8:41 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-02 17:52 bug#59784: [version 1.4.0rc1] Retrying a failed install fails pelzflorian (Florian Pelz)
2022-12-09  9:42 ` Ludovic Courtès
2022-12-09 11:11   ` Ludovic Courtès
2022-12-10  8:39   ` pelzflorian (Florian Pelz) [this message]
2022-12-13  9:40     ` Ludovic Courtès
2022-12-13  9:48       ` Ludovic Courtès
2022-12-13 22:22         ` pelzflorian (Florian Pelz)
2022-12-13 23:16           ` Ludovic Courtès
2022-12-14 13:36             ` pelzflorian (Florian Pelz)
2022-12-14 21:47               ` pelzflorian (Florian Pelz)
2022-12-14 23:50                 ` Ludovic Courtès
2022-12-15 17:46                   ` pelzflorian (Florian Pelz)
2022-12-15 20:44                     ` pelzflorian (Florian Pelz)
2022-12-16 16:57                       ` Ludovic Courtès
2022-12-16 20:28                         ` pelzflorian (Florian Pelz)
2022-12-17 11:01                           ` Ludovic Courtès
2022-12-17 19:36                             ` pelzflorian (Florian Pelz)
2022-12-17 16:15                         ` Ludovic Courtès
2022-12-17 19:27                           ` pelzflorian (Florian Pelz)
2022-12-17 21:30                             ` Ludovic Courtès
2022-12-18  0:23                               ` Ludovic Courtès
2022-12-16 13:55                 ` Maxime Devos
2022-12-16 20:17                   ` pelzflorian (Florian Pelz)
2022-12-18 16:41                 ` pelzflorian (Florian Pelz)
2022-12-12 12:07 ` pelzflorian (Florian Pelz)

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=87y1rf649x.fsf@pelzflorian.de \
    --to=pelzflorian@pelzflorian.de \
    --cc=59784@debbugs.gnu.org \
    --cc=ludo@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).