After updating GRUB starts on emergency mode

[draconk]

After updating with the GUI package manager (pamac?) and getting the reboot prompt I rebooted and now after GRUB it starts on emergency mode, on the logs on journalctl -xb I only see two main errors

modules-load[445]: Failed to find module 'crypto_user'
modules-load[445]: Failed to find module 'i2c-dev'

and

mount: /boot/efi: unknown filesystem type 'vfat'

Any tips on how to proceed?

[Mirdarthos]

This might help:

[HowTo] Resolve an unbootable Manjaro (black screen, login failed, cant boot, etc)

When we have problems gaining access to our systems it is difficult to gather information, let alone fix any problems. Here we will cover common causes and solutions to ‘manjaro wont boot’. TTY If your desktop does not load properly then you might still be able to use most, if not all, functionality by dropping to a non-graphical TTY. By default your system will have multiple TTYs, with each corresponding to an Fx key. Your desktop is assigned to one as well - most often F1. You can change…

or perhaps even this:

[HowTo] Recovering from an interrupted update/upgrade

Difficulty: ★★☆☆☆ So you couldn’t wait until the update process had completed and you went for the reset/power button, didn’t you? And now you’re getting the message that you don’t have a kernel installed. Well, you’re not the only one — we’re seeing it happen all the time. So, here’s how to fix it, you impatient n00b. If you don’t happen to have a recent Manjaro installer USB/DVD/CD handy, direct your browser to this wonderful page, download t…

[TheDubster]

Same issue here. Have you found any solutions?

[andreas85]

Did you already try to start with “full” initramdisk ? ( or with another kernel)

[Marsa]

This looks similar to mount: unknown file system type "vfat" during boot - after update / Kernel & Hardware / Arch Linux Forums

You can also check the failing units with systemctl --failed

[TheDubster]

Second attempt to upgrade went fine. All good now.

[draconk]

Found my issue, some months ago I cloned the manjaro ssd to an nvme with higher capacity and left the original one untouched just in case, it seems that the UUID for the efi boot partition were the same in the original and the clone and when it updated it updated the EFI in the nvme as it should but it was loading the one on the ssd.

I deleted the partitions on the old disk and it booted perfectly at the first time.