Windows boot manager not showing in grub menu

While following the article, I ran into issue:

[liveuser@eos-2023.05.28 ~]$ sudo mount /dev/sdb5 /mnt
[liveuser@eos-2023.05.28 ~]$ sudo cat /mnt/etc/fstab
cat: /mnt/etc/fstab: No such file or directory
[liveuser@eos-2023.05.28 ~]$ sudo mount /dev/sdb4 /mnt/efi
mount: /mnt/efi: mount point does not exist.
       dmesg(1) may have more information after failed mount system call.
[liveuser@eos-2023.05.28 ~]$ sudo mount /dev/sdb4 /mnt/boot/efi
mount: /mnt/boot/efi: mount point does not exist.
       dmesg(1) may have more information after failed mount system call.
[liveuser@eos-2023.05.28 ~]$ sudo mount /dev/sdb3 /mnt/boot/efi
mount: /mnt/boot/efi: mount point does not exist.
       dmesg(1) may have more information after failed mount system call.
[liveuser@eos-2023.05.28 ~]$ sudo mount /dev/sdb4 /mnt/efi
mount: /mnt/efi: mount point does not exist.
       dmesg(1) may have more information after failed mount system call.

See the post above yours.

You have a Btrfs file system and Grub so the instructions for chrooting are a bit different.
They are further down on the wiki page I linked to.

there shows some errors:

[liveuser@eos-2023.05.28 @]$ sudo arch-chroot /mnt
[root@EndeavourOS /]# grub-install
Installing for x86_64-efi platform.
Installation finished. No error reported.
[root@EndeavourOS /]# grub-mkconfig -o /boot/grub/grub.cfg
Generating grub configuration file ...
Found background: /usr/share/endeavouros/splash.png
Found linux image: /boot/vmlinuz-linux-zen
Found initrd image: /boot/intel-ucode.img /boot/initramfs-linux-zen.img
Found fallback initrd image(s) in /boot:  intel-ucode.img initramfs-linux-zen-fallback.img
Found linux image: /boot/vmlinuz-linux
Found initrd image: /boot/intel-ucode.img /boot/initramfs-linux.img
Found fallback initrd image(s) in /boot:  intel-ucode.img initramfs-linux-fallback.img
Warning: os-prober will be executed to detect other bootable partitions.
Its output will be used to detect bootable binaries on them and create new boot entries.
ERROR: mkdir /var/lock/dmraid
grub-probe: error: cannot find a GRUB drive for /dev/sdc1.  Check your device.map.
Adding boot menu entry for UEFI Firmware Settings ...
done
[root@EndeavourOS /]# 

I have not come across this one before. I think for now you could ignore that.

Exit chroot and chek efibootmgr.

here’s the output

BootCurrent: 0000
Timeout: 0 seconds
BootOrder: 0001,0002,2001,2002,2003
Boot0000* USB HDD: UFDBM   T7 38	PciRoot(0x0)/Pci(0x14,0x0)/USB(3,0)/HD(1,MBR,0xb15bb315,0x399a80,0x37800)RC
Boot0001* endeavouros	HD(4,GPT,59ef96c6-2deb-5849-977d-e8bf2440016d,0x12d2c800,0x12c000)/File(\EFI\endeavouros\grubx64.efi)
Boot0002* Windows Boot Manager	HD(4,GPT,59ef96c6-2deb-5849-977d-e8bf2440016d,0x12d2c800,0x12c000)/File(\EFI\Microsoft\Boot\bootmgfw.efi)57494e444f5753000100000088000000780000004200430044004f0042004a004500430054003d007b00390064006500610038003600320063002d0035006300640064002d0034006500370030002d0061006300630031002d006600330032006200330034003400640034003700390035007d00000000000100000010000000040000007fff0400
Boot2001* EFI USB Device	RC
Boot2002* EFI DVD/CDROM	RC
Boot2003* EFI Network	RC

That looks good!

However I am not seeing that os-prober has detected your Windows. I am not sure why.

Anyways, rebooting, you should get the grub boot menu. Let’s see if we can fix adding Windows later on.

in the article it stated to ensure the chroot is working by checking content of /home.
I did ls /home
and there were no users shown

Yes, that is because we didn’t mount it.

There is no need for mounting the home partition/subvolume for (re-)installing Grub.

I rebooted the system. Howerver no grub was shown. Windows booted by default

According to this, you should now have an EFI boot entry for your EnOS and it should be first in boot order. Go into UEFI settings and check again.

If it is not there I am not sure if I have more ideas at the moment. I also need to logout from the forum now and probably it would be good that other forum members have a look at this with ā€œfresh eyesā€.

Thanks alot for helping out

1 Like

No problem! Hopefully we will sort the whole thing out eventually.

And also welcome to EnOS’ community @rapper!

:enos: :handshake:t5:

Do I understand correctly that Windows and Endeavouros are installed on the same disk? Also, what Motherboard do you have?

Yes they both are installed on same disk

I donot know the motherboard name…laptop is acer aspire e5-575

It’s unlikely, but by any chance, can you find a ā€œBoot BBS Priorityā€ setting in your BIOS? Or something like that. Naming may vary. You could be able to select the partition which you want to boot first there. Helped me when I had similar problems, but I had Windows and Endeavousos on different disks. Worth a shot anyway.

there is no such thing like Boot BBS Priority though there is a section named BOOT where boot order available device can be changed. In my case only there are several options available but none of them corresponded to the endeavouros, I checked all of them.

This is mostly unusual since the output of efibootmgr above showed an entry was indeed created :thinking:

However there is another option to create a boot entry for EnOS from within Windows using bcdedit command.

If I am not wrong something like the following:

Open the command prompt as administrator and run:

bcdedit /set {bootmgr} path \EFI\endeavouros\grubx64.efi

Reboot and check.

:warning: Please do some research about it!

I can’t really guaranty that it would work. I don’t have a dualboot with Windows to try. So please make some research on your own.

There is also an application for this called EasyBCD you can look into.

Sorry for being late. I solved my issue by formatting the SSD completely, then installing windows alone in it. Then I shrinked the disk and installed EnOS. Thanks for the support

3 Likes

To the OP and all that replied: thanks for this discussion, I’ve recently had an ā€œissueā€ with other operating systems being listed in grub. I’ll start a separate thread when I have more time, and a little better definition of the details.

1 Like