Manjaro KDE and windows dual boot. Linux will not boot

Sorry, I am a bit new to Linux. I have Manjaro set to my main M.2 SSD and Windows on my second SSD. The bootloader randomly showed up after update Manjaro recently, I selected windows to boot and now it only allows me to boot into windows. What is the best way to fix the bootloader and allow me to select which OS I can boot too?

*edit, set my grub timeout back to 8. Or just holding f1 allowed me to select os to boot to again.

Hi and welcome to the forum :+1:

Help others to help you better:

Start by booting from a Live USB/DVD of Manjaro.
Then paste the output of the following commands with ``` before and after (on separate lines) of the pasted texts

  • sudo lsblk --fs
  • efibootmgr -v

and also inxi if it helps

System:    Host: manjaro Kernel: 5.4.23-1-MANJARO x86_64 bits: 64 
           parameters: BOOT_IMAGE=/boot/vmlinuz-x86_64 lang=en_US keytable=us tz=UTC driver=free nouveau.modeset=1 
           i915.modeset=1 radeon.modeset=1 misobasedir=manjaro misolabel=MANJARO_KDE_1902 quiet systemd.show_status=1 
           apparmor=1 security=apparmor 
           Desktop: KDE Plasma 5.17.5 Distro: Manjaro Linux 
Machine:   Type: Desktop Mobo: ASUSTeK model: TUF GAMING X570-PLUS v: Rev X.0x serial: <filter> UEFI: American Megatrends 
           v: 2607 date: 08/14/2020 
CPU:       Topology: 8-Core model: AMD Ryzen 7 3700X bits: 64 type: MT MCP family: 17 (23) model-id: 71 (113) stepping: N/A 
           microcode: 8701021 L2 cache: 4096 KiB 
           Speed: 3583 MHz min/max: 2200/3600 MHz Core speeds (MHz): 1: 3590 2: 2050 3: 2052 4: 2052 5: 3600 6: 2053 7: 2022 
           8: 2060 9: 2049 10: 2052 11: 3600 12: 2053 13: 2053 14: 2147 15: 3587 16: 2045 
           Vulnerabilities: Type: itlb_multihit status: Not affected 
           Type: l1tf status: Not affected 
           Type: mds status: Not affected 
           Type: meltdown status: Not affected 
           Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl and seccomp 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 mitigation: Full AMD retpoline, IBPB: conditional, STIBP: conditional, RSB filling 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: NVIDIA GM204 [GeForce GTX 970] driver: nouveau v: kernel 
           Device-2: Advanced Micro Devices [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] driver: amdgpu 
           v: kernel 
           Display: x11 server: X.Org 1.20.7 driver: amdgpu,nouveau FAILED: ati unloaded: modesetting 
           resolution: 1920x1080~60Hz 
           OpenGL: renderer: AMD Radeon RX 480 Graphics (POLARIS10 DRM 3.35.0 5.4.23-1-MANJARO LLVM 9.0.1) v: 4.5 Mesa 19.3.4 
Audio:     Device-1: NVIDIA GM204 High Definition Audio driver: snd_hda_intel 
           Device-2: AMD Ellesmere HDMI Audio [Radeon RX 470/480 / 570/580/590] driver: snd_hda_intel 
           Device-3: Advanced Micro Devices [AMD] Starship/Matisse HD Audio driver: snd_hda_intel 
           Device-4: Razer USA type: USB driver: hid-generic,snd-usb-audio,usbhid 
           Sound Server: ALSA v: k5.4.23-1-MANJARO 
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169 
           IF: enp5s0 state: up speed: 100 Mbps duplex: full mac: <filter> 
Drives:    Local Storage: total: 4.14 TiB used: 216.1 MiB (0.0%) 
           ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 960 EVO 250GB size: 232.89 GiB block size: physical: 512 B 
           logical: 512 B 
           ID-2: /dev/sda vendor: Seagate model: ST1000DM003-1CH162 size: 931.51 GiB block size: physical: 4096 B 
           logical: 512 B 
           ID-3: /dev/sdb vendor: Crucial model: CT240BX500SSD1 size: 223.57 GiB block size: physical: 512 B logical: 512 B 
           ID-4: /dev/sdc vendor: Toshiba model: HDWD130 size: 2.73 TiB block size: physical: 4096 B logical: 512 B 
           ID-5: /dev/sdd type: USB vendor: Lexar model: USB Flash Drive size: 59.62 GiB block size: physical: 512 B 
           logical: 512 B 
Partition: ID-1: / raw size: N/A size: 11.71 GiB used: 216.1 MiB (1.8%) fs: overlay source: ERR-102 
Sensors:   System Temperatures: cpu: 41.2 C mobo: N/A 
           Fan Speeds (RPM): N/A 
           GPU: device: amdgpu temp: 50 C fan: 709 device: nouveau temp: 39 C fan: 0 
Info:      Processes: 311 Uptime: 14m Memory: 15.61 GiB used: 2.21 GiB (14.2%) Shell: bash inxi: 3.0.37 

Can you edit your post with the lsblk output and replace it with the output of the command i gave?
(The --fs is important)

Ok so what you want to do is move the UEFI OS Boot 0002 to the top.

First, copy the current boot order. For example, my boot order is:


Then type in the following command

sudo efibootmgr -o

And append the boot order to the above command.

sudo efibootmgr -o 0013,0012,0014,0000,0001,0002,0003,000D,0011,0007,0008,0009,000A,000B,000C,000E

Let’s say you want 0012 to be the first boot entry. All you have to do is move it to the left of 0013 and press Enter.

sudo efibootmgr -o 0012,0013,0014,0000,0001,0002,0003,000D,0011,0007,0008,0009,000A,000B,000C,000E

     squash 4.0                                                    0   100% /run/miso/
     squash 4.0                                                    0   100% /run/miso/
     squash 4.0                                                    0   100% /run/miso/
     squash 4.0                                                    0   100% /run/miso/
     ext4   1.0   Game Drive
│    vfat   FAT32       C624-FDD6                                           
│    ntfs               B84E9A8A4E9A4154                                    
     ntfs               A41E0F311E0EFBD4                                    
     ntfs         Video/Storage Drive
sdd  iso966 Jolie MANJARO_KDE_1902
│                       2020-03-11-13-57-55-00                              
│    iso966 Jolie MANJARO_KDE_1902
│                       2020-03-11-13-57-55-00                     0   100% /run/miso/
     vfat   FAT12 MISO_EFI
│    vfat   FAT32       1611-5124                                           
│    swap   1           c2a598ad-44ff-450a-aedb-fe468d63e503                
     ext4   1.0         7d8ef26d-4c2c-400d-a55b-31ab31a184d3

BootCurrent: 0002
Timeout: 1 seconds
BootOrder: 0002,0003,0001,0000
Boot0000 Windows Boot Manager HD(1,GPT,0cfade25-99ed-40af-97bc-f244bb5142a0,0x800,0x32000)/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.}…d…
Boot0001 UEFI OS HD(1,GPT,ee7437bc-34e0-db40-97af-0a123f16eb78,0x800,0xfa000)/File(\EFI\BOOT\BOOTX64.EFI)…BO
Boot0002* UEFI: Lexar USB Flash Drive 1100 PciRoot(0x0)/Pci(0x1,0x2)/Pci(0x0,0x0)/Pci(0x8,0x0)/Pci(0x0,0x1)/USB(8,0)/CDROM(1,0x5ab7e8,0x8000)…BO
Boot0003* UEFI: Lexar USB Flash Drive 1100, Partition 2 PciRoot(0x0)/Pci(0x1,0x2)/Pci(0x0,0x0)/Pci(0x8,0x0)/Pci(0x0,0x1)/USB(8,0)/HD(2,MBR,0x0,0x5ab7e8,0x2000)…BO

From the lsblk --fs command, it looks like manjaro is in the sdd but it is actually on the nvme. Seems like it got messed around after something happened with windows or manjaro update.

The sdd that is shown is the USB live media he used to boot with…

Looks like you don’t have any boot entry for Manjaro specific, are you sure you installed in UEFI mode?
Besides that the output of the lsblk --fs shows that you have two ESP partitions across two disks.
You should only have 1 ESP available to your system because the UEFI bios will use the first it finds…
Maybe that is the reason why your Manjaro boot entry is not shown, because it is in the ESP nvme0n1p1 ?

To summarize what you have at moment: (disregarding the USB-Live media at sdd)

  1. A “Legacy boot” entry, which most probably is a copy of the M$ bootloader below in (2).
    Boot0001 UEFI OS HD(1,GPT,ee7437bc-34e0-db40-97af-0a123f16eb78,0x800,0xfa000)/File(\EFI\BOOT\BOOTX64.EFI)…BO
  2. An “UEFI boot” entry for M$:
    Boot0000 Windows Boot Manager HD(1,GPT,0cfade25-99ed-40af-97bc-f244bb5142a0,0x800,0x32000)/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.}…d…

We might be able to manually add an “UEFI boot” entry for your Manjaro install on your nvme0n1 disk.
To check if that would be a possibility can you perform these steps?:

  1. Boot again using your Live media of manjaro.
  2. systemd-mount /dev/disk/by-uuid/1611-5124 /test-efi
  3. pamac install tree xclip
  4. sudo tree /test-efi | xclip
  5. Make a reply with the output of that last command between ```
    • You need to put each pair of the three backticks on separate lines on their own.
    • The output of that last command is in your clipboard ready to be pasted.

the “pamac install tree xclip” just gave me an error Could not connect: No route to host Could not connect: No route to host Could not connect: No route to host

Don’t you have internet connection after booting with the Live media?

never mind that… sorry

so should i just “apply transaction” yes?

To remove (4):
  user-manager                        5.17.5-1                                                  
  pygobject-devel                     3.34.0-3                                                  
  libwbclient                         4.10.10-2                                                 
  libutil-linux                       2.35.1-1.1                                                

Total download size: 1.9 GB
Total installed size: 543.5 MB
Total removed size: 4.1 MB

Although it’s weird that it needs to remove those packages, but it’s a Live media anyhow so no harm…

might be because it’s an older manjaro live media.

Ahhh, well if you have the posibility, then download the latest iso and burn it to your USB before doing these steps…
(Always better to use latest iso…)

oof, my 1.8 mbps internet… lol.
will do.

I would also like to mention that when this happened, windows booted up and did a “disk fix” thing to one of my drives that is ntfs “storage drive” which i share between both OS’s. (had to do the NTFS fix on linux for me to write to it)

Yea some M$ updates screw with the system in a not so user friendly way (read unwanted)
And the NTFS fix is to clean the state of it, otherwise it is left in a read-only way indeed

here’s the output

│   └── desktop.ini
├── EFI
│   ├── boot
│   │   └── bootx64.efi
│   └── Manjaro
│       └── grubx64.efi
└── System Volume Information
    ├── EDP
    │   └── Recovery
    ├── IndexerVolumeGuid
    └── WPSettings.dat

7 directories, 5 files