1

I have a dual boot setup with:

  • A fresh installation of Arch Linux (manual) on a SATA HDD
  • Windows 11 installed on an NVMe M.2 SSD

Grub is installed on the HDD, and both operating systems are installed in UEFI mode.

My boot order is:

  1. SATA HDD (Grub, Arch)
  2. NVMe SSD (Windows Boot Manager, Windows 11)
  3. USB (Ventoy)

When I boot directly into Windows from the UEFI/BIOS and upon reboot into default boot, GRUB can successfully chainload Windows from the NVMe drive.
However, upon booting into Arch, rebooting, and selecting Windows from the GRUB menu, GRUB fails to chainload with the following error:

error: no such device: 72BE-12C2
error: file 'EFI/Microsoft/Boot/bootmgfw.efi' not found

In the GRUB shell, ls does not list the NVMe SSD at all. From what I have gathered, this means GRUB loses any visibility of the NVMe device after Arch is booted; however, I may be mistaken.

I have tried:

  • Mounting /dev/nvme0n1p1 to /boot/windows and running os-probe and then grub-mkconfig -o /boot/grub/grub.cfg which both successfully state that /dev/nvme0n1p1@/efi/Microsoft/Boot/bootmgfw.efi:Windows Boot Manager:Windows:efi has been found and in turn added to the boot list.
  • Manual GRUB entry
  • Verifying the correct UUID via lsblk -f which returns
├─nvme0n1p1 vfat FAT32 72BE-12C2
  • I have ensured that Fast Startup is disabled on Windows.
  • Both OSes are using UEFI
  • Arch is not mounting or modifying the EFI partition
Improve this question
5
  • Whenever there are major updates in the Windows side, one typically has to update GRUB on the Linux side. In Debian derived OSes we use sudo update-grub , a nice and convenient script. You need to find the equivalent for Arch. Commented Jun 11 at 19:48
  • 1
    And, of course, when dual-booting, disabling the Windows' Fast Startup feature is a must. Commented Jun 11 at 19:49
  • The EFI environment can provide some forms of low-level access to block-devices. Some parts of this environment even survive a reboot. It is quite possible that either GRUB, the Linux kernel or even the EFI firmware implementation change the environment in such a way the access to NVME devices is lost or purposely unloaded (since the successful boot happened from the SATA HDD). Can you install GRUB onto the NVME and check whether that provides a consistent path to booting either system? Commented Jun 12 at 0:08
  • @ChanganAuto I have ensured that the startup feature was disabled Commented Jun 19 at 6:49
  • however, I may be mistaken I don't think you are. I suppose it comes back when you do a "cold reboot"? (Like shutdown and power on instead of just "reboot")? See if there are UEFI and SSD firmware updates for your devices. Also see if disabling "fast boot" and anything alike in the UEFI firmware setting (i.e. NOT Windows Fast Startup) helps. (You may also consider filing a kernel bug report, but...) Commented Sep 18 at 5:52

0

Reset to default

You must log in to answer this question.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.