Bug 26763 - Install UEFI KO
Summary: Install UEFI KO
Status: RESOLVED INVALID
Alias: None
Product: Mageia
Classification: Unclassified
Component: Installer (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal critical
Target Milestone: ---
Assignee: Martin Whitaker
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-06-10 14:59 CEST by Nicolas Lécureuil
Modified: 2020-06-15 18:26 CEST (History)
0 users

See Also:
Source RPM:
CVE:
Status comment:


Attachments
draks report file (196.76 KB, application/x-xz)
2020-06-14 14:51 CEST, Nicolas Lécureuil
Details

Description Nicolas Lécureuil 2020-06-10 14:59:51 CEST
I installed mageia 8 alpha1 on a UEFI machine.

Install is OK but when rebooting i obtain the uefi shell with a message telling

error: unknown filesystem
Nicolas Lécureuil 2020-06-11 12:19:51 CEST

Assignee: bugsquad => mageia

Comment 1 Martin Whitaker 2020-06-11 12:28:04 CEST
Please attach the /root/drakx/report.bug.xz file.

Keywords: (none) => NEEDINFO

Comment 2 Nicolas Lécureuil 2020-06-14 14:51:47 CEST
Created attachment 11700 [details]
draks report file
Comment 3 Nicolas Lécureuil 2020-06-14 14:55:27 CEST
interesting, in ddebug.log i can see:


Created symlink /etc/systemd/system/multi-user.target.wants/acpid.service â /usr/lib/systemd/system/acpid.service.
* running: update-grub2  with root /mnt
* update-grub2 logs: Création du fichier de configuration GRUBâŠ
ThÚme trouvé : /boot/grub2/themes/maggy/theme.txt
Image Linux trouvée : /boot/vmlinuz-5.6.15-desktop-1.mga8
Image mémoire initiale trouvée : /boot/initrd-5.6.15-desktop-1.mga8.img
Jun 07 13:31:48 | DM multipath kernel driver not loaded
grub2-probe : erreur : impossible de trouver un périphérique GRUB pour /dev/sdb1. Vérifiez device.map..
fait

which means

grub2-probe : error: impossible to find a device GRUB for /dev/sdb1.  Please check device.map




i think there is a problem as i think /dev/sdb1 is the usb key used for the install
Comment 4 Martin Whitaker 2020-06-14 17:25:37 CEST
OK, so this was a net install, not an alpha1 install.

That error from grub2-probe is normal. It probes all the disks in the system, but doesn't have a driver for reading the iso9660 filesystem.

Have you installed a UEFI-booted system on that disk before? It has a DOS partition table, not a GPT one. Your BIOS might not support that. Try using gdisk to convert it to GPT.
Comment 5 Nicolas Lécureuil 2020-06-14 23:09:06 CEST
i had a debian UEFI installed before.

In fact didn't noticed but now i have 

debian
mageia 


in the list of UEFI.


If i reinstall using alpha1 iso it should work correctly ?
Comment 6 Martin Whitaker 2020-06-15 09:42:44 CEST
I wouldn't expect the alpha1 ISO to do any different. According to the installer log, /boot/grub2/install.sh ran without errors, and you can see it has added an entry to the UEFI NVRAM.

From the installer log, before the partitioning step the disk had the following partition table:

* fdisk before:
Disk /dev/sda: 298.9 GiB, 320072933376 bytes, 625142448 sectors
Disk model: HGST HTS725032A7
Units: sectors of 1 * 512 = 512 bytes 
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0x7c78ffc3
  
Device     Boot     Start       End   Sectors   Size Id Type
/dev/sda1  *         2048 616984575 616982528 294.2G 83 Linux
/dev/sda2       616986622 625141759   8155138   3.9G  5 Extended
/dev/sda5       616986624 625141759   8155136   3.9G 82 Linux swap / Solaris

There is no ESP there, so I don't think that can have been a UEFI installation.

You say that on boot it drops to the UEFI shell, which is why I think your BIOS can't read the ESP. If you really meant the GRUB shell, that's different.
Comment 7 Nicolas Lécureuil 2020-06-15 11:21:14 CEST
this is what i get:

error: unknown filesystem.
Entering rescue mode...
grub rescue>
Comment 8 Martin Whitaker 2020-06-15 13:49:32 CEST
OK, it's a GRUB shell. What do you get if you enter the commands

  set
  ls

at the grub rescue prompt?
Comment 9 Nicolas Lécureuil 2020-06-15 16:38:02 CEST
grub rescue> set
cmdpath=(hd0)
prefix=(hd0,msdos1)/boot/grub
root=hd0,msdos1
grub rescue> ls
(hd0)(hd0,msdos7) (hd0,msdos6)  (hd0,msdos5)  (hd0,msdos1) 
grub rescue>
Comment 10 Martin Whitaker 2020-06-15 17:05:53 CEST
Try entering the following commands:

set prefix=(hd0,msdos5)/boot/grub2
set root=(hd0,msdos5)
normal
Comment 11 Nicolas Lécureuil 2020-06-15 17:43:12 CEST
grub rescue> normal
Unknown command 'normal'.
Comment 12 Martin Whitaker 2020-06-15 17:53:10 CEST
Try inserting

  insmod normal

between the 'set root=' and 'normal'
Comment 13 Nicolas Lécureuil 2020-06-15 18:03:32 CEST
sorry :)

grub rescue> insmod normal
error: file '/i386-pc/normal.mod' not found
Comment 14 Martin Whitaker 2020-06-15 18:07:03 CEST
OK, what do

  ls (hd0,msdos5)

and

  ls (hd0,msdos5)/

show?
Comment 15 Nicolas Lécureuil 2020-06-15 18:12:27 CEST
grub rescue> ls (hd0,msdos5) 
(hd0,msdos5): Filesystem is ext2


and grub rescue> ls (hd0,msdos5)/
it show the harddrive ( ./ ../ lost+found/ boot/   etc )
Comment 16 Martin Whitaker 2020-06-15 18:15:28 CEST
I missed something:

"error: file '/i386-pc/normal.mod' not found"

If it's searching in i386-pc, that suggests you're booting in legacy mode...
Comment 17 Nicolas Lécureuil 2020-06-15 18:26:19 CEST
I just suck sometimes :(

it was both legacy and UEFI but default to legacy i think.

I rebooted, did F12 selected mageia and now i can see lightdm :(

sorry for the noise

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


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