I’ve installed a number of Linux distros over the years including Manjaro without ever an issue. But EOS has me almost completely defeated. I had no problem setting up the installer. But when I try to install (KDE Plasma version) there are errors each time I’ve tried. and I go to emergency boot. The errors shown are ‘failed to install packages for grub’, and ‘failing to start rules-based manager for device events and files’, this one repeated several times. I can also see from there that my Home folder is empty (or not set up this far). Each attempt at installation produces the same result.
I installed from the UK mirror. Can anyone suggest what is going wrong here, please?
I did an installation the day before yesterday and encountered odd problems as well. I was able to fix it by updating the mirrors (there is an option to do this on the main menu that comes up) and then running the following command from a terminal:
Yes. Your ‘keyring’ theory appears to be at the heart of my issue too. Finally, I installed on the 4th attempt, and on this occasion it completed without an emergency boot.
I didn’t use the command you recommended. The only difference this time was that I did not update the mirrors before installation. I just clicked the install button without doing anything else beforehand.
The first thing I noticed at the start of installation is that the ‘configuring keyring’ message was seen. which did not occur previously. Other points I might mention is that the ‘Install Alongside’ option did not seem to work, causing the install to hang for about 10 minutes, at which point I gave up and switched to the manual install option instead, Another point was that it mentioned I needed an EFI partition at least 2048 MB. This is nonsense. I’ve always used an ESP of 100 MB which was more than sufficient for any other Linux and Windows system.
What a palaver! I dread to think what any Linux novice coming straight to EOS from Windows would make of this awkward and misleading installation process.It does seem to me there’s some bug with the installation process and I’m surprised no-one else has mentioned it.
I think (but am not sure) that between the two boot systems:
GRUB: The traditional boot loader uses the “traditional” FAT32 EFI partition on /boot/efi plus a supplemental partition on /boot. If installed on its on partition, the supplemental partition is between 1GB and 2GB in size. [EDIT: It is possible to “merge” the /boot partition into the / root partition depending on how the system is configured.]
Systemd-boot: This newer boot loader stores everything on the FAT32 EFI partition on /efi, eliminating the supplemental partition. If follows that the EFI partition would need to be larger to store the information previously split between two partitions.
I installed system, day before yesterday, I think, and I did not have any issues. Also, there have not been number of new threads considering install process, so unfortunately it seems that issue is on your end.
I understand that failed install can be frustrating. Although EndeavourOS is easy to install, on daily use it requires will to learn some tricks and understanding, that on rolling release, sometimes things can break. Quite rarely, but sometimes. By this I mean to adress to your point about beginner friendliness.
In my opinion EOS is beginner friendly, but newcomer from Windows should come with open attitude and willingness to learn and ask help if needed.
I’m glad that you managed to solve your issue. You should provide logs for example to this thread, so if there’s issue on installer, it gets noticed.
Looking at the log, it only records my last attempt at installing, which on that occasion was successful. So it wouldn’t be much use. I can still put it up if anyone wants to see that.
hmm strange issue would like to see the complete installer logs from such failed install.
From what i read the failed attemts all was by ranking mirrors before starting installer?
Online or offline install was used? (as of kde would be available at offline too) and yes even the installer log from the successfull attempt can show some internals that could be intersting.
We decided to set 2GB by default as of it opens for tinkering with options.. may one want to switch from Grub to Systemd-boot or other things. And nowadays 2 GB more or less should not hurt most users?
And indeed you can use manual partition and set ESP to smaller size if you use Grub.
I’ve tried online & offline KDE installs. Both failed except the last online which finally succeeded - except:
Later I did reduce the size of the ESP to 100 MB (I was on grub boot), after everything seemed to be working OK, only to find that the next boot took me straight back to square 1 - emergency boot. I went back to the installer and used gparted to reformat my partitions (ext 4 on root & home) and even that failed and produced an error. Never had an issue with gparted before.
I booted from Live Mint and used gparted there to reformat the same partitions, and no problem. That convinced me to give up on Endeavour, I’m sorry to say. The only other Arch based distro I have is Manjaro and that’s always been reliable other than the odd AUR breakage, but I’m aware of the AUR issues there.
I just seem to have an unlucky streak with Endeavour so I’m not pursuing this further.
as expected.. the ESP is in front of the root partition, so reducing its size and resize the root partition in the beginning will change the startpoint of the root partiiton.
There is manual partition option to use custom schemes on the installer.
Sadly “error” is not info enough to be able to see the cause of the issue you were falling in to.
There is also no installer log providied here so also no way to be able to see what exactly was causing the issue.
I am sorry for you to have such issues, but simply us ewhat is working best for you.
I’ve been using the manual install option the whole time. Root is sdb3. My ESP is on sdb7. I left its size at 100 MB.
Had a change of heart and decided to give Endeavour one more shot. At last it’s up and running and is no longer going into emergency boot after several reboots, so my system seems stable (for now).
The only thing I did differently this time was to remove the USB stick just after installation, which I hadn’t done previously. But even testing with the USB stick replaced I’m not going to emergency boot again, so still in the dark as to why I had this issue.
If i do massive testings i have some strange hickups from time to time too.. even with exatcly the same setups in use. Partly thats a thing happen on rolling releases.. as some very little issues come and go very fast. ISO is pretty stable and we put a lot effort into testing it and before that into using implementations and cod ethat is secure and stable and one thing over all SIMPLE !
Mice to see you are up and running! And of caus eeven better if its EndeavourOS
