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

Right, since no-one responded, I assumed that no-one had an answer.  So I created one.

This is my new fan_ctrl.sh script that works for the C1 hardware revision.  Has switch on/off hysteresis and now, after some tweaks, won't keep the hard drives spun up either.

#!/bin/sh
#
# Script by getik
# It sets the fanspeed on the DNS-323 hardware revision
# C1 depending on the device temperature.
# It is loosely based on scripts originally by FIB,
# leper, fonz, gartylad and Uriel which can be found
# at http://dns323.kood.org.
# All temps in Fahrenheit.  If your device measures in
# Celcius, you will need to adjust the script.

PATH=/usr/bin:/bin:/usr/sbin:/sbin

# Kill fancontrol process
OLDPID=`pidof fancontrol`
if [ "$OLDPID" != "" ]; then
    kill -9 $OLDPID
fi

# T1 = temp where fan switches on
# T2 = temp where fan switches to high
# T3 = temp where fan switches off when it is already running
update_interval=30
T1=110
T2=120
T3=105

while [ 1 ]
do
# get the current temperature and fan status
T=`temperature g 0`
T=${T##*=}
S=`fanspeed g`

if [ $S -lt 1 ]; then
#    echo "Fan status: stopped"
    if [ $T -gt $T2 ]; then
#        echo "Fan set: high"
        fanspeed h > /dev/null
    elif [ $T -gt $T1 ]; then
#        echo "Fan set: low"
        fanspeed l > /dev/null
    fi
else
#    echo "Fan status: running"
    if [ $T -lt $T3 ]; then
#        echo "Fan set: stop"
        fanspeed s > /dev/null
    elif [ $T -lt $T2 ]; then
#        echo "Fan set: low"
        fanspeed l > /dev/null
    else
#        echo "Fan set: high"
        fanspeed h > /dev/null
    fi
fi 

sleep $update_interval
done

I've also had to make changes to my fan.sh startup script to copy this script to the ramdrive.  This MIGHT not be required any more, but was one of the things I ended up doing to ensure that my drives spin down.

#!/ffp/bin/sh
 
# PROVIDE: fan_ctrl.sh
# REQUIRE: LOGIN
 
. /ffp/etc/ffp.subr
 
name="fan_ctrl.sh"
command="/ffp/bin/$name"
sshd_flags=
 
start_cmd="fan_ctrl_start"
 
fan_ctrl_start()
{
        cp $command /usr/bin/fan_ctrl.sh
        proc_start_bg /usr/bin/fan_ctrl.sh
}
 
run_rc_command "$1"

If you use this, please post here and let me know if it works for you too.  You will most likely have to tweak the temperatures for your ambient and your device's temperature sensor (mine seems to over read significantly).  I also haven't ever had my device breach the upper limit, so my fan is always on low or off.

Enjoy!

Could you write a "how to" to make this script work?
I have the C1 and i dont get the fanct1 script to work, could i just copy your script and set it in the fanct1.conf???

Sorry for the late reply but I don't check this forum very often...

Anyways I've also written my own fan control script some time ago and I've shared it here on this post: http://dns323.kood.org/forum/viewtopic.php?id=6072

My approaches uses cron (and copying script to ramdisk) to avoid accessing the harddisk.

I have revision B1 but I wrote the script so that it would work on C1 too. It also has hysteresis.

konke wrote:

Could you write a "how to" to make this script work?
I have the C1 and i dont get the fanct1 script to work, could i just copy your script and set it in the fanct1.conf???

When someone answers Mizu can you also let me know how to use this script?

I understand what it is doing based on the comments but I am really new to all this scripting and linux and I dont know what to do with it. 

I know you dump the contents of the script into a notepad++ and save as a .sh extension, but what do I do with the file afterwards and what commands to use in the ssh terminal to set them to be persistent on reboot?

Thanks

Thanks! this looks great. 

Only problem is I dont have access to the start folder when I browse to it from windows

What is the command to allow access or the CP syntax to copy from local windows PC to the NAS?

Thanks bgravato, managed to run all the commands and save all appropriate scripts.

Does this work with C1 though? 

I saved the sh files to proper directory's and set permissions as per step 3, but my fan is on after reboot and temperature g 0 shows current temp as 91, according to the script that should mean the fan is off correct?

Last edited by mfpockets (2011-01-11 04:23:00)

Just edited my previous post while you were posting.   See above

Ok so

fanspeed s did stop my fan.  I saw it took a minute from what I did understand from the script.  Where would I need to alter this?  "fanspeed s|l|h"

Or is applying the script from the OP the same as applying this one?  How do I appropriately remove the one I applied?  simply cd to the directory and then use whatever command is the unix command for del?

Last edited by mfpockets (2011-01-11 04:34:26)

it gave me an output of 0 as it is currently stopped I guess

I guess it was fanspeed h for high and then it returned 1 and it returns a 1 as well.....

mfpockets wrote:

Ok so

fanspeed s did stop my fan.  I saw it took a minute from what I did understand from the script.  Where would I need to alter this?  "fanspeed s|l|h"

My script already has that changed, so it works on all A1/B1/C1

mfpockets wrote:

Or is applying the script from the OP the same as applying this one?  How do I appropriately remove the one I applied?  simply cd to the directory and then use whatever command is the unix command for del?

If you have another script installed and running it might be getting in the way...

To delete a file the command is rm file but use it very carefully... to avoid mistakes always add the option -i like this rm -i file
It will prompt before deleting.

Another safer option for disabling other scripts without deleting them is to remove the executing permissions.
You can do this similarly to what you did in step 3 but changing "+x" to "-x" like this:
chmod -x file.sh

A few basic linux commands:
ls - list files (similar to dir in old DOS system)
cd - change directory (works like cd in the old DOS)
cp - copy files
mv - move files
rm - delete files

You can get a manual page for commands by typing: man command-name
For example, to get the man page for 'cp' type: man cp
To scroll down in the page use the arrow keys/pageup/pagedown or space bar. To quit the man page press 'q'

Another trick to avoid typing by hand all the filenames: type just the first letters of the filename or directory name and press TAB. If only one completing option is available it will write the rest of it automatically, If nothing happens press TAB again, if more than one option is available it will show the available options (type more letters of the filename until it differs from the other options then you can use TAB again to complete). If pressing TAB twice doesn't do anything that it's because there's not completion options available with the letters you typed.

mfpockets wrote:

should I just replace this:

# variables (temperatures are in Fahrenheit)
#
# fan will stop when temperature reaches this value
TEMP_STOP=96
# fan will spin at low speed when temperature reaches this value
TEMP_LOW=104
# fan will spin at high speed when temperature reaches this value
TEMP_HIGH=113
# this is fan's rpm (rotations per minute) reference point to determine
# wether the fan is rotating at high or low speed
RPM_REF=4000

# get current temperature and fan speed
TEMP=$(temperature g 0)
TEMP=${TEMP##*=}
SPEED=$(fanspeed g)

# check fan speed
if [ $SPEED -lt 1 ]
    # fan is stopped
then
    if [ $TEMP -ge $TEMP_HIGH ]
    then
        # set high speed
        fanspeed h
    elif [ $TEMP -ge $TEMP_LOW ]
    then
        # set low speed
        fanspeed l
    fi
else
    # fan is spinning
    if [ $TEMP -le $TEMP_STOP ]
    then
        # stop the fan
        fanspeed s
    elif [ $SPEED -lt $RPM_REF ]
        # fan at low speed
    then
        if [ $TEMP -ge $TEMP_HIGH ]
        then
            # set high speed
            fanspeed h
        fi
    else
        # fan at high speed
        if [ $TEMP -le $TEMP_LOW ]
        then
            # set low speed
            fanspeed l
        fi
    fi
fi   

WITH THIS INSTEAD

# T1 = temp where fan switches on
# T2 = temp where fan switches to high
# T3 = temp where fan switches off when it is already running
update_interval=30
T1=110
T2=120
T3=105

while [ 1 ]
do
# get the current temperature and fan status
T=`temperature g 0`
T=${T##*=}
S=`fanspeed g`

if [ $S -lt 1 ]; then
#    echo "Fan status: stopped"
    if [ $T -gt $T2 ]; then
#        echo "Fan set: high"
        fanspeed h > /dev/null
    elif [ $T -gt $T1 ]; then
#        echo "Fan set: low"
        fanspeed l > /dev/null
    fi
else
#    echo "Fan status: running"
    if [ $T -lt $T3 ]; then
#        echo "Fan set: stop"
        fanspeed s > /dev/null
    elif [ $T -lt $T2 ]; then
#        echo "Fan set: low"
        fanspeed l > /dev/null
    else
#        echo "Fan set: high"
        fanspeed h > /dev/null
    fi
fi

sleep $update_interval
done

No. It does about the same, but in a different manner, and uses the sleep mode which isn't compatible with the cron method I use for my script. My script already has the commands set for working with C1 in the same way as that script... So there's no need to change anything.

mfpockets wrote:

I swapped the code from the first post with yours, only starting at the Temp variables and keeping the your original portion that specifies script dir and the part about killing the pid of the original, but still the unit turns on, this time 89 fareiheint (I readjust your his code to match your F ratings) and still the fan is on instead of off...  Do I need to turn off the fan control in the Dlink Web UI ?  or the Kill process takes care of that?

It should take care of it but they might have changed the behaviour in C1, so try changing it to manual (it should put it to full speed I think but then the script will take over in the next minute).

Copying my script to the other and mixing the two might not be such good idea... My script does pretty much the same thing as the other, but in a different manner. Mixing the two might give unexpected results.

Also the file names for the scripts matter. If you save it with a different filename that what I suggested it will fail to copy it to ramdisk and to launch it from the crontab (this is what the script in ffp/start does).

I'll try to explain this better... The script fan-cron.sh in ffp/start is run one time at boot time. It copies a file named "fan_ctrl_cron.sh" to ram and add it to the crontab list, if that file does not exist with that name it will fail and the script won't run.

As a side note (and this is somewhat irrelevant here) I forgot that ffp creates a simlink in the root dir for ffp so in the commands where I wrote "/mnt/HD_a2/ffp/..." I could have simply written "/ffp/..." omitting the "mnt/HD_a2/" which might lead to some confusion, sorry for that.