DSM-G600, DNS-3xx and NSA-220 Hack Forum

I implemented a fan_ctrl.sh script as part of my ffp enhancement. It had been working flawlessly for several days, shutting off the fan when "temperature g 0" returned temps below 100F, and varying speeds as needed when the temp was above 100F. I even have the script logging each reading to a log file on my USB flash disk where ffp resides.

Well, yesterday I came home and found the DNS-323 very warm to touch, the drives spinning, and the fan OFF (physically not spinning).  I telneted in and checked the log and ps - the script was still running and logging readings.  The log was showing fan speed set to "0" and temperature at 32F.  I ran a "temperature g 0" and it reported 32F (thus the fan was legitimately stopped based on that reading).  I ran a "fanspeed g" and the speed was reported back at something like 3400 (not 0) even though the fan was not actually spinning.  I then ran "fanspeed w 4000" to turn the fan on...  No response. The fan did not start.

I changed the fan_ctrl.sh script to non-execute and rebooted the DNS (so as to use the built in fancontrol program).  Upon reboot, the fan started normally.  I immediately ran "temperature g 0" and got a reading of 122F and the fan was spinning at around 4K RPM. The unit quickly cooled down.

I am now back to running the Dlink fancontrol as opposed to my script.

Any thoughts?

BTW. I see in the v 1.06 firmware that fancontrol is being modified to shut the fan off now if temps get low enough to do so.  That is a welcome addition as it makes the fan_ctrl.sh script unnecessary.

Last edited by jesbo (2008-10-22 22:11:52)