Feb 28 09:15:15 nuc kernel: JBD2: journal reset failed
Feb 28 09:15:15 nuc kernel: EXT4-fs (sdc1): error loading journal
The above was in journalctl when mount command failed.
So tried fsck
$ sudo fsck /dev/sdc1
fsck from util-linux 2.39.3
e2fsck 1.47.0 (5-Feb-2023)
/dev/sdc1: recovering journal
/dev/sdc1 has gone 66 days without being checked, check forced.
Pass 1: Checking inodes, blocks, and sizes
Inode 118489333 extent tree (at level 2) could be narrower. Optimize<y>? yes
Inode 118489579 extent tree (at level 1) could be narrower. Optimize<y>? yes
Inode 118489629 extent tree (at level 2) could be narrower. Optimize<y>? yes
Inode 118489674 extent tree (at level 1) could be narrower. Optimize<y>? yes
Inode 236848701 extent tree (at level 1) could be shorter. Optimize<y>? yes
Pass 1E: Optimizing extent trees
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Free blocks count wrong (203470928, counted=202796926).
Fix<y>? yes
/dev/sdc1: ***** FILE SYSTEM WAS MODIFIED *****
/dev/sdc1: 1818337/244187136 files (0.2% non-contiguous), 773948802/976745728 blocks
After fsck
I tried mount
and ls
which took some time, but fortunately it worked