[Solved?] Dual Boot not working as intended.

If none of the more specific forums is the right place to ask

[Solved?] Dual Boot not working as intended.

Postby Coulomb » 2019-12-28 19:18

I can not boot Windows 10 after I boot into linux. I get an error: https://i.imgur.com/uD44pKK.jpg

But the weird thing is that AFTER I boot into Windows 10 from its own bootloader (which sits on a different physical drive), I can boot again using grub. even though It looks different. Normally when booting, I don't see the blue windows 10 logo.

the issue is reproduceable by these steps:

1: normal boot: https://i.imgur.com/RLlUF5U.jpg

2: boot via grub: https://i.imgur.com/SjwC4tg.jpg

3: boot debian ...

4: boot Windows 10 from grub: https://i.imgur.com/uD44pKK.jpg

5: boot windows 10 via its own bootloader: https://i.imgur.com/RLlUF5U.jpg

...


Edit: Sorry I cannot include thumbnails to the pictures, I get an internal server error when I attempt to do that :cry:
Last edited by Coulomb on 2020-01-02 18:58, edited 1 time in total.
Coulomb
 
Posts: 15
Joined: 2019-10-26 07:07

Re: Dual Boot not working as intended.

Postby Dai_trying » 2019-12-28 22:45

Depending on your firmware you might need to simply set the boot order to pick up the esp partition to use.

I have had a similar issue, in my case I had two different esp partitions and my system was reading the wrong one, I could select the boot options from the UEFI settings and then manually boot a specific device, or point to the esp partition to use.
Dai_trying
 
Posts: 858
Joined: 2016-01-07 12:25

Re: Dual Boot not working as intended.

Postby Coulomb » 2019-12-29 07:27

As far as the UEFI Bios is concerned, it does pick up the esp partition where the grub bootloader is located. but that is not the issue.

again for clarification:

nvme drive: windows bootloader
ssd drive: grub bootloader

If I boot from the ssd, i.e. boot grub, I have the option to boot windows and linux.
But trying to boot into windows fails (https://i.imgur.com/uD44pKK.jpg
) as grub does not find the windows drive/partition...

I can boot into linux just fine. But I want to be able to boot into windows using grub

how do I trouble-shoot this?
Coulomb
 
Posts: 15
Joined: 2019-10-26 07:07

Re: Dual Boot not working as intended.

Postby Dai_trying » 2019-12-29 07:37

have you updated grub? usually it can pick up other OS's although if the bootloader is on another esp partition I'm not sure how that will work... My understanding is you should only have one...

What I would do if it were me would be to re-install grub but install it to the esp partition that has the windows bootloader, it is not like the old days where grub will overwrite the boot sector, with efi it will create its own folder with it's own boot config stuff, I would imagine this would solve your issue.
Dai_trying
 
Posts: 858
Joined: 2016-01-07 12:25

Re: Dual Boot not working as intended.

Postby Coulomb » 2019-12-29 08:11

Like I mentioned I have also Ubuntu on the same ssd. The weird thing is that if I boot into Ubuntu and use the Grub-Customizer, I can boot windows just fine from grub. Sine I'm mainly using debian these days I wanted to "manage" the grub bootloader in debian.

What I don't understand is why the grub-bootloader that Ubuntu installs works, the one that debian installs doesn't.

There are other differences as well. Like larger fonts and different UI scaling during the boot process.

I can go back to ubuntu, run update-grub from there and it works.

The reason I wanted to keep the bootloaders for Windows and Linux on physically seperate Drives is because of that issue. Now at least I can boot into windows, but what if I install grub on that parturition and cannot boot at all...


So to reiterate: grub-customizer when ran from Ubuntu works just fine. It is only when I ran these commands from Debian that I run into issues when trying to boot Windows from grub. there must be something that can be tweaked
Coulomb
 
Posts: 15
Joined: 2019-10-26 07:07

Re: Dual Boot not working as intended.

Postby p.H » 2019-12-29 08:39

1) Please post the output of the following commands from Debian.
Code: Select all
efibootmgr -v
blkid
fdisk -l

2) Post the Windows menu entry in /boot/grub/grub.cfg.
3) At the GRUB boot screen press "c" to enter the command line and post the output of "ls".
p.H
 
Posts: 1225
Joined: 2017-09-17 07:12

Re: Dual Boot not working as intended.

Postby Coulomb » 2019-12-29 09:31

efibootmgr -v
Code: Select all
phil@debian:~$ efibootmgr -v
BootCurrent: 0004
Timeout: 1 seconds
BootOrder: 0004,0001,0000,000B,000C,0005,0003,000D,000E,0002,0006,0007
Boot0000* Windows Boot Manager   HD(2,GPT,d023ba8a-2b4b-4311-acd6-aa1c60d4cbae,0xfa000,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.4.7.9.5.}...d................
Boot0001* ubuntu   HD(2,GPT,d023ba8a-2b4b-4311-acd6-aa1c60d4cbae,0xfa000,0x32000)/File(\EFI\UBUNTU\SHIMX64.EFI)
Boot0002* UEFI:CD/DVD Drive   BBS(129,,0x0)
Boot0003* kali   HD(2,GPT,d023ba8a-2b4b-4311-acd6-aa1c60d4cbae,0xfa000,0x32000)/File(\EFI\KALI\GRUBX64.EFI)
Boot0004* debian   HD(2,GPT,d023ba8a-2b4b-4311-acd6-aa1c60d4cbae,0xfa000,0x32000)/File(\EFI\DEBIAN\SHIMX64.EFI)
Boot0005* steamos   HD(2,GPT,d023ba8a-2b4b-4311-acd6-aa1c60d4cbae,0xfa000,0x32000)/File(\EFI\STEAMOS\GRUBX64.EFI)
Boot0006* UEFI:Removable Device   BBS(130,,0x0)
Boot0007* UEFI:Network Device   BBS(131,,0x0)
Boot000B* UEFI: SanDisk, Partition 1   PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x2)/USB(0,0)/HD(1,MBR,0xd5946f2e,0x20,0xe51ffe0)..BO
Boot000C* UEFI: Lexar CF USB_3_0 Read0576, Partition 1   PciRoot(0x0)/Pci(0x14,0x0)/USB(16,0)/USB(3,0)/HD(1,MBR,0x0,0x3f,0x7743fc1)..BO
Boot000D* debian   HD(2,GPT,d023ba8a-2b4b-4311-acd6-aa1c60d4cbae,0xfa000,0x32000)/File(\EFI\DEBIAN\GRUBX64.EFI)..BO
Boot000E* debian   HD(1,GPT,0c5a8cf6-107f-48b7-8d9a-bf4c94e8d086,0x22,0x807de)/File(\EFI\debian\grubx64.efi)..BO


blkid
Code: Select all
/dev/nvme0n1p1: LABEL="Recovery" UUID="C02A3D572A3D4C22" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="c3ea05b6-f467-4f17-9759-1dfe19b72e02"
/dev/nvme0n1p2: UUID="5848-9D29" TYPE="vfat" PARTLABEL="EFI system partition" PARTUUID="d023ba8a-2b4b-4311-acd6-aa1c60d4cbae"
/dev/nvme0n1p4: UUID="E452638E526363F0" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="8ef24ff9-bd24-4ab5-8a98-d89e3e10c483"
/dev/sdd2: LABEL="amazon" UUID="02EC6352EC633F53" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="a84612c9-0035-4bd3-b972-542b5c4e6a6b"
/dev/sdc1: LABEL="8Ball" UUID="085D177E085D177E" TYPE="ntfs" PTTYPE="atari" PARTLABEL="My Book" PARTUUID="5446ee86-d4c8-438b-b7c0-be7408d023ea"
/dev/sdc2: UUID="c24e63f7-3c6a-40fc-9916-ddcd80c72843" TYPE="swap" PARTLABEL="ubuntu" PARTUUID="707d9d0e-7132-4dea-b76f-ba4a94d803ab"
/dev/sdc3: UUID="cfbb9f52-f2f7-4f90-a434-342a9cbe290b" TYPE="swap" PARTLABEL="debian" PARTUUID="28045d45-8741-4978-84fd-e1ba2ab26389"
/dev/sdc4: UUID="aa4cb112-c15d-4ca9-9aa1-071b51f8defd" TYPE="swap" PARTLABEL="mint/manjaro" PARTUUID="af79e3d4-17eb-490e-81fc-82dde1e7c769"
/dev/sdf1: UUID="4AE0-85D2" TYPE="vfat" PARTUUID="0c5a8cf6-107f-48b7-8d9a-bf4c94e8d086"
/dev/sdf2: UUID="5c597227-6d8e-4136-a9f1-4612d66f1a19" TYPE="ext4" PARTLABEL="ubuntu" PARTUUID="a0c1163e-42d8-4605-bb82-e4889e0cd345"
/dev/sdf3: UUID="53bac549-35da-4cee-927a-2c3ee54ccecd" TYPE="ext4" PARTLABEL="debian" PARTUUID="64dd8af7-340d-4d52-aef9-6a80a3d25376"
/dev/sdf4: UUID="5010b0be-7a97-46d4-9713-8c18e7ae3254" TYPE="ext4" PARTLABEL="mint/manjaro" PARTUUID="6e61d61c-0532-48bf-9cd8-77c2547364c7"
/dev/sde2: LABEL="TessesD" UUID="46AC3AFAAC3AE3D9" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="1ca5bebe-93d4-4046-9287-d1a621391c73"
/dev/sdb1: LABEL="0.5TB SSData2" UUID="144EF2684EF24252" TYPE="ntfs" PARTUUID="e3f462f3-01"
/dev/sda1: LABEL="1TB SSData" UUID="C46CA2E46CA2D10A" TYPE="ntfs" PARTUUID="baf345ce-01"
/dev/sdg1: LABEL="LightRoom" UUID="B2EE1BBDEE1B7935" TYPE="ntfs" PARTUUID="c7a94f3b-781d-8702-c124-7507f1c739f8"
/dev/sdh1: LABEL="GoogleDrive" UUID="36B5-4C75" TYPE="exfat" PARTUUID="d5946f2e-01"
/dev/nvme0n1: PTUUID="890cc01e-987d-4f3c-afaa-cbc23b100130" PTTYPE="gpt"
/dev/nvme0n1p3: PARTLABEL="Microsoft reserved partition" PARTUUID="026e0b93-eee1-4fc4-a27d-f9b9b12d5969"
/dev/sdd1: PARTLABEL="Microsoft reserved partition" PARTUUID="4a9a3c69-4c7e-4e8b-a86e-a019201ec662"
/dev/sde1: PARTLABEL="Microsoft reserved partition" PARTUUID="4a9e3224-a6b6-46fd-9e8e-90ad28cdd653"
/dev/sdi1: LABEL_FATBOOT="EOS_DIGITAL" LABEL="EOS_DIGITAL" UUID="1675-1251" TYPE="vfat"


fdisk -l
Code: Select all
Disk /dev/nvme0n1: 232.9 GiB, 250059350016 bytes, 488397168 sectors
Disk model: Samsung SSD 960 EVO 250GB               
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: 890CC01E-987D-4F3C-AFAA-CBC23B100130

Device           Start       End   Sectors   Size Type
/dev/nvme0n1p1    2048   1023999   1021952   499M Windows recovery environment
/dev/nvme0n1p2 1024000   1228799    204800   100M EFI System
/dev/nvme0n1p3 1228800   1261567     32768    16M Microsoft reserved
/dev/nvme0n1p4 1261568 488394751 487133184 232.3G Microsoft basic data


Disk /dev/sdd: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: CT1000MX500SSD1
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: 158749EE-2C0D-4178-A44D-85BD359E7E7A

Device     Start        End    Sectors   Size Type
/dev/sdd1     34      32767      32734    16M Microsoft reserved
/dev/sdd2  32768 1953521663 1953488896 931.5G Microsoft basic data

Partition 1 does not start on physical sector boundary.


Disk /dev/sdc: 7.3 TiB, 8001563222016 bytes, 15628053168 sectors
Disk model: WDC WD80EZAZ-11T
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: 7DA955F5-1E34-4EBA-AE7C-BBCA14F1EC6C

Device           Start         End     Sectors  Size Type
/dev/sdc1         2048 15346749439 15346747392  7.1T Microsoft basic data
/dev/sdc2  15346749440 15432828927    86079488   41G Linux swap
/dev/sdc3  15432828928 15529660415    96831488 46.2G Linux swap
/dev/sdc4  15529660416 15628052479    98392064 46.9G Linux swap


Disk /dev/sdf: 223.6 GiB, 240057409536 bytes, 468862128 sectors
Disk model: Crucial_CT240M50
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: CD46154D-1C46-404F-BCF9-45F43CF77DDF

Device         Start       End   Sectors   Size Type
/dev/sdf1         34    526335    526302   257M EFI System
/dev/sdf2     526336 235629851 235103516 112.1G Linux filesystem
/dev/sdf3  235630592 359378943 123748352    59G Linux filesystem
/dev/sdf4  359378944 468860927 109481984  52.2G Linux filesystem

Partition 1 does not start on physical sector boundary.


Disk /dev/sde: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: SanDisk SDSSDH3
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: BA3E747D-A2E2-4393-8D25-3A1F17297660

Device     Start        End    Sectors   Size Type
/dev/sde1     34      32767      32734    16M Microsoft reserved
/dev/sde2  32768 1953521663 1953488896 931.5G Microsoft basic data


Disk /dev/sdb: 447.1 GiB, 480103981056 bytes, 937703088 sectors
Disk model: Crucial_CT480M50
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: 0xe3f462f3

Device     Boot Start       End   Sectors   Size Id Type
/dev/sdb1  *     2048 937699327 937697280 447.1G  7 HPFS/NTFS/exFAT


Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: Samsung SSD 840
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: dos
Disk identifier: 0xbaf345ce

Device     Boot Start        End    Sectors   Size Id Type
/dev/sda1        2048 1953521663 1953519616 931.5G  7 HPFS/NTFS/exFAT


Disk /dev/sdg: 119.2 GiB, 128035676160 bytes, 250069680 sectors
Disk model: 2115           
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 33553920 bytes
Disklabel type: gpt
Disk identifier: C72EFD2A-00A8-4A14-A7A1-90F030C35F89

Device     Start       End   Sectors   Size Type
/dev/sdg1     40 250067597 250067558 119.2G Microsoft basic data


Disk /dev/sdh: 114.6 GiB, 123010547712 bytes, 240254976 sectors
Disk model: Ultra USB 3.0   
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: dos
Disk identifier: 0xd5946f2e

Device     Boot Start       End   Sectors   Size Id Type
/dev/sdh1          32 240254975 240254944 114.6G  7 HPFS/NTFS/exFAT


Disk /dev/sdi: 59.6 GiB, 64030244864 bytes, 125059072 sectors
Disk model: CF  USB_3_0 Read
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: dos
Disk identifier: 0x00000000

Device     Boot Start       End   Sectors  Size Id Type
/dev/sdi1          63 125059071 125059009 59.6G  c W95 FAT32 (LBA)


___
/boot/grub/grub.cfg
Code: Select all
### BEGIN /etc/grub.d/40_custom_proxy ###
menuentry "Windows Boot Manager (on /dev/nvme0n1p2)" --class windows --class os $menuentry_id_option 'osprober-efi-5848-9D29' {
   insmod part_gpt
   insmod fat
   if [ x$feature_platform_search_hint = xy ]; then
     search --no-floppy --fs-uuid --set=root  5848-9D29
   else
     search --no-floppy --fs-uuid --set=root 5848-9D29
   fi
   chainloader /EFI/Microsoft/Boot/bootmgfw.efi
}
### END /etc/grub.d/40_custom_proxy ###



grub ls

Code: Select all
(proc) (hd0) (hd0,msdos1) (hd1) (hd1,msdos1) (hd2)(hd2,gpt1) (hd3) (hd3,msdos1) (hd4) (hd4,msdos1) (hd5) (hd5,gpt4) (hd5,gpt3) (hd5,gpt2) (hd5,gpt1) (hd6) (hd6,gpt2) (hd6,gpt1) (hd7) (hd7,gpt2) (hd7,gpt1) (hd8) (hd8,gpt4) (hd8,gpt3) (hd8,gpt2) (hd8,gpt1) (hd9) (hd9,gpt4) (hd9,gpt3) (hd9,gpt2) (hd9,gpt1)
Coulomb
 
Posts: 15
Joined: 2019-10-26 07:07

Re: Dual Boot not working as intended.

Postby Head_on_a_Stick » 2019-12-29 18:22

Both GRUB and the firmware boot entries are looking at /dev/nvme0n1p2 for the EFI loaders and according to the error message Windows' bootmgfw.efi loader isn't there.

Check with
Code: Select all
# mount /dev/nvme0n1p2 /mnt
find /mnt -name bootmgfw.efi
# umount /mnt

Then see if it's on /dev/sdf1

Make a custom entry for the other ESP with this file at /boot/grub/custom.cfg:
Code: Select all
menuentry "Windows Boot Manager (on /dev/sdf1)" --class windows --class os $menuentry_id_option 'osprober-efi-4AE0-85D2' {
   insmod part_gpt
   insmod fat
   if [ x$feature_platform_search_hint = xy ]; then
     search --no-floppy --fs-uuid --set=root  4AE0-85D2
   else
     search --no-floppy --fs-uuid --set=root 4AE0-85D2
   fi
   chainloader /EFI/Microsoft/Boot/bootmgfw.efi
}
User avatar
Head_on_a_Stick
 
Posts: 11021
Joined: 2014-06-01 17:46
Location: /dev/chair

Re: Dual Boot not working as intended.

Postby p.H » 2019-12-30 10:45

Head_on_a_Stick wrote:Both GRUB and the firmware boot entries are looking at /dev/nvme0n1p2 for the EFI loaders

I agree.
Head_on_a_Stick wrote:according to the error message Windows' bootmgfw.efi loader isn't there.

I disagree. According to the first error message, GRUB does not find the partition with the searched UUID, although the searched UUID seems correct. The second error message is only a consequence of the first error.

I would be very surprised if Windows boot loader was not in the EFI partition of the same drive as the Windows installation.
But it is worth checking.
p.H
 
Posts: 1225
Joined: 2017-09-17 07:12

Re: Dual Boot not working as intended.

Postby Coulomb » 2019-12-30 13:21

Head_on_a_Stick wrote:according to the error message Windows' bootmgfw.efi loader isn't there.



I would be very surprised if Windows boot loader was not in the EFI partition of the same drive as the Windows installation.
But it is worth checking.[/quote]

The Windows Bootloader is on a 100mb EFI Partition on the nvme-drive, i.e. the drive that Windows is installed on, i.e. the same physical drive.

Head_on_a_Stick wrote:Both GRUB and the firmware boot entries are looking at /dev/nvme0n1p2 for the EFI loaders and according to the error message Windows' bootmgfw.efi loader isn't there.

Check with
Code: Select all
# mount /dev/nvme0n1p2 /mnt
find /mnt -name bootmgfw.efi
# umount /mnt

Then see if it's on /dev/sdf1

Make a custom entry for the other ESP with this file at /boot/grub/custom.cfg:
Code: Select all
menuentry "Windows Boot Manager (on /dev/sdf1)" --class windows --class os $menuentry_id_option 'osprober-efi-4AE0-85D2' {
   insmod part_gpt
   insmod fat
   if [ x$feature_platform_search_hint = xy ]; then
     search --no-floppy --fs-uuid --set=root  4AE0-85D2
   else
     search --no-floppy --fs-uuid --set=root 4AE0-85D2
   fi
   chainloader /EFI/Microsoft/Boot/bootmgfw.efi
}


Thanks, I will try that later when I have time.

I want to point out two things again:
1 if I use the grub-customizer in Ubuntu, I can boot into Linux and Windows no problem. The issues only arise when I use grub-customizer on debian.

2 The grub-bootloader only doesn't find the partition with the Windows bootloader AFTER I booted into any Linux distribution once.

If that happens, and grub does not find the windows bootloader-partition, I need to interfere with the boot-process. That means hitting F8 to bring up the UEFI Bios's boot-selector, I can select Windows, the system boots. I restart, THEN grub finds the partition again. I can restart the machine many times without issues, but once I boot a Linux distro again, grub won't find the Windows bootloader.
Coulomb
 
Posts: 15
Joined: 2019-10-26 07:07

Re: Dual Boot not working as intended.

Postby p.H » 2019-12-31 10:25

One note :
Coulomb wrote:nvme drive: windows bootloader
ssd drive: grub bootloader

But according to the EFI boot entries, most GRUB bootloaders, including Debian's one (Boot0004), Ubuntu, Kali, SteamOS, are in the same EFI partition as Windows.
There is only one Debian entry in the other EFI partition (Boot000E), but it is not the one which was booted (BootCurrent).

Coulomb wrote:1 if I use the grub-customizer in Ubuntu, I can boot into Linux and Windows no problem. The issues only arise when I use grub-customizer on debian.

Why do you use grub-customizer ? What happens if you don't use it ?

Coulomb wrote:2 The grub-bootloader only doesn't find the partition with the Windows bootloader AFTER I booted into any Linux distribution once.

What happens if you select Windows in GRUB right after power-on, without booting any Linux system before ?
p.H
 
Posts: 1225
Joined: 2017-09-17 07:12

Re: Dual Boot not working as intended.

Postby Coulomb » 2020-01-01 18:26

p.H wrote:One note :

But according to the EFI boot entries, most GRUB bootloaders, including Debian's one (Boot0004), Ubuntu, Kali, SteamOS, are in the same EFI partition as Windows.
There is only one Debian entry in the other EFI partition (Boot000E), but it is not the one which was booted (BootCurrent).


This is because I have installed many Linux distros before on my system to experiment a bit. The reason they are on the same EFI Partition as Windows was before I dedicated a seperate physical ssd drive to the three Distros I have now (ubuntu, mint and debian) I used my partitioned nvme-drive. I have since got rid of these and the nvme drive is exclusive for windows. However, the entries still remain. Mounting the partition /dev/nvme0n1p2 contains the folders
boot
debian
kali
Microsoft
steamos
ubuntu

But as far as I'm concerned these are leftovers from my very early experimentations. The only real bootloader on that drive is supposed to be the windows one. I was never sure if I could just delete them, and didn't find another way to get rid of them


p.H wrote:Why do you use grub-customizer ? What happens if you don't use it ?


I am using the grub-customizer out of convenience. I like to add pictures and have a gui for playing with fonts and margins. But on debian I have also done it using command line only, following this guide: https://wiki.debian.org/GrubEFIReinstall - which had the same result.

p.H wrote:What happens if you select Windows in GRUB right after power-on, without booting any Linux system before ?


Then the system boots Windows. But it does not boot it the same way as if I boot directly into windows. Directly meaning selecting Windows 10 bootloader form UEFI-Bios, not selecting Grub

Selecting the Windows 10 bootloader directly AND using grub-customizer in Ubuntu is 100% success and Windows 10 boots without the logo: https://i.imgur.com/RLlUF5U.jpg

Installing grub through Debian fails to boot Windows 10 after having booted into a linux Distro and shows the blue Windows 10 Logo: https://imgur.com/SjwC4tg


__

Head_on_a_Stick wrote:
I would be very surprised if Windows boot loader was not in the EFI partition of the same drive as the Windows installation.
But it is worth checking.


The Windows Bootloader is on a 100mb EFI Partition on the nvme-drive, i.e. the drive that Windows is installed on, i.e. the same physical drive.

Head_on_a_Stick wrote:Both GRUB and the firmware boot entries are looking at /dev/nvme0n1p2 for the EFI loaders and according to the error message Windows' bootmgfw.efi loader isn't there.

Check with
Code: Select all
# mount /dev/nvme0n1p2 /mnt
find /mnt -name bootmgfw.efi
# umount /mnt

Then see if it's on /dev/sdf1

It is on /dev/nvme01p2 located under /EFI/Microsoft/Boot/bootmgfw.efi - but this bootloader is not on /dev/sdf1. In fact, /dev/sdf1 only contains 1 folder, called debian.

Head_on_a_Stick wrote:Make a custom entry for the other ESP with this file at /boot/grub/custom.cfg:
Code: Select all
menuentry "Windows Boot Manager (on /dev/sdf1)" --class windows --class os $menuentry_id_option 'osprober-efi-4AE0-85D2' {
   insmod part_gpt
   insmod fat
   if [ x$feature_platform_search_hint = xy ]; then
     search --no-floppy --fs-uuid --set=root  4AE0-85D2
   else
     search --no-floppy --fs-uuid --set=root 4AE0-85D2
   fi
   chainloader /EFI/Microsoft/Boot/bootmgfw.efi
}


So now it seems to work. I have just placed the file inside the location and have not ran the commands
Code: Select all
grub-install
or
Code: Select all
update-grub
. I have booted my computer now 15 times going through all the linux distros and Windows. No error message so far!
Coulomb
 
Posts: 15
Joined: 2019-10-26 07:07


Return to General Questions

Who is online

Users browsing this forum: No registered users and 8 guests

fashionable