Hi, My working Dual Boot system (Leap 15 and Win10) suddenly is no longer dual boot (I think, after an automatic grub update), the Win10 boot option on the grub screen has disappeared and the Leap15 options are duplicated, does anyone know if there is a bug going around that has this effect? I’m not sure how to go about fixing it. Thanks for any guidance.
Does “os-prober” show windows in its output (you should run that as root)?
nrickert, thanks for the reply, and helpful prompt
run as root :
laptop:~ # os-prober
/dev/sda8:openSUSE Leap 15.0:openSUSE:linux:btrfs:UUID=1834f47e-5630-4646-bb05-7e04ee5d35ba:subvol=@
that’s all it reports.
I can mount the win10 partition in Dolphin, so I know the filesystem is still there.
It seems that something is damaged in the Windows setup.
Is this UEFI booting or legacy booting?
It’s a UEFI booting system, the results of fdisk are :
laptop:~ # fdisk -l /dev/sda
Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: ######### (redacted)
Device Start End Sectors Size Type
/dev/sda1 2048 1026047 1024000 500M EFI System
/dev/sda2 1026048 1288191 262144 128M Microsoft reserved
/dev/sda3 1288192 985305087 984016896 469.2G Microsoft basic data
/dev/sda4 1925433344 1926354943 921600 450M Windows recovery environment
/dev/sda5 1926354944 1951332351 24977408 11.9G Windows recovery environment
/dev/sda6 1951334400 1953523711 2189312 1G Windows recovery environment
/dev/sda7 985305088 989523967 4218880 2G Linux swap
/dev/sda8 989523968 1073414143 83890176 40G Linux filesystem
/dev/sda9 1073414144 1925433343 852019200 406.3G Linux filesystem
Partition table entries are not in disk order.
########
What’s the output from:
efibootmgr -v
On UEFI systems, there is often a way of getting a BIOS boot menu. For example, on my system I can hit F12 during boot, and that gives me a boot menu. With HP computers, I think it is F9. Are you able to boot into Windows that way?
laptop:~ # efibootmgr -v
BootCurrent: 0003
Timeout: 0 seconds
BootOrder: 0003,2002,0000,0005,2003,2001
Boot0000* openSUSE HD(1,GPT,26015494-84ad-4609-bd5d-38b34d69e689,0x800,0xfa000)/File(\EFI\opensuse\grubx64.efi)RC
Boot0001* UEFI Onboard LAN IPv4 (50-9A-4C-BD-A8-B5) PciRoot(0x0)/Pci(0x2,0x2)/Pci(0x0,0x0)/MAC(509a4cbda8b5,0)/IPv4(0.0.0.0:0<->0.0.0.0:0,0,0)RC
Boot0002* UEFI Onboard LAN IPv6 (50-9A-4C-BD-A8-B5) PciRoot(0x0)/Pci(0x2,0x2)/Pci(0x0,0x0)/MAC(509a4cbda8b5,0)/IPv6(::]:<->::]:,0,0)RC
Boot0003* opensuse-secureboot HD(1,GPT,26015494-84ad-4609-bd5d-38b34d69e689,0x800,0xfa000)/File(\EFI\opensuse\shim.efi)
Boot0004* UEFI DVD1 PATH1 (PLDS DVD+/-RW DU-8A5LH) PciRoot(0x0)/Pci(0x11,0x0)/Sata(1,0,0)/CDROM(1,0x39a,0x1680)/HD(1,MBR,0x0,0x0,0x1680)RC
Boot0005* Windows Boot Manager HD(1,GPT,26015494-84ad-4609-bd5d-38b34d69e689,0x800,0xfa000)/File(\EFI\Microsoft\Boot\bootmgfw.efi)WINDOWS…x…B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}…
Boot2001* EFI USB Device RC
Boot2002* EFI DVD/CDROM RC
Boot2003* EFI Network RC
I’ve tried to get to the boot menu a few times now, hitting F12 [Dell], but it seems the grub screen appears almost immediately.
My main desktop is a Dell. To get that boot menu, I keep hitting F12 during boot (about twice per second). That makes it more likely that I will hit the key at the right time.
In any case, you should be able to boot Windows as follows:
While running openSUSE, use the following command (as root):
efibootmgr -n 0005
That tells your firmware (BIOS) to use boot entry 0005 on the next boot.
You will need to do that every time that you want to boot Windows, because it has a one-time effect.
And then I want you to report this as a bug.
openSUSE:Submitting bug reports
Maybe list the bug number here. And perhaps provide a link to this forum thread in your bug report.
nrickert, first I want to say thankyou for your guidance, I really feel like I am getting somewhere with this issue.
I’d actually done a bit of reading after your previous reply, and found the :
efibootmgr -t 10
efibootmgr -n 0005
commands, which I ran as root.
the second of which resulted in win10 booting successfully. I took the opportunity to fully update both Windows/Dell, while it was running. The first command gave me more time to F12 to the BIOS boot screen, and I find that I can start both “Win10” and “OPENSuse (secure boot)” from there.
One thing I notice on the BIOS boot screen, it says at the top “Boot mode is set to UEFI : Secure Boot : OFF”, and I wonder if that’s part of the problem.
There another OPENSuse boot option, just plain “OPENSuse”, I haven’t yet tried to boot this.
I wonder what it is that messed up the grub boot options, the machine was working well (apart from some niggly issue with startup WiFi connection) for several weeks, but then as I say I did notice a grub update, and then subsequently I noticed the grub screen had changed for the worse. I don’t use Windows unless I can help it (I find it so infuriating), so I didn’t address the problem straight away.
I will do as you say, and file a bug report. Hopefully I can somehow get the Grub boot menu fixed, and then be back to normal, using my favourite linux distro OPENSuse Leap.
Be sure that Windows fast boot is off it leave the FS in a state that make it difficult dor Linux to see.
Once you are sure that fast boot is off and os-prober sees Windows then reinstall grub. Easiest from Yast - boot loaderbe sure that scan for foreign OS box is check. In any case make a change then set it back to trick Yast into thinking a change made and accept
Bug filed as :
https://bugzilla.opensuse.org/show_bug.cgi?id=1105638
gogalthorp : thanks for your guidance, I will investigate accordingly, and report back
No, that should be fine. Your problem is that os-prober is not finding Windows.
There another OPENSuse boot option, just plain “OPENSuse”, I haven’t yet tried to boot this.
You won’t be able to tell the difference. However, that one will only work with secure-boot disabled. If you enable secure-boot, that one will give an error message.
I wonder what it is that messed up the grub boot options, the machine was working well (apart from some niggly issue with startup WiFi connection) for several weeks, but then as I say I did notice a grub update, and then subsequently I noticed the grub screen had changed for the worse. I don’t use Windows unless I can help it (I find it so infuriating), so I didn’t address the problem straight away.
It depends on running “os-prober” to create a boot menu. And it seems that “os-prober” is not working properly on your system. I don’t know why. It is working fine here. But I’m using “ext4” for the root file system and you are probably using “btrfs”. A bug might have crept in somewhere. That’s why you should file a bug report.
gogalthorp : I can confirm that FastBoot was enabled in Win10, as you suggest it likely was. I have just disabled it (unchecked box, and saved change). I have then rebooted machine back into Win10, and confirmed that the enable FastBoot box was still unchecked.
A further reboot, this time to openSUSE, and the results of os-prober (run as root) are unchanged.
laptop:~ # os-prober
/dev/sda8:openSUSE Leap 15.0:openSUSE:linux:btrfs:UUID=1834f47e-5630-4646-bb05-7e04ee5d35ba:subvol=@
This is in-line with nrickert’s assertion.
So I’m unsure whether I should try a re-install of grub or not.
Another thing that can make Window invisible is if the format is Dynamic disks. This is a Windows version of LVM but is Linux incomputable.
Can you mount the Windows partition(s)?
Note that the hot key to get to the UEFI boot menu varies between machines. Consult the docs to the hardware. Often it is displayed on the splash screen but that may go by too fast to read
I am able to mount the Win10 partition in Dolphin, and access files ok (though I tend not to try write to that partition from linux, generally it’s copy a file to the linux side, and get out of there as quickly as possible). I have noticed that “disk” entries are duplicated (or even triplicated on the navigation pane in Dolphin), and if I choose to mount the wrong one, it causes an error dialoque at the top of the right hand file pane saying it’s busy, but I can then just go to the other similarly named “disk” entry and it is mounted already. It does seem like there is something wrong generally. It’s not just the Win10 “disk” that’s duplicated by the way.
I am now able to boot either to Win10 or openSUSE from the Bios boot screen by tapping F12 at the splash screen, which is a definite improvement from this morning, and I have learned a lot more than I would have without the help from both you and nrickert, so thanks again.