unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
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 21:42:35 -0600	[thread overview]
Message-ID: <CHFAN1BVWNBC.18LG1NI62TCZD@masaki> (raw)
In-Reply-To: <D7C8F08A-C5C0-4719-8BB3-C17C81A6AEE7@tilde.team>

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.




  reply	other threads:[~2022-01-26  3:46 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 ` bdju via Bug reports for GNU Guix [this message]
2022-01-26  4:08   ` bug#53541: backtrace during fresh Guix System install " bdju via Bug reports for GNU Guix
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=CHFAN1BVWNBC.18LG1NI62TCZD@masaki \
    --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).