It had been a while since I used my laptop, so last night I powered it up and got 53 updates for the Opensuse, in stalled them all OK, rebooted and back in to Liux find, so thought I would also run up Windows.
Several hours later and I have just windows booting up, no option to select Opensuse leap at all.
In management services in Windows it looks as though the partitions are still there as it lists them all as RAW.
So after reading several articles it looks as though Grub has been disabled.
Can anyone let me know how I get this back please.
As far as I remember I had EUFI boot thingy?
I did not use Btrfs file system in linux but probably Ext4.
Any pointers would be appreciated or point me to a recent thread oin this as a quick search did not provide any answers, I am a bit dumb with this type of thing.
The problem you face is the uncontrollable update of Windows 10. Of course you can fix and again use Grub, but judging from the behavior of Windows 10, soon your Grub will be scrapped again.
Therefore no sense to lose time fixing the grub, just use the Windows 10 boot loader and add Tumbleweed through Windows 10 bcd command line, or the 3d party EasyBCD graphical utility.
If you however decide to restore grub, you can do it by loading openSuse from bootable DVD to fix it.
Ok just downloaded EasyBCD installed and tried to run, again I stress I am not that good at this but
"EasyBCD has detected that your machine is currently booting in EFI mode. Due to the limitations set by Microsoft, many of EasyBCD’s multi-booting facilities have been disabled.
Press Ok to continue etc."
So when I see if I can add an entry I note it is all greyed out
Now I do not wish to do more damage by doing things I do not understand here so please note my caution.
I know that I the grub boot loader was also UEFI compatable and I thought the whole idea was that nothing went in to change it, apart from Windows apparently.
You mention: If you however decide to restore grub, you can do it by loading openSuse from bootable DVD to fix it.
So if I find my Leap Iso on disk how would I restore it without going through a full install?
But your case is the other one with UEFI and no wiki for this in openSuse knowledge database??
However I can provide you the universal way for restoration of grub in the UEFI case despite the distro: https://sites.google.com/site/easylinuxtipsproject/6 (11 steps procedure)
Keep in mind that step 8 is debian specific!
For Leap it should be ‘zypper in grub2-x86_64-efi’
Which is exactly what I’ve written many times in this Forum – glad to see that, you have exactly the same experience as me!
Actually this happens every time that, you boot into Windows – the UEFI order in the BIOS doesn’t change – the openSUSE Secure Boot remains at the top of the list . . .
It’s actually a useful “feature” (“It’s not a bug, it’s a feature!”) for Windows updates – at the reboot Windows auto-magically does it’s update things without any human intervention at the GRUB2 “choices” screen . . .
What??!! Nobody’s time has been wasted by your query . . .
Here too – Lenovo G505s with Dual-Boot Windows 8.1 and openSUSE Leap 42.1.
Only until the next time you boot into Windows – the way out is to power off from Windows and then restart with the Lenovo “Novo” button – choose “BIOS” – right arrow to flip through the tabs until “Exit and save” – do it!
I have switched off the machine, booted to windows, powered down from windows, powered back on and still have the machine giving me the dual boot option which is the open suse one.
I do not think after all this that it changes the boot order in bios when I select windows and power down from there, but, thinking aloud when the computer is doing an update such as the Anniversary one where the PC is needing to restart several times during the reboot, I could see it make sense to re-order the boot list so that it starts up in windows to keep the update going, pity it did not change the order back at the end.
Maybe the Lenovo G505s (AMD) BIOS/UEFI is sufficiently different (it is anyway) to that of the Lenovo G50 (Intel???) . . .
Given the number of “I’ve never seen that” comments, what I’m seeing may be a Lenovo AMD-only behaviour . . .