Can you share more of the output when it fails? Maybe take a picture of the whole screen?
Only thing that I changed recently was enabling fast_commit:
Filesystem features: has_journal ext_attr resize_inode dir_index fast_commit filetype needs_recovery extent 64bit flex_bg sparse_super large_file huge_file dir_nlink extra_isize metadata_csum
Are you sure that is your EFI partition that is failing to mount? That looks more like your root filesystem to me.
Compare that UUID to your disk to see which partition it is. If it is your root partition, try running fsck on it.
1 Like
dev/disk/by-uuid/dca1…
is my root partition according to fstab. So I run fsck on /dev/nvme0n1p2 ?
liveuser@eos-2022.12.17 ~]$ sudo fsck /dev/nvme0n1p2
fsck from util-linux 2.38.1
e2fsck 1.46.5 (30-Dec-2021)
/dev/nvme0n1p2 contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Unattached inode 4195698
Connect to /lost+found<y>? yes
Inode 4195698 ref count is 2, should be 1. Fix<y>? yes
Pass 5: Checking group summary information
/dev/nvme0n1p2: ***** FILE SYSTEM WAS MODIFIED *****
/dev/nvme0n1p2: 261903/30474240 files (0.2% non-contiguous), 4911097/121870848 blocks
[liveuser@eos-2022.12.17 ~]$
I will reboot and see what happens
That fixed the issue, I’m up and running again. Any idea what caused it, I mean is there something I need to look out for next time I update the system?
Thank you for the invaluable help getting my system back again!
1 Like
It probably has nothing to do with updating the system.
That looked like filesystem corruption. It can be caused by hardware issues, losing power to the drive while it is in use, not properly powering down the system, etc, etc
Never had any issues with the hardware or the other possible causes you mentioned. Just have to wait and see if it happens again.
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.