From: Josselin Poiret via Bug reports for GNU Guix <bug-guix@gnu.org>
To: Bruno Haible <bruno@clisp.org>, 65412@debbugs.gnu.org
Subject: bug#65412: Guix installer failed to install
Date: Tue, 22 Aug 2023 11:08:01 +0200 [thread overview]
Message-ID: <87y1i3v40e.fsf@jpoiret.xyz> (raw)
In-Reply-To: <3890128.2RXx4rv9zb@nimes>
[-- Attachment #1: Type: text/plain, Size: 1207 bytes --]
Hi Bruno,
Bruno Haible <bruno@clisp.org> writes:
>
> The problem is not so much that it failed, but that the warning
> message does not sufficiently describe the cause:
> * I understand the figure of 6 GB: that's the expected size for
> a GUI environment with MATE.
> * But I don't understand the figure of 1 GB.
> - Is /mnt a RAM disk (the VM has 2 GB of RAM), or did the installer fail
> to mount /mnt?
> - Or is /mnt overloaded to the swap partition (which has 1 GB in my config)?
> - Or is /mnt the 10 GB partition of my disk, and the downloaded binaries
> already filled 9 GB of it?
> If I knew this, I would know what to do to fix the problem: Add more RAM?
> Partition differently? Use a larger main partition?
My guess is that, because a Guix system init installs some stuff in
steps, one of these steps ended up requiring too much space, that would
be bullet point 3 above. You can check that it's not 1 or 2 by, once
you reproduce this bug, going to tty3 (using ctrl+alt+f3), and typing
`lsblk` to check which partition is mounted where. In the meantime, I
would probably recommend adding some space for /.
Best,
--
Josselin Poiret
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 682 bytes --]
next prev parent reply other threads:[~2023-08-22 9:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-20 16:02 bug#65412: Guix installer failed to install Bruno Haible
2023-08-22 9:08 ` Josselin Poiret via Bug reports for GNU Guix [this message]
2023-09-02 11:55 ` Bruno Haible
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=87y1i3v40e.fsf@jpoiret.xyz \
--to=bug-guix@gnu.org \
--cc=65412@debbugs.gnu.org \
--cc=bruno@clisp.org \
--cc=dev@jpoiret.xyz \
/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).