| Summary: | rescue mode seems broken | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Pascal Terjan <pterjan> |
| Component: | Installer | Assignee: | Mageia tools maintainers <mageiatools> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | thierry.vignaud |
| Version: | Cauldron | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | drakx-installer-rescue | CVE: | |
| Status comment: | |||
|
Description
Pascal Terjan
2020-06-12 21:15:08 CEST
Thanks for reporting this, but can you please give the background: the Classic ISO, 64-bit, Mageia 8 Alpha, from USB - for example; all guessed. CC:
(none) =>
lewyssmith The cauldron netinstall iso x86_64, as a cdrom in kvm.
Pascal Terjan
2020-06-12 22:07:53 CEST
Source RPM:
(none) =>
drakx-installer-stage2 I confirmed the problem is with the stage 2 by manually selecting mirror after booting on the cauldron image and pointing to http://ftp.free.fr/mirrors/mageia.org/distrib/7, it works well. Thank you for the extra information, which should help looking at this. Assigning to the 'tools' team. CC:
lewyssmith =>
(none)
Thierry Vignaud
2020-06-13 21:29:10 CEST
CC:
(none) =>
thierry.vignaud This looks to me more like the big systemd update broke rescue when it got rebuilt… One thing I noticed is that mageia-rescue starts with: systemctl start systemd-udevd udevadm trigger --type=subsystems --action=add udevadm trigger --type=devices --action=add While I would expect systemd-udevd to already be running from the initrd. I don't know if it could cause a problem but at least it doesn't seem useful anymore I was wondering if gcc 10 might miscompile rescue bits in mdk-stage1 Launching rescue-gui works fine on my machine so I think the problem is in the service (mageia-rescue) but not sure where it gets stuck Fixed Resolution:
(none) =>
FIXED A late addendum (been sitting around), for the record, even though the bug is fixed. I tried this with the M8 alpha 1 Classic ISO, and the bug was true. I got the output shown in comment 0 on the Ctl/Alt/F1 console; and on the Ctl/Alt/F3 one: * third party: no modules found * killed shell * stage 1: disconnecting life support system |