UEFI only boots to Windows

[heebo1974]

From: Update broke grub. No Manjaro showing. Only Snapshots

I have kind a same problem. My problem is that if try to boot with uefi it only boots Windows.
Before update when UEFI_OS was selected the machine booted to Manjaro. Now it boots windows. M2_1: does give some grub error. SATA1 & SATA2 also don’t boot anything.
Windows Boot Manager: boot windows
manjaro (M2_1): boots manjaro
Linux Boot Manager: boots windows

I don’t quite understand why UEFI_OS and Linux Boot Manager boots now to Windows.

Summary

[ -d /sys/firmware/efi ] && echo UEFI || echo BIOS          
UEFI

sudo fdisk -l   
Disk model: Crucial_CT128MX1
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: dos
Disk identifier: 0x9f5e2c67

Device     Boot Start       End   Sectors   Size Id Type
/dev/sda1        2048 250066943 250064896 119,2G 83 Linux


Disk /dev/sdb: 119,24 GiB, 128035676160 bytes, 250069680 sectors
Disk model: Crucial_CT128MX1
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: 60CE4AC0-3182-44F9-8260-BD3D0574DEAC

Device         Start       End   Sectors   Size Type
/dev/sdb1       2048     34815     32768    16M Microsoft reserved
/dev/sdb2      34816 248745983 248711168 118,6G Microsoft basic data
/dev/sdb3  248745984 250066943   1320960   645M Windows recovery environment


Disk /dev/nvme0n1: 465,76 GiB, 500107862016 bytes, 976773168 sectors
Disk model: KIOXIA-EXCERIA G2 SSD                   
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: CF8ABE85-F58C-4B97-87F6-9858F81E8EDB

Device             Start       End   Sectors   Size Type
/dev/nvme0n1p1      4096    618495    614400   300M EFI System
/dev/nvme0n1p2    618496 958313126 957694631 456,7G Linux filesystem
/dev/nvme0n1p3 958313127 976768064  18454938   8,8G Linux swap

sudo parted -l                                                                                                         ✔ 
Model: ATA Crucial_CT128MX1 (scsi)
Disk /dev/sda: 128GB
Sector size (logical/physical): 512B/4096B
Partition Table: msdos
Disk Flags: 

Number  Start   End    Size   Type     File system  Flags
 1      1049kB  128GB  128GB  primary  ext4


Model: ATA Crucial_CT128MX1 (scsi)
Disk /dev/sdb: 128GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt
Disk Flags: 

Number  Start   End     Size    File system  Name                          Flags
 1      1049kB  17,8MB  16,8MB               Microsoft reserved partition  msftres, no_automount
 2      17,8MB  127GB   127GB   ntfs         Basic data partition          msftdata, no_automount
 3      127GB   128GB   676MB   ntfs                                       hidden, diag, no_automount


Model: KIOXIA-EXCERIA G2 SSD (nvme)
Disk /dev/nvme0n1: 500GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: 

Number  Start   End    Size    File system     Name  Flags
 1      2097kB  317MB  315MB   fat32                 boot, esp
 2      317MB   491GB  490GB   ext4            root
 3      491GB   500GB  9449MB  linux-swap(v1)        swap

---

Mod edit: I have moved your post to a dedicated topic, so that it will get more exposure.

[linux-aarhus]

The confusion has to do with a mix of EFI and BIOS installations.

Those two cannot be mixed into the GRUB loader.

It does look like

• sda disk contains a single linux partition (could be BIOS/MBR Linux installation - impossible to know)
• sdb disk contains a BIOS/MBR Windows
• nvme0n1 disk contains a Manjaro EFI installation.

The only way you can change this - if you don’t want to zap your Windows - is to disable EFI boot in your system’s firmware.

Boot a Manjaro ISO - replace the first partition on the nvme with an unformatted GPT partition designated bios-boot - in cgdisk the partition 16M size - type is 0xEF02 then run the grub bios install command to write the bootloader.

GRUB/Restore the GRUB Bootloader

[stephane]

can you report :

sudo efibootmgr 

the only boot UEFI is on
Model: KIOXIA-EXCERIA G2 SSD (nvme)
Disk /dev/nvme0n1

from his size , this is windows , you may still have grub installed for linux ,
i think there is no more entry efibootmgr ( thanks window$ ) for boot on linux

[Wollie]

@heebo1974

I don’t quite understand why UEFI_OS and Linux Boot Manager boots now to Windows.

So like us as. There are not enough information provided. We can see that you mixed BIOS and UEFI - always a very bad idea in a multi boot scenario as grub won’t be able to generate entries to boot all OS, you always must use your firmware to switch.

You are the system administrator for your system, so you could start to explain the purpose of each partition…

and don’t forget to answer @stephane:

@stephane

sudo efibootmgr

At the end, best would be most likely to reinstall all what is currently installed in BIOS mode. Then grub in combination with os-prober should be able to manage the boot process.

[soundofthunder]

@heebo1974

My problem is that if try to boot with uefi it only boots Windows.

@heebo1974

I don’t quite understand why UEFI_OS and Linux Boot Manager boots now to Windows.

This is your Windows disk. Very obvious is the fact that it doesn’t show an $ESP; this disk is a BIOS/MBR type disk installed as Legacy;

@heebo1974

Device         Start       End   Sectors   Size Type
/dev/sdb1       2048     34815     32768    16M Microsoft reserved
/dev/sdb2      34816 248745983 248711168 118,6G Microsoft basic data
/dev/sdb3  248745984 250066943   1320960   645M Windows recovery environment

Whereas the Manjaro disk does have an $ESP; it is a UEFI/GPT type disk clearly installed using UEFI technology:

@heebo1974

Device             Start       End   Sectors   Size Type
/dev/nvme0n1p1      4096    618495    614400   300M EFI System
/dev/nvme0n1p2    618496 958313126 957694631 456,7G Linux filesystem
/dev/nvme0n1p3 958313127 976768064  18454938   8,8G Linux swap

@linux-aarhus

The confusion has to do with a mix of EFI and BIOS installations.

Those two cannot be mixed into the GRUB loader.

---

@Wollie

At the end, best would be most likely to reinstall all what is currently installed in BIOS mode. Then grub in combination with os-prober should be able to manage the boot process.

---

The following is a tutorial which illustrates general methods to avoid situations such as this when multibooting Linux and Windows.

Regards.

[Multiboot] Windows and Linux on Separate Disks

Multiboot Windows and Linux …on Separate Disks Firstly, this guide is intended for multibooting with each OS on a separate disk. If you have a laptop with only one disk, or If you wish to install an OS on it’s own partition on the same disk, this guide is not for you (but read on regardless, if interested). Secondly, this guide assumes each OS will be installed using UEFI and not UEFI’s CSM or Legacy mode. This guide does not support the traditional BIOS boot method. Additionally, all disks …

[heebo1974]

I was just wondering why that behavior changed. Previously, the system booted into Manjaro with the UEFI_OS option, but that no longer works. I can still select Manjaro, and it is now the first option in the boot menu.
So basically I don’t have problem. Of course at first I was scared, because after upgrade it didn’t work.

sudo efibootmgr                                                                                                        ✔ 
BootCurrent: 0000
Timeout: 1 seconds
BootOrder: 0000,0001,0003,0002,0004
Boot0000* manjaro       HD(1,GPT,bc72a726-8033-4c8e-976f-bbc52b716a37,0x1000,0x96000)/\EFI\MANJARO\GRUBX64.EFI
Boot0001* Windows Boot Manager  HD(1,GPT,bc72a726-8033-4c8e-976f-bbc52b716a37,0x1000,0x96000)/\EFI\MICROSOFT\BOOT\BOOTMGFW.EFI57494e444f5753000100000088000000780000004200430044004f0042004a004500430054003d007b00390064006500610038003600320063002d0035006300640064002d0034006500370030002d0061006300630031002d006600330032006200330034003400640034003700390035007d00000000000100000010000000040000007fff0400
Boot0002* UEFI OS       HD(1,GPT,bc72a726-8033-4c8e-976f-bbc52b716a37,0x1000,0x96000)/\EFI\BOOT\BOOTX64.EFI0000424f
Boot0003* Linux Boot Manager    HD(1,GPT,bc72a726-8033-4c8e-976f-bbc52b716a37,0x1000,0x96000)/\EFI\SYSTEMD\SYSTEMD-BOOTX64.EFI
Boot0004* Hard Drive    BBS(HD,,0x0)0000474f00004e4fa9000000010000006b004b0049004f005800490041002d004500580043004500520049004100200047003200200053005300440000000501090002000000007fff040002010c00d041030a0000000001010600010101010600000003171000010000008ce38e0300943b697fff040001042e00ef47642dc93ba041ac194d51d01b4ce631003400330042003700310037004a004b0037003000530000007fff04000000424f00004e4fb50000000100000075004300720075006300690061006c005f00430054003100320038004d005800310030003000530053004400310000000501090002000000007fff040002010c00d041030a0000000001010600020801010600000003120a000000ffff00007fff040001043e00ef47642dc93ba041ac194d51d01b4ce62000200020002000200020002000200034003100360034004400300031004300410039003100430000007fff04000000424f00004e4fb50000000100000075004300720075006300690061006c005f00430054003100320038004d005800310030003000530053004400310000000501090002000000007fff040002010c00d041030a0000000001010600020801010600000003120a000100ffff00007fff040001043e00ef47642dc93ba041ac194d51d01b4ce62000200020002000200020002000200034003100330032004300300045003300420045003900440000007fff04000000424f