Reply
Highlighted
Aspirant

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:
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
Message 1 of 172
Highlighted
Aspirant

Re: Easy fix fan/temp issues on OS6 legacy #no support

To create your own /etc/fancontrol file, use pwmconfig command
Here is an example for Ultra 6 model

execute the following commands and give answers according to your system
/etc/init.d/fancontrol stop
pwmconfig

# pwmconfig revision 5857 (2010-08-22)
This program will search your sensors for pulse width modulation (pwm)
controls, and test each one to see if it controls a fan on
your motherboard. Note that many motherboards do not have pwm
circuitry installed, even if your sensor chip supports pwm.

We will attempt to briefly stop each fan using the pwm controls.
The program will attempt to restore each fan to full speed
after testing. However, it is ** very important ** that you
physically verify that the fans have been to full speed
after the program has completed.

Found the following devices:
hwmon0/device is coretemp
hwmon1/device is it8721

Found the following PWM controls:
hwmon1/device/pwm1
hwmon1/device/pwm2
hwmon1/device/pwm3

Giving the fans some time to reach full speed...
Found the following fan sensors:
hwmon1/device/fan1_input current speed: 0 ... skipping!
hwmon1/device/fan2_input current speed: 0 ... skipping!
hwmon1/device/fan3_input current speed: 2265 RPM

Warning!!! This program will stop your fans, one at a time,
for approximately 5 seconds each!!!
This may cause your processor temperature to rise!!!
If you do not want to do this hit control-C now!!!
Hit return to continue: >> hit return <<

Testing pwm control hwmon1/device/pwm1 ...
hwmon1/device/fan3_input ... speed was 2265 now 2265
no correlation

No correlations were detected.
There is either no fan connected to the output of hwmon1/device/pwm1,
or the connected fan has no rpm-signal connected to one of
the tested fan sensors. (Note: not all motherboards have
the pwm outputs connected to the fan connectors,
check out the hardware database on http://www.almico.com/forumindex.php)

Did you see/hear a fan stopping during the above test (n)? >> n <<

Testing pwm control hwmon1/device/pwm2 ...
hwmon1/device/fan3_input ... speed was 2265 now 2257
no correlation

No correlations were detected.
There is either no fan connected to the output of hwmon1/device/pwm2,
or the connected fan has no rpm-signal connected to one of
the tested fan sensors. (Note: not all motherboards have
the pwm outputs connected to the fan connectors,
check out the hardware database on http://www.almico.com/forumindex.php)

Did you see/hear a fan stopping during the above test (n)? >> n <<

Testing pwm control hwmon1/device/pwm3 ...
hwmon1/device/fan3_input ... speed was 2265 now 0
It appears that fan hwmon1/device/fan3_input
is controlled by pwm hwmon1/device/pwm3
Would you like to generate a detailed correlation (y)? >> y <<
PWM 255 FAN 2257
PWM 240 FAN 2250
PWM 225 FAN 2235
PWM 210 FAN 2213
PWM 195 FAN 2149
PWM 180 FAN 2083
PWM 165 FAN 2020
PWM 150 FAN 1934
PWM 135 FAN 1849
PWM 120 FAN 1748
PWM 105 FAN 1646
PWM 90 FAN 1520
PWM 75 FAN 1380
PWM 60 FAN 1218
PWM 45 FAN 1040
PWM 30 FAN 831
PWM 28 FAN 416
PWM 26 FAN 512 (probably incorrect)
PWM 24 FAN 512 (probably incorrect)
PWM 22 FAN 516 (probably incorrect)
PWM 20 FAN 516 (probably incorrect)
PWM 18 FAN 517 (probably incorrect)
PWM 16 FAN 519 (probably incorrect)
PWM 14 FAN 521 (probably incorrect)
PWM 12 FAN 522 (probably incorrect)
PWM 10 FAN 522 (probably incorrect)
PWM 8 FAN 521 (probably incorrect)
PWM 6 FAN 519 (probably incorrect)
PWM 4 FAN 516 (probably incorrect)
PWM 2 FAN 0
Fan Stopped at PWM = 2


Testing is complete.
Please verify that all fans have returned to their normal speed.

The fancontrol script can automatically respond to temperature changes
of your system by changing fanspeeds.
Do you want to set up its configuration file now (y)? >> y <<
What should be the path to your fancontrol config file (/etc/fancontrol)? >> hit return <<
Loading configuration from /etc/fancontrol ...

Select fan output to configure, or other action:
1) hwmon1/device/pwm3 3) Just quit 5) Show configuration
2) Change INTERVAL 4) Save and quit
select (1-n): >> 1 <<

Devices:
hwmon0/device is coretemp
hwmon1/device is it8721

Current temperature readings are as follows:
hwmon0/device/temp2_input 38
hwmon0/device/temp3_input 38
hwmon1/device/temp1_input 0
hwmon1/device/temp2_input 0
hwmon1/device/temp3_input 0

Select a temperature sensor as source for hwmon1/device/pwm3:
1) hwmon0/device/temp2_input
2) hwmon0/device/temp3_input
3) hwmon1/device/temp1_input
4) hwmon1/device/temp2_input
5) hwmon1/device/temp3_input
6) None (Do not affect this PWM output)
select (1-n): >> 1 <<

Enter the low temperature (degree C)
below which the fan should spin at minimum speed (20): >> 51 <<

Enter the high temperature (degree C)
over which the fan should spin at maximum speed (60): >> 58 <<

Enter the minimum PWM value (0-255)
at which the fan STOPS spinning (press t to test) (100): >> 40 <<

Enter the minimum PWM value (40-255)
at which the fan STARTS spinning (press t to test) (150): >> 40 <<

Enter the PWM value (0-40) to use when the temperature
is below the low temperature limit (0): >> 40 <<

Enter the PWM value (40-255) to use when the temperature
is over the high temperature limit (255): >> 255 <<


Select fan output to configure, or other action:
1) hwmon1/device/pwm3 3) Just quit 5) Show configuration
2) Change INTERVAL 4) Save and quit
select (1-n): >> 4 <<

Saving configuration to /etc/fancontrol...
Configuration saved
/etc/init.d/fancontrol start
Message 2 of 172
Highlighted
Aspirant

Re: Easy fix fan/temp OS6 issues on x86 legacy #no support

Thanks to the forum, which gives examples for some systems ( /etc/fancontrol file ):

Example values for Ultra4 model:
# Configuration file generated by pwmconfig, changes will be lost
INTERVAL=10
DEVPATH=hwmon0=devices/platform/coretemp.0 hwmon1=devices/platform/it87.2576
DEVNAME=hwmon0=coretemp hwmon1=it8721
FCTEMPS=hwmon1/device/pwm1=hwmon0/device/temp2_input
FCFANS= hwmon1/device/pwm1=hwmon1/device/fan1_input
MINTEMP= hwmon1/device/pwm1=50
MAXTEMP= hwmon1/device/pwm1=60
MINSTART= hwmon1/device/pwm1=60
MINSTOP= hwmon1/device/pwm1=60
MINPWM= hwmon1/device/pwm1=60
MAXPWM= hwmon1/device/pwm1=255


Example values for Ultra6 model:
# Configuration file generated by pwmconfig, changes will be lost
INTERVAL=10
DEVPATH=hwmon0=devices/platform/coretemp.0 hwmon1=devices/platform/it87.2576
DEVNAME=hwmon0=coretemp hwmon1=it8721
FCTEMPS= hwmon1/device/pwm3=hwmon0/device/temp2_input
FCFANS= hwmon1/device/pwm3=hwmon1/device/fan3_input
MINTEMP= hwmon1/device/pwm3=51
MAXTEMP= hwmon1/device/pwm3=58
MINSTART= hwmon1/device/pwm3=40
MINSTOP= hwmon1/device/pwm3=40
MINPWM= hwmon1/device/pwm3=40
MAXPWM= hwmon1/device/pwm3=255


Example values for Pro6 model:
# 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


Example values for 2100V2 model:
# Configuration file generated by pwmconfig, changes will be lost
INTERVAL=10
DEVPATH=hwmon0=devices/platform/coretemp.0 hwmon1=devices/platform/it87.2576
DEVNAME=hwmon0=coretemp hwmon1=it8721
FCTEMPS=hwmon1/device/pwm3=hwmon0/device/temp2_input hwmon1/device/pwm2=hwmon0/device/temp2_input hwmon1/device/pwm1=hwmon0/device/temp2_input
FCFANS=hwmon1/device/pwm3=hwmon1/device/fan2_input hwmon1/device/pwm2=hwmon1/device/fan1_input hwmon1/device/pwm1=
MINTEMP=hwmon1/device/pwm3=51 hwmon1/device/pwm2=51 hwmon1/device/pwm1=51
MAXTEMP=hwmon1/device/pwm3=58 hwmon1/device/pwm2=58 hwmon1/device/pwm1=75
MINSTART=hwmon1/device/pwm3=40 hwmon1/device/pwm2=40 hwmon1/device/pwm1=150
MINSTOP=hwmon1/device/pwm3=40 hwmon1/device/pwm2=40 hwmon1/device/pwm1=0
MINPWM=hwmon1/device/pwm3=40 hwmon1/device/pwm2=40
MAXPWM=hwmon1/device/pwm3=255 hwmon1/device/pwm2=255
Message 3 of 172
Highlighted
Aspirant

Re: Easy fix fan/temp issues on OS6 legacy #no support

Great topic! Would love to see a config for Ultra4
Message 4 of 172
Highlighted
Aspirant

Re: Easy fix fan/temp issues on OS6 legacy #no support

If anyone wants their temperatures logged in Frontview in OS6 its just a standard round robin database that is meant to updated by readystatsd. For some reason my Pro 6 wont log anything. I guess there something wrong in readystatsd. It is running fine but fails to update the temperature databases. It's a compiled elf and I am not able to fix it so I made a simple script called every minute from crontab to sort it out. This is my first go at scripting so its a bit basic! My guess is that it will need to be modded for anything other than a Pro 6. Anyone with a bit more knowledge fancy sorting it properly? Ideally it would be best to decompile the elf and fix it at source.


#!/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_cputemp_deg.rrd N:$C
rrdtool update /run/readynasd/stats/temperature_systemp_deg.rrd N:$S
rrdtool update /run/readynasd/stats/temperature_system_deg.rrd N:$S


Message 5 of 172
Highlighted
Aspirant

Re: Easy fix fan/temp issues on OS6 legacy #no support

Ok upgraded to 6.0.8 and the rrd files have been changed. New script is:

#!/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



Edit: There is a problem in 6.0.8 as readynasd also updates the rrd file and gives odd readings on the trend. I have made a hacked elf to stop it, but I would prefer to correct the temperatures it reads and let it update the file itself.
Message 6 of 172
Highlighted
Aspirant

Re: Easy fix fan/temp issues on OS6 legacy #no support

I am not sure how to build the script. Can you show the commands for that?
ReadyNAS Pro 6 6.0.8 fancontrol UpdateTemp HTOP
Message 7 of 172
Highlighted
Aspirant

Re: Easy fix fan/temp issues on OS6 legacy #no support

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.
Message 8 of 172
Highlighted
Aspirant

Re: Easy fix fan/temp issues on OS6 legacy #no support

Does this work on a Pro 6?
ReadyNAS Pro 6 6.0.8 fancontrol UpdateTemp HTOP
Message 9 of 172
Highlighted
Aspirant

Re: Easy fix fan/temp issues on OS6 legacy #no support

Yep I have Pro 6
Message 10 of 172
Highlighted
Aspirant

Re: Easy fix fan/temp issues on OS6 legacy #no support

I think I have other issues. I cannot get fancontrol to work properly. I put this in place, thank you for doing that!

On the crontab, does */1 mean to use * or 1 in the first field?
ReadyNAS Pro 6 6.0.8 fancontrol UpdateTemp HTOP
Message 11 of 172
Highlighted
Aspirant

Re: Easy fix fan/temp issues on OS6 legacy #no support

*/1 means repeat every minute.
Message 12 of 172
Highlighted
Aspirant

Re: Easy fix fan/temp issues on OS6 legacy #no support

Can I get a copy of your fancontrol file?
ReadyNAS Pro 6 6.0.8 fancontrol UpdateTemp HTOP
Message 13 of 172
Highlighted
Aspirant

Re: Easy fix fan/temp issues on OS6 legacy #no support

here 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
Message 14 of 172
Highlighted
Aspirant

Re: Easy fix fan/temp issues on OS6 legacy #no support

It 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
ReadyNAS Pro 6 6.0.8 fancontrol UpdateTemp HTOP
Message 15 of 172
Highlighted
Aspirant

Re: Easy fix fan/temp issues on OS6 legacy #no support

I 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?
ReadyNAS Pro 6 6.0.8 fancontrol UpdateTemp HTOP
Message 16 of 172
Highlighted
Aspirant

Re: Easy fix fan/temp issues on OS6 legacy #no support

It's ALIVE. It is graphing temps!!!

Thank you!!!
ReadyNAS Pro 6 6.0.8 fancontrol UpdateTemp HTOP
Message 17 of 172
Highlighted
Aspirant

Re: Easy fix fan/temp issues on OS6 legacy #no support

sensors and frontview show different temp levels.
ReadyNAS Pro 6 6.0.8 fancontrol UpdateTemp HTOP
Message 18 of 172
Highlighted
Tutor

Re: Easy fix fan/temp issues on OS6 legacy #no support

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 :?:
Message 19 of 172
Highlighted
Virtuoso

Re: Easy fix fan/temp issues on OS6 legacy #no support

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
ls
(Of course, use the directory name you found on your system; "it87.2576" is only an example.)

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:$S


ATCIS 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.
2 × Pro 6 [Main & Backup] – XRAID2 Dual-Redundant (RAID6): 14.53TB (110MB/s Write, 123MB/s Read)
    CPU: 2.4GHz E6600 SL9ZL - RAM: 8GB (PSD28G800K) - BIOS: 07/26/2010 - OS: 6.10.3 w/ custom kernel - Drives: 6 × ST4000VN000 / ST4000VN008
    Fans: Noctua NF-S12A FLX (Case), NF-R8 PWM (CPU), NF-R8 w/LNA (Power Supply) - USB: STGY8000400 - UPS: APC BR1000G
Ultra 2 Plus [for experimentation and testing] – JBOD: 8TB (110MB/s Write, 123MB/s Read)
    CPU: Standard 1.8GHz Atom D525 - RAM: 2GB (CT25664BC1067) - BIOS: 11/02/2011 - OS: 4.2.31 - Drives: 2 × ST4000VN000 - Fan: Noctua NF-B9 - USB: ST31000340
Message 20 of 172
Highlighted
Tutor

Re: Easy fix fan/temp issues on OS6 legacy #no support

Thank 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 Smiley Sad 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:
Message 21 of 172
Highlighted
Virtuoso

Re: Easy fix fan/temp issues on OS6 legacy #no support

ATCIS wrote:
find / -name syslog --> Yields nothing Smiley Sad It would appear that syslog is M.I.A.

Check the process list:
ps -A | grep syslogd

That should return something like "1234 ? 00:00:01 syslogd". If it returns nothing at all, syslogd isn't even running.

Tracking down WHY it isn't running might be an interesting exercise. Could be something as simple as an old lockfile preventing it from starting (to check, look in /var/run for a file called "syslogd.pid"; if you see it there even though syslogd isn't running, delete it and restart).
2 × Pro 6 [Main & Backup] – XRAID2 Dual-Redundant (RAID6): 14.53TB (110MB/s Write, 123MB/s Read)
    CPU: 2.4GHz E6600 SL9ZL - RAM: 8GB (PSD28G800K) - BIOS: 07/26/2010 - OS: 6.10.3 w/ custom kernel - Drives: 6 × ST4000VN000 / ST4000VN008
    Fans: Noctua NF-S12A FLX (Case), NF-R8 PWM (CPU), NF-R8 w/LNA (Power Supply) - USB: STGY8000400 - UPS: APC BR1000G
Ultra 2 Plus [for experimentation and testing] – JBOD: 8TB (110MB/s Write, 123MB/s Read)
    CPU: Standard 1.8GHz Atom D525 - RAM: 2GB (CT25664BC1067) - BIOS: 11/02/2011 - OS: 4.2.31 - Drives: 2 × ST4000VN000 - Fan: Noctua NF-B9 - USB: ST31000340
Message 22 of 172
Highlighted
Tutor

Re: Easy fix fan/temp issues on OS6 legacy #no support

fastfwd wrote:
ATCIS wrote:
find / -name syslog --> Yields nothing Smiley Sad It would appear that syslog is M.I.A.

Check the process list:
ps -A | grep syslogd

That should return something like "1234 ? 00:00:01 syslogd". If it returns nothing at all, syslogd isn't even running.

Tracking down WHY it isn't running might be an interesting exercise. Could be something as simple as an old lockfile preventing it from starting (to check, look in /var/run for a file called "syslogd.pid"; if you see it there even though syslogd isn't running, delete it and restart).


I edited the crap out of my original post above. . . Check it out Smiley Happy
I have to go to bed now. I have to get back up in less than 5 hours. A special THANK YOU" to fastfwd for all your guidance.
I'll catch up with you guys later. . .
Message 23 of 172
Highlighted
Virtuoso

Re: Easy fix fan/temp issues on OS6 legacy #no support

ATCIS wrote:
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.

The -128 is certainly erroneous. The temp3 input is clearly not being used.

The 57-degree SYS temperature is probably right; is that how hot your Ultra4 ran when you were using RAIDiator 4.2.23?

ATCIS wrote:
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. . .

You stil need to modify your crontab, as described by Iridabike, in order to make the script automatically execute every minute.

ATCIS wrote:
Any chance that the file in there named "systemd" is important?

Not to the syslog mystery, no. Unfortunately, I don't run OS6 so I can't suggest anything further. With luck, someone who does run OS6 will be able to tell you how to get syslogd running again.
2 × Pro 6 [Main & Backup] – XRAID2 Dual-Redundant (RAID6): 14.53TB (110MB/s Write, 123MB/s Read)
    CPU: 2.4GHz E6600 SL9ZL - RAM: 8GB (PSD28G800K) - BIOS: 07/26/2010 - OS: 6.10.3 w/ custom kernel - Drives: 6 × ST4000VN000 / ST4000VN008
    Fans: Noctua NF-S12A FLX (Case), NF-R8 PWM (CPU), NF-R8 w/LNA (Power Supply) - USB: STGY8000400 - UPS: APC BR1000G
Ultra 2 Plus [for experimentation and testing] – JBOD: 8TB (110MB/s Write, 123MB/s Read)
    CPU: Standard 1.8GHz Atom D525 - RAM: 2GB (CT25664BC1067) - BIOS: 11/02/2011 - OS: 4.2.31 - Drives: 2 × ST4000VN000 - Fan: Noctua NF-B9 - USB: ST31000340
Message 24 of 172
Highlighted
Tutor

Re: Easy fix fan/temp issues on OS6 legacy #no support

fastfwd wrote:
The -128 is certainly erroneous. The temp3 input is clearly not being used.

The 57-degree SYS temperature is probably right; is that how hot your Ultra4 ran when you were using RAIDiator 4.2.23?


Probably not, but I honestly don't remember without a shadow of a doubt. I may switch it to temp2_input even though 31 degrees C seems too low. On the GUI I have three thermometers: AUX = 40 C / 104 F, CPU = 43 C / 109 F, and System = 40 C / 104 F. Which leads me to believe that those graphical indications are also erroneous or I'm CAT'ing the wrong files. Wouldn't you agree that for a device residing in an 80 to 85 degree ambient environment that a System temperature of 134.6 F seems kind of high when the CPU temperature is only 109.4 F?

I've changed the script accordingly. It now looks like this:
#!/bin/sh
#######################################################
Coretemp="/sys/devices/platform/coretemp.0/temp2_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:$S


Additionally, my /etc/crontab file now looks like this (perhaps my script file is okay, I just dorked up the crontab):
# /etc/crontab: system-wide crontab
# Unlike any other crontab you don't have to run the `crontab'
# command to install the new version when you edit this file
# and files in /etc/cron.d. These files also have username fields,
# that none of the other crontabs do.

SHELL=/bin/sh
PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin

# m h dom mon dow user command
17 * * * * root cd / && run-parts --report /etc/cron.hourly
25 6 * * * root test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily )
47 6 * * 7 root test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.weekly )
52 6 1 * * root test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.monthly )

# Delete the lines below if things get wacky. They are supposed to enable
# temperature graphing in the Frontview GUI. Good luck!
*/1 * * * * root /usr/local/etc/scripts/UpdateTempGraph.cron


You thoughts?
Thanks again!
Message 25 of 172
Top Contributors
Discussion stats
Announcements