NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
glem
May 22, 2013Aspirant
Easy fix fan/temp OS6 issues on x86 legacy #no support
>> EDIT - 2014-04-12 <<
Before to hack your system, update first to 6.1.7. Built-in fancontrol support is there!
6.1.7 has been released: http://www.readynas.com/forum/viewtopic.php?f=1&t=76000
>> EDIT <<
Here is how to fix fan and temperature issues on legacy x86 systems running OS 6.x, until built-in support is there.
I'd previously created this post http://www.readynas.com/forum/viewtopic.php?f=51&t=70133&start=255#p393886 but it will be easier for community to have fancontrol file examples for all models in a dedicated post.
It's a very easy and reliable method to monitor fan and temperature with lm-sensors and fancontrol standard packages.
No change on GUI reports.
NO WARRANTY / NO SUPPORT !!!
with root access, execute the following commands:
edit /etc/fancontrol file and copy the following file example corresponding to your model http://www.readynas.com/forum/viewtopic.php?f=51&t=71155#p395324
or create your own /etc/fancontrol file using pwmconfig command http://www.readynas.com/forum/viewtopic.php?f=51&t=71155&p=395324#p395318
fancontrol daemon start automaticaly when you install it.
restart fancontrol daemon for changes in file /etc/fancontrol take effect
to interact with fancontrol daemon, use
You can display sensors values with sensors command
Before to hack your system, update first to 6.1.7. Built-in fancontrol support is there!
6.1.7 has been released: http://www.readynas.com/forum/viewtopic.php?f=1&t=76000
>> EDIT <<
Here is how to fix fan and temperature issues on legacy x86 systems running OS 6.x, until built-in support is there.
I'd previously created this post http://www.readynas.com/forum/viewtopic.php?f=51&t=70133&start=255#p393886 but it will be easier for community to have fancontrol file examples for all models in a dedicated post.
It's a very easy and reliable method to monitor fan and temperature with lm-sensors and fancontrol standard packages.
No change on GUI reports.
NO WARRANTY / NO SUPPORT !!!
with root access, execute the following commands:
apt-get update && apt-get upgrade
apt-get install lm-sensors fancontrol
echo "#fancontrol" > /etc/fancontrol
edit /etc/fancontrol file and copy the following file example corresponding to your model http://www.readynas.com/forum/viewtopic.php?f=51&t=71155#p395324
or create your own /etc/fancontrol file using pwmconfig command http://www.readynas.com/forum/viewtopic.php?f=51&t=71155&p=395324#p395318
fancontrol daemon start automaticaly when you install it.
restart fancontrol daemon for changes in file /etc/fancontrol take effect
/etc/init.d/fancontrol restart
to interact with fancontrol daemon, use
/etc/init.d/fancontrol stop
/etc/init.d/fancontrol start
/etc/init.d/fancontrol restart
You can display sensors values with sensors command
root@nas-xx-xx-xx:~# sensors
coretemp-isa-0000
Adapter: ISA adapter
Core 0: +43.0°C (high = +80.0°C, crit = +100.0°C)
Core 1: +49.0°C (high = +80.0°C, crit = +100.0°C)
it8721-isa-0a10
Adapter: ISA adapter
in0: +12.19 V (min = +8.06 V, max = +10.66 V) ALARM
in1: +4.98 V (min = +2.20 V, max = +3.51 V) ALARM
in2: +3.28 V (min = +0.02 V, max = +0.18 V) ALARM
in3: +0.00 V (min = +0.00 V, max = +0.00 V) ALARM
in4: +1.02 V (min = +1.42 V, max = +2.21 V) ALARM
in5: +1.80 V (min = +1.66 V, max = +0.54 V) ALARM
in6: -12.10 V (min = -25.78 V, max = -0.01 V)
in7: +3.24 V (min = +0.00 V, max = +2.86 V) ALARM
in8: +3.34 V
fan1: 0 RPM (min = 10 RPM) ALARM
fan2: 0 RPM (min = 44 RPM) ALARM
fan3: 851 RPM (min = 11 RPM)
temp1: +0.0°C (low = +57.0°C, high = -25.0°C) ALARM sensor = thermistor
temp2: +0.1°C (low = -16.0°C, high = -123.0°C) ALARM sensor = thermal diode
temp3: +0.1°C (low = +37.0°C, high = -44.0°C) ALARM sensor = thermal diode
cpu0_vid: +2.050 V
173 Replies
Replies have been turned off for this discussion
- IridabikeAspirant*/1 means repeat every minute.
- scottminorAspirantCan I get a copy of your fancontrol file?
- IridabikeAspiranthere you go:
# Configuration file generated by pwmconfig, changes will be lost
INTERVAL=10
DEVPATH=hwmon0=devices/platform/coretemp.0 hwmon1=devices/platform/w83627ehf.2576
DEVNAME=hwmon0=coretemp hwmon1=w83627dhg
FCTEMPS= hwmon1/device/pwm2=hwmon1/device/temp2_input hwmon1/device/pwm1=hwmon1/device/temp1_input
FCFANS= hwmon1/device/pwm2=hwmon1/device/fan2_input hwmon1/device/pwm1=hwmon1/device/fan1_input
MINTEMP= hwmon1/device/pwm2=30 hwmon1/device/pwm1=55
MAXTEMP= hwmon1/device/pwm2=60 hwmon1/device/pwm1=60
MINSTART= hwmon1/device/pwm2=70 hwmon1/device/pwm1=16
MINSTOP= hwmon1/device/pwm2=70 hwmon1/device/pwm1=16
MINPWM= hwmon1/device/pwm2=70 hwmon1/device/pwm1=16
MAXPWM= hwmon1/device/pwm2=200 hwmon1/device/pwm1=80 - scottminorAspirantIt seems to be working. It shut down due to a high temp alert. I don't think the chassis fan is responding. Look at temp1.
coretemp-isa-0000
Adapter: ISA adapter
Core 0: +37.0°C (high = +76.0°C, crit = +100.0°C)
Core 1: +35.0°C (high = +76.0°C, crit = +100.0°C)
w83627dhg-isa-0a10
Adapter: ISA adapter
Vcore: +1.18 V (min = +0.00 V, max = +1.74 V)
in1: +20.93 V (min = +15.26 V, max = +12.67 V) ALARM
AVCC: +3.23 V (min = +2.98 V, max = +3.63 V)
+3.3V: +3.23 V (min = +2.98 V, max = +3.63 V)
in4: +6.06 V (min = +2.01 V, max = +3.07 V) ALARM
in5: +1.55 V (min = +2.48 V, max = +2.40 V) ALARM
in6: +1.55 V (min = +2.48 V, max = +2.40 V) ALARM
3VSB: +3.23 V (min = +2.98 V, max = +3.63 V)
Vbat: +3.18 V (min = +2.70 V, max = +3.63 V)
fan1: 856 RPM (min = 1214 RPM, div = 8) ALARM
fan2: 1467 RPM (min = 4821 RPM, div = 8) ALARM
fan3: 0 RPM (min = 1171 RPM, div = 128) ALARM
fan4: 0 RPM (min = 10546 RPM, div = 128) ALARM
fan5: 0 RPM (min = 878 RPM, div = 128) ALARM
temp1: +50.0°C (high = -3.0°C, hyst = +127.0°C) sensor = thermistor
temp2: +37.5°C (high = +80.0°C, hyst = +123.0°C) sensor = CPU diode
temp3: +1.5°C (high = +80.0°C, hyst = +123.0°C) sensor = thermistor
cpu0_vid: +0.000 V - scottminorAspirantI changed the temp from 60 to 40 and it seems to be calming down.
I added the "stuff" for the temp graph, but I am not seeing it post in the browser. Is there anything I can test to see if it's running? - scottminorAspirantIt's ALIVE. It is graphing temps!!!
Thank you!!! - scottminorAspirantsensors and frontview show different temp levels.
- ATCISTutor
Iridabike wrote: Paste the script text into a text file using a Linux compatible text editor. In Windows you can use Textpad. Save the file on the Nas with a name like TempUpdate.I store mine in the directory /data/Tims
Then edit /etc/crontab and add the line below:
*/1 * * * * root /data/Tims/UpdateTemp
I am no expert but Google is a good help for each step.
Dear Iridabike,
I'm tinkering around with the script that you wrote. Are you (or anyone else for that matter) familiar enough with the Ultra 4 hardware to know how to modify your script (if necessary) to make it work on an Ultra 4?
Thanks in advance!
EDIT: P.S. - Where the heck are the system logs on this crazy thing? I looked in/var/log directory and all I see is alternatives.log apt dmesg pkg.log fsck LeafP2P.log news samba apache2 btmp dmesg.0 frontview journal netatalk.log readynasd and wtmp :-? ?
I commonly refer to myself as the "Linux Idiot" (not to be confused with the VILLAGE IDIOT). I know back in the day one could issue the command # tail /var/log/messages and watch for system related events, but apparently that is no longer the case on modern Linux OS's. . .
Google'ing the topic didn't help much as most of the search results say something like this: "Troubleshooting and Common Problems - Edits to a user's crontab and jobs that are run on their behalf are all logged by default to /var/log/syslog and that's the first place to check if things are not running as you expect." Unless it's hidden, I do not see that one :?: - fastfwdVirtuoso
ATCIS wrote: Are you (or anyone else for that matter) familiar enough with the Ultra 4 hardware to know how to modify your script (if necessary) to make it work on an Ultra 4?
I don't have an Ultra4, but I can tell you how to discover the necessary modifications on your own.
Original Iridabike script for Pro6:#!/bin/sh
#######################################################
Coretemp="/sys/devices/platform/coretemp.0/temp2_input"
Systemp="/sys/devices/platform/w83627ehf.2576/temp2_input"
Coretemp2="/sys/devices/platform/coretemp.0/temp3_input"
Ct=`cat $Coretemp`
C=`expr $Ct / 1000`
Ct2=`cat $Coretemp2`
C2=`expr $Ct2 / 1000`
St=`cat $Systemp`
S=`expr $St / 1000`
rrdtool update /run/readynasd/stats/temperature_int_deg.rrd N:$C:$S
First, log in to your Ultra4's web GUI and see what its CPU and system temperatures are.
Next, SSH to the NAS. You're going to find the names of the temperature-reporting devices: CPU temp first, then System temp.cd /sys/devices/platform
ls
You're looking for "coretemp.n" directories. Your Ultra4 has a single-core CPU, I believe, so there should just be one "coretemp.n" directory, probably called "coretemp.0". Change to it and see what's in there:cd coretemp.0
ls
You'll see a number of files. The one you're interested in is "tempn_input", which reports the CPU core temperature. There's probably just one, called "temp1_input". See what it's reporting:cat temp1_input
If there are other "tempn_input" files, cat them as well. You're looking for one that reports a number approximately 1000 times the Celsius CPU temperature that was reported in the web GUI. When you find it, write down its full path and filename; that will replace "/sys/devices/platform/coretemp.0/temp2_input" in the first line of Iridabike's script.
Next, look for the system temperature:cd /sys/devices/platform
ls
You'll see a number of directories. One will have a name like "w83627ehf.2576", "it87.2576", etc. The name is actually the part number of the system-monitoring chip on your motherboard. Change to that directory and see what's in it:cd it87.2576
(Of course, use the directory name you found on your system; "it87.2576" is only an example.)
ls
You'll probably see a number of "tempn_input" files here. Look at each of them in turn:cat temp1_input
cat temp2_input
cat temp3_input
One of them will report a number that's either equal to the Celsius SYS temperature that was reported in the web GUI or 1000 times that temperature. When you find it, write down its full path and filename; that will replace "/sys/devices/platform/w83627ehf.2576/temp2_input" in the second line of Iridabike's script.
Delete the third line of Iridabike's script; it isn't used. Also delete the line that begins "Ct2=" and the line that begins "C2=".
If the temperature reported in the "it87.2576" directory was equal to the SYS temperature reported in the web GUI, change the "S=`expr $St / 1000`" line in Iridabike's script to "S=`expr $St / 1`". If it was 1000 times the temperature, leave that line alone.
When you're done, your new script should look something like this:
Example modification of Iridabike's script for the Ultra4:#!/bin/sh
#######################################################
Coretemp="/sys/devices/platform/coretemp.0/temp1_input"
Systemp="/sys/devices/platform/it87.2576/temp2_input"
Ct=`cat $Coretemp`
C=`expr $Ct / 1000`
St=`cat $Systemp`
S=`expr $St / 1`
rrdtool update /run/readynasd/stats/temperature_int_deg.rrd N:$C:$SATCIS wrote: Where the heck are the system logs on this crazy thing? I looked in/var/log directory and all I see is alternatives.log apt dmesg pkg.log fsck LeafP2P.log news samba apache2 btmp dmesg.0 frontview journal netatalk.log readynasd and wtmp :-? ? .... back in the day one could issue the command # tail /var/log/messages and watch for system related events, but apparently that is no longer the case on modern Linux OS's. . .
My syslog file (using RAIDiator 4) is in /var/log ; I'm not sure where OS6 puts it. Maybe in /tmp ? You can find it using the find command:find / -name syslog
And once you find it, you can watch it:tail -f /var/log/syslog
(or wherever it is on your system).
Hit ctrl-c to stop watching it. - ATCISTutorThank you for that awesome detailed reply fastfwd! :worship:
I'll try out your suggestions above and report back later. . .
Update #1: find / -name syslog --> Yields nothing :( It would appear that syslog is M.I.A.
Update #2: I followed the rest of your awesome instructions above (very helpful BTW). When I did the -/sys/devices/platform/it87.2576# cat temp1_input
I got 57
When I -sys/devices/platform/it87.2576# cat temp2_input
I got 31
and when I -/sys/devices/platform/it87.2576# cat temp3_input
I got -128 (so I assumed that was erroneous)
I wound up using the temp1_input as the ambient room temperature is a about 85 degrees F and 87.8 degrees F for temp2_input seemed too low to me.
My resulting script looks like this:#!/bin/sh
#######################################################
Coretemp="/sys/devices/platform/coretemp.0/temp2_input"
Systemp="/sys/devices/platform/it87.2576/temp1_input"
Ct=`cat $Coretemp`
C=`expr $Ct / 1000`
St=`cat $Systemp`
S=`expr $St / 1`
rrdtool update /run/readynasd/stats/temperature_int_deg.rrd N:$C:$S
So do I need to do anything to make it GO? My temperature graph is still quite empty. . .
Update #3: ps -A | grep syslogd --> Also yields nada. . .
Update #4: The contents of /var/run = acpid.pid crond.pid lock nmbd.pid rccombiner sshd utmp acpid.socket crond.reboot mdadm nut readydrop sshd.pid winbindd.pid apache2 ctch minidlna proftpd readynasd systemd apache2.pid dbus minissdpd.pid qbittorrent-nox.pid samba udev avahi-daemon fancontrol.pid minissdpd.sock raidard.pid sendsigs.omit.d upnphttpd.pid connman initctl mount rcbrokerd.pid smbd.pid user
Any chance that the file in there named "systemd" is important?
Are we having fun yet? :woot:
Related Content
NETGEAR Academy

Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!