Sorry, I've chosen the Arch board, since there seems to be no EndeavourOS board available here.

My question:
Since I'm pretty much fed up with reinstalling some Debian or Ubuntu based distros, each two or three years, I'm curious about installing EndeavourOS on my computer (UEFI type), but since it is a multiboot system, I want to make absolutely sure, I don't destroy any of the other, already existing installations (which are a win10, a Debian based distro and an Ubuntu based one).
Maybe I should add, EndeavourOS will be my first Arch based distro ever.

As far as I know (please, correct me if I'm wrong), the EndeavourOS installation is done pretty much the ordinary way. I just choose "Something else..." or an according option to have control over the partitions, choose one partition for root, one for home, one for swap, choose /dev/sda2 (my EFI partition) for grub and then go for it.

But what if, some day, I want to reinstall grub?

On a Debian or an Ubuntu based distro, I'm used to use this command:
What would this command look like for EndeavourOS, please?

2nd question:
What should I prefer, ext4 or btrfs? And can both of them see each other, if I try to access a particular partition from another distro?

What should I prefer, ext4 or btrfs? In my opinion ext4 is the better choice on a mutiboot system.

Thank you very much. So,
is doing for EndeavourOS, what
is doing for Ubuntu/Debian?

I already tried to find the answer for my question in the Arch wiki, but I'm confused there, because there was some target option mentioned.
According to your post, I don't need that, right?

And how can I be sure, grub is being installed on /dev/sda2 (my EFI partition)?

Yes

Oh, I just noticed, I forgot to mention that I'm on 64bit, but on the other hand this should be obvious, since UEFI is usually used for 64bit, isn't it?

grub-install will install in the mode the system is booted in, unless changed by the --target= option.

Ok, thank you.
Now, I understand what --target is meant for.

I found this Youtube video, with a guide on how to install EndeavourOS on a dual boot system.
It says there, you should create a FAT32 partition with the mount point /boot/efi.

This confuses me.

If there's a Win10 (installed in UEFI mode) already existing on my SSD, then there's a /boot/efi (a FAT32) already there, as well.
This efi partition is usually on /dev/sda2.

I wonder, now, why would I create another /boot/efi for EndeavourOS, if I can just choose the already existing /dev/sda2 for grub.
Doesn't seem to make sense from my point of view, does it?

So, that's why I think, as far as grub is concerned, I shouldn't follow that guide and instead, I should simply put grub into /dev/sda2,
right where the Win10 bootloader is already (I'd like to know this exactly, because by no means, I want to risk any harm to my already existing systems).

Am I right about not creating that 2nd efi partition for grub?

It depends. Windows usually makes the efi partition 100MB. If you are dual booting the existing efi partition is large enough to house the two os boot loaders. If you are multi-booting several distros then the existing efi partition is probably not large enough. If you are only dual booting windows and EndeavourOS you don't need to create a second efi partition.

In the end, I'd like to have one Win10 Pro, one EndeavourOS and a 2nd Linux, but I'm not sure, yet, which distro the 2nd one will be (maybe the latest MX Linux 23.1 xfce, or so).

I want grub to let me choose between Win10 and these two Linux distros in the same menu.

But if I have two efi partitions, I guess, I also have two grubs. How do I choose between these two? In the UEFI-GUI (that's how I call the BIOS successor)?

So far, I have Win10 Pro, a Bodhi Linux 6.0 and an MX Linux 19.4 xfce (I want to replace the two Linux distros, soon).

Together, they are using 35.38MB of my 100MB efi partition.

Since I will have three systems in the future, just as I used to have in the past, I guess, 100MB will still be ok.
Do you agree?

Not necessarily. GRUB constructs its user menu in real time using a configuration file called grub.cfg. I don't see why two different GRUBs on two ESPs couldn't use the same grub.cfg file. Maybe someone here who uses GRUB could show you how to do that.

That would be absolutely great!
But that also makes me wonder, does EndeavourOS not use GRUB usually?

Did you create the second efi partition or did one of the distros you installed create the second efi partition?


will show Bootloaders registered in the firmware/bios nvram, the bootloader boot order and what efi partition a bootloader is located on. If you plan on keeping EndeaverOS while installing uninstalling other distros you can use



to set control back to the EndeaverOS



sets a bootloader to load on the next reboot only.

When uninstalling distros, bootloader folders will be left on the efi partition that may need to be deleted to keep the efi partition from filling up with unused bootloaders.
to removed unused bootloaders from firmware/bios nvram

Sorry, for my delayed response, but I will have to postpone my EndeavourOs installation for a few days because, even that I want to install it on my desktop computer first, I need my laptop to be able to compare and verify my settings.

Sadly, my laptop died on 29th of december and I will have to wait for it to be fixed again (there's probably something wrong about the power supply).
Or, in the worst case, I will have to buy a new one.

So far, I have only one efi partition, which was installed when I installed win10 the first time, a few years ago.
That's where my existing grub is also installed.

I mentioned the 2nd efi only because the video from post #8 says it should be installed.

Snugbug,

Why don't you install VirtualBox and then install EndeavourOS inside VB, just to see how EOS performs?

https://www.virtualbox.org/wiki/Linux_Downloads

https://discovery.endeavouros.com/ap...albox/2021/03/

There is no need to use UEFI boot for EOS in VB. Just use the default setting.