I also ran fsck and there are minor errors (I think I can live with it), but if anyone knows how to trigger fsck on the root partition either at reboot or by remounting the volume rw, I won't mind fixing this too.
Indeed, looks like minor errors. Actually, I believe they aren't really errors.
I might be wrong, but looks like you were running efsck while there was activity on /var/spool.
The activity seems related to photostation indexing or thumbnail generation.
During indexing or thumbnail generation, temporary files are created for short time /var/spool.
If such files are created and deleted between fsck test phases we may get error/warning messages....
For the time being, don't worry about fsck on rootfs. It's checked at each boot.... So you want/need to run fsck on your rootfs? Just reboot ;-D.
Over the weekend I extracted the initrd files of my ds216play and a DS916+ to check what's done during booting phases.
Wanted to find out if a mechanism was used (like ubuntu's /forcefsck file) to force root filesystem fsck.
According to "/linuxrc.syno", it is done each time system boots (before root files system of DS hard drive is mounted).
You can check by looking at output of "sudo tune2fs -l
". See line "Last checked:". Should be close to last time your DS booted.