Dual boot with Windows 10 EFI on a separate disk (NVMe)

Newbie Corner
, ,
#1

Hello
I had Windows 10 EFI install on the NVMe drive. I installed Manjaro EFI on the HDD. /boot/efi is also on the HDD. Grub found my Windows 10 and even able to boot Windows 10 if I start UEFI menu first or reboot from Windows. But if I try to boot Windows after rebooting from Manjaro I have following error:

error: no such device: 4074-F391.
error: file '/efi/Microsoft/Boot/bootmgfw.efi' not found.

SysInfo:

$ sudo parted --list
Model: ATA SPCC Solid State (scsi)
Disk /dev/sda: 120GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: 

Number  Start   End    Size   File system  Name                          Flags
 1      17,4kB  134MB  134MB               Microsoft reserved partition  msftres
 2      135MB   120GB  120GB  ntfs         Basic data partition          msftdata


Model: ATA WDC WD10EZEX-60Z (scsi)
Disk /dev/sdb: 1000GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt
Disk Flags: 

Number  Start   End     Size    File system     Name  Flags
 1      1049kB  839GB   839GB   ntfs                  msftdata
 2      839GB   840GB   1074MB  fat32                 boot, hidden, esp
 3      840GB   872GB   32,2GB  ext4
 4      872GB   980GB   107GB   ext4
 5      980GB   1000GB  20,4GB  linux-swap(v1)


Model: Unknown (unknown)
Disk /dev/nvme0n1: 250GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: 

Number  Start   End    Size    File system  Name                          Flags
 1      1049kB  524MB  523MB   ntfs         Basic data partition          hidden, diag
 2      524MB   629MB  105MB   fat32        EFI system partition          boot, esp
 3      629MB   646MB  16,8MB               Microsoft reserved partition  msftres
 4      646MB   225GB  224GB   ntfs         Basic data partition          msftdata
 5      225GB   225GB  511MB   ntfs                                       hidden, diag


$ sudo efibootmgr -v
BootCurrent: 0007
Timeout: 1 seconds
BootOrder: 0007,0005,0001,0000,0009,0002,0003,0004
Boot0000* Windows Boot Manager  HD(2,GPT,ecd779ca-937f-46c9-b260-e46113ffa3ca,0xfa008,0x32008)/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.4.7.9.5.}....................
Boot0001* Manjaro       HD(2,GPT,bf077e0b-3739-4535-9dbf-5bf6a7d419d8,0x61b06000,0x200000)/File(\EFI\Manjaro\grubx64.efi)
Boot0002* UEFI:CD/DVD Drive     BBS(129,,0x0)
Boot0003* UEFI:Removable Device BBS(130,,0x0)
Boot0004* UEFI:Network Device   BBS(131,,0x0)
Boot0005* Windows Boot Manager  HD(2,GPT,ecd779ca-937f-46c9-b260-e46113ffa3ca,0xfa000,0x32000)/File(\EFI\Microsoft\Boot\bootmgfw.efi)
Boot0007* UEFI OS       HD(2,GPT,bf077e0b-3739-4535-9dbf-5bf6a7d419d8,0x61b06000,0x200000)/File(\EFI\BOOT\BOOTX64.EFI)
Boot0009* Hard Drive    BBS(HD,,0x0)..GO..NO........O.W.D.C. .W.D.1.0.E.Z.E.X.-.6.0.Z.F.5.A.0.................>..Gd-.;.A..MQ..L. . . . .W. .-.D.M.W.1.C.6.S.2.5.9.4.7.5........BO..NO........O.S.P.C.C. .S.o.l.i.d. .S.t.a.t.e. .D.i.s.k.................>..Gd-.;.A..MQ..L.E.F.A.C.7.0.6.4.0.1.8.0.0.0.0.4.6.5.0.5........BO..NO........y.S.a.m.s.u.n.g. .S.S.D. .9.7.0. .E.V.O. .2.5.0.G.B. .S.4.6.5.N.B.0.K.6.1.2.1.2.2.B.................h..Gd-.;.A..MQ..L.S.a.m.s.u.n.g. .S.S.D. .9.7.0. .E.V.O. .2.5.0.G.B. .S.4.6.5.N.B.0.K.6.1.2.1.2.2.B........BO
#2

Please post

inxi -SMCDpuo
cat /etc/fstab
#3 
$ inxi -SMCDpuo
System:    Host: Valhalla Kernel: 4.19.0-2-MANJARO x86_64 bits: 64 Desktop: KDE Plasma 5.14.2 Distro: Manjaro Linux 
Machine:   Type: Desktop System: ASUS product: All Series v: N/A serial: <root required> 
           Mobo: ASUSTeK model: MAXIMUS VI FORMULA v: Rev 1.xx serial: <root required> UEFI: American Megatrends v: 1603 
           date: 08/15/2014 
CPU:       Topology: Quad Core model: Intel Core i5-4670 bits: 64 type: MCP L2 cache: 6144 KiB 
           Speed: 798 MHz min/max: 800/3800 MHz Core speeds (MHz): 1: 798 2: 798 3: 798 4: 798 
Drives:    Local Storage: total: 1.25 TiB used: 195.43 GiB (15.3%) 
           ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 970 EVO 250GB size: 232.89 GiB 
           ID-2: /dev/sda model: SPCC Solid State Disk size: 111.79 GiB 
           ID-3: /dev/sdb vendor: Western Digital model: WD10EZEX-60ZF5A0 size: 931.51 GiB 
Partition: ID-1: / size: 29.40 GiB used: 19.68 GiB (66.9%) fs: ext4 dev: /dev/sdb3 uuid: 7d28817e-e8b5-45e3-b0ba-feee44cd148d 
           ID-2: /boot/efi size: 1022.0 MiB used: 276 KiB (0.0%) fs: vfat dev: /dev/sdb2 uuid: F299-F6C0 
           ID-3: /home size: 97.93 GiB used: 17.66 GiB (18.0%) fs: ext4 dev: /dev/sdb4 
           uuid: 1c86eaa0-d336-4fdd-a6e3-e2e4d1f609e3 
           ID-4: /media/Files size: 781.51 GiB used: 158.08 GiB (20.2%) fs: ntfs dev: /dev/sdb1 uuid: 01D3B6C4D970F420 
           ID-5: /media/NAS/Multimedia size: 3.54 TiB used: 3.15 TiB (89.2%) fs: cifs remote: //192.168.0.100/Multimedia 
           uuid: N/A 
           ID-6: /media/NAS/serjflint size: 3.54 TiB used: 3.15 TiB (89.2%) fs: cifs remote: //192.168.0.100/serjflint 
           uuid: N/A 
           ID-7: /media/USB/Multimedia size: 3.54 TiB used: 3.15 TiB (89.2%) fs: cifs remote: //198.18.0.81/Multimedia 
           uuid: N/A 
           ID-8: /media/USB/serjflint size: 3.54 TiB used: 3.15 TiB (89.2%) fs: cifs remote: //198.18.0.81/serjflint uuid: N/A 
           ID-9: swap-1 size: 19.00 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sdb5 uuid: 776f91bb-5268-4fe5-8e5c-a28696d24a4a 
Unmounted: ID-1: /dev/nvme0n1p1 size: 499.0 MiB fs: ntfs 
           label: \xd0\x92\xd0\xbe\xd1\x81\xd1\x81\xd1\x82\xd0\xb0\xd0\xbd\xd0\xbe\xd0\xb2\xd0\xb8\xd1\x82\xd1\x8c 
           uuid: 301A70741A703944 
           ID-2: /dev/nvme0n1p2 size: 100.0 MiB fs: vfat label: N/A uuid: 4074-F391 
           ID-3: /dev/nvme0n1p3 size: 16.0 MiB fs: <root required> label: N/A uuid: N/A 
           ID-4: /dev/nvme0n1p4 size: 208.52 GiB fs: ntfs label: Samsung 970 EVO uuid: 24C47F7CC47F4ED4 
           ID-5: /dev/nvme0n1p5 size: 487.0 MiB fs: ntfs label: N/A uuid: E4D00D22D00CFD14 
           ID-6: /dev/sda1 size: 128.0 MiB fs: <root required> label: N/A uuid: N/A 
           ID-7: /dev/sda2 size: 111.66 GiB fs: ntfs label: SSD uuid: 9A0C7C150C7BEB21 

$ cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a device; this may
# be used with UUID= as a more robust way to name devices that works even if
# disks are added and removed. See fstab(5).
#
# <file system>             <mount point>  <type>  <options>  <dump>  <pass>
UUID=F299-F6C0                            /boot/efi      vfat    defaults,noatime 0 2
UUID=7d28817e-e8b5-45e3-b0ba-feee44cd148d /              ext4    defaults,noatime 0 1
UUID=1c86eaa0-d336-4fdd-a6e3-e2e4d1f609e3 /home          ext4    defaults,noatime 0 2
UUID=776f91bb-5268-4fe5-8e5c-a28696d24a4a swap           swap    defaults,noatime 0 2
//192.168.0.100/serjflint   /media/NAS/serjflint         cifs    noauto,x-systemd.automount,nofail,x-systemd.device-timeout=10,_netdev,workgroup=workgroup,credentials=/root/.cifs 0 0
//192.168.0.100/Multimedia  /media/NAS/Multimedia        cifs    noauto,x-systemd.automount,nofail,x-systemd.device-timeout=10,_netdev,workgroup=workgroup,credentials=/root/.cifs 0 0
//198.18.0.81/serjflint     /media/USB/serjflint         cifs    noauto,x-systemd.automount,nofail,x-systemd.device-timeout=10,_netdev,workgroup=workgroup,credentials=/root/.cifs 0 0
//198.18.0.81/Multimedia    /media/USB/Multimedia        cifs    noauto,x-systemd.automount,nofail,x-systemd.device-timeout=10,_netdev,workgroup=workgroup,credentials=/root/.cifs 0 0
LABEL=Files                 /media/Files                 ntfs-3g rw,nosuid,nodev,nofail,allow_other 0 0
#4

Short answer: There is no issue, live with it. :grin:

Long answer: It is the hardware/BIOS that decides/sees how/where to boot, looking for esps and entries. Booting normally works fine, so your system works. Rebooting from linux seems to bypass some part of interrogation with hardware, keeping it from scanning properly for devices. It looks at booted grub, sitting on a different $esp than Windows, while a hardware scan and mount has not been done, so Windows $esp is not visible.
By experience, some hardware work fine on reboot, while others not.
At least, this is my personal experience. Maybe someone else may know more..

#5

Tried to search for similar issues. Disabling Fast Boot solved the problem.

2 Likes
#6

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.

Forum kindly sponsored by