Hi,
Looking at the script /sbin/do_fsck.sh on my NAS220 with firmware version "sg2000-2000-1231.img" - I note that the script "/sbin/do_fsck.sh" wants to clean the file system with
/sbin/fsck.ext3 -fy /dev/vg0/lv0
(this is on line 43 of the script)
PROBLEM - /sbin/fsck.ext3 does not exist.
I discovered this because I noticed some strange behaviour and undeletable files on a share. In fact, they were ALSO shown as "file not found" when I used my host system (linux) to list them. This (in my experience) is sometimes symptomatic of a corrupted filesystem. SO.... I logged into the NAS to see if I could do an fsck. Having unmounted the LV i just tried
"fsck /dev/vg0/lv0" and got an error telling me that there was no fsck.ext3.
I then checked through all the scripts and references to fsck and the "automatic clean" feature and found that (as of this firmware update) it will never be able to clean the filesystem via this method.
(NB This is the method that flashes the ID,Power and "USB Baqckup" LED's.)
My SOLUTION was simple - I linked /sbin/e2fsck with fsck.ext3.
ln /sbin/e2fsck /sbin/fsck.ext3
The only repercussions of NOT fixing it (as far as I can see) is that your machine could get into a loop (witha particularly dirty file system) where it constantly reboots and yet SAYS that the filesystem is clean (when of course it isn't - because it hasn't been fsck'd)
Maybe this information is of little or no use to anyone. But, I did hunt and search to see if anyone had already noticed/solved it and could only find a single reference to fsck and it wasn't this issue.
I don't know what other methods one should use to report (possible) errors in the firmware. Any suggestions?
Dave M
