NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
ReadyData 5200 running OS 6.10.3 with Sys fan control on the motherboard.
Hi I know this is an unsupported configuration, thought I'd let others know my experiences of attempting to run OS6 on a ReadyData5200 unit. I followed some instructions online which bizarrely ...
Hi
I've since settled for 40 degrees as my target temperature otherwise as soon as the machine ceases to idle the fans start ramping up. Essentially with the mode I've selected , the sensor connected to temp2 controls the three fans. The readynasd process still controls the CPU fan.
These datasheets/documents were my source of info on the fan/temp chip.
https://www.kernel.org/doc/Documentation/hwmon/w83627ehf
http://read.pudn.com/downloads649/doc/2643726/W83627DHG-Programming-Guide.pdf
https://www.nuvoton.com/resource-files/DA00-WW83627DHG-P.pdf
Bullfrog2
I've had problems with OS6 controlling the fans on my converted RD5200 and had turned to using the BIOS for it (which just sets a set percentage of full speed). I'm now testing the pwm2_enable = 1 change (mine was set to 4) and will post more. I'm using a copy of the RD4200V2.conf as my RN5200conf.
Note that both of us moved the fans from the SAS backplane, where they always run full blast, to the motherboard, with the connections as Bullfrog2 described. That's the same as in an RN4200V2, which has the same motherboard (sans IPMI hardware).
Hi
With pwm_enable set to 1 you have to set the speed yourself. I suspect the BIOS is taking over once the temperature gets to a critical value, it's hard to tell as I believe I'm fighting a hardware fault too.
My pwm_enable was also originally set to 4.
Anyway here is some more info i've discovered while researching this.
Chip is capable of controlling 4 seperate fan outputs using either DC or PWM.
Controlled by pwm1 to pwm4, not sure what order these are in but this is the names of the 4 pins on the chip for fans.SYSFANOUT
CPUFANOUT0
CPUFANOUT1
AUXFANOUTOn the supermicro board all fan headers including CPU are wired to the same pwm2 output, so they all go up and down together. I don't have anything plugged into header 5 at the back of the motherboard so this connector isn't verified.
Chip is capable of monitoring 5 Fans ,showing their speed, or setting triggers for alerts if they fail.
Some fans generate 4 pulses per revolution others 2 per revolution, so settings need to be tweeked to accomodate this. Nothing to do with divisor which is more to do with showing and having better control between min and max speed.
The Netgear conf file monitors temp1 which doesn't budge much to control the cpu fan, the other fans we've added to the motherboard just tag along for fun.
The chip is also capable of controlling fan speed via the southbridge, so our fan pcb headers may not be connected directly to the w83627 chip at all, also it appears the IPMI can override stuff too.
I've also discovered that temp2 rather than temp1 on the w83627 is the cpu temp diode, so perhaps all that is needed on a properly functioning machine is for the RD5200.conf file to check temp2 rather than temp1.
Bullfrog2
Another update - at one point I'd updated readynasd's debug level to 5 (
/etc/systemd/system/multi-user.target.wants/readynasd.service - change this line
ExecStart=/usr/sbin/readynasd -v 3 -t --- change 3 to a 5)
which generated more logging information available for view by running journalctl or viewing systemd-journal.log. journalctl -b will show entries from last boot.
This now lists lots of information amongst other things about the device Id's it uses to sense temperature/fan speeds etc.
It then seems to make a calculation based on drive temperatures, cpu temp, system temp to make an assesment as to whether to increase/decrease fan speeds.
It appears that conceptually readynasd expects to write to fan1 to control fan1 , write to fan2 to control fan2....., write to fan5 to control 5 and this appears to be where the source of our permission denied error message is coming from, this chip can only control 4 fan outputs although it can monitor 5
If you change the .conf file to ignore fan5, the "Permission Denied" error stops.
And if you type echo "64" > pwm5 you indeed get a "Permission Denied" error message.
So I'm now running with yet another conf file.
I've also just ordered some fan extension cables, so I can plug a fan into the header at the back of the motherboard to see if that is controlled seperately.
I'm also now running from one PSU only to see if my random notifications of voltages out of spec disappears, this being the original reason for me adding in entries for the voltages in the conf file.
Bullfrog2
Fortunately, the power supplies are standard ones for 2U SuperMicro chassis and readily available. The newer "gold" versions are also a lot more quiet, as I understand it. You can try each one separately and see if one is your problem, but the problem could be the monitoring system rather than the actual voltage. You should probably also try both slots The NAS only runs on one, even if two are plugged in. The other is a hot spare. I just run mine with one and purchased a blank to fill the other spot. I don't have a place to plug both into my UPS (too much other stuff in the rack) and wasn't sure the same one always comes up as primary, and I want the primary to be on the UPS so it sees the current draw for the hold-up time estimate and so the UPS doesn't see a load spike at the same time it shifts to battery. Plus, it's more quiet with just one of those little fans running and my spare is now in the closet and won't go bad before even called on to power the NAS. You can just leave it not fully engaged or totally missing instead of getting the blank, but I figured the air flow would be better with the blank and they are pretty cheap on eBay. If both are inserted and only one plugged in, you'll get an incessant alarm.
My .conf, which is just a copy of RN4200.conf has ignore fan3, and fan3 seemed to be the rear one when I did my experiments. So something you've done with lmsensors may have changed the designations from the what Netgear uses. My fan5 is labeled "Fan 3", and that does show up in the GUI.
chip "coretemp-isa-0000" ignore temp1 ignore temp2 ignore temp3 ignore temp4 ignore temp5 ignore temp6 ignore temp7 ignore temp8 ignore temp9 chip "w83627dhg-isa-*" ignore in1 ignore in4 ignore in5 ignore in6 label fan1 "Fan 2" set fan1_min 400 label fan2 "CPU" set fan2_min 0 ignore fan3 label fan4 "Fan 1" set fan4_min 400 label fan5 "Fan 3" set fan5_min 400 label temp1 "System" set temp1_max 60 label temp2 "CPU" set temp2_max 74 ignore temp3 ignore temp4 ignore temp5 ignore temp6 ignore temp7 ignore temp8 ignore temp9 ignore temp10 ignore intrusion0 ignore intrusion1 ignore beep_enableI've seen posts concerning this family of Supermicro boards that makes me think I may also be getting the access denied errors because the BIOS and/or IPMI are trying to access the fan control at the same time as the OS. There is no "external control" BIOS fan setting like there is on newer boards. I don't know if your problems with the other sensors could be associated with colliding reads of the data by the BIOS and/or IPMI, as I don't get them. I don't see anything in the .conf file to set them up, either, but I see the voltages in the log files.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
