Which of these (various) installs is “in charge” of the grub-setup? (Beware of os-prober on multi-boot systems; only one distro should run it at all, and only that one should be allowed to “install or re-install grub” to the ESP, or EFI.
Each install is separate. os-prober is disabled on all of them. rEFIND manages the boot but they boot from grub.
Same thing applies. If you have multiple systems installing grub things go haywire easily. Only one should be “in charge”, i.e. allowed to re-install grub to the main boot-drive.
Each desktop is individual. They each boot on their own. They have nothing to do with each other. The desktop that boots with rEFInd allows you to boot the other desktops via it’s own grub installation on that disc. That’s how it works. The problem is grub on any newly installed desktop does the same thing usually.
Edit: I’m not having the issue of it booting directly into UEFI. It’s just the other errors such as out of memory or bring up the black arch standard boot menu instead of the EOS menu. Which causes me to have to fix it.
Alright I just rechecked and made sure secure boot is disabled. Still not able to boot from the ISO.
Well, sorry for my lack of insight, re: refind.
Then I guess each separate distro needs a re-install of grub, the way pinned to the top of the forum.
Shure your EFI is set up correctly? As @dalto hinted?
This might possibly give some insights (not sure), @Yackasone also:
In addition iso do not use grub to boot, we use systemd-boot and syslinux ( For legacy systems)
2 Likes
Now you mention it, I think I didn’t start getting the ‘out of memory’ errors until I did a fresh online install over an old EOS that kept booting to the bios. It’s all very strange…
Turns out my ISO USB wasn’t formatted properly, unrelated issue. I’ve booted into the live environment now.
3 Likes
Following this guide on how to chroot I’m stuck on the mounting step. The drive I’m trying to access is sdb so I use:
sudo mount /dev/sdb /mnt/boot/efi
I get this error:
mount: /mnt: wrong fs type, bad option, bad superblock on /dev/sdb, missing codepage or helper program, or other error.
Looking at the guide I’m inferring that my filesystem on that drive is different to the default, but I don’t remember fiddling with it at all. How do I find what filesystem I have on that drive? What should I do differently to properly mount it? I know I’m probably doing something foolish, and I can’t express enough how much I appreciate the help.
its not sdb nr’s importand 
if you find a adres you need also the nr’s
As Ringo say 
Show lsblk -f
You need partitions not drives to mount
AME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS
loop0
squash 4.0 0 100% /run/archiso/airootfs
sda
├─sda1
│ ntfs Recovery 9288782988780DCB
├─sda2
│ vfat FAT32 EE79-27A5
├─sda3
│
├─sda4
│ ntfs 16B87ABEB87A9BC5
└─sda5
ntfs A2B2574CB2572457
sdb
├─sdb1
│ vfat FAT32 NO_LABEL F742-07D4
└─sdb2
ext4 1.0 8ba6df0b-46ba-4d27-af84-8a1e5ed5c4d5
sdc
├─sdc1
│
└─sdc2
ntfs Disk2 8E5C735A5C733BD1
sdd
└─sdd1
vfat FAT32 EOS_202208
0A8D-87F6 13.1G 11% /run/archiso/bootmnt
Just as an explanation. When you want to chroot you need to first mount the partition that your system is installed which is the root partition. Then you have to mount the efi partition which is your boot partition then you need to arch-chroot. Hopefully this makes more sense to you.
1 Like
if all mounted properly then sudo arch-chroot /mnt
do you wanna have little fun : sudo systemd-nspawn -b -D /mnt
but going out that container i dont know my keys are sketchy
Thank you for this explanation. The guide had me a bit confused but you’ve cleared it up. I’m now back on my regular installation, and I’m so grateful for the help I got from this thread. I’m still new to linux as you can probably tell and without your help I would probably be dead in the water.
1 Like
Hey
So i recently made the switch to linux from windows so im still new to this.
Today i updated my system and restarted my pc when i came back it had booted to Windows(as i had not uninstalled it yet) and i think that might have broken something because when i tried to boot Endeavour again it just fails. It tries to boot but then the screen goes black and it opens bios.
Would give a video but not sure how to include it here.
Hope someone can help me with this.
this is exactly the issue discussed here or not?
the solution is here:
Hello,
To recover my system, I would like to follow the instructions >>>
https://discovery.endeavouros.com/system-rescue/arch-chroot-for-efi-uefi-systems/2021/03/
But I don’t understand them.
My partition is encrypted and I don’t know which commands apply to me.
Here is info:
Just what are the commands specific to my case
Could you please help me ?
Thanks in advance.
pls check arcolinux they kept grub on hold for 5 years
EnOs can this as well?
