Edit: I have edited the title, I don’t believe this has anything to do with EndeavourOS or Arch now, but rather an issue on the Ubuntu installers that is not shared with Endeavour.
My progression on this desktop was Mint → Manjaro → EndeavourOS. After a lot of time spent, I’ve come to the conclusion that Arch based distros don’t fit my use case very well.
Having a VERY frustrating (and concerning) issue right now trying to format my desktop to a Ubuntu based distro. Even using the “guided install - entire desk” option on multiple distributions (Mint, Kubuntu) results in a non-bootable drive after installation. I do not receive any error during installation, just a non-bootable system afterwards.
After multiple install failures I decided to attempt installing EndeavourOS again - it boots right up after the installer completes off the USB drive.
I’ve checked the USB drive for bad blocks. I’ve confirmed the SHA256 sums of the OS’s I’m attempting to install. When on Kubuntu live, I even attempted completely rewriting the partitioning table on the SSD (GPT) to make sure it was 100% empty for the Kubuntu install. It still wouldn’t boot.
Only EndeavourOS can install and boot successfully now. Any help would be greatly appreciated, when I was first attempting to change the distro on this PC I had an important 10TB drive plugged in, and I saw something during this weird process on that drive that is somewhat concerning. I don’t think at this point I have data loss, I’ve unplugged all drives other than the SSD at this point as well, but I really want to get this system booted back up ASAP so I can check.
EndeavourOS doesn’t do anything special to your drive. If you pick the entire disk method, it writes a new partition table and then creates the partitions.
There should be no barrier to installing another OS. If you are having trouble installing an OS, we would need to understand exactly what you are seeing. My best guess would be it has something to do with the fact that you are trying to install to a USB device.
That being said, it would probably make sense for the distro which you are trying to install to provide support for your install in this scenario.
I’m considering that as well - that the issue could be with the installer from Mint/Kubuntu and nothing to do with Endeavour. Honestly if I’m completely wiping the drive, like you said I think that must be the case (issue with Ubuntu installer).
I’m not installing the OS to a USB, it’s going onto an internal SSD - I’m just using a live USB for the installer.
I’m not seeing any error messages, at all, which is making this hard to identify as well. Installer closes out, asks to reboot, no error. On restart I just never hit GRUB, it just sits at the UEFI splash screen. You’re right, this may be a question more for Mint/Ubuntu.
I agree it could be related but hard to tell at this stage. I would also have CSM disabled, Secure boot disabled obviously and set it to UEFI mode only.
Edit: Obviously if it was already installed with EOS secure boot would be off.
Here is the output from inxi, I ran this off of a Kubuntu live so I was unable to pipe it to eos-sendlog (let me know if you want and I can go into an Endeavour desktop and run it again). Thank you Luna and Rick for the input, I will check CSM settings, i think it should be disabled. I will also attempt booting to Neon and see if I’m able to get that installed correctly.
Thank you everyone for the help. This is not what I planned on doing today, lol.
This is mentioned in another post on Mint. I’m trying to figure out what the issue is on it. If it were me i would boot on the live ISO for EndeavourOS and launch gparted and create a new GPT partition. Then shutdown and reboot with the distro you want to install and try again.
Edit: Looks like it might be installed in legacy mode and your system is UEFI. This can happen with CSM on sometimes as the installer gets fooled.
Edit: Make sure CSM is disabled and you have UEFI mode only.
I checked my BIOS settings, CSM was already disabled. I did see one option under “Trusted Computing” that had “Security Device Support: Enabled”. I disabled that, however there hasn’t been any change (attempted reinstalling Kubuntu).
I’ll attempt running Gparted off an Endeavour stick, although I don’t know if that will have different results than when I ran Gparted during the Kubuntu live. I also have yet to attempt installing Neon.
Do you know where I can check that? This is definitely more a question for Ubuntu/Mint now, I may make a topic over there depending on what I end up landing on today.
I do know that these distros are complaining if I try to manually partition the drives using their installer. I make one 300MB Fat32 partition and mount it to /boot/EFI, and then allocate the rest of the drive to btrfs and mount it to / - The installer however will complain and say there is no partition for EFI, despite there being one. I ignored this error when installing on my laptop, and the system still booted appropriately.
That’s why I bailed on that and just went with “guided - full disk” to remove that variable. The only reason I bring it up now, is I don’t know if the installer would be asking for the EFI partition were it not installing in UEFI mode.
Edit: Still no change after using Gparted under Endeavour live. Created an empty GPT table, rebooted, Kubuntu install still completes without error but is unbootable. Trying Neon now.
Edit2: The issue is definitely the installer used by Mint and Kubuntu. EndeavourOS installs and boots without any issue, and so does Neon as suggested by Dalto.
I’m going to try setting myself up on Neon for now and see if it works OK for my goals. If I need further help beyond this, I’ll ask on a Ubuntu based forum since this seems to be an issue on their side.
Thank you all very much for your ideas and help, especially since this ended up having nothing to do with Endeavour.