GNU bug report logs -
#48762
Bug in guix installer (seems to be unable to create swap) - reproducable
Previous Next
To reply to this bug, email your comments to 48762 AT debbugs.gnu.org.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-guix <at> gnu.org
:
bug#48762
; Package
guix
.
(Mon, 31 May 2021 15:07:01 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
"Andrew \"Truck\" Holland" <gutruck9 <at> trebel.org>
:
New bug report received and forwarded. Copy sent to
bug-guix <at> gnu.org
.
(Mon, 31 May 2021 15:07:01 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
I have attempted to install 1.3.0 from the iso, but the "guided"
install encounters an error after partitioning; which if I read
correctly, indicates swap cannot be created.
This happens when I use _any_ partitioning scheme, manual or
automatic.
The command 'mkswap -f /dev/sda3' executes correctly from the shell
session on tty3 from the installer.
Sadly, this is also fatal and the installation cannot continue, so
I'm a bit surprized no one has reported this - as I can recreate
this situation reliably every time I attempt it. (Maybe I just am
blind and cannot find the bug report at the guix bug tracker, if
so, my apologies for the duplicate.)
Error file attached.
---
[guix_last-installer-error (text/plain, attachment)]
Information forwarded
to
bug-guix <at> gnu.org
:
bug#48762
; Package
guix
.
(Tue, 01 Jun 2021 12:47:02 GMT)
Full text and
rfc822 format available.
Message #8 received at 48762 <at> debbugs.gnu.org (full text, mbox):
Hello Andrew,
> This happens when I use _any_ partitioning scheme, manual or
> automatic.
Thanks for the complete bug report. I think that this bug falls into the
same category as https://issues.guix.gnu.org/47996,
https://issues.guix.gnu.org/47567, https://issues.guix.gnu.org/44872 and
probably some others.
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.
We may need to come up with a new procedure that provides stronger
guarantees.
Thanks,
Mathieu
Information forwarded
to
bug-guix <at> gnu.org
:
bug#48762
; Package
guix
.
(Sun, 13 Jun 2021 13:13:01 GMT)
Full text and
rfc822 format available.
Message #11 received at 48762 <at> debbugs.gnu.org (full text, mbox):
Hi,
Mathieu Othacehe <othacehe <at> 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’.
Information forwarded
to
bug-guix <at> gnu.org
:
bug#48762
; Package
guix
.
(Sun, 13 Jun 2021 15:20:02 GMT)
Full text and
rfc822 format available.
Message #14 received at 48762 <at> debbugs.gnu.org (full text, mbox):
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 <at> 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’.
>
This bug report was last modified 4 years and 7 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.