Archives
Archives
| From: | thelma@×××××××××××.com |
|---|---|
| To: | Gentoo mailing list <gentoo-user@l.g.o> |
| Subject: | [gentoo-user] fsck: caught SIGTERM, aborting |
| Date: | Sat, 12 Dec 2020 21:03:12 |
| Message-Id: | a63c84f4-7b5f-f268-4918-8293190a4463@sys-concept.com |
| 1 | I created empty "forcefsck" file in root (and reboot) to see what happens and I get this: |
| 2 | |
| 3 | /dev/nvme0n1p4 780154/12206080 files (0.2% non-continous), 90753174/488213782 blocks |
| 4 | fsck.fat 4.1 (2017-01-24) |
| 5 | Open: No such file or directory |
| 6 | * Filesystem couldn't be fixed |
| 7 | * rc: Aborting! |
| 8 | * * fsck: caught SIGTERM, aborting |
| 9 | INIT: Entering runlevel: 3 |
| 10 | * Checking local filesystems (check forced) ... |
| Subject | Author |
|---|---|
| Re: [gentoo-user] fsck: caught SIGTERM, aborting | thelma@×××××××××××.com |