From: bdju via Bug reports for GNU Guix <bug-guix@gnu.org>
To: bdju <bdju@tilde.team>, 53541@debbugs.gnu.org
Subject: bug#53541: backtrace during fresh Guix System install during formatting
Date: Tue, 25 Jan 2022 22:08:07 -0600 [thread overview]
Message-ID: <4791697A-84BE-4E11-AFED-2D219DC5BB32@tilde.team> (raw)
In-Reply-To: <CHFAN1BVWNBC.18LG1NI62TCZD@masaki>
[-- Attachment #1.1: Type: text/plain, Size: 991 bytes --]
First drive was using Ventoy. Tried a regular dd'd drive in case that worked better. Got past formatting. Pressed edit on the system config preview screen and got a new/different backtrace. Picture attached.
Sorry if this top-posts after bottom-posting, have to send the pics from my phone.
On January 25, 2022 9:42:35 PM CST, bdju <bdju@tilde.team> wrote:
>On Tue Jan 25, 2022 at 9:21 PM CST, bdju via Bug reports for GNU Guix wrote:
>> Using a "latest" installer image from the last day or two
>> Picture of error taken with my phone attached (eh, what can ya do?)
>>
>> >Device /dev/sdc is still in use.
>>
>> This sticks out and appears in a couple spots.
>if I don't view the details of /boot it tells me it can't read
>/dev/sda1 and to format it, then if I select it, it
>becomes ext4 by default and format is set to no
>
>Should the boot partition be fat32, ext4, or could it even be btrfs? I'm
>doing an encrypted install and I want btrfs for the root partition.
[-- Attachment #1.2: Type: text/html, Size: 1521 bytes --]
[-- Attachment #2: IMG_20220125_220553.jpg --]
[-- Type: image/jpeg, Size: 5769879 bytes --]
next prev parent reply other threads:[~2022-01-26 5:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-26 3:21 bug#53541: backtrace during fresh Guix System install after during formatting bdju via Bug reports for GNU Guix
2022-01-26 3:42 ` bug#53541: backtrace during fresh Guix System install " bdju via Bug reports for GNU Guix
2022-01-26 4:08 ` bdju via Bug reports for GNU Guix [this message]
2022-01-26 4:14 ` bdju via Bug reports for GNU Guix
2022-02-03 18:34 ` bug#53541: backtrace during fresh Guix System install after " Leo Famulari
2022-02-04 3:34 ` bdju via Bug reports for GNU Guix
2022-02-04 4:15 ` Leo Famulari
[not found] ` <877d0uebt9.fsf_-_@gnu.org>
2022-10-22 17:00 ` bug#53541: [installer] " Mathieu Othacehe
2022-10-22 20:34 ` Mathieu Othacehe
2022-10-31 8:35 ` Mathieu Othacehe
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=4791697A-84BE-4E11-AFED-2D219DC5BB32@tilde.team \
--to=bug-guix@gnu.org \
--cc=53541@debbugs.gnu.org \
--cc=bdju@tilde.team \
/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).