[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.
[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 /]#
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ā.
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.
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
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.