From: "So'n Typ im Internet" <sontypiminternet@gmail.com>
To: Mathieu Othacehe <othacehe@gnu.org>
Cc: 59823@debbugs.gnu.org
Subject: bug#59823: an installer dump was sent
Date: Wed, 7 Dec 2022 10:48:04 +0100 [thread overview]
Message-ID: <CAMLcmSzLeQH_h0dppwrYVzo0Dp1yv+-r-sogmLsiYoCSEsLo9Q@mail.gmail.com> (raw)
In-Reply-To: <87lenj8srr.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1505 bytes --]
Hallo Mathieu,
Thank you so much for your effort.
I already managed the installation by burning the iso directly to my usb
drive and not via Ventoy.
Everything works fine.
I should have try this in the first place. Sometimes the ways of the lord
gnu are inscrutable.
Big thanks again and a warm regards to you and your team.
Typ.
Mathieu Othacehe <othacehe@gnu.org> schrieb am Mi. 7. Dez. 2022 um 10:31:
>
> Hello,
>
> So I had a closer look and we do have this strange kernel warning:
>
> --8<---------------cut here---------------start------------->8---
> Dec 4 10:49:05 localhost vmunix: [ 1351.610773] device-mapper: ioctl:
> remove_all left 1 open device(s)
> --8<---------------cut here---------------end--------------->8---
>
> I also noticed that we do not have the following trace:
>
> --8<---------------cut here---------------start------------->8---
> /dev/sdX is not eligible because it is the installation device.
> --8<---------------cut here---------------end--------------->8---
>
> which indicates that the "eligible-devices" procedure failed to identify
> the installation device. So /dev/sdd could be the installation device
> and the "with-delay-device-in-use?" always reports true because it is in
> fact always in use.
>
> My proposed patch probably won't help and the question is, why is the
> installation device not detected?
>
> Would it be possible for you to try the installation with an
> instrumented installer that I would provide you with?
>
> Thanks,
>
> Mathieu
>
[-- Attachment #2: Type: text/html, Size: 2217 bytes --]
next prev parent reply other threads:[~2022-12-07 14:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-04 9:57 bug#59823: an installer dump was sent So'n Typ im Internet
2022-12-05 8:18 ` Mathieu Othacehe
2022-12-05 8:33 ` So'n Typ im Internet
2022-12-07 9:31 ` Mathieu Othacehe
2022-12-07 9:48 ` So'n Typ im Internet [this message]
2022-12-07 15:36 ` Mathieu Othacehe
2022-12-08 12:28 ` bug#59823: [1.4.0rc1] Installer fails to identify installation device on Ventoy-made images Mathieu Othacehe
2022-12-09 22:16 ` Ludovic Courtès
2022-12-10 10:26 ` Mathieu Othacehe
2022-12-10 11:01 ` Ludovic Courtès
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAMLcmSzLeQH_h0dppwrYVzo0Dp1yv+-r-sogmLsiYoCSEsLo9Q@mail.gmail.com \
--to=sontypiminternet@gmail.com \
--cc=59823@debbugs.gnu.org \
--cc=othacehe@gnu.org \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.