[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#987377: rescue-mode: when in graphical mode, locks up one prompt before the shell



Salut Étienne,

Étienne Mollier <etienne.mollier@mailoo.org> (2021-04-25):
> I did further testing, so tried to wrap up my findings in a
> hopefully nice Karnaugh table below (dreading mta rewrap at
> this instant):
> 
> 	Layout	Plain	Raid	LVM	LVM+Crypto
> Locale	Device
> en_US	Sata	blank	blank	ok	ok
> en_US	NVMe	ok	blank	ok	ok
> fr_FR	Sata	ok	ok	 extrapolating things are ok
> fr_FR	NVMe	ok	ok	 here, worth a double check?
> 
> Values:
>   - "blank" is for when the screen hangs on the intro window
>     before the shell;
>   - "ok" when I can reach the prompt.
> 
> Fields:
>   - "Layout" is the partitioning scheme chosen when installing
>     the rescued system:
>       - "Plain" for the simplest automatic partition scheme;
>       - "Raid" for a simple automatic partition scheme where the
>         root partition is on a single member Raid 0 array;
>       - "LVM" for the automatic partition scheme;
>       - "LVM+Crypto" for the configuration involving crypto;
>   - "Locale" depends on the language selected when starting
>     rescue-mode: en_US for the default, or fr_FR;
>   - "Device" is the interconnection to the physical drive:
>     Sata for the Thinkpad W500 and virtual machines, or NVMe for
>     the Zbook15 G6
> 
> Each time I selected automatic assembly of the Raid array, and
> tried to chroot inside a /dev/md/0.  I couldn't check Bios mode
> with NVMes (Zbook15 G6), and didn't check EFI mode with the Sata
> physical machine (Thinkpad W500); but on virtual machine,
> neither Bios nor EFI did any difference to the testing results.
> All tests are carried on with a root partition in Ext4, no other
> format tested yet.

Your tests are much appreciated.

> For short, the know problematic situation is when rescuing soft
> Raid, or plain partitions on Sata drives, but only when one
> speaks english.

This summary is absolutely EPIC!


Are you happy to trust me with a netboot/gtk/mini.iso build that you
would deploy on some USB device (like you would with a Netinst ISO,
except it'll need network access to download all d-i components that
aren't in the initramfs), to see if the problem goes away entirely for
you?

If so, I'd be happy if you could just verify at least one “known-bad”
case with the official image first:
  http://deb.debian.org/debian/dists/bullseye/main/installer-amd64/20210415/images/netboot/gtk/mini.iso

so that we are sure the issue is produced this way… in which case we'll
be able to test a modified image to see if it helps. :)


Cheers,
-- 
Cyril Brulebois (kibi@debian.org)            <https://debamax.com/>
D-I release manager -- Release team member -- Freelance Consultant

Attachment: signature.asc
Description: PGP signature


Reply to: