… but today EndeavourOS bricked itself after an update. Unfortunately no idea how to fix this, the journalctl is just way too much to read.
systemd said it right there: failed to mount /efi. Either that partition is destroyed or something else happened.
It’s time for the time honored tradition of using the liveCD to repair your system. People here will help out. Get yourself the EndeavourOS liveCD USB flash drive you have used for the install and boot into it.
Adding onto winnyace’s response, if you don’t have experience of it, now’s a good time to pick up how to arch chroot into your system to run what may potentially be a quick repair;
https://discovery.endeavouros.com/system-rescue/arch-chroot/2022/12/
Don’t give up, stuff like this can happen, the key bit is to grow your skills over time so that it’s a non-event when it happens. I didn’t know a thing about chrooting in a few years ago. I’ve now got it down to just under twenty mins for a repair process. See how far you get, don’t be afraid to ask questions.
It says “vfat” is an unknown filesystem. tbh I think going back just one kernel earlier would resolve things, but I have no idea how to do this.
You have a couple of options, the downgrade tool once you’ve chrooted it. Or manually installing a kernel version from the package source repo. eg
sudo pacman -U /var/cache/pacman/pkg/linux-<version>.pkg.tar.zst
Well a bit more information about your system might also help.
https://discovery.endeavouros.com/forum-log-tool-options/how-to-include-systemlogs-in-your-post/2021/03/
Did you use UUID’s in the fstab? If you didn’t it is possible the BIOS changed the mapping if using logical
Guys, thanks for encouraging me, I fixed it. booted a gentoo live stick, ssh’d into it and chrooted the drive. No idea what went wrong but a simple “pacman -Syu” fixed it.