Can't boot Manjaro anymore after Windows update (EFI)

Support
1

I there,

I run a dual boot system with EFI dual booting Windows 10 & Manjaro. After a windows update I can’t boot into Manjaro anymore. I’ve read a lot of the topics on this but can’t figure out what’s wrong with my installation. Any help would be greatly appreciated. Based on the previous topics I read this is the info you need to help me:

inxi -Fza 

System:    Kernel: 5.9.16-1-MANJARO x86_64 bits: 64 compiler: gcc v: 10.2.0 
       parameters: BOOT_IMAGE=/boot/vmlinuz-x86_64 lang=en_US keytable=us tz=UTC misobasedir=manjaro 
       misolabel=MANJARO_KDE_2021 quiet systemd.show_status=1 apparmor=1 security=apparmor driver=free nouveau.modeset=1 
       i915.modeset=1 radeon.modeset=1 
       Desktop: KDE Plasma 5.20.4 tk: Qt 5.15.2 wm: kwin_x11 dm: SDDM Distro: Manjaro Linux 
Machine:   Type: Desktop System: Gigabyte product: X570 I AORUS PRO WIFI v: -CF serial: <filter> 
       Mobo: Gigabyte model: X570 I AORUS PRO WIFI serial: <filter> UEFI: American Megatrends v: F31o date: 12/03/2020 
CPU:       Info: 12-Core model: AMD Ryzen 9 5900X bits: 64 type: MT MCP arch: Zen 3 family: 19 (25) model-id: 21 (33) 
       stepping: N/A microcode: A201009 L2 cache: 6 MiB 
       flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 177342 
       Speed: 2192 MHz min/max: 2200/3700 MHz boost: enabled Core speeds (MHz): 1: 2192 2: 2193 3: 2194 4: 2192 5: 2187 
       6: 2196 7: 2198 8: 2193 9: 2191 10: 2189 11: 2193 12: 2191 13: 2195 14: 2195 15: 2192 16: 2195 17: 2193 18: 2196 
       19: 2194 20: 2189 21: 2195 22: 2194 23: 2193 24: 2198 
       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, IBRS_FW, STIBP: always-on, RSB filling 
       Type: srbds status: Not affected 
       Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: Advanced Micro Devices [AMD/ATI] driver: amdgpu v: kernel bus ID: 0c:00.0 chip ID: 1002:73bf 
       Display: x11 server: X.Org 1.20.10 compositor: kwin_x11 driver: amdgpu,ati unloaded: modesetting,radeon 
       alternate: fbdev,vesa display ID: :0 screens: 1 
       Screen-1: 0 s-res: 3840x2160 s-dpi: 96 s-size: 1016x571mm (40.0x22.5") s-diag: 1165mm (45.9") 
       Monitor-1: HDMI-A-0 res: 3840x2160 hz: 60 dpi: 163 size: 600x340mm (23.6x13.4") diag: 690mm (27.2") 
       OpenGL: renderer: AMD SIENNA_CICHLID (DRM 3.39.0 5.9.16-1-MANJARO LLVM 11.0.0) v: 4.6 Mesa 20.3.1 
       direct render: Yes 
Audio:     Device-1: Advanced Micro Devices [AMD/ATI] driver: snd_hda_intel v: kernel bus ID: 0c:00.1 chip ID: 1002:ab28 
       Device-2: Advanced Micro Devices [AMD] Starship/Matisse HD Audio vendor: Gigabyte driver: snd_hda_intel v: kernel 
       bus ID: 0e:00.4 chip ID: 1022:1487 
       Device-3: SteelSeries ApS Arctis Pro Wireless type: USB driver: hid-generic,snd-usb-audio,usbhid bus ID: 7-2.3:6 
       chip ID: 1038:1294 
       Sound Server: ALSA v: k5.9.16-1-MANJARO 
Network:   Device-1: Intel I211 Gigabit Network vendor: Gigabyte driver: igb v: kernel port: f000 bus ID: 05:00.0 
       chip ID: 8086:1539 
       IF: enp5s0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
       Device-2: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel port: f000 bus ID: 06:00.0 chip ID: 8086:2723 
       IF: wlp6s0 state: down mac: <filter> 
Drives:    Local Storage: total: 3.67 TiB used: 173 MiB (0.0%) 
       SMART Message: Unable to run smartctl. Root privileges required. 
       ID-1: /dev/nvme0n1 maj-min: 259:1 vendor: Western Digital model: WDS100T1X0E-00AFY0 size: 931.51 GiB block size: 
       physical: 512 B logical: 512 B speed: 63.2 Gb/s lanes: 4 serial: <filter> rev: 611100WD temp: 51.9 C 
       ID-2: /dev/nvme1n1 maj-min: 259:0 vendor: Western Digital model: WDS100T3X0C-00SJG0 size: 931.51 GiB block size: 
       physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 serial: <filter> rev: 111110WD temp: 57.9 C 
       ID-3: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 860 EVO 2TB size: 1.82 TiB block size: physical: 512 B 
       logical: 512 B speed: 6.0 Gb/s serial: <filter> rev: 4B6Q 
       ID-4: /dev/sdb maj-min: 8:16 type: USB vendor: SanDisk model: Extreme size: 29.82 GiB block size: physical: 512 B 
       logical: 512 B serial: <filter> rev: 0001 
Partition: ID-1: / raw size: N/A size: 23.52 GiB used: 173 MiB (0.7%) fs: overlay source: ERR-102 
Swap:      Alert: No Swap data was found. 
Sensors:   System Temperatures: cpu: 16.8 C mobo: 16.8 C gpu: amdgpu temp: 56.0 C mem: 54.0 C 
       Fan Speeds (RPM): N/A gpu: amdgpu fan: 0 
Info:      Processes: 426 Uptime: 16m wakeups: 0 Memory: 31.36 GiB used: 3.61 GiB (11.5%) Init: systemd v: 247 Compilers: 
       gcc: N/A Packages: pacman: 1264 lib: 375 flatpak: 0 Shell: Bash v: 5.1.0 running in: konsole inxi: 3.2.01

sudo parted -l

Model: ATA Samsung SSD 860 (scsi)
Disk /dev/sda: 2000GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: 

Number  Start   End     Size    File system  Name  Flags
 1      1049kB  2000GB  2000GB                     legacy_boot, msftdata


Model: SanDisk Extreme (scsi)
Disk /dev/sdb: 32.0GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags: 

Number  Start   End     Size    Type     File system  Flags
 2      3226MB  3230MB  4194kB  primary               esp


Model: WDS100T1X0E-00AFY0 (nvme)
Disk /dev/nvme0n1: 1000GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: 

Number  Start   End     Size    File system     Name                          Flags
 1      1049kB  317MB   316MB   fat32                                         bios_grub, legacy_boot
 2      317MB   630GB   630GB   ext4
 3      630GB   630GB   16.8MB                  Microsoft reserved partition  msftres
 4      630GB   991GB   360GB   ntfs            Basic data partition          msftdata
 5      991GB   1000GB  9449MB  linux-swap(v1)                                swap


Model: WDS100T3X0C-00SJG0 (nvme)
Disk /dev/nvme1n1: 1000GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: 

Number  Start   End     Size    File system     Name  Flags
 1      1049kB  1000GB  1000GB  linux-swap(v1)        legacy_boot, msftdata

Sandisk Extreme is the USB Live CD from Manjaro. Main system was installed on /dev/nvme0n1

sudo efibootmgr -v

BootCurrent: 000A
Timeout: 1 seconds
BootOrder: 000A,000B,000D
Boot000A* UEFI: SanDisk Extreme 0001    PciRoot(0x0)/Pci(0x8,0x1)/Pci(0x0,0x3)/USB(4,0)/CDROM(1,0x60247c,0x8000)..BO
Boot000B* UEFI: SanDisk Extreme 0001, Partition 2       PciRoot(0x0)/Pci(0x8,0x1)/Pci(0x0,0x3)/USB(4,0)/HD(2,MBR,0x0,0x60247c,0x2000)..BO
Boot000D* Windows Boot Manager  HD(4,GPT,ecb0ef81-418d-44f4-a49d-01a5f6d13d4f,0x49594000,0x29f6e000)/File(\EFI\MICROSOFT\BOOT\BOOTMGFW.EFI)..BO

Juding by this it’s missing the entry for Manjaro. But bare with me, I’ve followed steps from previous help topics and ended up with Manjaro in there, but still not being able to boot. More on this later.

test -d /sys/firmware/efi && echo efi || echo bios

efi

So what I have tried:

  • Some of the help topics here with the various commands with various degrees of different output (sorry I lost track)
  • Start Manjaro Architect from the live CD and went into “prepare installation” to mount the drives.
    I mounted my Manjaro partition (the 500gb one), my windows partition, my swap partition and afterwards let Arthictect fix my efi partition under prepare installation. Afterwards I went to “system rescue” and selected “install bootloader”, where I picked “grub” and set it as default. Afterwards I selected “chroot into installation” and ran “efibootgmr -v” again with this result:

Output:

BootCurrent: 000A
Timeout: 1 seconds
BootOrder: 0000,000A,000B,000D
Boot0000* manjaro       HD(1,GPT,cc5f53eb-e612-ac42-a08f-eb5d45e314fc,0x800,0x96800)/File(\EFI\manjaro\grubx64.efi)
Boot000A* UEFI: SanDisk Extreme 0001    PciRoot(0x0)/Pci(0x8,0x1)/Pci(0x0,0x3)/USB(4,0)/CDROM(1,0x60247c,0x8000)..BO
Boot000B* UEFI: SanDisk Extreme 0001, Partition 2       PciRoot(0x0)/Pci(0x8,0x1)/Pci(0x0,0x3)/USB(4,0)/HD(2,MBR,0x0,0x60247c,0x2000)..BO
Boot000D* Windows Boot Manager  HD(4,GPT,ecb0ef81-418d-44f4-a49d-01a5f6d13d4f,0x49594000,0x29f6e000)/File(\EFI\MICROSOFT\BOOT\BOOTMGFW.EFI)..BO

Only after rebooting I wouldn’t end up in Manajro (eventhough it’s the first listed) but would end up in the Live CD. When from the LIve CD menu selected “detect EFI bootloaders” it would find manjaro, but I’m not able to boot into it. When rebooting after that, and going to the live CD I can repeat all steps because efibootmgr -v wouldn’t list manjaro anymore.

Any help would be greatly appreciated.

2

Hi @gidogeek,

I’m no expert, but from what I read, it might be necessary for you to install the GRUB boot loader. I might be wrong, but it IS the impression I got.

See GRUB/Restore the GRUB Bootloader - Manjaro for more information.

3

Thanks for trying to help. I think Manjaro Architect took care of reinstalling that. When chrooted into the system and I run

sudo update-grub

I get this output:

Generating grub configuration file ...            │ You will now chroot into your installed system. You can do        │
Found theme: /usr/share/grub/themes/manjaro/theme.txthanges almost as if you had booted into your installation.       │
Found linux image: /boot/vmlinuz-linux-mainline   │                                                                   │
Found initrd image: /boot/intel-ucode.img /boot/amd-ucode.img /boot/initramfs-linux-mainline.imgn to the installer.   │
Found initrd fallback image: /boot/initramfs-linux-mainline-fallback.img                                              │
Found linux image: /boot/vmlinuz-5.9-x86_64       └───────────────────────────────────────────────────────────────────┘
Found initrd image: /boot/intel-ucode.img /boot/amd-ucode.img /boot/initramfs-5.9-x86_64.img
Found initrd fallback image: /boot/initramfs-5.9-x86_64-fallback.img
grub-probe: error: cannot find a GRUB drive for /dev/sdb1.  Check your device.map.
grub-probe: error: cannot find a GRUB drive for /dev/sdb1.  Check your device.map.
Adding boot menu entry for UEFI Firmware Settings ...
done
4

It would seem, to me, that you need to reinstall grub from the chroot environment. From the link:

Restore your GRUB

  1. Install a new GRUB bootloader with grub-install /dev/sda
  2. Recheck to ensure the that installation has completed without any errors grub-install --recheck /dev/sda
  3. Finally, configure the freshly installed GRUB bootloader typing update-grub

Edit:
Something else for reference: Reinstall grub2

Edit 2:
This, to me, looks remarkably to what it sounds like you’re facing: Manjaro: recover GRUB after a Windows Update - YouTube

1 Like
5

This is what I get from that:

[manjaro /]# grub-install --recheck /dev/nvme0p1                
Installing for x86_64-efi platform.
Installation finished. No error reported.
[manjaro /]# update-grub
Generating grub configuration file ...
Found theme: /usr/share/grub/themes/manjaro/theme.txt
Found linux image: /boot/vmlinuz-linux-mainline
Found initrd image: /boot/intel-ucode.img /boot/amd-ucode.img /boot/initramfs-linux-mainline.img
Found initrd fallback image: /boot/initramfs-linux-mainline-fallback.img
Found linux image: /boot/vmlinuz-5.9-x86_64
Found initrd image: /boot/intel-ucode.img /boot/amd-ucode.img /boot/initramfs-5.9-x86_64.img
Found initrd fallback image: /boot/initramfs-5.9-x86_64-fallback.img
grub-probe: error: cannot find a GRUB drive for /dev/sdb1.  Check your device.map.
grub-probe: error: cannot find a GRUB drive for /dev/sdb1.  Check your device.map.
Adding boot menu entry for UEFI Firmware Settings ...
done

Which to mee seems it still can’t locate my manjaro install…

6

I have absolutely no idea what can cause the issue.

Do yourself a favor and double check your BIOS setting. Specifically those regarding booting. Other than that, I have no idea further.

It’s very possible someone else can help, but unfortunately I’m all out of ideas.

1 Like
7

Thanks for trying :slight_smile:

8

You’re welcome! Sorry I couldn’t be of much help.

9

have you tried to remove usb live cd then boot? can you still boot into windows? have you mounted /dev/nvme0n1p1 on /boot/efi or /boot when repairing?

10

Have you tried the easy option of inserting the installation USB
and in the menu you get presented with
scroll down, past the “help” and “memtest” items that are immediately visible

For me, there is then an entry to boot the already installed system
which I didn’t know of it being there.

11

I’ve mounted it on /boot/efi

12

image
image2016×1512 561 KB
image
image2016×1512 462 KB
image
image2016×1512 271 KB
image
image2016×1512 448 KB

13

seems like your windows install efi file in it’s own part, then your UEFI treat that ntfs part as efi part and ignored ‘real’ efi part, so whatever you do with nvme0n1p1, it won’t boot manjaro via grub.

i would advise you install manjaro and Windows in separate disks, each has its own efi part, so they won’t disturb each other when update. it works for me, perfectly.

for now, maybe you can try to change part label(flags?), to make your nvme0n1p1 a real esp part, i don’t know if it works, but even if it works, you may lose your windows, then you need to rebuild windows bootloader on nvme0n1p1( i don’t know if two efi parts are alowed in one disk or if UEFI can recognize two efi parts in one disk)

14

I will suggest doing a full reinstall. It could a case that your grub file is corrupted or something of the sort. You can go back to windows and try and remove the partition and either create a new partition or use the install along side current operating system to avoid issues.

15

I have a Windows10/muliple linux installation.

My Windows 10 has the ability to start a linux installation.

I have a german local so i don’t know the english menue’s

In a running windows start windows system with Win+i key

Look for system restore (?) and there “advanced”?

There i can select my Manjaro and reboot it!

In Manjaro reinstall(!!) grub as mentioned from others

I do it this way ( don’t know if that works for you):

grub-install blkid|grep EFI|awk '{print $1;}'|tr -d ':' && update-grub && reboot

That will reinstall grub to your efi partition, update grub and reboot

Good luck!

Started Win 10 for some screenshots:

image
image878×620 20.7 KB

Win+i

Update und Sicherheit

A) Wiederherstellung
B) Erweiterter Start, Jetzt neu starten
C) Ein Gerät verwenden

Now i see Manjaro button

Another possibility:

SuperGrubDisk from

SuperGrubDisk from sourceforge

Use Rufus on Windows to write that *.img to USB-Stick and reboot from USB-Stick.

Look for Manjaro or partition in SuperGrubDisk menue.

If Manjaro booted: reinstall grub to efi partition.

As i just see, you have TWO EFI partitions … no idea how to handle that!

1 Like
16

Excuse my curiosity, but may I ask whether
/dev/nvme0p1
referes to a device or to a partition?

Asking cause I noticed Midhartos had adviced to install grub to the device /dev/sda which might make a big difference.

17

/dev/nvme0p1 refers to the partition, AFAIK.

The device would be, according to me, /dev/nvme0.

18