The first error line happened before already but didn’t cause boot issues. The two duplicates afterwards are new and it just throws me back into the grub menu, which also lost it’s theming a couple updates ago. Snapshots don’t work, as I assume that grub sits outside of them.
Guess I have to distro hop again, because I have no idea how to chroot. Ironic that EOS broke so soon while Manjaro didn’t even once. Sucks to backup & reinstall everything again too.
It’s not that difficult, there is a tutorial in the endeavouros wiki.
Manjaro… 
That tutorial is as helpful as the arch wiki when you use btrfs + encryption. Like it or not, Manjaro ran for longer without as much or as severe issues. As far as I’m concerned it’s reputation is worse than the reality. Meanwhile glorious EOS constantly had issues and now a full breakage.
Scroll towards the bottom of the tutorial you’ll find BTRFS and encryption.
Have used Manjaro for two years on one system and had way more issues then on Endeavour or Arch in a similar time.
Bare bones ready to setup as you like… EndeavourOS is not Manjaro.
Keep it friendly.
As @BendTheKnee mention EndeavourOS wiki has tutorial for BTRFS and encryption inside arch-chroot article.
when was the last time you rewrite grub files into bootloader partition? (grub-install) pacman/yay any… always warn about to do so.
And you have tried to enable secure boot and solving to boot OS with secure boot enabled?
Could be also false error casued by a Bios reset that may enabled secure boot ? i would check Bios for that.
There’s no warning about it but I did so after the update yesterday and most of the updates before that anyway. The only times I didn’t was when those issues started to appear for others and I simply wasn’t aware of it, as it didnt’t affected me at the time.
Again, that tutorial is as helpful as the arch wiki and I have simply no idea what I’m looking at or have use and do. It’s useless unless you already know your way around. Me fiddling with this would likely make it worse and risk my data.
First of all, welcome @DarkThoughts to the wonderful world of EndeavourOS, a wonderful distro and a wonderful community.
I will tell give my humble opinion. (I am just a user by the way).
I have distrohoped for a year till I got settled on EndeavourOS.
The problem you have is with Grub not with EndeavourOS.
As long as you said you will do a fresh install, my advise is just do it, but while installing be sure to chose the default boot loader which is systmd bootloader AND NOT Grub.
You may check my other posts here to know more.
(I have been on Manjaro by the way for some time… but… well, not for me, neither the distro nor the community there.
My advice, reinstall EndeavourOS again but with the default systemd-boot. You won’t regret it.
Tell you what, I have been on Linux since 2000, tried many distros, and distrohopped for a year, since 2000 till this moment never found a distro like EndeavourOS or like this community,
I hope this helps!
I’m pretty sure grub was the default boot loader when I installed it. The reason I didn’t switch when the issues occurred were the fact that I didn’t know how to do it safely, that it didn’t support things like the auto timeshift snapshots for grub and I heard it didn’t support encryption. Now I have to figure out how to backup my shit without running into permission issues… As well as what to use after. Shifting the blame to the user for using grub certainly isn’t making a great case for the distro either.
I apologise if you got it as I am shifting the blame on you. Maybe I unintentionally gave this impression as English is not my mother tongue. (I will appreciate if you show me where did you get I was blaming you to avoid repeating such)
Again I was not blaming you absolutely. I was just trying to help.
Of course it is absolutely up to you to reinstall whatever distro you like, with whatever bootloader, whatever desktop, whatever you want. This is the spirit of Linux after all and what I believe in, freedom!
You’re wasting your time my friend. He’s clearly frustrated that his install wont boot (rightfully so I might add) and he clearly doesn’t know what a rolling release is about.
If one is not willing to learn how to chroot into their system to recover files or repair it then a rolling release should not be an option.
1 Like
First off, welcome to EnOS’ community!
I would suggest installing Arch the Arch Way at least once.
Not only you will learn how to use chroot but you may find ArchWiki quite helpful as well.
Knowing how to use arch-chroot from a live session to rescue a system is a must on, not only EnOS or Arch but on any Arch-based system.
Good luck with your endeavours on Archland!
Sincerly,
1 Like
I can’t install arch the arch way because the terminal installer is way beyond me as soon as it comes to partitioning and encrypting.
I stopped caring so yeah…good luck!!
You care so little that you still continue to reply useless garbage by the second.
At this point I’m trolling. If you don’t want help then don’t ask for it.
You were trolling since your first reply. But thanks for proving my point.
Where do these people come from?