| Summary: | Rescue: offer a full image | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Marc Krämer <mageia> |
| Component: | RPM Packages | Assignee: | Mageia tools maintainers <mageiatools> |
| Status: | NEW --- | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | Normal | ||
| Version: | 9 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | drakx-installer-rescue | CVE: | |
| Status comment: | |||
|
Description
Marc Krämer
2024-05-22 12:23:27 CEST
since reinstall bootloader often fails, the procedure you have to make with a normal user via telephone or a second laptop via video is more than complicated: after starting the rescue image, you continue with the following steps: - "mount partitions /mnt" - this usally fails, but inserts modules and decrypts encrypted deviced - goto console - loadkeys de - mount /dev/mapper/xxx-root /mnt - mount -B /proc /mnt/proc - mount -B /sys /sys - chroot /mnt - mount devpts /dev/pts -t devpts - mount -a - ifconfig - ifup enp... to start the network - /usr/sbin/sshd finally you may connect to the remote computer and search for the problem yourself. And keep in mind, if this does not work, the whole procedure must be done again by the user. Does not the Classic installer have a 'rescue 'option at boot? True, you would need that to hand. CC:
(none) =>
lewyssmith a 4GB installer image for a rescue system? Didn't we discuss the size of the image - this is the first thing to remove and put in an extra image for download.... OK, you were aware of that. Forwarding your request. CC:
lewyssmith =>
(none) |