Hello, I used EndeavourOS for a while and this morning I decide to install window 11 as dual boot
Endeavour will run on SSD and window 11 run on HDD
But the problem is after I install window 11, I can’t find the bootloader for Endeavour anymore
I followed this thread and created Linux boot manager but still only see window 11 on boot
I also try grub-install --target=x86_64-efi --efi-directory=/boot/EFI --bootloader-id=endeavouros --recheck --removable
But nothing seem work
How does this happen?
I’m on live usb right now and I think here’s some log might useful
Model: ATA Samsung SSD 870 (scsi)
Disk /dev/sda: 500GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
1 2097kB 317MB 315MB fat32 boot, esp
2 317MB 500GB 500GB ext4 root
Model: ATA TOSHIBA MQ04ABF1 (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 17.8MB 16.8MB Microsoft reserved partition msftres, no_automount
2 858MB 108GB 107GB ntfs Basic data partition msftdata
3 108GB 1000GB 893GB ext4 root
Model: ASolid USB (scsi)
Disk /dev/sdc: 31.5GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
1 1049kB 31.5GB 31.5GB fat32 Main Data Partition msftdata
Also this is what I see in /mnt chroot, idk if it useful or not.
Maybe I’ve done something wrong because there’s a dir name EFI inside EFI dir?
[liveuser@eos-2023.05.28 endeavouros]$ sudo chroot /mnt
[root@EndeavourOS /]# ls
bin dev home lib lost+found mnt proc run snap sys usr
boot etc install-script.sh lib64 media opt root sbin srv tmp var
[root@EndeavourOS /]# cd /boot
[root@EndeavourOS boot]# ls
boot dev EFI grub loader proc sys 'System Volume Information'
[root@EndeavourOS boot]# cd EFI
[root@EndeavourOS EFI]# ls
boot Dell EFI endeavouros Linux Microsoft systemd
[root@EndeavourOS EFI]# cd endeavouros
[root@EndeavourOS endeavouros]# ls
grubx64.efi
[root@EndeavourOS endeavouros]#
Your system doesn’t seem to be using systemd-boot for two reasons: first, EnOS’ uses an ESP of the size 1000MB for systemd-boot (yours is 315MB); second the ESP would be mounted at /efi (you don’t seem to have such a directory)
This doesn’t look quite right, I think.
The default directory in EnOS when using Grub should be /boot/efi.
Could you show the content of /etc/fstab from your installed system?
[liveuser@eos-2023.05.28 etc]$ cat fstab
# Static information about the filesystems.
# See fstab(5) for details.
# <file system> <dir> <type> <options> <dump> <pass>
If you install Windows after and is also on another drive on UEFI it will take over as the boot drive, You need to boot from the drive that had endeavourOS and run the update grub command. It possibly may also be necessary to reinstall grub and update it. I would try the grub update command first if you can boot from the right drive from UEFI settings.