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

note : Initially I ask this forum because I have looked few times and it always was half the speed between the 2 speed displayed.
viewtopic.php?f=24&t=71904&p=399532#p399532

This morning I spent more than one hour playing around and I now understand how it's "working" :
1) the langage used by Frontview is based on the langage used by the browser (for me it was a french Safari). Thanks to apple I changed the langage in 5 sec and reboot, so I confirm my that the text explained in Frontview under "system>language" is true : IT IS based on the browser's language.
And about the fan speed I noticed the same problem : the 2 readings where completely different, but not anymore with "half/double" relation.
2) I refreshed pages many times, recalibrated, etc and then I understood the pattern :
When connecting to the Frontview homepage the speed of the fan is read at this moment even i the mouse is not put on the green light to display the speed in the overlay menu. Then it's stored somehow. To refresh this reading I had to refresh completely the webpage (like F5)
3) the fan speed inside the frontview text page under the menu "Status>health" is read when the menu is clicked onto it.
4)Here is why the 2 speeds are different 90% of the time because they are not read at the same moment. And apparently the fan speed reading varies a lot for an unknown reason. I believe waiting for 10 sec helps displaying the real fan speed (to stabilized)
The solution to obtain the same speed is, when logged in frontview is to display very fast the menu "Status>health" (the refresh is like avery few seconds).

conclusion :
Sorry to have bothered you all, but now I am confident about the usual fan speed I am having, therefore I am ready 'upgrade' to R6 when I'll catch enough hard drive space to backup all files.

Hi, I'd appreciate some help here. I have an Ultra 6 which is running 6.0.8
I've been through the fan control settings but the fan is still running at max speed.
I think the problem is that i'm getting null results for all the temp readings.
if i run the SENSORS command i get the following.

root@NASBACK6:~# sensors
coretemp-isa-0000
Adapter: ISA adapter
Core 0: N/A (high = +80.0°C, crit = +100.0°C)
Core 1: N/A (high = +80.0°C, crit = +100.0°C)

it8721-isa-0a10
Adapter: ISA adapter
in0: +12.19 V (min = +11.86 V, max = +9.89 V) ALARM
in1: +5.02 V (min = +4.82 V, max = +5.12 V)
in2: +3.32 V (min = +4.97 V, max = +2.35 V) ALARM
in3: +0.00 V (min = +0.00 V, max = +0.00 V) ALARM
in4: +1.15 V (min = +2.83 V, max = +1.45 V) ALARM
in5: +1.79 V (min = +2.57 V, max = +2.89 V) ALARM
in6: -12.10 V (min = +6.37 V, max = +2.04 V) ALARM
in7: +3.29 V (min = +3.05 V, max = +1.32 V) ALARM
in8: +3.36 V
fan1: 0 RPM (min = 31 RPM) ALARM
fan2: 0 RPM (min = 12 RPM) ALARM
fan3: 2242 RPM (min = 28 RPM)
temp1: +0.0°C (low = -28.0°C, high = -11.0°C) ALARM sensor = thermistor
temp2: +0.0°C (low = +19.0°C, high = -75.0°C) ALARM sensor = thermal diode
temp3: +0.0°C (low = +84.0°C, high = +115.0°C) sensor = thermal diode
cpu0_vid: +2.050 V

The fan previously ran fine under 4.X.X.

Anyone have any ideas about what the problem here might be?

many thanks
Steve

Have you followed these steps with root user ?
1) install lm-sensors and fancontrol packages
2) create /etc/fancontrol file
2) restart fancontrol

May be you can try to remove and reinstall lm-sensors packages

apt-get remove lm-sensors fancontrol
apt-get install lm-sensors fancontrol

Thanks - have done this but still get exactly the same result.

Any further ideas much appreciated.....

thanks
Steve

hm, the coretemp.0 temp input files seem to represent temp multiplied by 1000 and pwmconfig recognises this fine. However, it87.2576 files have temp without multiplied by 1000, and pwmconfig sees it as 0. What to do?

I am having issues on my Pro6, I used one of the profiles here, and basically my fans keep powering up and down every few seconds. Doesn't happen in a cooler room, so I think I have my profile set incorrectly. The problem is I can't seem to find the accurate live temperatures from my device so I can change my thresholds, to stop the fans going on and off constantly. When I look under performance (firmware 6.0.8 and 6.1.1) the AUX, CPU and System are all steady at 40c, 43c and 40c respectively and NO information is available on the temperature graphcs. Is there a nice simple way I can log the true fan speeds and temperatures on my device for 5-10 minutes to work out what I need to do to fix the problem?

Ok here is some info from an Ultra 4. Have only just set it up, so am not specifically recommending these settings, and it may depend on your personal trade-off between noise & temperature.

For what's it's worth, 6.1.1 on the Ultra 4 seems to adjust the fan speed about every 25 minutes, and the temperature graph has a very regular variation to it:



I'm guessing the fan speed is adjusted every ~25 minutes, as it's pretty close to 100 minutes between the peaks, and about 25 minutes between when it drops and when it starts to slowly rise again. Just a guess (could easily be 10 or 12.5 minutes).

First up, here's the output from "sensors":

coretemp-isa-0000
Adapter: ISA adapter
Core 0:       +34.0°C  (high = +80.0°C, crit = +100.0°C)

it8721-isa-0a10
Adapter: ISA adapter
in0:          +0.00 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in1:          +4.88 V  (min =  +0.56 V, max =  +4.36 V)  ALARM
in2:          +0.00 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in3:          +0.00 V  (min =  +0.00 V, max =  +0.00 V)
in4:          +3.30 V  (min =  +2.48 V, max =  +0.06 V)  ALARM
in5:          +1.16 V  (min =  +1.18 V, max =  +0.41 V)  ALARM
in6:         +12.18 V  (min =  +7.06 V, max =  +1.67 V)  ALARM
in7:          +3.24 V  (min =  +3.84 V, max =  +4.20 V)  ALARM
in8:          +3.22 V  
fan1:        2481 RPM  (min = 4017 RPM)  ALARM
fan2:           0 RPM  (min =  607 RPM)  ALARM
temp1:         +0.1°C  (low  = +120.0°C, high = +94.0°C)  sensor = thermal diode
temp2:         +0.0°C  (low  = -61.0°C, high = -127.0°C)  ALARM  sensor = thermal diode
temp3:         -0.1°C  (low  = +32.0°C, high = -112.0°C)  sensor = disabled
cpu0_vid:    +2.050 V

The ReadyNAS front-end shows both CPU and Case temperature sensors, but I can only see the CPU temperature here. Not sure how to access the case temperature, but suspect that's not a big deal.

The Ultra 4 has only one PWM-controlled fan (CPU fan is fixed speed I think). Here's the output from pwmconfig detecting the hardware:

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

Found the following PWM controls:
   hwmon1/device/pwm1           current value: 96
   hwmon1/device/pwm2           current value: 0
   hwmon1/device/pwm3           current value: 255

And here is pwmconfig characterising the chassis fan:

    PWM 255 FAN 3358
    PWM 240 FAN 3358
    PWM 225 FAN 3358
    PWM 210 FAN 3341
    PWM 195 FAN 3341
    PWM 180 FAN 3308
    PWM 165 FAN 3229
    PWM 150 FAN 3125
    PWM 135 FAN 2973
    PWM 120 FAN 2812
    PWM 105 FAN 2626
    PWM 90 FAN 2410
    PWM 75 FAN 2163
    PWM 60 FAN 1880
    PWM 45 FAN 1537
    PWM 30 FAN 1130
    PWM 28 FAN 1033
    PWM 26 FAN 975
    PWM 24 FAN 924
    PWM 22 FAN 876
    PWM 20 FAN 827
    PWM 18 FAN 774
    PWM 16 FAN 716
    PWM 14 FAN 636
    PWM 12 FAN 534
    PWM 10 FAN 421
    PWM 8 FAN 260
    PWM 6 FAN 115
    PWM 4 FAN 0
    Fan Stopped at PWM = 4

Further testing showed the fan started back up with a PWM value between 24 and 34, so 64 was chosen by pwmconfig as a safe value.

Finally, here is the /etc/fancontrol file generated by pwmconfig, just using the defaults, having selected the one appropriate pwm & temp sensor for the Ultra 4:

# 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=20
MAXTEMP=hwmon1/device/pwm1=60
MINSTART=hwmon1/device/pwm1=64
MINSTOP=hwmon1/device/pwm1=4

And to get the fan control up and running...
# sudo /etc/init.d/fancontrol start

Having run it for the time it's taken to write this post, I've learned:

• it seems to be updating more regularly (ie at the 10 second interval specified)


• so far CPU temp has risen from ~30 to ~34 with fan speed rising in line (around 2000 up to 2400)


• it looks like it's going to be a much steadier temperature (almost perfectly flat at 34º), but won't know for an hour or two i guess if its got any variation anymore


• I don't remember what my CPU/case temps were like before, but it's definitely noisier than before... so either I can set the MINTEMP higher (maybe 40) or OS 6.1.1 is wasting more cpu with btrfs daemons or readynasd perhaps...

20°C is not enough for ATOM mintemp cpu, and the fan always run noisy to decrease temperature. 50°C would be a realistic and better value.
minpwm & maxpwm are missing in your fancontrol file paste. I assume it is just a paste error.

You can try these values :
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

glem wrote:
20°C is not enough for ATOM mintemp cpu, and the fan always run noisy to decrease temperature. 50°C would be a realistic and better value.

Ok, I'll give a higher value a go, just enough to get it silent (its pretty good at 1800rpm and below on the Ultra 4).

glem wrote:
minpwm & maxpwm are missing in your fancontrol file paste. I assume it is just a paste error.

They actually weren't saved in the file for some reason. Strange...

Also having installed fancontrol and used the above settings, it's indeed rock-solid at 34º CPU and 30º case temps, no more cyclic variation, so it does at least seem to be working more as expected.

Hi,

I'm on Os 6 from Os 4 on my ultra2.

By now I've got trouble getting logged via SSH. Yes it's enable but keep kicking me out after login.



I would love to fix the temp-fan issue...



Anything that I,m missing?

Anyone got into the same trouble?


Thx for helping!