Troubleshooting • Cannot properly scan system for error: fsck at reboot scan only the fat32 partition rather than main OS partition

I have a Raspberry Pi with latest RaspiOS bookworm all updates installed. Pishrink reports me some errors that almost certainly have been caused by blackouts faced in these days... I have tried to perform fscheck manually withbut it doesn't work because in use OS partition cannot be unmounted and scanned...fair enough, although I would have expected a request for automatically scheduling it at next reboot, so I have tried the ways normally suggested everywhere to force fsck at reboot:

- appending to cmdline.txt the check is performed only on the little fat32 partition of SD named mmcblk0p1 not to the main ext4 partition named mmcblk0p2 as I can see from the journal (and it was also evident by the fact the process ended too much fast)

- creating a forcefsck file in the main directory.... same result plus a warning to not use this way because deprecated.

It blows my mind how it is so confusing scan for errors the main OS partition.
This is an important thing and rather basilar in any modern OS... but unfortunately I cannot find anywhere the proper way to achieve it.

How should I do? and where is the config file where are specified fsck parameters for fsck executed at boot time?
Being forced to have physical access to the device and use another operating system to scan it seems ridiculous, I refuse to think that is the only solution.

Statistics: Posted by JohnAmstrong — Fri Sep 13, 2024 8:34 pm

---