On 12/12/2020 02:03 PM, the...@sys-concept.com wrote: > I created empty "forcefsck" file in root (and reboot) to see what happens and > I get this: > > /dev/nvme0n1p4 780154/12206080 files (0.2% non-continous), 90753174/488213782 > blocks > fsck.fat 4.1 (2017-01-24) > Open: No such file or directory > * Filesystem couldn't be fixed > * rc: Aborting! > * * fsck: caught SIGTERM, aborting > INIT: Entering runlevel: 3 > * Checking local filesystems (check forced) ...
I booted from USB and run: fsck -fy /dev/nvme0n1p4 fsck from util-linux 2.35.2 e2fsck 1.45.5 (07-Jan-2020) Pass 1: Checking inodes, blocks, and sizes Pass 2: Checking directory structure Pass 3: Checking directory connectivity Pass 4: Checking reference counts Pass 5: Checking group summary information /dev/nvme0n1p4: 780154/122060800 files (0.2% non-contiguous), 90753174/488213782 blocks fsck -n /dev/nvme0n1p4 fsck from util-linux 2.35.2 e2fsck 1.45.5 (07-Jan-2020) /dev/nvme0n1p4: clean, 780154/122060800 files, 90753174/488213782 blocks (check after next mount)
