Description of problem: Download boot.iso image and try to get a rescue, it's not possible anymore Version-Release number of selected component (if applicable): Duno How reproducible: Always Steps to Reproduce: 1. Download install/images/boot.iso 2. Try type rescue at prompt 3. You are sent in installer (instead of rescue shell in mageia5 iso)
When you're in stage2, you should be able to switch to tty2 and fetch /tmp/stage1.log /tmp/ddebug.log Can you fetch both of them when you've reached stage2, copy them to a USB-stick and attach them here? See also https://wiki.mageia.org/en/Triage_guide#Traditional_installer Btw, what was the timestamp of the boot.iso you used?
Keywords: (none) => NEEDINFOCC: (none) => ennael1, marja11, thierry.vignaud, tmb
Btw, IIRC, the network install isos have a "Rescue" option in the bootloader screen. Why don't you use that?
I can confirm similar behavior. Mageia-Cauldron-netinstall-nonfree-x86_64.iso 6/7/16, 8:16:00PM MBR boots in text mode. Enter rescue at prompt. After a lengthy time stage1 passes off to stage2 mdkinst.sqfs NOT rescue. EFI boots also in text mode but does present Install and Rescue options. Selecting Rescue eventually stage1 passes to stage2 rescue.sqfs EFI rescue works MBR rescue does not work. If users system can boot EFI, rescue from it will work even if the install had been done in MBR mode.
CC: (none) => cae
(In reply to Charles Edwards from comment #3) > I can confirm similar behavior. > > Mageia-Cauldron-netinstall-nonfree-x86_64.iso 6/7/16, 8:16:00PM > > MBR boots in text mode. > Enter rescue at prompt. > After a lengthy time stage1 passes off to stage2 mdkinst.sqfs NOT rescue. > > EFI boots also in text mode but does present Install and Rescue options. > Selecting Rescue eventually stage1 passes to stage2 rescue.sqfs > > EFI rescue works > MBR rescue does not work. > > If users system can boot EFI, rescue from it will work even if the install > had been > done in MBR mode. Thanks :-) We still need /tmp/stage1.log from when it fails (I asked for /tmp/ddebug.log because it mentions DrakX version, but that's useless because rescue.sqfs is created separately from mdkinst.sqfs)
Also confirmed, "rescue" in boot.iso launches the installer.
Created attachment 7966 [details] report.log for Stage1 This is the bug log made immediatly after stage1 pass to stage2. It includes stage1 log.
There's no mention of rescue in /proc/cmdline...
This still occurs with Jun 11 iso. Type rescue at prompt. It then takes some time for stage1 to actually launch. At time of launch TTY shows: Mdk-stage1, version 6 built Jun 11 2016 09:22:47 Boot entry used is: initrd=x86x-64/all.rdz noisumd vga=788 splash guiet
It also will not launch "text" for MBR installs I thinking now that it is only allowing "linux" boots and is either disregarding or not "receiving" any other input entry.
Maybe syslinux/isolinux still has micompilation with gcc5? Maybe fix for bug #17771 was incomplete?
Depends on: (none) => 17771Assignee: bugsquad => tmbSummary: Unable to get rescue shell from boot.iso => Unable to get rescue shell from boot.iso (parameters are ignored by isolinux)Source RPM: (none) => syslinux
Yeah, I just spotted another gcc5 fix in upstream git... will test it and push if it works
Fixed in syslinux-6.03-6.mga6 and drakx-installer-images-2.35-13.mga6 and drakx-installer-images-2.35-14.mga6.nonfree
Status: NEW => RESOLVEDResolution: (none) => FIXED