I recently installed Leap 15.6, over a Leap 15.5 installation. I have a Windows 11 install on another partition and Grub2 is no longer finding this, even with probe other OSs selected.
But it doesn’t come up at boot. I wasn’t expecting it to help, but I ran update-bootloader --install after efibootmgr and indeed it made no difference!
I have two raid setups across 4 HDDs for various partions, but both the Windows and OpenSUSE OSs are installed on an SDD. cfdisk output:
Disk: /dev/nvme0n1
Size: 465.76 GiB, 500107862016 bytes, 976773168 sectors
Label: gpt, identifier: D88CAE17-7646-41E4-BF68-030C7848D415
Device Start End Sectors Size Type
>> /dev/nvme0n1p1 2048 923647 921600 450M Windows recovery environment
/dev/nvme0n1p2 923648 1128447 204800 100M Microsoft basic data
/dev/nvme0n1p3 1128448 1161215 32768 16M Microsoft reserved
/dev/nvme0n1p4 1161216 479515344 478354129 228.1G Microsoft basic data
/dev/nvme0n1p5 479516672 481279999 1763328 861M Windows recovery environment
Free space 481280000 481282047 2048 1M
/dev/nvme0n1p6 481282048 858785791 377503744 180G Linux filesystem
/dev/nvme0n1p7 858785792 925890559 67104768 32G Linux swap
/dev/nvme0n1p8 925890560 976773119 50882560 24.3G Linux filesystem
┌─────────────────────────────────────────────────────────────────────────────────┐
│ Partition name: Basic data partition │
│ Partition UUID: F1C0B712-E0CE-4278-83F6-35D2229F097B │
│ Partition type: Windows recovery environment (DE94BBA4-06D1-4D40-A16A-BFD50179D│
│ Attributes: RequiredPartition │
│ Filesystem UUID: C04A7CED4A7CE198 │
│Filesystem LABEL: Recovery │
└─────────────────────────────────────────────────────────────────────────────────┘
Hopefully there is a simple solution and I would be appreciative if someone can point me in the right direction.
Generating grub configuration file ...
Found theme: /boot/grub2/themes/openSUSE/theme.txt
Found linux image: /boot/vmlinuz-6.4.0-150600.23.38-default
Found initrd image: /boot/initrd-6.4.0-150600.23.38-default
Found linux image: /boot/vmlinuz-6.4.0-150600.23.33-default
Found initrd image: /boot/initrd-6.4.0-150600.23.33-default
Warning: os-prober will be executed to detect other bootable partitions.
Its output will be used to detect bootable binaries on them and create new boot entries.
61857.577012 | DM multipath kernel driver not loaded
Adding boot menu entry for UEFI Firmware Settings ...
done
(I then enabled multipath, but it made no difference to the output other than removing that warning)
Windows loader is on the partition with GUID bb0c9ac8-83ca-41f4-bdf6-3e106d8a0231 which is
with partition type GUID ebd0a0a2-b9e5-4433-87c0-68b6b72699c7. That is the reason it is ignored by os-prober which only looks on partitions marked as EFI System Partition (different partition type GUID).
BIOS probably does not care as long as it can read the filesystem on this partition. But I expect Windows may be confused if it ever has to change boot configuration (recovery, patch installation).
What exactly “no longer” means? When did it stop working? os-prober was not changed for ages (the code is from Windows 7 era). And most certainly there were no changes between Leap 15.5 and 15.6.
I would change partition type to the EFI System Partition (GUID c12a7328-f81f-11d2-ba4b-00a0c93ec93b) but I strongly recommend asking on Windows forums whether Windows needs some extra steps after having done it. For Linux it is transparent.
That much at least I had worked out, it was how to get grub2 to recognise it I had no idea about.
OK, thanks.
I rarely run Windows to be honest, perhaps once per month at most, so haven’t rushed to fix this. However, “no longer” means when I upgraded from Leap 15.5 to Leap 15.6, so something has changed in the install procedure as had no problems with previous versions of Leap (I’ve been running OpenSUSE on this machine since I built it quite a long time ago). What I am not sure of is whether it was the in place upgrade or the reinstall of 15.6 that nuked it, I’m guessing the latter.
Basically, I had so many issues after upgrading from 15.5 to 15.6 (in place, changing the repo versions and running DUP), that I did a clean instal (formatting most partitions, except /home and /opt). I’m guessing it was that which lost the Windows boot option.