Boot problem tumbleweed after a windows update

This morning pc was working fine.

Which means if I turn on my pc I get a grub screen.
Then I can choose, Tumbleweed, leap or windows.

After starting windows 10 which did an update the problem started.
Windows boots, no more grub screen.

I then started tumbleweed through the mother board.
Made sure in yast probe foreign OS was checked and clicked ok.

This used to fix this problem, but not today.
I then tried to change something else in yast, but now my motherboard does not recognize the tumbleweed disk anymore as bootable.

I can only boot from my motherboard, windows or Leap, but not tumbleweed.

From leap I can acces all files from Tumbleweed.

How to fix this ?
(I am posting this from windows 10)

Your problem likely is described here.

I dont understand what to do ? That page talks about Ubuntu

But a small update I just was able to start tumbleweed by using the install usb, and choose boot from harddisk.
It then asked a few question, but tumbleweed did start.

So I went into yast but again probe foreign os did not solve it.

Because I can’t edit my previous post, I add this reply.

The only way for me to currently start Tumbleweed, is with a tumble weed install USB.

Start rescue system, then I then go to more, and then pick boot a Linux system.
Then the rescue system has a look, and asks if I want to boot Tumbleweed or Leap.

I pick tumble weed, and after two more questions, Tumbleeweed does start.

If I then restart my pc, its again windows that boots.

Although the page talks about Ubuntu, I see nothing that is Ubuntu specific so just give it a try, it is a Microsoft induced problem, that procedure deletes the offending Microsoft SBAT Policy. If it does not work, please detail what you did and where things did go wrong.

There is not that much difference between Linux distributions apart from the package too (zypper/dnf/rpm etc.) and some GUI config tools (Yast…)

I don’t know if it matches your case, but I had a problem with Dell’s BIOS update/settings reset that overwrote my MBR with Windows’ boot loader (and I don’t even have Windows installed…)

However in UEFI settings I could set up a manual boot entry, and chose to boot from /boot/efi/EFI/opensuse/grubx64.efi. Made that the top of the boot list and it worked for me.

I never saw the error that the page mentions.

I will however check the bios to see if secure boot is enabled.
I remember though, turning it off because it caused trouble with my 100% legal win10.

I just tried this:

`mokutil --sb
EFI variables are not supported on this system
`

If I understand the problem right, my opensuse tumbleweed disk is not bootable anymore.

With an usb stick inserted, the tumbleweed installation USB, I am through the rescue system able to boot Tumbleweed. (option boot a Linux system)

Typing this from Tumbleweed, but as soon as I reboot, windows boots

 sudo mokutil --set-sbat-policy delete
[sudo] wachtwoord voor root: 
EFI variables are not supported on this system

If not sure how to use BIOS itself to repair, boot using USB into whichever installed openSUSE system you wish to be in control of boot, the take a look at output from sudo efibootmgr just FYI for reference. Is it obvious there is a Windows entry with priority over as many openSUSE’s as you have? Then use YaST Bootloader to update bootloader, making sure the update NVRAM checkbox is enabled. If it was not and you check it, then you should need do no more than save, exit YaST, and then be able to boot normally into that openSUSE installation.

After you’re successful, compare GRUB_DISTRIBUTOR= in file /etc/default/grub in each openSUSE installation. You’ll probably find they are both equal to null (blank, empty). This in turn would mean in /boot/efi/EFI/ there is only a BOOT directory and one opensuse directory, with nothing for your other openSUSE installation. This is the standard boot usurpation configuration of multiple installations for same vendor. If you change the GRUB_DISTRIBUTOR= to a unique string, such as “opensusetw” for your tW, then on next update to the TW installation’s grub setup, TW would have its own directory in /boot/efi/EFI/, and your BBS menu would have one EFI opensuse and one EFI opensusetw among the other selections.

BBS (Bios Boot Specification) hotkeys:

* Abit		F9
* Acer		F12 or ESC or F9
* ASRock	F11
* Asus		F8
* Biostar	F9
* Dell		F12
* DFI		ESC
* eCS		F12 or F10
* eMachines	F10
* EVGA		F7
* Gateway	F12 or F10
* Gigabyte	F12
* HP/Compaq	F9  or ESC or ESC,F9
* Intel		F10
* Lenovo	F12 or F8 or F10
* MSI		F11
* Shuttle	ESC or F11 or F7
* Toshiba	F12

Maybe this

sudo efibootmgr
EFI variables are not supported on this system.

I have an Asrock mobo, with F11, I am able to start from the Tumbleweed installation usb.

Then from the rescue system I am able to boot Tumbleed by choosing:
boot a Linux system

Normally I would see tumblewee after hitting F11

Never seen that error, but the problem did start with a win10 update.

Have you tried to reinstall GRUB from Leap installation?

@Gps2010 It’s this perhaps Microsoft confirms August updates break Linux boot in dual-boot systems

Can I do this from Tumble weed too ?

Its possible, and its part why I hate windows.

Windows did not ask me if I wanted to update, I just wanted to start windows and off it went updating.

Are the installed OSes installed in UEFI mode? Did you boot the USB in UEFI mode? When CSM is enabled, many UEFI BIOS will lead you into a legacy boot by default. You may need to take action to boot in UEFI, probably BBS hotkey, or change BIOS setup to disable CSM (legacy) booting. All my PCs that have OSes installed in UEFI mode have CSM disabled, so that such nuisance doesn’t arise here.

@malcolmlewis Looks like link is to same subject as comment #2’s link. :stuck_out_tongue:

@mrmazda yes, but there also info on a registry setting to disable…

Secureboot is disabled in my bios, I just checked.
I remember why its turned off, it gave me problems with booting windows.
(the irony)
OpenSUSE Tumbeleweed did not have an issue. ( this was years ago, when I build this pc)

When I hit F11, I can choose windows or Leap, Tumbleweed has disappeared from that menu.

I can however still boot Tumbleweed with help from an installation usb stick.

Boot from the usb stick, then choose more and pick boot Linux medium.
Then select Tumbleweed.

When I look in my bios at the boot order, I can’t choose Tumbleweed anymore.
My bios does not seem to recognize the Tumbleweed disk as bootable anymore.

lsblk -fs
NAME      FSTYPE  FSVER            LABEL                            UUID                                 FSAVAIL FSUSE% MOUNTPOINTS
sda1      ntfs                     Herstel                          A63A73D93A73A549                                    
└─sda                                                                                                                   
sda2      vfat    FAT32                                             9474-CF21                                           
└─sda                                                                                                                   
sda3                                                                                                                    
└─sda                                                                                                                   
sda4      ntfs                                                      EA0E76BE0E76837D                                    
└─sda                                                                                                                   
sdb1      vfat    FAT32                                             9A90-3F07                                           
└─sdb                                                                                                                   
sdb2      ext4    1.0                                               5a26a5e5-5a43-4deb-9eae-f6e82d358dc2                
└─sdb                                                                                                                   
sdb3      ext4    1.0                                               64d5c6b8-8098-497b-b56a-beb464958102  367,5G    48% /home/guus/leaphome
└─sdb                                                                                                                   
sdb4      swap    1                                                 9f94c7ef-ce94-4d99-8ebd-187f0d37b0e1                
└─sdb                                                                                                                   
sdb5      ext4    1.0                                               b9cf1de0-e38d-46a4-ba88-08665ca8d340   30,1G    56% /home/guus/VMmount
└─sdb                                                                                                                   
sdc1      vfat    FAT16            openSUSE-Tumbleweed-DVD-x86_6429 0B56-CCF4                                           
└─sdc     iso9660 Joliet Extension openSUSE-Tumbleweed-DVD-x86_6429 2021-09-25-17-04-25-59                              
sdc2      iso9660 Joliet Extension openSUSE-Tumbleweed-DVD-x86_6429 2021-09-25-17-04-19-63                              
└─sdc     iso9660 Joliet Extension openSUSE-Tumbleweed-DVD-x86_6429 2021-09-25-17-04-25-59                              
nvme0n1p1 vfat    FAT32                                             3AB8-553F                               503M     2% /boot/efi
└─nvme0n1                                                                                                               
nvme0n1p2 btrfs                                                     9c8140f9-0b81-41eb-ab94-d7342c38d218  454,5G    51% /var
│                                                                                                                       /usr/local
│                                                                                                                       /root
│                                                                                                                       /srv
│                                                                                                                       /home
│                                                                                                                       /opt
│                                                                                                                       /boot/grub2/x86_64-efi
│                                                                                                                       /boot/grub2/i386-pc
│                                                                                                                       /.snapshots
│                                                                                                                       /
└─nvme0n1                               

Hope this helps? The DVD part is because of the usb stick I have inserted

Sure, but first check if CSM legacy support is disabled.
I guess that F11 gives you the UEFI boot. Can you see GRUB when you choose Leap? Is Tumbleweed there?