New install, dual boot with windows 10, but windows is not in boot option

Linux installed and works great, but windows is not showing as an option in grub.

fdisk -l it shows the Disklabel type: gpt

G-parted shows the EFI system partition (fat32) is flagged as boot, esp

G-parted shows the grub2.core.img partition is flagged as bios_grub

Yast boot manager under options is looking for all bootable os

I have been digging through the similar posts, but can’t find the answer.
The closest I found was: https://forums.opensuse.org/showthread.php/553549-Tumbleweed-not-showing-Windows-10-in-grub-menu?highlight=windows+grub

thanks for the help

Was this your first time installing multiple operating systems on the same PC?

Try running efibootmgr. If you get a ‘not installed’ response, you’ve installed TW in legacy mode. For both to be bootable, Windows and Linux must both be installed in the same mode, either UEFI, or legacy (enabled via CSM setting in BIOS setup). If CSM is enabled, disable it and reinstall TW.

These are the partitions and file systems of a multi boot machine. Windows was installed from the iso download.

**erlangen:~ #** fdisk -l /dev/sdc     
**Disk /dev/sdc: 465.76 GiB, 500107862016 bytes, 976773168 sectors**
Disk model: Samsung SSD 850  
Units: sectors of 1 * 512 = 512 bytes 
Sector size (logical/physical): 512 bytes / 512 bytes 
I/O size (minimum/optimal): 512 bytes / 512 bytes 
Disklabel type: gpt 
Disk identifier: 90C1973B-4A41-4E96-85BA-B7358EA77CCC 

**Device****    Start****      End****  Sectors****  Size****Type**
**/dev/sdc1       2048    208895    206848   101M EFI System **
/dev/sdc2     208896  63119359  62910464    30G Linux filesystem 
/dev/sdc3   63119360 126033919  62914560    30G Linux filesystem 
/dev/sdc4  126033920 512202751 386168832 184.1G Linux filesystem 
/dev/sdc5  512202752 638033919 125831168    60G Linux filesystem 
/dev/sdc6  638033920 700948479  62914560    30G Linux filesystem 
/dev/sdc7  700948480 734502911  33554432    16G Linux swap 
/dev/sdc8  734502912 793495551  58992640  28.1G Linux filesystem 
/dev/sdc9  793495552 852088831  58593280  27.9G Linux filesystem 
**/dev/sdc10 852088832 852121599     32768    16M Microsoft reserved **
**/dev/sdc11 852121600 976773119 124651520  59.4G Microsoft basic data **
**erlangen:~ #** lsblk -f /dev/sdc 
NAME    FSTYPE FSVER LABEL       UUID                                 FSAVAIL FSUSE% MOUNTPOINT 
sdc                                                                                   
**├─sdc1  vfat   FAT16             4A24-B10D                                            **
├─sdc2  ext4   1.0   ArchLinux   690b51d7-7034-4585-b362-615f8056be45                 
├─sdc3  ext4   1.0   SLED        492c5d5e-5d9b-4a99-9d34-e1f9cee09fe9                 
├─sdc4  ext4   1.0   spare       f4c5463f-f43d-420a-a0ea-4456cfbc54fa                 
├─sdc5  btrfs        Tumbleweed  204f7d0f-979a-41e1-a483-a597d0357e0b                 
├─sdc6  ext4   1.0   Manjaro-SSD bf6ba7c9-9068-4a9b-b210-84b6d105df5c                 
├─sdc7  swap   1                 96df969e-8897-4a5c-8473-3ed007f97b29                 
├─sdc8  btrfs        Leap-15.2   69774d55-8da2-4599-9c27-766b1012771d                 
├─sdc9  ext4   1.0   Ubuntu      9a3eec78-dd20-44c0-a38a-f705b3bbbc66                 
**├─sdc10                                                                               **
**└─sdc11 ntfs                     7CB4EC04B4EBBEB0                                     **
**erlangen:~ #**

The most likely explanation, is that Windows is using UEFI booting, but you installed Tumbleweed for legacy booting. This might be fixable without complete reinstall, but the reinstall is probably easier.

There should not be such a partition unless you installed Tumbleweed for legacy boot.

To further check, try:

grep LOADER_TYPE /etc/sysconfig/bootloader

For UEFI booting, that should show the loader type as “grub2-efi”, but it probably shows just “grub2”

Thank you,
The reinstall with EPI did it. The error was mine. I have installed multiple times, but all as legacy. I wasn’t familiar with the EPI boot. I was installing this on my daughter’s computer.

Other than to be able to dual boot to a newer windoze system, is there any other reason to install the EPI version verses legacy?

thanks.

UEFI booting, being modern rather than ancient, is more reliable, less susceptible to corruption, and generally easier to fix if broken.

Great to see your problem solved!

Out of laziness I stayed with legacy BIOS from February 2014 until May 2018, my biggest blunder ever.

Other than to be able to dual boot to a newer windoze system, is there any other reason to install the EFI version verses legacy?

Thank you for the insight. The legacy is all I knew about and have always installed that way. Your comments above are great answers, but especially the drive note. That has driven me nuts for years.

Next question,
Can I simply reinstall the bootloader from Legacy to EPI or do I have to reinstall the the whole deal? I am now working on my computer. I am starting from scratch with two new hard drives. I finished the Legacy install, but now want to change it to EPI. I am open to a full reinstall since it is early in the process if that is the best answer.

thanks again for your reply.

I’ve done it. IIRC:

  1. boot installation media in UEFI mode to rescue mode
  2. mount /dev/<rootdevicename|volumelabel|UUID> /mnt
  3. mount -o bind /dev /mnt/dev
  4. mount -o bind /sys /mnt/sys
  5. mount -o bind /proc /mnt/proc
  6. chroot /mnt
  7. mount -a
    At this point you are running the installed system with a few limitations. You can install and remove software, reconfigure most things. So at this point grub2-efi needs to be installed if it hasn’t been already, and the ESP partition needs to be added to /etc/fstab if it isn’t already there. This can be done manually with zypper and your favorite text editor using elevated permissions, or with YaST. YaST will conveniently update your boot loader after you select “probe foreign OS”, or make any other change if it was already selected. Before rebooting, verify success:
(sudo) efibootmgr

If there is an opensuse entry listed ahead of the windows entry, you should be good to reboot normally, newly in UEFI mode, with an entry in Grub for Windows.

Fo me it’s difficult to remember all the detail of what I have done. So I write up and revise it upon important changes, such as switching from legacy to uefi bios.

This should have been written as ‘…efibootmgr and grub2-efi…’. Not likely one would have already been installed and not the other, and they might not be mutually dependent.

I am trying to install a linux only system, but cannot get the installation to accept grub2-efi as an option.

It shows in red, under the Booting at the installation summary at the end:
Unsupported combination of hardware platform x86_64 and bootloader grub2-efi

Additionally, at the end of setting up the Partitions an error shows stating a Bios boot partition is needed. It is set up already. I have not seen this message when installing in the past.

Frustrating!

The only OS being installed is OpenSuse with Cinnamon.
Using a separate partition for /home

Hi
So what/how is the pmbr set up, 8MB?

I set it up with the partition tool
Set it at 100 MB as a efi-boot partition and the type as Bios boot partition

Hi
BIOS boot and EFI boot are two different things…

PMBR boot is for gpt disk and BIOS boot, if the system supports EFI booting then the partition type needs to be ef00

Legacy (BIOS boot) on a gpt disk is like;


Model: ATA OCZ-VERTEX4 (scsi)
Disk /dev/sda: 128GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: pmbr_boot

Number  Start   End     Size    File system     Name  Flags
 1      1049kB  9437kB  8389kB                        bios_grub
 2      9437kB  53.7GB  53.7GB  btrfs                 legacy_boot
 3      53.7GB  127GB   73.0GB  xfs
 4      127GB   128GB   1325MB  linux-swap(v1)        swap

EFI Boot on a gpt disk;


Model: SPCC M.2 PCIe SSD (nvme)
Disk /dev/nvme0n1: 512GB
Sector size (logical/physical): 4096B/4096B
Partition Table: gpt
Disk Flags: 

Number  Start   End     Size    File system     Name                  Flags
 1      8389kB  281MB   273MB                   EFI system partition  msftdata
 2      281MB   64.7GB  64.4GB  btrfs           Linux filesystem
 3      64.7GB  118GB   53.7GB  xfs             Linux filesystem
 4      118GB   226GB   107GB   xfs             Linux filesystem
 5      226GB   247GB   21.5GB  xfs             Linux filesystem
 6      247GB   510GB   263GB   xfs             Linux filesystem
 7      510GB   512GB   1802MB  linux-swap(v1)  Linux filesystem      swap

I would like to install it as EFI. Is there a way to change the GPT to EFI?
Or will what you have above do the same?

I am at the point of a clean install on this SSD. Is there anything I can do to modify that disk as EFI, (non GPT).

Hi
No, a fresh install as the disk needs to change to type gpt not dos.

If GPT is correct, there is a line that says : Create GPT on /dev/sda

Above the example using efi-boot
What is the msftdata note at the end of that line?

btw, thank you for the help

Hi
I would boot into a rescue system and pre-allocated the disk with gdisk…

Here is a better example from an ssd, the info is just parted output…


 gdisk -l /dev/sda

GPT fdisk (gdisk) version 1.0.1

Partition table scan:
  MBR: protective
  BSD: not present
  APM: not present
  GPT: present

Found valid GPT with protective MBR; using GPT.
Disk /dev/sda: 234441648 sectors, 111.8 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): 9ACEE01D-A680-489B-B0B5-9C56E3C655DB
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 234441614
Partitions will be aligned on 2048-sector boundaries
Total free space is 2014 sectors (1007.0 KiB)

Number  Start (sector)    End (sector)  Size       Code  Name
   1            2048          534527   260.0 MiB   0700  EFI system partition
   2          534528       105392127   50.0 GiB    8300  Linux filesystem
   3       105392128       231221247   60.0 GiB    8300  Linux filesystem
   4       231221248       234441614   1.5 GiB     8200  Linux swap

parted -l /dev/sda

Model: ATA Crucial_CT120M50 (scsi)
Disk /dev/sda: 120GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt
Disk Flags: 

Number  Start   End     Size    File system     Name                  Flags
 1      1049kB  274MB   273MB   fat16           EFI system partition  msftdata
 2      274MB   54.0GB  53.7GB  btrfs           Linux filesystem
 3      54.0GB  118GB   64.4GB  xfs             Linux filesystem
 4      118GB   120GB   1649MB  linux-swap(v1)  Linux swap            swap

I have both rescue and g-parted disks
Between the two, you recommend the rescue?
I am installing a new system on this SSD, so is there anything to rescue?

I haven’t used the rescue disk for years, I am not quite sure what you mean by:
“into a rescue system and pre-allocated the disk with gdisk…”

clarifying, I am still in the installation tool, process.