Page 1 of 2 12 LastLast
Results 1 to 10 of 15

Thread: Leap, Windows 10, 2 disks, dual boot, UEFI

  1. #1

    Question Leap, Windows 10, 2 disks, dual boot, UEFI

    I added a second hard drive to my computer. Windows 10 is on the first drive and I want to place openSUSE on the second drive. On startup, I want to display a boot menu where I can select either Windows 10 or openSUSE. You know, what you would expect if I repartitioned the first drive and installed openSUSE in addition to Windows. Nothing I have tried gives me the boot menu.

    1. I installed openSUSE Leap onto the second drive with partitions as follows:
    sdb1 whatever size the default install gives it /boot/efi
    sdb2 8 GiB swap
    sdb3 40 GiB /
    sdb4 rest of the drive /home
    When the installation completes and the system restarts, I am taken directly into Windows 10.

    2. An Internet search yielded an article that states the /boot/efi mount point should be placed on the Windows EFI partition. I repartitioned sdb to eliminate sdb1 above and placed the /boot/efi mount point on the Windows EFI partition. When the installation completes, I get:
    grub>
    Entering exit displays the Boot Option Menu. I selected the openSUSE entry and openSUSE started up. When the startup was complete, I restarted the computer and bang, Windows 10 again.

    3. I also found an article that states I should select sdb first in the UEFI Boot Order. I think it was referring to installing openSUSE on a USB drive, but I looked anyway:
    UEFI Boot Order
    OS boot manager
    USB Diskette on Key/USB Hard Disk
    Internal CD/DVD ROM Drive
    USB CD/DVD ROM Drive
    ! Network Adapter
    So, no entry for sdb, and OS boot manager goes straight to Windows 10.

    What do I do to get a boot menu when the computer starts?

  2. #2
    Join Date
    Aug 2010
    Location
    Chicago suburbs
    Posts
    15,677
    Blog Entries
    3

    Default Re: Leap, Windows 10, 2 disks, dual boot, UEFI

    I'm not sure what you did there.

    On my current desktop, I have two hard drives.

    "/dev/sda" contains Windows 8.1, and nothing else.

    "/dev/sdb" contains openSUSE 42.3 and openSUSE 15.0 Beta.

    I normally get a grub boot menu, where I can choose Windows, openSUSE 42.3 or openSUSE 15.0 Beta (default is 42.3).

    I have an EFI partition on "/dev/sdb" used by openSUSE. And the EFI partition on "/dev/sda" is used by Windows.

    So I think I'm doing close to what you want.

    However: UEFI implementations vary. The one on my computer is actually broken, but having two EFI partitions allows me to work around that.

    In your case, I don't know if you set things up wrongly, or you have a broken UEFI implementation on your system. You did not provide enough information.

    Here's what would help:
    1. Details on your computer (manufacturer, model, etc);
    2. The output of "fdisk -l" (run that as root) or of "parted -l". Be sure to use code tags if you post this output. Or upload it to susepaste ("paste.opensuse.org") and provide a link. If you cannot get into openSUSE to run those commands, then boot the installer to the rescue system and get the output of "fdisk -l /dev/sda" and "fdisk -l /dev/sdb". Or maybe you can use "diskpart" in windows to get partition information.
    3. The output of "df" if you are able to boot openSUSE. If not, a list of mount points for your openSUSE system.


    Or whatever information you can provide.
    openSUSE Leap 15.3; KDE Plasma 5.18.6;

  3. #3
    Join Date
    Sep 2014
    Location
    Germany
    Posts
    915

    Default Re: Leap, Windows 10, 2 disks, dual boot, UEFI

    Quote Originally Posted by jimo View Post
    ... What do I do to get a boot menu when the computer starts?
    Given that your UEFI is NOT broken this

    https://forums.opensuse.org/showthre...-boot-scenario

    might help you to repair your installation.

    Regards

    susejunky

  4. #4

    Default Re: Leap, Windows 10, 2 disks, dual boot, UEFI

    To get to a closer playing field, I reinstalled openSUSE Leap onto sdb. Here are the answers to your requests for more info.

    Quote Originally Posted by nrickert View Post
    Here's what would help:
    1. Details on your computer (manufacturer, model, etc);
    HP Envy 17 circa 2015
    Quote Originally Posted by nrickert View Post

    1. The output of "fdisk -l" (run that as root) or of "parted -l". Be sure to use code tags if you post this output. Or upload it to susepaste ("paste.opensuse.org") and provide a link. If you cannot get into openSUSE to run those commands, then boot the installer to the rescue system and get the output of "fdisk -l /dev/sda" and "fdisk -l /dev/sdb". Or maybe you can use "diskpart" in windows to get partition information.
    Code:
    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: 9580E8EA-B872-4CEE-89A5-DF7F667ABD72
    
    Device          Start        End    Sectors   Size Type
    /dev/sda1        2048    1333247    1331200   650M Windows recovery environment
    /dev/sda2     1333248    1865727     532480   260M EFI System
    /dev/sda3     1865728    2127871     262144   128M Microsoft reserved
    /dev/sda4     2127872 1904401458 1902273587 907.1G Microsoft basic data
    /dev/sda5  1904402432 1906321407    1918976   937M Windows recovery environment
    /dev/sda6  1906321408 1953513471   47192064  22.5G Microsoft basic data
    
    Disk /dev/sdb: 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: EC0F229B-449A-49CB-AE60-D133A6711741
    
    Device         Start        End    Sectors   Size Type
    /dev/sdb1       2048     321535     319488   156M EFI System
    /dev/sdb2     321536   17092607   16771072     8G Microsoft basic data
    /dev/sdb3   17092608  100984831   83892224    40G Microsoft basic data
    /dev/sdb4  100984832 1953523711 1852538880 883.4G Microsoft basic data
    Quote Originally Posted by nrickert View Post


    1. The output of "df" if you are able to boot openSUSE. If not, a list of mount points for your openSUSE system.


    Or whatever information you can provide.
    sdb1 is /boot/efi
    sdb2 is swap
    sdb3 is /
    sdb4 is /home

  5. #5
    Join Date
    Nov 2009
    Location
    West Virginia Sector 13
    Posts
    16,288

    Default Re: Leap, Windows 10, 2 disks, dual boot, UEFI

    DO you see the openSUSE entry in the UEFI boot menu?? Can you set the boot to that entry?

  6. #6

    Default Re: Leap, Windows 10, 2 disks, dual boot, UEFI

    Quote Originally Posted by gogalthorp View Post
    DO you see the openSUSE entry in the UEFI boot menu?? Can you set the boot to that entry?
    No and no. No menu is displayed at startup.

  7. #7
    Join Date
    Nov 2009
    Location
    West Virginia Sector 13
    Posts
    16,288

    Default Re: Leap, Windows 10, 2 disks, dual boot, UEFI

    You must press the UEFI key to bring up the UEFI boot menu. This is hardware dependent so can't tell you which hot key it is (f10/f12 Maybe??). Sometimes it is displayed on the UEFI/BIOS splash screen. Or you have to dig into the hardware docs.

  8. #8
    Join Date
    Aug 2010
    Location
    Chicago suburbs
    Posts
    15,677
    Blog Entries
    3

    Default Re: Leap, Windows 10, 2 disks, dual boot, UEFI

    Quote Originally Posted by jimo View Post
    To get to a closer playing field, I reinstalled openSUSE Leap onto sdb. Here are the answers to your requests for more info.
    I'm not requoting all of what you wrote.

    It all looks good.

    You should have a directory "/boot/efi/EFI/opensuse" and it should contain: shim.efi, grub.efi, grub.cfg (and other files).

    Check whether the "pmbr_boot" flag is on for either disk. If it is on, then turn it off. Google can help guide you through this.

    Some BIOS implementations ignore this flag. Others use it to control whether to use legacy booting or UEFI booting.
    openSUSE Leap 15.3; KDE Plasma 5.18.6;

  9. #9

    Default Re: Leap, Windows 10, 2 disks, dual boot, UEFI

    Quote Originally Posted by gogalthorp View Post
    You must press the UEFI key to bring up the UEFI boot menu. This is hardware dependent so can't tell you which hot key it is (f10/f12 Maybe??). Sometimes it is displayed on the UEFI/BIOS splash screen. Or you have to dig into the hardware docs.
    I get the following:
    Code:
    Boot Option Menu
    OS boot Manager
    Boot from EFI File
    Selecting OS boot Manager starts Windows. Selecting Boot from EFI File opens File Explorer and shows two entries:
    Code:
    NO VOLUME LABEL.
    [Acpi(PNP0A03,0)/PCI(1FI2)/Sata(0,0,0)/HD(Part2, sig<a UUID>)]
    
    NO VOLUME LABEL.
    [Acpi(PNP0A03,0)/PCI(1FI2)/Sata(4,0,0)/HD(Part1, sig<a different UUID>)]
    Selecting the first volume displays:
    Code:
    <EFI>
    <Boot>
    <System Volume Information>
    Selecting <EFI> displays:
    Code:
    <.>
    <..>
    <Microsoft>
    <Boot>
    <HP>
    Selecting the second volume displays:
    Code:
    <EFI>
    and selecting it displays:
    Code:
    <.>
    <..>
    <boot>
    <opensuse>
    Selecting <boot> displays:
    Code:
    <.>
    <..>
    bootx64.efi
    fallback.efi
    Selecting either efi file displays the openSUSE GRUB menu.

    Instead, if I select <opensuse>, I get:

    Code:
    <.>
    <..>
    MokManager.efi
    grub.efi
    shim.efi
    grubx64.efi
    Selecting any of these efi files displays the openSUSE GRUB menu.

  10. #10

    Default Re: Leap, Windows 10, 2 disks, dual boot, UEFI

    Quote Originally Posted by nrickert View Post
    You should have a directory "/boot/efi/EFI/opensuse" and it should contain: shim.efi, grub.efi, grub.cfg (and other files).
    Yes.

    Quote Originally Posted by nrickert View Post
    Check whether the "pmbr_boot" flag is on for either disk. If it is on, then turn it off. Google can help guide you through this.
    I set pmbr_boot to off for both disks. Still boots directly into Windows unless I press:

    Code:
    ESC, F9, Down, Enter, Down, Enter, Down, Down, Down, Enter, Down, Down, Down Enter
    See my answer to gogalthorp directly above.

    I was expecting the openSUSE GRUB menu when I start the computer, not having to press a minimum of 13 keys to display the menu.

Page 1 of 2 12 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •