Description of problem: My laptop has 2 ssd and a raid0 array. Windows is on /sdd, with all its partitions including its own ESP. MGA5 public was installed on /sda2, with esp /sda1. I then installed Suse on the raid array, but constraining it to use /sda1 as the ESP. The grub generated by Suse correctly shows mageia on sda2 and Suse on /md126p8. and windows on sdd. Booting back into Mageia and rerunning the MCC bootloader generation produces a Mageia grub showing only itself and windows - no Suse. Here is a snippet from /root/drakx/repot.bug.xz ...... Generating grub configuration file ... Found theme: /boot/grub2/themes/maggy/theme.txt Found linux image: /boot/vmlinuz-desktop Found initrd image: /boot/initrd-desktop.img Found linux image: /boot/vmlinuz-3.19.8-desktop-3.mga5 Found initrd image: /boot/initrd-3.19.8-desktop-3.mga5.img grub2-probe: error: cannot find a GRUB drive for /dev/sde1. Check your device.map. Found Mageia 5 on /dev/sda2 Found Windows Boot Manager on /dev/sdd2@/EFI/Microsoft/Boot/bootmgfw.efi Found Mageia 5 (5) on /dev/mapper/isw_cijgfgdgbd_Volume1p8 done Now, the OS on /isw_c...d_Volume1p8 is actually Suse. There was an MGA5 instance there before, but the partition was reformatted as part of the Suse installation process. Just found and ran osprober. No sign of Suse. It is there on on md126p8 and bootable from grub2 via Uefi. Here is the output: root@linux-yim0 grub.d]# sh 30_os-prober Found Mageia 5 on /dev/sda2 Found Windows Boot Manager on /dev/sdd2@/EFI/Microsoft/Boot/bootmgfw.efi menuentry 'Windows Boot Manager (on /dev/sdd2)' --class windows --class os $menuentry_id_option 'osprober-efi-B60B-AA81' { insmod part_gpt insmod fat set root='hd3,gpt2' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd3,gpt2 --hint-efi=hd3,gpt2 --hint-baremetal=ahci3,gpt2 B60B-AA81 else search --no-floppy --fs-uuid --set=root B60B-AA81 fi chainloader /EFI/Microsoft/Boot/bootmgfw.efi Seems not to have looked in md126 partitions at all. ---------------------------------------------------------------- Installed Suse 13.2, on a root partition formatted in XFS. Suse system operated normally. Returned to Mageia5, booted fron UEFI menu, rebuilt grub through MCC. Suse was missing from grub menu. Reinstalled suse on ext4 root partition, same process as above and this time suse was an option on the Mageia grub. Concluded that os-prober could not create entry for os on XFS partition. Request enhancement to op-prober to handle XFS and other less common filesystems, possibly read from some sort of file. Attachment is an extract from syslogs showing behaviour of os-prober Reproducible: Steps to Reproduce:
Created attachment 6777 [details] syslog from os-prober Please refer to timestamp Jun 24 17:09:50 linux-yim0.gateway logger[2053
CC: (none) => vzawalin1, zen25000
Assigning to maintainer.
Component: Release (media or process) => RPM PackagesAssignee: bugsquad => zen25000Source RPM: (none) => os-prober
Sorry it's taken a while to get to this. Can you please check whether your SUSE install has the file /etc/SuSE-release
Keywords: (none) => NEEDINFO
Ignore comment #3 Looking at your syslog, I don't think that the "05efi: debug: /dev/mapper/isw_cijgfgdgbd_Volume1p8 is xfs partition: exiting" is relevant, as 05efi is only looking for Windows iiuc. I have tried to reproduce this bug in a UEFI VM and so far os-prober finds opensuse on XFS, from Mageia 5, but I have no raid set up. [baz@localhost ~]$ su Password: [root@localhost baz]# update-grub Generating grub configuration file ... Found theme: /boot/grub2/themes/maggy/theme.txt Found linux image: /boot/vmlinuz-desktop Found initrd image: /boot/initrd-desktop.img Found linux image: /boot/vmlinuz-3.19.3-desktop-1.mga5 Found initrd image: /boot/initrd-3.19.3-desktop-1.mga5.img Found openSUSE 13.2 (x86_64) on /dev/sda3 done I will attempt to replicate your installation more accurately with raid.
I can't replicate it and this is probably fixed in Cauldron as there have been many updates to os-prober since this version, so closing as wontfix for Mageia 5. If this is still an issue please re-open.
Status: NEW => RESOLVEDResolution: (none) => WONTFIX