Hello. After full system update I can no longer boot and am thrown into an emergency shell. Looking at the output of ‘journalctl -xb’ it seems several of my partitions are failing to mount. There are messages towards the end saying that file system types "vfat"and “xfs” are unrecognized and each of those partitions has a message saying mount failed. The efi partion is vfat The other partitions which are explicitly listed as failing to mount are xfs. Root is an ext4 partition and I don’t see it mentioned in any messages. ‘lsblk’ suggests it mounted but is the only partition showing a mount point.
This system was working fine until this update. Does anyone have any advice for me?
‘systemctl status efi.mount’ returns “mount: /efi: unknown filesystem type ‘vfat’” and “efi.mount: Mount process exited, code=exited, status=32/n/a” and “failed to mount /efi”
There is an identical sequence for each of the other partitions which fail to mount, the only difference being that they are ‘xfs’ file systems and the unknown filesystem type is “xfs”
Okey, I am not able to copy text from the emergency shell and paste it here on another computer and I’m not going to try to type 2993 lines of output from ‘journalctl -xb’ almost none of which is relevant. There isn’t any more information from the output beyond what I have relayed here. ‘lsblk’ sees and lists all my partitions, shows only the root partition is mounted. It’s a UEFI system using systemd-boot.
if you use eos-sendlog you can just post the url here. Even if you don’t have interenet with the system you can copy the journal to a file and then get on the internet and use eos-sendlog then to get us the url
for easier reading only include the relevant dates of information
Maybe it’s easier to chroot into it and copy paste the needed logs? But, I don’t know. Maybe both ways are complicated in this case, it is up to the op
Thank you all so much for the amazingly helpful help, deep insight, and wonderful suggestions for how to solve my problem. I have it working now. While I don’t know exactly what the origin of the problem was, I did get useful clues and good information from posts made in the Arch forum and at r/archlinux regarding these symptoms and log messages that suggested arch-chroot might yet again my friend and indeed it was. I ended up with another interesting but minor issue of mysterious origin once I got it booting but solved that without too much head scratching.