Hey guys! I have an issue with trying to get endeavouros to work on my pc.
I have windows 11 on one SSD and I have a different sata-SSD where I’m trying to install EndeavousOS.
So I use my live usb, go through the installation steps and go to the page that says finished installing and reboot.
But when I try to boot into that drive I get different errors everytime. Sometimes it throws me back into the menu where I can select a boot device, sometimes I get into the menu where I can select endeavouros but see these 2 errors (screenshots) afterwards, sometimes just a black screen.
Adding to what @ricklinux just posted above, If you have two different ssd, one for Win 11 and one for EOS, then ideally you should have two EFI/ESP partitions. One for Win 11 and one for EOS. It seems that you are using systemd-boot and not GRUB for your boot loader. For systemd-boot typically the ESP is mounted on /efi
Please run the following command from the live-usb terminal and give the output over here.
$ lsblk -T -f
$ fdisk -l
$ inxi -pojDP -xxx
ESP = EFI System Partition. Typically a FAT32 partition
EFI = Extensible Firmware Interface. The new system for booting which replaced MBR method.
@Archie1 All right these are the outputs (dev sda is the drive i try putting it in, the other 1tb is windows, 500gb is just normal storage and 16gb is the live usb)
You probably can show us the current install log by booting with the USB installer, arch-chroot to the installed system, and run either of the commands
@aki, Would it be possible for you to please edit your reply and enclose the output of the 3 commands inside a code block or a Preformatted Text block? You will see “Preformatted Text” block option in the editor.
It appears that there are 4 drives in your computer. Windows is installed on the NVMe SSD drive, i.e. /dev/nvme0n1 which is a Samsung 980. There are 2 SATA drives, /dev/sda which is Crucial 1TB and /dev/sdb.
And there is a USB Flash drive, i.e. /dev/sdc which I am assuming is live-USB for OES.
Did you install EOS on the /dev/sda drive, i.e. Crucial drive or the /dev/sdb drive, which appears to be a USB external drive? Because it appears Linux is installed on /dev/sda while there is another windows installation, with its own esp in /dev/sdb.
Please carry out the instructions given by @cactux. Those logs will help us determine what is the issue.
Either the Crucial drive, i.e. /dev/sda may have an issue or while installing the Systemd-boot EFI partition it might have overwritten something. The logs will help us determine that.
@Archie1 Thanks for the suggestion! I edited it now. For your question regarding my drives, it’s sda where i’m trying to install the os, it has 1tb storage. sdb isn’t or shouldnt be a boot device, I even have steam games on it. I forgot the windows one but it has a distinct name and also 1tb storage, and the live usb is the 16gb one.
btw I also tried to install without any other drive plugged in besides the one where I’m trying to install and the live usb, but that didn’t work either
Also I have these boot devices that I can select when I only have the Windows nvme and the SSD that’s supposed to be EndeavourOS:
ubuntu (Samsung SSD 980 1TB) Windows Boot Manager (Samsung SSD 980 1TB) Linux Boot Manager (P0: CT1000BX500SSD1) Windows Boot Manager (P0: CT1000BX500SSD1)
No idea where the ubuntu came from, maybe it’s Linux Mint that I used to have on the drive where I wanna download EndeavourOS. And I notice that there are 2 windows boot managers, the one on the bottom doesn’t work, but interestingly it shares that name id thing as Linux Boot Manager
What seems strange to me , if you selected erase disk during install that the second windows bootloader is still there. Something must have gone wrong there somehow (maybe a bug in the installer). Best way to go in my opinion is delete all partitions on the drive you want to install eos, and create a new one with partition manager from the live ISO. During install select replace partition and don’t select the bootloader from the Samsung drive but let the installer create a new partition like this. Make sure you select the right drive
Select new to be clear.
On second thought the second windows bootloader would have been a option on your systemd bootloader menu, anyway the method I described is the way I always do it and it has never failed me.
When I’m home in a few hours I’m going to check if the sata ssd even works in the first place.
If it does, I’m going to try with a different 32gb usb stick and if that doesn’t work, remove the windows 11 nvme drive as well so it’s only 1 drive + live usb
Ngl I could also just try another distro like plain arch but now I’m really interested in finding the solution to this, it’s like a game to me now haha.
Thank you guys for being so helpful so far. If it actually works, I’ll send the pastebin with installation logs anyway in case some of you want to see the what the difference is.
Well it was worth a try .
Anyway just to rule somethings out, did you disable secure boot before installing.
And if you run efibootmgr does it show the right boot sequence ?
You also mentioned ubuntu, that somehow can be the culprit , if I remember this correctly from another topic somewhere on this forum.
So I tried the things I mentioned I would do when I get back home and none of them worked. So I gave up on this distro and tried plain arch.
Arch didn’t seem to work either. I couldn’t even get it to show up on the boot device list, and sometimes I tried again and again and it did show up but would boot me off.
I even saw kernel panic just when I was about to give up completely. I asked claude AI with full detailed description and it told me to check if there’s a problem with the ssd. I put the cables in different ports and tried to install arch and it still didn’t work.
and then I tried archinstall cuz why not, and lo and behold, IT WORKED.
So my conclusion is I don’t know where it went wrong but something went wrong and now arch works at least .
Thanks you all for trying to help and sorry for wasting your time, I assume the ssd wasn’t seated in properly but still don’t know what the problem was.
.