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
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.
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.
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.
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 :?:
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.
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:
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:
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 😞 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.
Re: Easy fix fan/temp issues on OS6 legacy #no support
ATCIS wrote:
find / -name syslog --> Yields nothing 😞 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).
Re: Easy fix fan/temp issues on OS6 legacy #no support
fastfwd wrote:
ATCIS wrote:
find / -name syslog --> Yields nothing 😞 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 🙂 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. . .
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?
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.
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:
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.
# 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
