After using EndeavourOS on my laptop for 1.5 years, I finally got around to installing on my desktop PC. But, well, see title.
When I went through Calamares, after I opted to replace my Windows partition with endeavourOS, the installer prompted me to select an EFI system partition from a list of “New”, blank, and then about 4 more "New"s. Only changing to and from the blank option would refresh the partition screen; changing the selection between the “New” options did seemingly nothing. I decided to play it safe and select the first “New”, and now, here we are.
This is a screenshot of my current partitions. I really don’t want to erase the partition labeled “Shared” (/dev/sda6)—a backup of my totally-important files—thus I really don’t want to erase my entire disk. I have an ASUS TUF Gaming–BIOS, in which I my “Secure Boot” configuration is already “Other OS” (search it up, I can’t disable it and this is what Superuser said I should do). How should I proceed from here?
That partition table is an absolute mess, if I was in this position, I would backup all the files I want to keep (so the shared partition?) to another drive, and then delete all the partitions and then let endeavouros install itself on the blank drive as it wants, you’l end up with a clean partition scheme and a working os.
The reason it boots to windows automatic repair is probably that your windows boot loader is still on your EFI partition and your whole setup is so messy that i’m not entirely sure if your linux boot loader is there as well (judging by the used space in fact I would suspect it isn’t,)
partitions really look like it only replaced sda4 and it has all the rescue stuff from windows still there. but i do not see any new created efi partition… only sda2 100mb what will be the one left from windows install. not sure if you have to kill all on the drive … you can also go to backup sda6 files and go cleaning off old windows partitions…
remove sda1 sda2 sda3 sda4 and sda7… expand sda6 to the end of the drive and create an empty placeholder partition out of the new free space in the beginning of the drive…
(judging by the used space in fact I would suspect it isn’t,)