Unfortunately no one can be told what fun_plug is - you have to see it for yourself.
You are not logged in.
Hi all,
yesterday i resetted my NAS to factory defaults. Spindown works so far, but the fan runs continuously.
So i installed Fonz Fun_Plug 0.3 from the Wiki. After reboot, the fan adjusted to temperature, but no hdd-spindown happens.
Only when i disable "mnt/HD_a2/ctrl_speedfan.sh" in the "fun_plug" file, reboot and start it manually, spindown works.
Does anybody know why?
I will try to insert a "sleep 60" in the "fun_plug", but i don't know, what it shoul help...
Offline
the same happens here... i used funplug 0.5 with 1.03 fw on chsnas without ANY trouble. then i updated o 1.04rc3 (now rc4) and resetted to defaults, as suggested by the maker(s) of the 1.04 firmware - but i can have EITHER spindown with fan runnin all the time (doesnt funplug work here?) OR fancontrol but NO spindown (with funplug 0.5)
oddly, after going back to fw 1.03 this behaviour did NOT change. but it used to work before. now i am stuck! any ideas?
cheerio
Offline
w00 wrote:
the same happens here... i used funplug 0.5 with 1.03 fw on chsnas without ANY trouble. then i updated o 1.04rc3 (now rc4) and resetted to defaults, as suggested by the maker(s) of the 1.04 firmware - but i can have EITHER spindown with fan runnin all the time (doesnt funplug work here?) OR fancontrol but NO spindown (with funplug 0.5)
oddly, after going back to fw 1.03 this behaviour did NOT change. but it used to work before. now i am stuck! any ideas?
cheerio
I lost the spindown completely after upgrading to fw 1.04rc4 on my CH3SNAS. It does not matter if i use the fancontrol script or not.
edit: after removing the fanscript and restarting the nas, my spindown works again!
Last edited by knireis (2008-07-14 22:22:47)
Offline
but i dont understand why spindown AND fancontrol DO NOT work again after downgrading fw to 1.03...
i guess we must wait for a new funplug version by fonz, hope he'll be back soon
cheerio
EDIT: major error: of course it should be ...DO NOT work again...
Last edited by w00 (2008-07-17 22:15:26)
Offline
I also lost the spindown feature with the fancontrol script. It used to work fine with firmware 1.03.
The script must be accessing the harddrive, even while it is supposed to run from ramdrive (according to the fancontrol-script and logging has been disabled). I think something has changed in the firmware and the path to the ramdrive is not correct anymore. But i have not much linux knowledge. Maybe zeroday, who is associated with conceptronic can confirm this.
Can it be the same cause of the cleanboot script not working on the CH3SNAS?
Offline
I had the same problem on a CH3SNAS (fw 1.03, ffp 0.4, 0.5): Either the fan would stop, but the disks would spin or vice versa. Tried many different ways, none worked for me. :-/
Still hoping to get it fixed one day.
Offline
any news on this? still suffering from the same problem described in this thread, also under fw 1.04rc5
cheerio
Offline
Try adding the line
PATH=/usr/bin:/bin:/usr/sbin:/sbin
just below the #!/bin/sh line at the top of the fan control script (and make sure it's running from the ramdrive, I use /fanctrl).
Offline
using this script, its a nogo
#!/bin/sh
#
# This script was created at http://dns323.kood.org by FIB,
# it has been slightly modified by leper (with help from
# fonz). It sets the fanspeed of the device depending on
# the temperature, which is measured in Fahrenheit. If
# your box measures temperature in Celsius, you need to
# edit it to work.
# Additional changes by gartylad.
# Set the path to use RAM-disk instead of harddrive, to
# execute from. This is done so that the disks will go
# into sleep mode, while the script is running.
PATH=/usr/bin:/bin:/usr/sbin:/sbin
# Create a logfile on the RAM-disk.
LOGDIR=/log
FANLOGFILE=${LOGDIR}/fan_ctrl.log
mkdir -p ${LOGDIR}
# Kill the old fan controller.
kill -9 `pidof fancontrol`
echo "Fancontrol killed. Installing fan_ctrl.sh" >${FANLOGFILE}
# With temps between T1 and T2, the script automatically
# lowers/raises the fanspeed between RPM1 and RPM2. This
# it does every update_interval seconds.
update_interval=60
T1=108
T2=140
RPM1=2300
RPM2=4500
while [ 1 ]
do
T=`temperature g 0`
T=${T##*=}
# Check if temperature has fallen below T1 value
if [ $T -lt $T1 ]; then
# Temp below T1 fan stops
CALCTEMP=`expr 0`
else
# Temp above T1 fan starts
CALCTEMP=`expr \( \( $T2 \< $T \) \* $RPM2 \) \| \( \( $RPM1 + \( $RPM2 - $RPM1 \) \* \( $T - $T1 \) \/ \( $T2 - $T1 \) \) \& \( $T \>= $T1 \) \)`
fi
CONVFTOC=`expr \( \( $T - 32 \) \* 10 + 9 \) \/ 18`
newRPM=${CALCTEMP}
fanspeed w $newRPM
echo `date`" ::CURRENT::" $T"F" ${CONVFTOC}"C -- fanspeed:" $newRPM "(written to "${FANLOGFILE}")." >>${FANLOGFILE}
# wait for next cycle
sleep $update_interval
done
Offline
That's the script mine is very similar to. Is the script itself running from the ramdisk?
Also, the 'echo' near the bottom of that will eventually fill the ramdisk because it only appends to the log, I reccommend making it
echo `date`" ::CURRENT::" $T"F" ${CONVFTOC}"C -- fanspeed:" $newRPM >${FANLOGFILE}
- it replaces it every time and doesn't have the pointless "(written to the file you're looking at)" on the end.
Offline
Solution to this/my spindown-problem was found here:
http://www.aroundmyroom.com/2008/08/04/ … ment-34194
this means a small change via editing the fun_plug file did the trick. dont ask me why reverting to formware 1.03 and reinstall of the funplug didnt undo the problem. however, now you know how to fix it in 1.04rc5 and fun_plug 0.5
good blog btw, itsthe programmer of the firmware
cheerio
Offline
w00 wrote:
Solution to this/my spindown-problem was found here:
http://www.aroundmyroom.com/2008/08/04/ … ment-34194
this means a small change via editing the fun_plug file did the trick. dont ask me why reverting to formware 1.03 and reinstall of the funplug didnt undo the problem. however, now you know how to fix it in 1.04rc5 and fun_plug 0.5
good blog btw, itsthe programmer of the firmware
cheerio
I read the comment in the link you provided, but i am not sure if i understand what and where to change. Can you be a bit more specific?
Offline
knireis: what i did was
1. flash to 1.04rc5
2. install latest fun_plug 0.5
3. reboot
4. edit the file /mnt/HD_A2/fun_plug via telnet on the ch3snas - in order to avoid incompatibility with the xp-editor's return codes ('vi /mnt/HD_A2/fun_plug') like this:
4.1 edit the line containing FFP_LOG= to 'FFP_LOG= /dev/null'
4.2 after the line '# run commands'
i manually add this line: 'cd /'
5. reboot.
thats it. works here. fonz knows about it and will hopefully include these chages in the next 0.5 funplug (which is still beta now)
hope this helps.
cheerio
Offline
ok thanks, i can manage that. Which fancontrolscript do you use?
Offline
w00 wrote:
4.1 edit the line containing FFP_LOG= to 'FFP_LOG= /dev/null'
4.2 after the line '# run commands'
i manually add this line: 'cd /'
fonz knows about it and will hopefully include these chages
4.1. No. Actually I think that change should not be necessary. If all services started from fun_plug (i.e. start/*.sh) detach properly, the log file is closed when fun_plug ends. Also, the log file has helped with problems many times, already. It's not wise to turn it off in the default.
4.2. Yes, will add 'cd /'
Offline
w00 wrote:
Solution to this/my spindown-problem was found here:
http://www.aroundmyroom.com/2008/08/04/ … ment-34194
this means a small change via editing the fun_plug file did the trick. dont ask me why reverting to formware 1.03 and reinstall of the funplug didnt undo the problem. however, now you know how to fix it in 1.04rc5 and fun_plug 0.5
good blog btw, itsthe programmer of the firmware
cheerio
it's my blog, but I'm not the programmer .. lucky me ..
Offline
I lost the spindown completely after firmware 1.04rc5. I have only ffp0.5 with telnet and twonky. It used to spindown with older firmware. Can it be the buildin upnp mediaserver? I have it disabled but still shows up on my mediaplayer.
Offline
Anyone found a proper fan script yet?
I'm running FFP from a usb stick, so the drives spin down normally, but when running the fun script from the wiki (which claims to be run from the ramdisk?) the drives stay on.
For testing purpopes I put the interval variable at 600 secs and then the log is full of HD standby and awake messages. So the fanscript is somehow awaking the discs. But why? I don't see any commands accessing the disk...
EDIT: as I'm thinking about it, maybe it uses some room in the swap which actives the drives (to write there)?
Last edited by Jimmie (2008-08-21 22:11:50)
Offline