Bug 18884 - 6_s1: installer rescue fail "/usr/lib/grub/x86_64-efi/modinfo.sh doesn't exist"
Summary: 6_s1: installer rescue fail "/usr/lib/grub/x86_64-efi/modinfo.sh doesn't exist"
Status: RESOLVED INVALID
Alias: None
Product: Mageia
Classification: Unclassified
Component: Installer (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal major
Target Milestone: ---
Assignee: Thierry Vignaud
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-07-06 23:54 CEST by Morgan Leijström
Modified: 2016-07-07 18:14 CEST (History)
1 user (show)

See Also:
Source RPM: drakx-installer-rescue
CVE:
Status comment:


Attachments

Description Morgan Leijström 2016-07-06 23:54:14 CEST
Description of problem:
Fresh installed but unbootable system [1] failed with some message that  partition could not be found,
so I booted the installer again (on USB stick) and chose rescue.

Here are the last few lines
(manually typed down from a bad focused phone photo, so may not be precise)

-----------------8<----------------------
running: sh /boot/grub2/install.sh with root /mnt
grub2-install failed:
()
Error: (grub2-install: error: /usr/lib/grub/x86_64-efi/modinfo.sh doesn't exist. Please specify --target or --directory.
>
grub2-install failed: grub2-install: error: /usr/lib/grub/x86_64-efi/modinfo.sh doesn't exist. Please specify --target or --directory.
(press Enter to return to Rescue menu)_
----------------->8----------------------
(yes error is displayed double)


==========================================================================
[1] how the broken system got installed:
64 bit sta1 DVD iso put by dd on a USB stick, booted in non uefi mode
partitionned manually;
first a ext 4 /boot.
then three partiitons used by a LVM
in that lvm: swap, /, /home
When there pressing next it refused and said something like it need /boot to be bootable.  Have never seen that before.  Tried by formattign /boot but same result.  It say in the desciption section below the partiiton graphics that the partiton is bootable.  Just for trying something i pressed teh button to partition automatically and then it added a very small partition in the LVM, but did not assign a mount point for it.  Weird.  But nor it could proceed and everything looked like it went OK, until reboot.
There it said it could not find a UUID.  I checked and there are no such partition ID in the system, that it was looking for...

Stupidly i did not retrieve the install log, sorry.

As i had to get it going quickly (not to make my son disappointed ;) ) , i reinstalled and this time let it partition automatically ( /, swap, /home) and that way it can boot and run OK.

So as a side note there is some problem when installing when LVM is used, and all partitions are defined using the mga6 installer.  A contributing cause may be that on sdb there is SteamOS installed (separately, and all sda is for mageia).

Sidenote: Mageia installer configured grub2 properly to be able to boot Steamos too :)
Comment 1 Morgan Leijström 2016-07-06 23:58:48 CEST
I see thierry amd thomas b have been on it lately

CC: (none) => tmb
Assignee: bugsquad => thierry.vignaud

Comment 2 Thomas Backlund 2016-07-07 00:03:48 CEST
You cant boot in non-efi mode to fix an efi setup as it needs efivars available ...

Hm,... I dont think I've ever tested rescue mode for efi...
Comment 3 Morgan Leijström 2016-07-07 00:10:19 CEST
The system that failed booting was installed by booting the installer NOT in uefi mode.

(in the cmputer bios boot menu I can select to boot any drive in UEFI or not)

(Sidenote: First i tried installing in UEFI mode but that failed with some message about it need bio sin /boot. As i did not understand what that meant i just rebooted and skipped using UEFI.)
Comment 4 Thomas Backlund 2016-07-07 00:16:12 CEST
ok, so for some reason we detected needing efi then ...
Comment 5 Morgan Leijström 2016-07-07 00:19:54 CEST
Hm, would this happen if i by mistake was running the *rescue* session booted in uefi mode?
Comment 6 Thierry Vignaud 2016-07-07 07:35:21 CEST
Yes
Comment 7 Morgan Leijström 2016-07-07 08:48:06 CEST
OK i could have made that mistake, and i did not try a second time.
Comment 8 Morgan Leijström 2016-07-07 08:50:59 CEST
Could there be added some information in rescue screen about making sure rescue is made in UEFI mode if system was installe din UEFI mode and vice versa

(did i get that right?)

And preferrably check and message if started in wrong mode?
Comment 9 Thierry Vignaud 2016-07-07 18:14:51 CEST
We cannot detect in the rescue env that you changed the firmware settings in such a way...

Status: NEW => RESOLVED
Resolution: (none) => INVALID


Note You need to log in before you can comment on or make changes to this bug.