Hi there,
I’ve run into an issue after upgrading my system yesterday. Now, when I try to boot, the efi partition won’t mount and my system enters into some kind of panic. See here:
I’ve tried various methods already suggested on the forum - I have chrooted into the system and reinstalled my kernels, tried to boot from a fallback image, etc, but I’ve been unable to identify the problem. Basically, when the boot fails, it offers me the opportunity to login or to continue with control + d, but I’m unable to update or do anything.
I’ve been using endeavour os for a few years now and really appreciate the forum. Normally I can figure things out on my own with help from past experiences, but I’ve struggled with this one. Any help you can offer would be greatly appreciated, thanks 
Chroot in again, install the linux-lts kernel and headers - see if that will boot.
Hi there, thanks very much for your reply. Unfortunately, I tried that already and it also failed (as well as the LTS fallback). Not sure what other information I should provide, but happy to do so!
Am at work, so no access to linux, so cannot be much help 
It looks like your kernel is core dumping?
Just to make sure, you mean upgrading as in pacman -Syu? Not hardware upgraded and not a Windows upgrade?
This is a tough one…you might try clearing your cache, then forcing a fresh download of the kernel or maybe install the LTS kernel (maybe files corrupted? Shouldn’t be..but I’m grasping for straws now)
Thanks to both of you for your replies. Yes, to be clear I upgraded using pacman -Syu (and have reinstalled kernels the same way). There is no windows stuff going on, I wiped that as soon as I got the computer.
And the hardware is a Dell XPS 13 9320. So far had gone two years or so with no issues (or issues I could solve haha)
A couple of things to do to get them out of the way:
Get the EFI partition UUID with sudo blkid and ensure it matches the entry in /etc/fstab
Run a filesystem check on your ESP
The fact that you can still boot successfully and chroot most probably means that your hardware is ok.
I’m still prone to suggest putting in the LTS kernel or the std kernel, if you’re running LTS already
Nvidia or AMD or Intel GPU?
So soldered memory, I was going to suggest reseating the ram sticks 
throw that idea away.
I was running the standard kernel, but then installed LTS to see if that would fix it. But unfortunately no… As for gpu, it’s Intel.
Thanks for the suggestions! I confirmed that the EFI UUID from sudo blkid matches what was found in /etc/fstab
How exactly can I run a filesystem check on the ESP? Sorry, just slightly beyond my knowledge…
In the live session open partitionmanager or gparted (not sure which is available).
Right click on your ESP (FAT32) partition and choose check (or something similar).
Ok, not sure what this means, but partitionmanager failed during the check:
Here is the detailed info:
Check and repair partition ‘/dev/nvme0n1p1’ (1.00 GiB, fat32)
Job: Check file system on partition ‘/dev/nvme0n1p1’
Command: fsck.fat -a -w -v /dev/nvme0n1p1
Check file system on partition ‘/dev/nvme0n1p1’: Error
Check and repair partition ‘/dev/nvme0n1p1’ (1.00 GiB, fat32): Error
Sorry, I jumped the gun… Ran it again and it was a success, all fine:
Maximize file system on ‘/dev/nvme0n1p1’ to fill the partition: Success
Check and repair partition ‘/dev/nvme0n1p1’ (1.00 GiB, fat32): Success
1 Like
OK, there were some issues with your ESP. They are hopefully gone now.
You can chroot into your system now.
Run pacman -Syu to update.
Also make sure that 1GB EFI partition is large enough for your kernels. The recommended/default size nowadays is 2 GB.
If it is nearly full, you may need to uninstall some kernels.
At any rate, rebuild your kernels once again. Reboot and report back!
1 Like
Why isn’t there a finger-crossed emoji ?
2 Likes
Ok, thank you so much for your help. Will do this now and report back ASAP.
It seems the partition size for the EFI is ok (only 220mbs used). But we’ll see if this works!
1 Like
If you have normal and LTS kernel, it seems like more than that should be used?
Am I off-base on size estimation, Cactux?
You are probably right. Perhaps a rebuild of kernel(s) will populate /efi correctly.
