Failed to mount /efi with timeshift restore

Hello. I’ve been using EnOS for a month. Last time, due to some ridiculous configuration setting I decided to use the timeshift feature for the first time. The OS didn’t load, (failed to mount /efi) yeah… quite the same as the person’s posted there:

Except I use ext4 file format. So I wanted to ask here and double check if the guide is still up to date / valid I have seen in the forums.

I had divided my 1TB disk into two parts when installing EnOs. (EFI partition, only 2GB) the rest is already the space I use (951,3GB)

To clarify the issued lines here:

[FAILED] Failed to mount /efi.
[DEPEND] Dependency failed for Local File Systems.

And the last lines:

You are in emergency mode. After logging in, type "journal -xb" to view system logs, "systemctl reboot" to reboot, or "exit" to continue to bootup.
Enter root password for system maintance (Or press Control-D to continue)

I usually solve Linux problems with ai but I only implement 20% of what it suggests. It just helps me to figure out what the issue is. I just brainstorm and come up with the right solution myself by considering forums + ai suggestions.

But … ahemm… it’s hard for me to be braining when I’m so stressed

First, I have checked this guide:

https://discovery.endeavouros.com/system-rescue/arch-chroot/2022/12/

I’m curious. Can’t we do it via emergency mode? Wouldn’t it be sufficient for this or live usb is still required?

I’m no expert on this but I would think you would need to arch-chroot so that you are able to mount the proper /efi partition in order to fix your issue.

@lcr8, your EFI partition, i.e. /efi is a EXT4 and not a FAT32 partition? And you are able to boot of it?

I was working under the impression that /efi had to be a FAT32 partition.

Got it figured out, and yeah you were right. Your suggestion was the easiest and safest play

My EFI partition was FAT32, not ext4. ext4 was my main partition, which I created when I installed EndeavourOS on the first day