Fsck.fat executed, or not?

I have SD-card as "mass storage", formatted as FAT, and in

config mount
        option uuid '....'
        option enabled '1'
        option options 'noatime'
        option target '/mnt/sda1'
        option enabled_fsck '1'

Access to SD-card works.

After "dirty" reboot, in logread I see

Sun Jul 14 09:40:26 2019 kern.warn kernel: [ 16.164475] FAT-fs (mmcblk0): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.

which is correct, but nothing from expected fsck.
Shouldn't there be at least some type of info, that fsck.fat ran ?

OK, found some trace: Looks like a bug in "block":
Actually there is in block.c:

const char *dosfsck = "/usr/sbin/dosfsck";

which is wrong.
Correct might be
const char* dosfsck = "/usr/sbin/fsck.fat";

Chances are, that a link will do the trick, as "First Aid".

Also, looks like instead of (deprecated ?)
option enabled_fsck '1'
in mount section
I should better use
option check_fs '1'
in global section.

Could be a good idea, to move this topic to developers section.

Having quite a few similar experiences ("The only doc is the source code") in the past, I take the liberty to remind to another , "ancient" principle of good programming:
"Software, which is not documented, does not exist."
From somebody, who did his first Assembler Code almost half a century ago.

1 Like

FWIW: this problem is exhibited in the arduino Yun using LEDE 17. I found the same error when reading the BLOCK utility. Any help with a link - how to construct - so I can move on? I am NOT a programmer, mind you. but have many Yuns and this error is crippling advances in sketches using the SD partition. Thank You.