From: Mathieu Othacehe <othacehe@gnu.org>
To: "bdju" <bdju@tilde.team>
Cc: 53541@debbugs.gnu.org, Leo Famulari <leo@famulari.name>
Subject: bug#53541: [installer] backtrace during fresh Guix System install after during formatting
Date: Sat, 22 Oct 2022 19:00:39 +0200 [thread overview]
Message-ID: <871qqzpzd4.fsf@gnu.org> (raw)
In-Reply-To: <877d0uebt9.fsf_-_@gnu.org> (Mathieu Othacehe's message of "Thu, 20 Oct 2022 17:48:02 +0200")
Hey,
> I was able to reproduce it on real hardware, following those
> instructions. The dump is available here if people want to join the
> party: dump.guix.gnu.org/download/installer-dump-304492ff.
So the backtrace suggests that we are trying to open /dev/nvme0n1p1 to
read its superblock:
--8<---------------cut here---------------start------------->8---
9 (open "/dev/nvme0n1p1" 524288 #<undefined>)
--8<---------------cut here---------------end--------------->8---
and that it fails because the file does not exist:
--8<---------------cut here---------------start------------->8---
1780:13 6 (_ #<&compound-exception components: (#<&external-error> #<&origin origin: "open-fdes"> #<&message message: "~A"> #<&irritants irritants: ("No such file or directory")> #<&exception-w…>)
--8<---------------cut here---------------end--------------->8---
This open call originates from check-user-partitions in (gnu installer
parted). If we arrive here, it means that the file *should* exist.
Looking at the kernel trace, the two last lines are:
--8<---------------cut here---------------start------------->8---
[ 72.271204] nvme0n1: p1 p2 p3 p4
[ 127.415648] nvme0n1: p1 p2
--8<---------------cut here---------------end--------------->8---
so the disk partition table is updated because we move from 4 to 2
partitions. Could it be possible that during a brief period of time the
/dev/nvme0n1p1 file disappears then re-appears?
I'll try to reproduce it a VM to conduct more testing.
Mathieu
next prev parent reply other threads:[~2022-10-24 2:13 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
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 ` Mathieu Othacehe [this message]
2022-10-22 20:34 ` bug#53541: [installer] " 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=871qqzpzd4.fsf@gnu.org \
--to=othacehe@gnu.org \
--cc=53541@debbugs.gnu.org \
--cc=bdju@tilde.team \
--cc=leo@famulari.name \
/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).