From: "Ludovic Courtès" <ludo@gnu.org>
To: Peter <sunspark@gmail.com>
Cc: 56572@debbugs.gnu.org
Subject: bug#56572: failed install on partition, backtrace attached
Date: Fri, 15 Jul 2022 12:58:26 +0200 [thread overview]
Message-ID: <87edym8wx9.fsf@gnu.org> (raw)
In-Reply-To: <CAHaGoVNUCRzFsJagMpxJzV4t_S0S=mkDmTBhv7J8OU9jXvGRZg@mail.gmail.com> (Peter's message of "Fri, 15 Jul 2022 01:29:44 -0400")
Hi Peter,
Peter <sunspark@gmail.com> skribis:
> I did manual partitioning because I didn't want to wipe the other
> partitions out.
>
> Set / and /home partitions, formatted as EXT4.
>
> Crashes as soon as it writes the changes, displays the backtrace and
> restarts the installer.
Ouch. Could you confirm it was with the 1.3.0 installer?
It would seem that the bug comes from ‘read-partition-uuid’ returning #f
in this function:
--8<---------------cut here---------------start------------->8---
(define (user-partition->file-system user-partition)
"Convert the given USER-PARTITION record in a FILE-SYSTEM record from
(gnu system file-systems) module and return it."
(let* ((mount-point (user-partition-mount-point user-partition))
(fs-type (user-partition-fs-type user-partition))
(crypt-label (user-partition-crypt-label user-partition))
(mount-type (user-fs-type->mount-type fs-type))
(file-name (user-partition-file-name user-partition))
(upper-file-name (user-partition-upper-file-name user-partition))
;; Only compute uuid if partition is not encrypted.
(uuid (or crypt-label
(uuid->string (read-partition-uuid file-name) fs-type))))
`(file-system
(mount-point ,mount-point)
(device ,@(if crypt-label
`(,upper-file-name)
`((uuid ,uuid (quote ,fs-type)))))
(type ,mount-type)
,@(if crypt-label
'((dependencies mapped-devices))
'()))))
--8<---------------cut here---------------end--------------->8---
This can happen if a partition you chose to create actually contains
random data or a file system not supported by (gnu build file-systems);
this, in turn, can happen if you chose not to format partitions during
the installation process.
Could it be what happened in your case?
Ludo’.
next prev parent reply other threads:[~2022-07-15 10:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-15 5:29 bug#56572: failed install on partition, backtrace attached Peter
2022-07-15 10:58 ` Ludovic Courtès [this message]
2022-07-15 14:15 ` sunspark
2022-07-15 19:55 ` Peter
2022-07-18 9:10 ` Ludovic Courtès
2022-07-21 16:18 ` Josselin Poiret via Bug reports for GNU Guix
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=87edym8wx9.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=56572@debbugs.gnu.org \
--cc=sunspark@gmail.com \
/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).