Re: [gentoo-user] fsck: caught SIGTERM, aborting

2020-12-12 Thread thelma
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

[gentoo-user] fsck: caught SIGTERM, aborting

2020-12-12 Thread thelma
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: