Since Yesterday all of a sudden Tumbleweed does not boot any more as it should but windows 10 starts, when I turn on my pc.
Dual boot setup were were I should get a grub screen were I can pick either Tumbleweed of Windows 10.
On the bright site typing this from Tumbleweed, so my Linux install is not really damaged, but I need to use the boot menu from my mobo to get Suse to boot.
After I have selected the Tumbleweed disk, ( F11 to get the boot menu from the mobo ) , Grub comes up and all looks as it should be.
So for some reason my pc seems to have forgotten it should start from the Linux disk.
I suspect windows to have done this, maybe an update, but more important how to fix this?
Both os have their own hard disk.
I am not impressed with uefi, or should I say windows 10. I have disabled fast boot on windows, but I often, not always, get when I do start windows 10, that it starts to fix the file system.
This only takes a few seconds, but I do suspect it to be related.
Feels like I should post this on a windows forum, because I am 99% sure windows is the problem here, but I doubt they can help me.
Knurpht, I don’t think this is an issue with GRUB and os-prober wouldn’t help since OP’s UEFI skips right to W10. I had this problem after some major W10 updates in my dualboot systems.
There was probably some sort of BIOS/UEFI update on the OP’s computer.
Gps2010, you need to set priority to “Opensuse secureboot” EFI. How to do this depends entirely on your machine and process is different from machine to machine. Set the boot order to boot from your OpenSUSE drive using OpenSUSE EFI file. This will open GRUB which will allow you to choose between W10/TW.
As for your W10 fixing its system. This I cannot tell you what’s wrong but it doesn’t sound normal. I have multiple dualboot systems with W10 and OpenSUSE LEAP/TW and “fixing system” only happens when something is wrong with my HDD/SSD (If you share a partition between the OSes, depending how you have it set up, it may cause issues regularly).
With UEFI, any update to booting might change the boot order. An update on Tumbleweed will put that first. An update (to booting) on Windows will put that first. It’s a minor annoyance that you can learn to live with.
On my system, if I hit F12 while booting, I get a BIOS boot menu where I can choose between Windows and openSUSE. There’s probably a key for that on your system. Use it as a fallback when booting goes wrong.
Windows uses fast-boot, so it does not properly shutdown the file system. And even if you turn off fast-boot, it does this. I eventually disable hibernation in Windows to prevent this. But there’s another simple solution. When rebooting from Windows to openSUSE, hold down the SHIFT key while clicking “restart”. That way, Windows will do a full shutdown. On the next screen, select “Boot from a device”, and it should give you a choice to boot openSUSE. That’s another workaround when the boot order goes wrong.
When back in openSUSE, as root, run:
That will tell you the boot order. You can then change the boot order with something like:
efibootmgr -o 0001,0003,0000
to set the order to what you want. The boot numbers to use are from what you see with the first “efibootmgr” command.
Here’s another possibility. I have had this happen.
You have openSUSE as first in booting. You boot to Windows using the openSUSE boot menu.
Your BIOS notices that you never use the Windows boot entry. So it decides to do some cleaning up of NVRAM, and deletes that entry.
No problem. You can still boot Windows with the openSUSE boot menu. But this time, Windows notices that there isn’t an NVRAM entry to boot Windows. So it puts one back. And that make Windows the first in boot order.
You no doubt had a Windows update that affected the bootloader, i.e. the EFI settings. Running the YaST bootloader module does what nrickert describes for you, by the choice of the default startup option.
I did not say that having more than one EFI system partition (ESP) “is not right”!
The specification https://uefi.org/specifications definitely allows for more than one ESP in a system. However if you do not yet feel familiar with UEFI having more than one ESP will make life not easier for you.
So far, I think ease really depends on machines. For my Dell Alienware 15 for example, the BIOS/UEFI allows me to browse and search for and specify /.efi for each boot option. This is the same for my custom work desktop.
At the same time my Lenovo T420, T430, W530, T480, Panasonic CF-19 do not let me specify which efi partition and efi file, but UEFI/BIOS seem to be able to automatically search and find them all of the time even if there are more than single /EFI partition on each drive (All of my setup other than Legacy Lenovo W530 have one EFI partition for Windows 10 and one for OpenSUSE).
Personally, I see an advantage of having two /EFI partitions because for my backups, I typically clone a whole setup and the backups are bootable if need be.
I might have to do more reading and look in he UEFI. I remember at one time, in the UEFI not seeing an option to add a second os.
This was most likely a user error on my site though, because I know this is possible with my mother board.
The only minor issue I have is after selecting WIN10 in the GRUB screen, windows 10 goes to check the file system, but not always.
This takes only a few seconds, so we can conclude it does not check the entire disk.
I will have to do some testing if holding the shift key on shutdown of Windows 10, will fix this.