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.
For short, the know problematic situation is when rescuing soft
Raid, or plain partitions on Sata drives, but only when one
speaks english.
Hth,
--
Étienne Mollier <etienne.mollier@mailoo.org>
Fingerprint: 8f91 b227 c7d6 f2b1 948c 8236 793c f67e 8f0d 11da
Sent from /dev/pts/7, please excuse my verbosity.
Attachment:
signature.asc
Description: PGP signature