Tag Info

New answers tagged


This is not normal... it suggests catastrophic failure. 512 MB is tiny so maybe the hardware is dying of old age now? FAT is pretty crude, I suggest you cut your losses and interrupt the fsck. It's not re-balancing b-trees or something intricate like that. Ctrl+c / kill -SIGINT is the gentlest approach, so it probably won't work. You can escalate to ...


As @fd0 has pointed out, change the pass value to 2 Why? Answer: pass – A number indicating the order in which the fsck program will check the devices for errors at boot time; this is 1 for the root file system and either 2 (meaning check after root) or 0 (do not check) for all other devices.


The latter (fsck.mode=force) is the right approach. However, to fsck a root, you must either: have a systemd-controlled initramfs (so that it could parse fsck.mode=force) with the corresponding fsck binary built in; have an initramfs which mounts rootfs read-only (so that systemd, started from rootfs, still can check it — checking a read-write mounted ...

Top 50 recent answers are included