| 1 |
On 12/12/2020 02:03 PM, thelma@×××××××××××.com wrote: |
| 2 |
> I created empty "forcefsck" file in root (and reboot) to see what happens and I get this: |
| 3 |
> |
| 4 |
> /dev/nvme0n1p4 780154/12206080 files (0.2% non-continous), 90753174/488213782 blocks |
| 5 |
> fsck.fat 4.1 (2017-01-24) |
| 6 |
> Open: No such file or directory |
| 7 |
> * Filesystem couldn't be fixed |
| 8 |
> * rc: Aborting! |
| 9 |
> * * fsck: caught SIGTERM, aborting |
| 10 |
> INIT: Entering runlevel: 3 |
| 11 |
> * Checking local filesystems (check forced) ... |
| 12 |
|
| 13 |
I booted from USB and run: |
| 14 |
|
| 15 |
fsck -fy /dev/nvme0n1p4 |
| 16 |
fsck from util-linux 2.35.2 |
| 17 |
e2fsck 1.45.5 (07-Jan-2020) |
| 18 |
Pass 1: Checking inodes, blocks, and sizes |
| 19 |
Pass 2: Checking directory structure |
| 20 |
Pass 3: Checking directory connectivity |
| 21 |
Pass 4: Checking reference counts |
| 22 |
Pass 5: Checking group summary information |
| 23 |
/dev/nvme0n1p4: 780154/122060800 files (0.2% non-contiguous), |
| 24 |
90753174/488213782 blocks |
| 25 |
|
| 26 |
|
| 27 |
fsck -n /dev/nvme0n1p4 |
| 28 |
fsck from util-linux 2.35.2 |
| 29 |
e2fsck 1.45.5 (07-Jan-2020) |
| 30 |
/dev/nvme0n1p4: clean, 780154/122060800 files, 90753174/488213782 blocks |
| 31 |
(check after next mount) |
Archives