Samsung 850 EVO 250 GB with Windows 10 (recently upgraded from windows 7, and then did a clean install of Windows 10)
1 TB HDD with Leap 42.1 (installed very recently, after the latest install of Windows 10)
The issue I’m having is that when I boot into GRUB it only has an option for LEAP, and does not present one for Windows 10. I’m using a ASUS Z97-A motherboard, with secure boot enabled in the bios settings as well.
I’m relatively new to Linux and would appreciate your help in resolving the issue.
Hi and welcome to the openSUSE forums
First of ensure your system is all up to date, so open up a terminal and switch to root user;
Maybe if you feel like it restart the system, then if you fire up YaST->System->Boot Loader and check the ‘Boot Code Options’ that secure boot is enabled, then on the ‘Bootloader Options’ tab ensure Probe Foreign OS is checked.
You can also do a pre check as root user from a terminal and run os-prober and you should see something like;
No volume groups found
/dev/sda1@/EFI/Microsoft/Boot/bootmgfw.efi:Windows Boot Manager:Windows:efi
If not, (still as root user) post the output from;
When checking my boot loader, I do not see an option for enabling secure boot under ‘Boot Code Options’ (note my current boot loader is set to GRUB2). Additionally under ‘Bootloader Options’ probe foreign OS is checked.
When entering ‘os-prober’ nothing is returned to the terminal.
Fatal: Couldn't open either sysfs or procfs directories for accessing EFI variables.
Try 'modprobe efivars' as root.
Then when trying ‘modprobe efivars’ nothing is returned to the terminal.
Given that Windows 10 currently holds the majority of my data, is there any way to boot into Leap 42.1 as UEFI? I noticed in the boot loader option where it says GRUB2 under ‘boot code options’ there is an option in the list for GRUB2-EFI, would that resolve the issue? If so are there any instructions on how to appropriately apply this, as to not leave the system in an unbootable state? I am a little hesitant to make the change without knowing if that’s the right direction as I feel it could make things a lot worse if it isn’t.
The problem is that you really need to have booted in UEFI mode to be able to install grub2-efi. And you need to have the EFI partition mounted as “/boot/efi”.
I’ve tried just switching. It gives an error message on incomplete boot installation. And then I had to use a UEFI boot of the rescue iso to complete the job.
Either way, you need to be able to boot the install media in UEFI mode – either for a reinstall or to switch to UEFI booting. A reinstall is probably easier. But first make sure that you are able to boot the installer in UEFI mode. The boot screen will be different (no Fn keys, for example) and that should help you recognize whether you have succeeded.
Thanks again for your help. After looking into your suggestions and doing some other research it seems to me that most solutions require me to change settings in the BIOS that cannot be easily reversed. As a result I’m just going to live with the current situation and change my boot device from the BIOS whenever I feel like switching to the other OS.
No need to change BIOS setting. Just select boot from what ever is your install device to boot as EFI. Should be an option at the BIOS splash screen maybe F12 but it is different on different hardware. Then do an update and be sure all the partitions are correct. one should be the exiting efi boot partition to be mounted as FAT at /efi/boot The boot code should be grub-efi not just grub
No You do not understand in EFI boot all OS’s must have an entry in the EFI boot partition. If an os is not represented there it will not boot. By erasing (formatting) that partition you lose ability to boot Windows… Must be fixed form the Windows side. However reinstalling or repairing Windows may erase the the openSUSE entries. At least some time it seems Windows does that. How ever it is a bit easier to repair the openSUSE boot then to repair the Windows boot.
Sorry it appears to be EFI boot partition is on a GPT partitioned disk with Windows installed on it so is likely EFI boot. You Linux is on a dos partitioned drive in an extended partition. EFI boot is normally done from GPT partitioned drives I honestly don’t know the ramification or such and odd mix of technology. In any case what you must do is to do a Windows recovery to repair to fix the fact that you effectively erased the Windows boot code in the efi boot partition by formatting. You should make no more random changes until you accomplish that.And you may not need to fix openSUSE after it all depends on how nice Windows feels.
You do not understand ALL OS in EFI boot use the same EFI boot partition by formatting that partition you erased the needed Windows boot information You must put it back via Windows, Linux can not do this only Windows can fix Windows