From: "Andrew \"Truck\" Holland" <truck@trebel.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 48762@debbugs.gnu.org, Mathieu Othacehe <othacehe@gnu.org>,
"Andrew \"Truck\" Holland" <gutruck9@trebel.org>
Subject: bug#48762: Bug in guix installer (seems to be unable to create swap) - reproducable
Date: Sun, 13 Jun 2021 16:01:52 +0300 [thread overview]
Message-ID: <20210613130152.GO16306@docka.amigadns.com> (raw)
In-Reply-To: <875yyh29j3.fsf@gnu.org>
I would _asume_ it could not be "EBUSY" as I see nothing in the script that
would mount the drive... Again: this is the script, not custom. This is
100% reproducable in all my setups: just try using the defaults from the
installer, and you should hit this.
This occurs immediately after partitioning, which _does_ succeed.
- you say "some configurations" - try the DEFAULT. Let it wipe the HD,
partition, and: fail.
A guess, but ... one that makes no sense:
Surely it isn't one of those "old kernel" type problems where the new
partition scheme isn't known, and therefore, kernel can't find the partition
that the script expects? I haven't seen one of those issues for... over
15 years (:
On Sun, Jun 13, 2021 at 03:12:32PM +0200, Ludovic Courtès wrote:
> Hi,
>
> Mathieu Othacehe <othacehe@gnu.org> skribis:
>
> > The "free-parted" procedure that makes sure that all the partitions are
> > created and not in use probably fails in some configurations. Otherwise,
> > I cannot understand why the "mkswap" binary would fail.
>
> Do we know why ‘mkswap’ exited with code 1, though? EBUSY or could it
> be something else?
>
> Thanks,
> Ludo’.
>
prev parent reply other threads:[~2021-06-13 15:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-31 13:44 bug#48762: Bug in guix installer (seems to be unable to create swap) - reproducable Andrew "Truck" Holland
2021-06-01 12:46 ` Mathieu Othacehe
2021-06-13 13:12 ` Ludovic Courtès
2021-06-13 13:01 ` Andrew "Truck" Holland [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=20210613130152.GO16306@docka.amigadns.com \
--to=truck@trebel.org \
--cc=48762@debbugs.gnu.org \
--cc=gutruck9@trebel.org \
--cc=ludo@gnu.org \
--cc=othacehe@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).