From: Julien Lepiller <julien@lepiller.eu>
To: Mathieu <matf@disr.it>, 52767@debbugs.gnu.org
Subject: bug#52767: Unexpected problem with Guix System installer
Date: Fri, 24 Dec 2021 06:15:47 -0500 [thread overview]
Message-ID: <7256B498-306F-4476-890C-738B3A8B2888@lepiller.eu> (raw)
In-Reply-To: <nmail.3.39.61c5268f.180115be.4062@debian-sid>
[-- Attachment #1: Type: text/plain, Size: 1067 bytes --]
From the backtrace I can't tell you more than this. The installer tried to run "mkfs.btrfs -f /dev/napper/crypt" but the command ended with status 1 (error). Unfortunately guix didn't capture the error. Next time you try, could you run the failid command (you'll find the exact one at the bottom) from another tty and report any error message?
Le 23 décembre 2021 20:46:55 GMT-05:00, Mathieu <matf@disr.it> a écrit :
>Hey,
>
>Trying to install Guix on a 32GB thum drive, I get the attached backtrace.
>
>The partition table is gpt with 500MB for ESP, 20GB for /, 2GB for swap and remaining space for /home. I have tried btrfs and ext4 for / and /home but got backtraces related to either mkfs.btrfs or mkfs.ext4 in both cases. I also have tried encryption or no encryption, but still got backtraces. The partitions are created to the drive because I can see they are still there when I restart the installer.
>
>This is not the drive that was used to boot the Guix installer in the first place.
>
>Thanks, hope someone can understand what the issue is.
[-- Attachment #2: Type: text/html, Size: 1333 bytes --]
next prev parent reply other threads:[~2021-12-24 11:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <nmail.3.39.61c52656.4f4ef005.4062@debian-sid>
2021-12-24 1:46 ` bug#52767: Unexpected problem with Guix System installer Mathieu
2021-12-24 11:15 ` Julien Lepiller [this message]
2022-11-12 16:35 ` Mathieu Othacehe
2022-11-12 22:51 ` Mathieu
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=7256B498-306F-4476-890C-738B3A8B2888@lepiller.eu \
--to=julien@lepiller.eu \
--cc=52767@debbugs.gnu.org \
--cc=matf@disr.it \
/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).