Register for the iXsystems Community to get an ad-free experience and exclusive discounts in our eBay Store.

Thermal and Accoustical Design Validation

SFoskett

Newbie
Joined
Jul 28, 2016
Messages
37
It seems so strange that four fans are controlled by CPU temperature and just one is controlled by "system" temperature. I would think it would have been more useful for Supermicro to have made one for the CPU fan and left the other four for system/case fans!

But I believe GrumpyBear is correct so I have the CPU fan connected to FAN1 and the case fans on FANA. Luckily, my case (NZXT H440) came with a nice PWM fan controller with external power, so I can have all the case fans controlled by FANA!
 

Omega

Newbie
Joined
Dec 12, 2015
Messages
15
I was a bit confused by this as well. My rationalisation of it is basically that (I guess) the expected design is that the boards sit in rack chassis which have a fan mid-plane (if that's the right word) while the CPU itself doesn't have a fan but rather sits in the flow, possibly/likely under an air shroud.
 

Stux

FreeNAS Wizard
Joined
Jun 2, 2016
Messages
4,166
Right,

I found the same thing. Ended up connecting the 3 120mm drive fanwall fans to FANA. 2 CPU fans to 1&2 and exhaust fans to 3&4.
 

Ceetan

FreeNAS Experienced
Joined
Apr 29, 2016
Messages
132
I recently bought 3 Noctua NF-F12 and one Noctua NF-A14 PWM (fan 4 is 140mm in my set up). Wen I set the up i ipmitool, they turned out quite loud, So I suspect I did something wrong, mostly likely with the sensor thresholds. Any one have any idea ?
Fan 3 and 4 are connected to the fan a header on the mobo via a y-cable, where one of the connectors only seems to have 3 pins (does that matter?) (a bit confusing with the image, I know) While fan2 and the top fan are connected to one of the other headers each.
fan-placement-node804.jpg


Sensor data from ipmitool
Code:
CPU Temp		 | 33.000	 | degrees C  | ok	| 0.000	 | 0.000	 | 0.000	 | 95.000	| 100.000   | 100.000
PCH Temp		 | 32.000	 | degrees C  | ok	| -11.000   | -8.000	| -5.000	| 90.000	| 95.000	| 100.000
System Temp	  | 30.000	 | degrees C  | ok	| -9.000	| -7.000	| -5.000	| 80.000	| 85.000	| 90.000
Peripheral Temp  | 32.000	 | degrees C  | ok	| -9.000	| -7.000	| -5.000	| 80.000	| 85.000	| 90.000
VcpuVRM Temp	 | 30.000	 | degrees C  | ok	| -9.000	| -7.000	| -5.000	| 95.000	| 100.000   | 105.000
DIMMA1 Temp	  | na		 |			| na	| na		| na		| na		| na		| na		| na
DIMMA2 Temp	  | 25.000	 | degrees C  | ok	| 1.000	 | 2.000	 | 4.000	 | 80.000	| 85.000	| 90.000
DIMMB1 Temp	  | na		 |			| na	| na		| na		| na		| na		| na		| na
DIMMB2 Temp	  | 26.000	 | degrees C  | ok	| 1.000	 | 2.000	 | 4.000	 | 80.000	| 85.000	| 90.000
FAN1			 | na		 |			| na	| na		| na		| na		| na		| na		| na
FAN2			 | 1400.000   | RPM		| cr	| 0.000	 | 100.000   | 200.000   | 1300.000  | 1400.000  | 1500.000
FAN3			 | 2900.000   | RPM		| ok	| 300.000   | 500.000   | 700.000   | 25300.000 | 25400.000 | 25500.000
FAN4			 | 1500.000   | RPM		| nr	| 0.000	 | 100.000   | 200.000   | 1300.000  | 1400.000  | 1500.000
FANA			 | 1400.000   | RPM		| cr	| 0.000	 | 100.000   | 200.000   | 1300.000  | 1400.000  | 1500.000
12V			  | 12.128	 | Volts	  | ok	| 10.144	| 10.272	| 10.784	| 12.960	| 13.280	| 13.408
5VCC			 | 4.896	  | Volts	  | ok	| 4.246	 | 4.298	 | 4.480	 | 5.390	 | 5.546	 | 5.598
3.3VCC		   | 3.282	  | Volts	  | ok	| 2.789	 | 2.823	 | 2.959	 | 3.554	 | 3.656	 | 3.690
VBAT			 | 3.140	  | Volts	  | ok	| 2.384	 | 2.496	 | 2.580	 | 3.476	 | 3.588	 | 3.672
Vcpu			 | 0.733	  | Volts	  | ok	| 0.085	 | 0.085	 | 0.085	 | 1.588	 | 1.750	 | 1.768
VDIMMAB		  | 1.182	  | Volts	  | ok	| 0.948	 | 0.975	 | 1.047	 | 1.344	 | 1.425	 | 1.443
5VSB			 | 4.974	  | Volts	  | ok	| 4.246	 | 4.376	 | 4.480	 | 5.390	 | 5.546	 | 5.598
3.3VSB		   | 3.231	  | Volts	  | ok	| 2.755	 | 2.840	 | 2.908	 | 3.503	 | 3.605	 | 3.639
VPCH 1.5V		| 1.032	  | Volts	  | ok	| 0.825	 | 0.852	 | 0.915	 | 1.176	 | 1.239	 | 1.266
Chassis Intru	| 0x0		| discrete   | 0x0000| na		| na		| na		| na		| na		| na


My gut feeling is that I need a script to control them adequately. I seems to remeber @Kevin Horton (among others) had one for a similar setup.
 

Stux

FreeNAS Wizard
Joined
Jun 2, 2016
Messages
4,166

Ceetan

FreeNAS Experienced
Joined
Apr 29, 2016
Messages
132

Stux

FreeNAS Wizard
Joined
Jun 2, 2016
Messages
4,166
That is what I was looking for. Now to get it to run...
Question: My boot device is an SSD drive mounted in the systems chamber. Will that affect the script in any way?
No
 

GrumpyBear

FreeNAS Experienced
Joined
Jan 28, 2015
Messages
141
I recently bought 3 Noctua NF-F12 and one Noctua NF-A14 PWM (fan 4 is 140mm in my set up). Wen I set the up i ipmitool, they turned out quite loud, So I suspect I did something wrong, mostly likely with the sensor thresholds. Any one have any idea ?
Fan 3 and 4 are connected to the fan a header on the mobo via a y-cable, where one of the connectors only seems to have 3 pins (does that matter?) (a bit confusing with the image, I know) While fan2 and the top fan are connected to one of the other headers each.
View attachment 14903

Sensor data from ipmitool
Code:
CPU Temp		 | 33.000	 | degrees C  | ok	| 0.000	 | 0.000	 | 0.000	 | 95.000	| 100.000   | 100.000
PCH Temp		 | 32.000	 | degrees C  | ok	| -11.000   | -8.000	| -5.000	| 90.000	| 95.000	| 100.000
System Temp	  | 30.000	 | degrees C  | ok	| -9.000	| -7.000	| -5.000	| 80.000	| 85.000	| 90.000
Peripheral Temp  | 32.000	 | degrees C  | ok	| -9.000	| -7.000	| -5.000	| 80.000	| 85.000	| 90.000
VcpuVRM Temp	 | 30.000	 | degrees C  | ok	| -9.000	| -7.000	| -5.000	| 95.000	| 100.000   | 105.000
DIMMA1 Temp	  | na		 |			| na	| na		| na		| na		| na		| na		| na
DIMMA2 Temp	  | 25.000	 | degrees C  | ok	| 1.000	 | 2.000	 | 4.000	 | 80.000	| 85.000	| 90.000
DIMMB1 Temp	  | na		 |			| na	| na		| na		| na		| na		| na		| na
DIMMB2 Temp	  | 26.000	 | degrees C  | ok	| 1.000	 | 2.000	 | 4.000	 | 80.000	| 85.000	| 90.000
FAN1			 | na		 |			| na	| na		| na		| na		| na		| na		| na
FAN2			 | 1400.000   | RPM		| cr	| 0.000	 | 100.000   | 200.000   | 1300.000  | 1400.000  | 1500.000
FAN3			 | 2900.000   | RPM		| ok	| 300.000   | 500.000   | 700.000   | 25300.000 | 25400.000 | 25500.000
FAN4			 | 1500.000   | RPM		| nr	| 0.000	 | 100.000   | 200.000   | 1300.000  | 1400.000  | 1500.000
FANA			 | 1400.000   | RPM		| cr	| 0.000	 | 100.000   | 200.000   | 1300.000  | 1400.000  | 1500.000
12V			  | 12.128	 | Volts	  | ok	| 10.144	| 10.272	| 10.784	| 12.960	| 13.280	| 13.408
5VCC			 | 4.896	  | Volts	  | ok	| 4.246	 | 4.298	 | 4.480	 | 5.390	 | 5.546	 | 5.598
3.3VCC		   | 3.282	  | Volts	  | ok	| 2.789	 | 2.823	 | 2.959	 | 3.554	 | 3.656	 | 3.690
VBAT			 | 3.140	  | Volts	  | ok	| 2.384	 | 2.496	 | 2.580	 | 3.476	 | 3.588	 | 3.672
Vcpu			 | 0.733	  | Volts	  | ok	| 0.085	 | 0.085	 | 0.085	 | 1.588	 | 1.750	 | 1.768
VDIMMAB		  | 1.182	  | Volts	  | ok	| 0.948	 | 0.975	 | 1.047	 | 1.344	 | 1.425	 | 1.443
5VSB			 | 4.974	  | Volts	  | ok	| 4.246	 | 4.376	 | 4.480	 | 5.390	 | 5.546	 | 5.598
3.3VSB		   | 3.231	  | Volts	  | ok	| 2.755	 | 2.840	 | 2.908	 | 3.503	 | 3.605	 | 3.639
VPCH 1.5V		| 1.032	  | Volts	  | ok	| 0.825	 | 0.852	 | 0.915	 | 1.176	 | 1.239	 | 1.266
Chassis Intru	| 0x0		| discrete   | 0x0000| na		| na		| na		| na		| na		| na


My gut feeling is that I need a script to control them adequately. I seems to remeber @Kevin Horton (among others) had one for a similar setup.
What fan mode are you using? It appears that all fans are running full-speed so you either have the fan mode set to "Full" or the thresholds are wonky and the BMC has panicked and is running all fans at full.

Looks like your running in a Fractal node 804. This case is a "Dual-Zone" case with a zone for the system (main) board and another zone for the hard disks.

One issue is that, if the X11SSL has two zone cooling, it is likely setup like similar boards in that FAN1-FAN4 are controlled by CPU temperature as is FAN-A except in "Optimal" and "Heavy-IO" modes where the FAN-A header is separately controlled by an additional thermal sensor usually located on the system-board close to the PCIe slots. This seems to be designed so that you can have a separate cooling zone to accommodate expansion cards that get hot such as GPUs or HBAs/RAID controllers. So the dual-zone controller on the motherboard is unlikely to work well in the dual zone case you have.

4-wire fans have 4 leads; 12V, Ground, TAC & PWM. The first two and the last are outputs and provide power and the speed signal to the fans and so can have multiple fans connected to them. The third line, TAC, is the tachometer signal, and is input from a connected fan that tells the motherboard at what speed the fan is rotating. This can only be extended from a single fan. That is why one of the fan connector on your "Y" connector has three wires and the other four. The one with the four wires is the one which will provide the connected fans speed to the motherboard.

Yes, you need to adjust the FAN thresholds more. I would use 1800, 1900 and 2000 for your upper thresholds as you already have one fan running at 1500 rpm so that may be causing the BMC to panic (see the alerts in the IPMI management) and force the fans to full speed.
Your lower thresholds should likely be fine but I'm not certain if zero is a valid value.

Have you tried rebooting your BMC from IPMI? - this will sometimes fix things.

The Noctua NF-F12 PWM fans as well as the Noctua NF-A14 PWM fan are both rated for:
300rpm +/- 20% so 240-360rpm minimal speed
1500 +/- 10% so 1350-1650rpm maximum speed OR 1200 +/-10%, so 1080-1320rpm maximum speed with the Low Noise Adapters (LNA)

Take these values with a healthy dose of salt and look at how they actually perform.

If I was using that case I would likely:

1. Put your "FAN-A" in the lower left position and not in the top of the case. Why? Because you have an LSI HBA chip on that board, at the bottom front, and it WILL get hot and is, aside from the CPU, the only thing in the hot zone you need to worry about keeping cool. Yes there is the PCH, VRM, DIMMs etc. but they will all survive most ambient temperatures and can, in normal circumstances, just be ignored. Try to visualize the airflow through the case as if you pass smoke through it so you could see it (don't do this please, I've looked inside cases of smokers and it's nasty) The best airflow is a direct path, in the front and out the back and this is the assumption most cases are built with. Top fans positions are usually meant for water coolers for gaming rigs and bottom fan positions for providing airflow for hot GPUs and I/O Cards.

The exception may be for the hard drive area where the fans might work better pulling hot air out from above the hard drives. Again - test while your system is under load.

2. Connect all the fans in the hot zone to FAN-1 through FAN-4 and run them using "Optimal" then they will be controlled by the CPU temp and should run slowly. If they are too loud then use the speed limiters provided with the Noctuas to drop them down a notch.

3. Connect the fans in the HDD zone to the FAN-A connector and use a script to monitor the HDD temperature from the SMART info to control the fans and tweak as necessary

OR just use a Y connector and connect them to the case's voltage-controlled fan speed controller. Start at the lowest setting and run a scrub or other utility that makes the disks run hard for at least 20 to 30 minutes for the heat to soak in and check the SMART data and see how hot the disks are. If there mostly at or below about 40C (season to taste here) then your good. If there still a little too hot then try the next higher speed setting and repeat until satisfied.

My Define R4 case is so silent under load that you can't tell that it is running especially since I disconnected the annoyingly bright blue power LED from the power lead and connected it to the FAN Fail/Pwr Problem LED. This works for me but I'm not certain what your design goals are. My NAS is buried in my basement and serves media to the house so it doesn't have to be pretty or quite. I assume that most people who buy the smallish cases are space-constrained and need to have to NAS situated in a livable space in the house and thus are willing to trade-off function to get form.
 
Last edited:

Ceetan

FreeNAS Experienced
Joined
Apr 29, 2016
Messages
132
What fan mode are you using? It appears that all fans are running full-speed so you either have the fan mode set to "Full" or the thresholds are wonky and the BMC has panicked and is running all fans at full.

Looks like your running in a Fractal node 804. This case is a "Dual-Zone" case with a zone for the system (main) board and another zone for the hard disks.

One issue is that, if the X11SSL has two zone cooling, it is likely setup like similar boards in that FAN1-FAN4 are controlled by CPU temperature as is FAN-A except in "Optimal" and "Heavy-IO" modes where the FAN-A header is separately controlled by an additional thermal sensor usually located on the system-board close to the PCIe slots. This seems to be designed so that you can have a separate cooling zone to accommodate expansion cards that get hot such as GPUs or HBAs/RAID controllers. So the dual-zone controller on the motherboard is unlikely to work well in the dual zone case you have.

4-wire fans have 4 leads; 12V, Ground, TAC & PWM. The first two and the last are outputs and provide power and the speed signal to the fans and so can have multiple fans connected to them. The third line, TAC, is the tachometer signal, and is input from a connected fan that tells the motherboard at what speed the fan is rotating. This can only be extended from a single fan. That is why one of the fan connector on your "Y" connector has three wires and the other four. The one with the four wires is the one which will provide the connected fans speed to the motherboard.

Yes, you need to adjust the FAN thresholds more. I would use 1800, 1900 and 2000 for your upper thresholds as you already have one fan running at 1500 rpm so that may be causing the BMC to panic (see the alerts in the IPMI management) and force the fans to full speed.
Your lower thresholds should likely be fine but I'm not certain if zero is a valid value.

Have you tried rebooting your BMC from IPMI? - this will sometimes fix things.

The Noctua NF-F12 PWM fans as well as the Noctua NF-A14 PWM fan are both rated for:
300rpm +/- 20% so 240-360rpm minimal speed
1500 +/- 10% so 1350-1650rpm maximum speed OR 1200 +/-10%, so 1080-1320rpm maximum speed with the Low Noise Adapters (LNA)

Take these values with a healthy dose of salt and look at how they actually perform.

If I was using that case I would likely:

1. Put your "FAN-A" in the lower left position and not in the top of the case. Why? Because you have an LSI HBA chip on that board, at the bottom front, and it WILL get hot and is, aside from the CPU, the only thing in the hot zone you need to worry about keeping cool. Yes there is the PCH, VRM, DIMMs etc. but they will all survive most ambient temperatures and can, in normal circumstances, just be ignored. Try to visualize the airflow through the case as if you pass smoke through it so you could see it (don't do this please, I've looked inside cases of smokers and it's nasty) The best airflow is a direct path, in the front and out the back and this is the assumption most cases are built with. Top fans positions are usually meant for water coolers for gaming rigs and bottom fan positions for providing airflow for hot GPUs and I/O Cards.

The exception may be for the hard drive area where the fans might work better pulling hot air out from above the hard drives. Again - test while your system is under load.

2. Connect all the fans in the hot zone to FAN-1 through FAN-4 and run them using "Optimal" then they will be controlled by the CPU temp and should run slowly. If they are too loud then use the speed limiters provided with the Noctuas to drop them down a notch.

3. Connect the fans in the HDD zone to the FAN-A connector and use a script to monitor the HDD temperature from the SMART info to control the fans and tweak as necessary

OR just use a Y connector and connect them to the case's voltage-controlled fan speed controller. Start at the lowest setting and run a scrub or other utility that makes the disks run hard for at least 20 to 30 minutes for the heat to soak in and check the SMART data and see how hot the disks are. If there mostly at or below about 40C (season to taste here) then your good. If there still a little too hot then try the next higher speed setting and repeat until satisfied.

My Define R4 case is so silent under load that you can't tell that it is running especially since I disconnected the annoyingly bright blue power LED from the power lead and connected it to the FAN Fail/Pwr Problem LED. This works for me but I'm not certain what your design goals are. My NAS is buried in my basement and serves media to the house so it doesn't have to be pretty or quite. I assume that most people who buy the smallish cases are space-constrained and need to have to NAS situated in a livable space in the house and thus are willing to trade-off function to get form.
Hmm, Thanks, an bunch! Will ponder! Currently set them in optimal mode through ipmiview. I'll see what I can do as sonn as i have someone to help med with the tinkering. (Disabled, so practical execution om these thins can sometimes be hard, as my fine motors are not up to it.). I need to learn how to pusetup scrips on the nas. Nay good reasorece where i can learn the basics?
 

GrumpyBear

FreeNAS Experienced
Joined
Jan 28, 2015
Messages
141
Hmm, Thanks, an bunch! Will ponder! Currently set them in optimal mode through ipmiview. I'll see what I can do as sonn as i have someone to help med with the tinkering. (Disabled, so practical execution om these thins can sometimes be hard, as my fine motors are not up to it.). I need to learn how to pusetup scrips on the nas. Nay good reasorece where i can learn the basics?
Not knowing your level of experience with Linux or other Linux like variants (i.e. FreeBSD) I'm not certain where to point you to learn how to use scripts. My background is Solaris (a really long time ago) and Linux over the last 20 so years so FreeNAS involved some learning for me but it is similar enough to Linux that I manage to muddle through. Learning scripting is probably not something you should do on a system you need to rely on so you might want to see if you can get access to another FreeBSD system (or install one in a Hypervisor under Windows or Mac) to experiment on. Someone else, more knowledgeable in FreeBSD/FreeNAS would be better to give you some pointers here.

I'm assuming that your disabilities do not make it as difficult to use a keyboard so with that in mind you might prefer options that don't involve too many adjustments to the hardware.

Your existing setup should work. It might not be the most efficient but might be a good compromise.

If it is running really loud then likely the fans are running at full speed. Try changing the fan mode from "Optimal" to "Full-Speed" in IPMI and see if you notice a difference. Try the other fan modes too and see if you notice any differences.

If you don't see any differences then there is likely an issue with the thresholds and you should try adjusting them. These thresholds are just for the system to detect when the fans might be starting to fail (lower and upper non-critical; i.e. the fans are running close to their minimal or maximal speeds) or have failed (lower and upper critical). The Baseboard Management Computer (BMC) monitors the TAC input from the fans to determine what action, if any, to take. At the non-critical thresholds it should just send an alert view able in IPMI log but at the critical limit the BMC is programmed to "panic" and run all the fans at the highest speed (100% PWM). See Eric Lowe's guide on setting the thresholds on these forums.

There are two opposing design goals usually at play here; the desire for system to be as quite as possible, and the need to keep the CPU and the drives adequately cooled. A little effort will yield an acceptable balance. Much more effort is required for close to perfection. This is some times referred to as the 80/20 rule. It takes 20% of the effort to get to 80% of the goal and 80% more effort to achieve the additional 20% to the goal.

@Kevin Horton
uses the same chassis and a similar motherboard and has written a script to control the temps in the fan bay.
 

Ceetan

FreeNAS Experienced
Joined
Apr 29, 2016
Messages
132
Regarding my disability is, you are indeed correct :). I work as a statistical programmer, primarily with the language SAS, Though way I've also got some experience with toying with Linux. My issue is mostly dealing with screws, but I have people that could help me about every other day.

I actually did consider the R4 but ultimately decided against it because I originally intended to put the box in a place that were a little more space constrains.
The main issue at the moment is that it is loud enough to be problematic. Originally I intended to store it somewhere else, which is why I picked The chassis I did. I later realised it would be impossible, so I (somewhat begrudgingly) put it in my combined office and living room. I have read about people managing to running The node 804 very silent but if worst comes to worst and might have to change Chassis.

I intend to see if I can start with the script someone else has already made, to see if I can get the noise level down. Maybe I should write with a little noise adapters too.

Strictly speaking I don't have to rely on the system at the moment, since there is not even a pool on it , much less any data, so as long as I don't wreck the hardware, it should be fine. Maybe should try resetting the BMC as well, there are some indications that it has panicked, as I tried out the threshold you suggested without any significant change. Thanks for all the advice!


Sent from my iPhone using Tapatalk
 

GrumpyBear

FreeNAS Experienced
Joined
Jan 28, 2015
Messages
141
Regarding my disability is, you are indeed correct :). I work as a statistical programmer, primarily with the language SAS, Though way I've also got some experience with toying with Linux. My issue is mostly dealing with screws, but I have people that could help me about every other day.

I actually did consider the R4 but ultimately decided against it because I originally intended to put the box in a place that were a little more space constrains.
The main issue at the moment is that it is loud enough to be problematic. Originally I intended to store it somewhere else, which is why I picked The chassis I did. I later realised it would be impossible, so I (somewhat begrudgingly) put it in my combined office and living room. I have read about people managing to running The node 804 very silent but if worst comes to worst and might have to change Chassis.

I intend to see if I can start with the script someone else has already made, to see if I can get the noise level down. Maybe I should write with a little noise adapters too.

Strictly speaking I don't have to rely on the system at the moment, since there is not even a pool on it , much less any data, so as long as I don't wreck the hardware, it should be fine. Maybe should try resetting the BMC as well, there are some indications that it has panicked, as I tried out the threshold you suggested without any significant change. Thanks for all the advice!

Sent from my iPhone using Tapatalk
Ah yes SAS - I remember when that was a HUGE program requiring a expensive memory upgrade to 2MB for an old girlfriend's IBM PC AT and having to load 20 - 30 1.44MB Disks to run ANCOVAs overnight on her data for her PhD thesis ...

Yes, many people are running FreeNAS on the Node 804 quietly, so you too should be able to do so with a little effort and expending some more effort with scripting get to near silent.

You have a good solid hardware platform and once you have it properly configured it should serve you well with minimal fuss.

If running Full Speed produced no discernible change in the system's noise then you definitely have an issue and the thresholds are likely the culprit. All the LNAs do (as far as I can tell) is lower just the upper speed of the Noctua fans from 1500 to 1200rpm so at a given PWM % they run slower (and quieter). The Noctuas should be almost silent in normal operation with no "tweaking" or scripts and just get noisy under heavy load. The issue will be likely that when the "hot" part of the case with the CPU requires more cooling the HDD side may not so you should be able to run that side slower but will need a script to do so.

You've some Linux under your belt so you should be OK. You might be more comfortable changing your shell to bash, ash or whatever your most familiar and using the the man pages. I love the midnight commander, "mc", the old orthogonal text-based file manager, which was available as a package for FreeNAS but appears to be installed by default now.

With no data you can't wreck (well you'd have to try really hard and be extremely foolish) the hardware. The CPU has thermal overloads and disks can be run hot with no ill effects for short periods it's just sustained overheating that tend to shorten their life.
 

Ericloewe

Not-very-passive-but-aggressive
Moderator
Joined
Feb 15, 2014
Messages
16,076
The CPU has thermal overloads
There's an ongoing discussion: Do CPUs react quickly enough if they're run without a heatsink of any kind?

So far, I don't think I've seen anyone try this on purpose. :p
 

Kevin Horton

FreeNAS Guru
Joined
Dec 2, 2015
Messages
624
I have read about people managing to running The node 804 very silent but if worst comes to worst and might have to change Chassis.
I've got a Node 804 case, and it is very possible to have it be almost inaudible. It is noisy if the fans are running full speed (as yours are). The trick now is to figure out why your fans are running so fast.

I initially used my own dumb script, which checked HD temperatures, then set the fans to one of three different duty cycles, depending on the temperature. This worked, but it by design had the temperature cycling up and down a bit, which is far from ideal for HD live.

I then started using the PID fan control script created by @Glorious1. The exact version of the script I'm currently using is below:

Code:
#!/usr/local/bin/bash
# spinpid.sh version 2016-11-01. Run as superuser. See notes at end.

##############################################
#
#  Settings
#
##############################################

# Drive Settings:
SP=36.00		#  Setpoint mean temperature
#  Time interval for checking drives in minutes.  This will only
#  be honored accurately when it is an even multiple of CPU_T.
T=3
Kp=6			#  Proportional tunable constant
Ki=0			#  Integral tunable constant
Kd=60		   #  Derivative tunable constant
PID=0

# CPU Settings:
CPU_T=60		#  Time interval for checking CPU in seconds
#  Reference temperature for scaling CPU_DUTY (NOT a setpoint).
#  Moving it up or down shifts the range of fan speeds
#  up or down the CPU temperature scale.
CPU_REF=68
#  Scalar for scaling CPU_DUTY.  Large number means
#  large changes in fan speed with change in CPU temp
#  (tighter control).  Try 20.
CPU_SCALE=20

LOG=/root/spinpid.log

##############################################
# function get_disk_name
# Get disk name from current LINE of DEVLIST
##############################################
# The awk statement works by taking $LINE as input,
# setting '(' as a _F_ield separator and taking the second field it separates
# (ie after the separator), passing that to another awk that uses
# ',' as a separator, and taking the first field (ie before the separator).
# In other words, everything between '(' and ',' is kept.

# camcontrol output for disks on HBA seems to reverse every version,
# so need 2 options to get ada/da disk name.
function get_disk_name {
   if [[ $LINE == *",d"* ]] ; then	 # for (pass#,da#) (HBA disks sometimes)
	  DEVID=$(echo $LINE | awk -F ',' '{print $2}' | awk -F ')' '{print$1}')
   else								# for (ada#,pass#) (motherboard disks)
	  DEVID=$(echo $LINE | awk -F '(' '{print $2}' | awk -F ',' '{print$1}')
   fi
}

############################################################
# function print_header
# Called when script starts and each quarter day
############################################################
function print_header {
   DATE=$(date +"%A, %b %d")
   let "SPACES = DEVCOUNT * 5 + 70"  # 5 spaces per drive
   printf "\n%-*s %-8s %s \n" $SPACES "$DATE" "Fan %" "Interim CPU"
   echo -n "		  "
   while read LINE ; do
	  get_disk_name
	  printf "%-5s" $DEVID
   done <<< "$DEVLIST"			 # while statement works on DEVLIST
   printf "%4s %5s %5s %6s %5s %6s %3s %s %4s %-7s %s %s" "Tmax" "Tmean" "ERRc" "P" "I" "D" "CPU" "Driver" "RPM" "MODE" "Curr/New" "Adjustments"
}

#################################################
# function drive_data: Read, process, print data
#################################################
function drive_data {
   Tmean=$(echo "scale=3; $Tsum / $i" | bc)
   ERRp=$ERRc
   ERRc=$(echo "scale=2; $Tmean - $SP" | bc)
   ERR=$(echo "scale=2; $ERRc * $T + $I" | bc)
   P=$(echo "scale=2; $Kp * $ERRc" | bc)
   I=$(echo "scale=2; $Ki * $ERR" | bc)
   D=$(echo "scale=2; $Kd * ($ERRc - $ERRp) / $T" | bc)
   PID=$(echo "scale=2; $P + $I + $D" | bc)  # add 3 corrections
   PID=$(printf %0.f $PID)  # round
   # Read duty cycle, convert to decimal.
   # May need to disable these 3 lines as some boards apparently return
   # incorrect data. In that case just assume $DUTY hasn't changed.
#   DUTY_CURR=$($IPMITOOL raw 0x30 0x70 0x66 0 0) # in hex
#   DUTY_CURR=$(printf "0x%s" $DUTY_CURR)				 # add Ox in front
#   DUTY_CURR=`echo $(($DUTY_CURR))`					  # convert to decimal
   # Read fan mode, convert to decimal.
   MODE=$($IPMITOOL raw 0x30 0x45 0) # in hex
   MODE=$(printf "0x%s" $MODE)				 # add Ox in front
   MODE=`echo $(($MODE))`					  # convert to decimal
   # Text for mode
   case $MODE in
	  0) MODEt="Standard" ;;
	  4) MODEt="HeavyIO" ;;
	  2) MODEt="Optimal" ;;
	  1) MODEt="Full" ;;
   esac
   # Get reported fan speed in RPM.
   # Takes the line with FAN2, then 2nd through the 5th
   # digit if there are that many.
   RPM=$($IPMITOOL sdr | grep "FAN2" | grep -Eo '[0-9]{2,5}')
   # print current Tmax, Tmean, CPU 0 temp, fan speed, mode, and duty and CPU 0 temperature
   printf "^%-3d %5.2f" $Tmax $Tmean
}

##############################################
# function CPU_check_adjust
# Get CPU temp. If above 59, calculate a new
# DUTY_CPU.
# If it is greater than the duty due to the
# drives, and different from current duty,
# apply it to the fans.
##############################################
function CPU_check_adjust {
   # Get temp of CPU 0, strip down to whole degrees C
   CPU_TEMP=$(sysctl -a dev.cpu.0.temperature | awk -F ' ' '{print $2}' | awk -F '.' '{print$1}')
   if [[ $CPU_TEMP -gt 59 ]]; then
	  DUTY_CPU=$( echo "scale=2; $CPU_TEMP - (($CPU_TEMP - $CPU_REF)/10 * -1 * $CPU_SCALE + $CPU_SCALE)" | bc )
	  DUTY_CPU=$( printf %0.f $DUTY_CPU )  # round
   else DUTY_CPU=20;
   fi
   if [[ $DUTY_CPU -gt $DUTY_DRIVE && $DUTY_CPU -ne $DUTY_NEW ]]; then
	  adjust_fans $DUTY_CPU
	  if [[ FIRST_TIME -eq 0 ]]; then printf "%d " $DUTY_CPU; fi
   fi
   FIRST_TIME=0
}

##############################################
# function DRIVES_check_adjust
# Print time on new log line.
# Go through each drive, getting and printing
# status and temp.  Calculate sum and max
# temp, then call function drive_data.
# Apply max of $PID and CPU_CORR to the fans.
##############################################
function DRIVES_check_adjust {
   echo  # start new line
   # print time on each line
   TIME=$(date "+%H:%M:%S"); echo -n "$TIME  "
   Tmax=0; Tsum=0  # initialize drive temps for new loop through drives
   i=0  # count number of spinning drives
   while read LINE ; do
	  get_disk_name
	  TEMP=$(/usr/local/sbin/smartctl -a -n standby "/dev/$DEVID" | grep "Temperature_Celsius" | grep -o "..$")
	  /usr/local/sbin/smartctl -n standby "/dev/$DEVID" > /var/tempfile
	  RETURN=$?			   # need to preserve because $? changes with each 'if'

	  if [[ $RETURN == "0" ]] ; then
		 STATE="*"  # spinning
	  elif [[ $RETURN == "2" ]] ; then
		 STATE="_"  # standby
	  else
		 STATE="?"  # state unknown
	  fi
	  printf "%s%-2d  " "$STATE" $TEMP
	  # Update temperatures each drive; spinners only
	  if [ "$STATE" == "*" ] ; then
		 let "Tsum += $TEMP"
		 if [[ $TEMP > $Tmax ]]; then Tmax=$TEMP; fi;
		 let "i += 1"
	  fi
   done <<< "$DEVLIST"
   drive_data  # manage data
#   let "DUTY_DRIVE = $DUTY_CURR + $PID"
   let "DUTY_DRIVE = $DUTY_DRIVE + $PID"
#   if [[ $DUTY_DRIVE -gt $DUTY_CPU ]]; then
#	  DRIVER="Drives"
#	  MAX=$DUTY_DRIVE
#   else
#	  DRIVER="CPU"
#	  MAX=$DUTY_CPU
#   fi
   DRIVER="Drives"
   adjust_fans $DUTY_DRIVE  # passing higher duty to the function adjust_fans
}

##############################################
# function adjust_fans
# Add correction to current duty,
# set duty, print diagnostic data
##############################################
function adjust_fans {
   # Reset BMC if fans seem stuck: cool and >80% OR warm and <30%
   # if [[ $Tmean<$(($SP - 1)) && $DUTY>0x50 ]] || [[ $Tmean>$(($SP + 5)) && $DUTY<0x1E ]]; then
   #	$IPMITOOL bmc reset warm; fi
   # $1 is the new duty
   # passed to this function when called
   DUTY_NEW=$1
   # Don't allow duty cycle beyond 20/95%
   if [[ $DUTY_NEW -gt 95 ]]; then DUTY_NEW=95; fi
   if [[ $DUTY_NEW -lt 20 ]]; then DUTY_NEW=20; fi
   # Change if different from current duty
   if [[ $DUTY_NEW -ne $DUTY ]]; then
	  DUTYhex=$( printf "0x%x" $DUTY_NEW )  #  hexify
	  # Set new duty cycle. "echo -n ``" prevents newline generated in log
	  echo -n `$IPMITOOL raw 0x30 0x70 0x66 1 0 $DUTYhex`
   fi
}

#####################################################
# All this happens only at the beginning
# Initializing values, list of drives, print header
#####################################################
CPU_LOOPS=$( echo "$T * 60 / $CPU_T" | bc )  # Number of whole CPU loops per drive loop
IPMITOOL=/usr/local/bin/ipmitool
I=0; ERRc=0  # Initialize errors to 0

# Creates logfile and sends all stdout and stderr to the log, as well as to the console.
# If you want to append to existing log, add '-a' to the tee command.
exec > >(tee -a -i $LOG) 2>&1

# Get list of drives
DEVLIST1=$(/sbin/camcontrol devlist)
# Remove lines with flash drives or SSD; edit as needed
# You could use another strategy, e.g., find something in the camcontrol devlist
# output that is unique to the drives you want, for instance only WDC drives:
# if [[ $LINE != *"WDC"* ]] . . .
DEVLIST="$(echo "$DEVLIST1"|sed '/KINGSTON/d;/ADATA/d;/SanDisk/d;/SSD/d')"
DEVCOUNT=$(echo "$DEVLIST" | wc -l)
# Set mode to 'Full' to avoid BMC changing duty cycle
# Need to wait a tick or it doesn't get 2nd command
# "echo -n ``" to avoid annoying newline generated in log
echo -n `$IPMITOOL raw 0x30 0x45 1 1`; sleep 1
# Then start with 60% duty cycle and let algorithm adjust from there
DUTY_NEW=60
DUTY_DRIVE=60
DUTYhex=$( printf "0x%x" $DUTY_NEW )
echo -n `$IPMITOOL raw 0x30 0x70 0x66 1 0 $DUTYhex`
sleep 3  # let fans respond

printf "\nDrive states:  * spinning;  _ standby;  ? unknown\n"
print_header
FIRST_TIME=1
CPU_check_adjust

###########################################
# Main loop through drives every T minutes
# and CPU every CPU_T seconds
###########################################
while [ 1 ] ; do
   # Print header every quarter day.  Expression removes any
   # leading 0 so it is not seen as octal
   HM=$(date +%k%M); HM=`expr $HM + 0`
   R=$(( HM % 600 ))  # remainder after dividing by 6 hours
   if (( $R < $T )); then
	  print_header;
   fi
   DRIVES_check_adjust
   printf "%6.2f %6.2f %5.2f %6.2f %3d %-6s %4d %-7s %2d/%-6d" $ERRc $P $I $D $CPU_TEMP $DRIVER $RPM $MODEt $DUTY_CURR $DUTY_NEW

   i=0
   while [ $i -lt $CPU_LOOPS ]; do
	  sleep $CPU_T
	  CPU_check_adjust
	  let i=i+1
   done
done

# Adjusts fans based on drive or CPU temperatures, whichever
# needs more cooling. Max temp among drives is maintained at a setpoint
# using a PID algorithm.  CPU temp regulation uses just core 0
# (they all stay within a few degrees of each other).  CPU temp
# need not and cannot be maintained at a setpoint, so PID is not
# used; instead fan duty cycle is simply increased with temp.

# Drives are checked and fans adjusted on a set interval, such as 6 minutes.
# Logging is done at that point.  CPU temps can spike much faster,
# so are checked at a shorter interval, such as 30 seconds.  Those
# adjustments are not logged.

# Logs:
#   - disk status (spinning or standby)
#   - disk temperature (Celsius) if spinning
#   - max and mean disk temperature
#   - CPU 0 temperature
#   - fan rpm and mode
#   - current and new fan duty cycle
#   - PID variables
#   - adjustments to fan duty cycle due to interim CPU loops

# Includes disks on motherboard and on HBA.

#  Relation between percent duty cycle, hex value of that number,
#  and RPMs for my fans.  RPM will vary among fans, is not
#  precisely related to duty cycle, and does not matter to the script.
#  It is merely reported.
#
#  Percent	Hex		RPM
#  10		  A		300
#  20		 14		400
#  30		 1E		500
#  40		 28		600/700
#  50		 32		800
#  60		 3C		900
#  70		 46		1000/1100
#  80		 50		1100/1200
#  90		 5A		1200/1300
# 100		 64		1300

# Some boards apparently report incorrect duty cycle.
# If that is happening, disable lines 86-88 in function drive_data.
# Then the script will assume the duty cycle is the
# same as it was last set.

# Tuning suggestions
# PID tuning advice on the internet generally does not work well in this application.
# First run the script spincheck.sh and get familiar with your temperature and fan variations without any intervention.
# Choose a setpoint that is an actual observed Tmean, given the number of drives you have.  It should be the Tmean associated with the Tmax that you want.
# Set Ki=0 and leave it there.  You probably will never need it.
# Start with Kp low.  Use a value that results in a rounded correction=1 when error is the lowest value you observe other than 0  (i.e., when ERRc is minimal, Kp ~= 1 / ERRc)
# Set Kd at about Kp*10
# Get Tmean within ~0.3 degree of SP before starting script.
# Start script and run for a few hours or so.  If Tmean oscillates (best to graph it), you probably need to reduce Kd.  If no oscillation but response is too slow, raise Kd.
# Stop script and get Tmean at least 1 C off SP.  Restart.  If there is overshoot and it goes through some cycles, you may need to reduce Kd.
# If you have problems, examine PK and PD in the log and see which is messing you up.  If all else fails you can try Ki. If you use Ki, make it small, ~ 0.1 or less.

# Uses joeschmuck's smartctl method for drive status (returns 0 if spinning, 2 in standby)
# https://forums.freenas.org/index.php?threads/how-to-find-out-if-a-drive-is-spinning-down-properly.2068/#post-28451
# Other method (camcontrol cmd -a) doesn't work with HBA

# Removed from drive_data.  Though it was working
# it doesn't seem right to hexify PID ?????
   # PID=$( printf "0x%x" $PID )  # fully hexify with '0x' in front



The above script is placed at /root/bin/spinpid.sh. Make the script executable by running "chmod +x /root/bin/spinpid.sh".

I created a startup task that runs that script: in the FreeNAS web interface, go to Tasks -> Init/Shutdown Scripts, and click the "Add Init/Shutdown Script" button. For Type, select "Command". For Command, enter "/root/bin/spinpid.sh". For When, select "Post Init".

Connect the CPU fan to the FANA header, so that it will be modulated by the motherboard in response to CPU temperature. Connect the chassis fans to FAN1, FAN2, FAN3 and/or FAN4 - they will be controlled by the script.

After doing all the above, restart FreeNAS, and see what happens. You should see a log at /root/spinpid.log. You can check fan speeds by running: ipmitool sdr | grep FAN.

Set up email warnings about excessive HD temperatures: In the FreeNAS web interface, go to Services. Enable "S.M.A.R.T.", and click the wrench icon to the right of the SMART service. Put the following values in S.M.A.R.T. Settings:

Check Interval: 30
Power Mode: Never - Check the device regardless of its power mode
Difference: 0
Informational: 40
Critical: 41
Email to report: enter your email address.

Set up email: in the FreeNAS web interface, select System -> Email. Enter appropriate values and then click the "Send Test Email" button at the bottom. Adjust as required until you actually receive a test email.

Do all the above and report back. We'll get this sorted out.
 

Ceetan

FreeNAS Experienced
Joined
Apr 29, 2016
Messages
132
What can I say, FreeNAS has an awesome community :). A minor update: I move the fan as per grumpybears suggestion. While having that done I naturally unpluges the computer. When I turned it back on, it was running super quiet. It has been doing so ever since. As has been suggested above, I think the BMC was panicking. Now it's running so quiet it's creepy. One thing I'm worried about, is with the fan in the lower left position rather than the top, is the airflow impeded by me having an SSD there? That's where I put the boot drive.

I'm certainly going to have a look at that whole script Kevin posted.


Sent from my iPhone using Tapatalk
 

Kevin Horton

FreeNAS Guru
Joined
Dec 2, 2015
Messages
624
What can I say, FreeNAS has an awesome community :). A minor update: I move the fan as per grumpybears suggestion. While having that done I naturally unpluges the computer. When I turned it back on, it was running super quiet. It has been doing so ever since. As has been suggested above, I think the BMC was panicking. Now it's running so quiet it's creepy.
Pay close attention to your hard drive temperatures. The fans are very quiet at low rpm, but they aren't moving much air either. I found during my burn-in testing that hard drive temperatures would be well over 40C if the fans were running too slowly. The system is still very quiet if the fans are running fast enough to keep my average HD temperature at 36C, so don't worry about noise.
 
Last edited:

Ceetan

FreeNAS Experienced
Joined
Apr 29, 2016
Messages
132
Yeah, I actually encounters the issue of overheating. Found out that the drives have been running at about 40° (some 41) for two days. Unfortunately the email alerts hadn't been working, so I'll have to look into that. I shut the machine down, and it will remain so until I can implement countermeasures. Fingers crossed nothing too bad happened. I have a question. I've been getting some different advice regarding the fanA Header. From what I understand it is originally intended for Peripherals such as hard drives. Stuxes script seems to use them that way.

The one that Kevin directed me to use is the fanA Header for CPU, correct? I assume this is simply dependent on what the script is written to do ( what sauce do you use as temperature inputs, and what headers/fan to send the resulting command to. Am I understanding this right?


Sent from my iPhone using Tapatalk
 

Kevin Horton

FreeNAS Guru
Joined
Dec 2, 2015
Messages
624
Yeah, I actually encounters the issue of overheating. Found out that the drives have been running at about 40° (some 41) for two days. Unfortunately the email alerts hadn't been working, so I'll have to look into that. I shut the machine down, and it will remain so until I can implement countermeasures. Fingers crossed nothing too bad happened. I have a question. I've been getting some different advice regarding the fanA Header. From what I understand it is originally intended for Peripherals such as hard drives. Stuxes script seems to use them that way.

The one that Kevin directed me to use is the fanA Header for CPU, correct? I assume this is simply dependent on what the script is written to do ( what sauce do you use as temperature inputs, and what headers/fan to send the resulting command to. Am I understanding this right?


Sent from my iPhone using Tapatalk
41C for a couple of days won't have done any significant damage to the drives.

I wrote fanA, as that lines up with how my board works, if I recall correctly. It may be different for different boards. You can tell by testing - hook up the CPU fan to a header, check the rpm of all fans using ipmitool sdr | grep FAN and CPU temperature using sysctl -a |egrep -E "cpu\.[0-9]+\.temp". Then, put a load on the CPU, wait a minute or two, then check again. Figure out which fan header responds quickly to CPU temperature.
 

Stux

FreeNAS Wizard
Joined
Jun 2, 2016
Messages
4,166
At least on my board FANA is the fan driven by the HeavyIO setting.

When using my script it doesn't actually matter as it takes total control over the fan zones.

If you want you can swap the zones around by editing the settings.
 

Ceetan

FreeNAS Experienced
Joined
Apr 29, 2016
Messages
132
At least on my board FANA is the fan driven by the HeavyIO setting.

When using my script it doesn't actually matter as it takes total control over the fan zones.

If you want you can swap the zones around by editing the settings.
That midnight require more scripting acumen then I currently posses, though I have not dug into it, so I am not sure.

A little update: I tried running both scripts of the suggested script yesterday yesterday, starting with @Stux s'. That one did run, but seemed to run incorrectly. Output below.
My guess is that need I better fan thresholds. What's also confusing is that when i alter the threshold of FANA, FAN3 (CPU) goes haywire. Why might that be? Of note is that from what I can glean, all headers in my mobo are listed as System/CPU-headers, according to the manual.
Code:

		http://freenas.org
Welcome to FreeNAS
[root@Darwin] ~# chmod +x /root/hybrid_fan_controller.pl
[root@Darwin] ~# /root/hybrid_fan_controller.pl
2016-12-22 22:22:50: CPU Temp: 40.0 dropped below 45, CPU Fan going med.
2016-12-22 22:22:50: Maximum HD Temperature: 31
2016-12-22 22:22:50: Drives are cool enough, going to 30%
2016-12-22 22:23:01: CPU Fan speed: No reading
2016-12-22 22:23:13: CPU Fan speed: No reading
2016-12-22 22:23:26: CPU Fan speed: No reading
2016-12-22 22:23:38: CPU Fan speed: No reading
2016-12-22 22:23:49: CPU Fan speed: No reading
2016-12-22 22:24:01: CPU Fan speed: No reading
2016-12-22 22:24:14: CPU Fan speed: No reading
2016-12-22 22:24:26: CPU Fan speed: No reading
2016-12-22 22:24:37: CPU Fan speed: No reading
2016-12-22 22:24:48: CPU Fan speed: No reading
2016-12-22 22:25:01: CPU Fan speed: No reading
2016-12-22 22:25:12: CPU Fan speed: No reading
2016-12-22 22:25:12: Fan speeds are unreadable after 120 seconds, rebooting BMC
2016-12-22 22:25:12: Resetting BMC
2016-12-22 22:26:01: CPU Temp: 57.0 >= 55, CPU Fan going high.
2016-12-22 22:26:01: Maximum HD Temperature: 32
2016-12-22 22:26:02: CPU Temp: 52.0 >= 45, CPU Fan going med.
2016-12-22 22:26:04: CPU Temp: 56.0 >= 55, CPU Fan going high.
2016-12-22 22:26:05: CPU Temp: 50.0 >= 45, CPU Fan going med.
2016-12-22 22:26:17: CPU Fan speed: No reading
2016-12-22 22:26:17: HD Fan speed: No reading
2016-12-22 22:26:28: CPU Fan speed: No reading
2016-12-22 22:26:28: HD Fan speed: No reading
2016-12-22 22:26:39: CPU Fan speed: No reading
2016-12-22 22:26:39: HD Fan speed: No reading
2016-12-22 22:26:50: CPU Fan speed: No reading
2016-12-22 22:27:02: CPU Fan speed: No reading
2016-12-22 22:27:14: CPU Fan speed: No reading
2016-12-22 22:27:27: CPU Fan speed: No reading
2016-12-22 22:27:38: CPU Fan speed: No reading
2016-12-22 22:27:49: CPU Fan speed: No reading
2016-12-22 22:28:00: CPU Fan speed: No reading
ipmitool sensorlia2016-12-22 22:28:12: CPU Fan speed: No reading
^R
2016-12-22 22:28:25: CPU Fan speed: No reading
2016-12-22 22:28:25: Fan speeds are unreadable after 120 seconds, rebooting BMC
2016-12-22 22:28:25: Resetting BMC
stop
2016-12-22 22:29:14: Maximum HD Temperature: 32
2016-12-22 22:29:16: CPU Temp: 55.0 >= 55, CPU Fan going high.
2016-12-22 22:29:17: CPU Temp: 52.0 >= 45, CPU Fan going med.
2016-12-22 22:29:28: CPU Fan speed: No reading
2016-12-22 22:29:29: HD Fan speed: No reading
2016-12-22 22:29:40: CPU Fan speed: No reading
2016-12-22 22:29:41: HD Fan speed: No reading
2016-12-22 22:29:52: CPU Fan speed: No reading
2016-12-22 22:29:53: HD Fan speed: No reading
2016-12-22 22:30:05: CPU Fan speed: No reading
2016-12-22 22:30:17: CPU Fan speed: No reading
2016-12-22 22:30:29: CPU Fan speed: No reading
2016-12-22 22:30:40: CPU Fan speed: No reading
2016-12-22 22:30:51: CPU Fan speed: No reading
2016-12-22 22:31:01: CPU Temp: 55.0 >= 55, CPU Fan going high.
2016-12-22 22:31:02: CPU Temp: 39.0 dropped below 45, CPU Fan going med.
2016-12-22 22:31:13: CPU Fan speed: No reading
2016-12-22 22:31:24: CPU Fan speed: No reading
2016-12-22 22:31:36: CPU Fan speed: No reading
2016-12-22 22:31:37: Fan speeds are unreadable after 120 seconds, rebooting BMC
2016-12-22 22:31:37: Resetting BMC
2016-12-22 22:32:25: CPU Temp: 55.0 >= 55, CPU Fan going high.
2016-12-22 22:32:25: Maximum HD Temperature: 32
2016-12-22 22:32:27: CPU Temp: 48.0 >= 45, CPU Fan going med.
2016-12-22 22:32:39: CPU Fan speed: No reading
2016-12-22 22:32:39: HD Fan speed: No reading
2016-12-22 22:32:50: CPU Fan speed: No reading
2016-12-22 22:32:50: HD Fan speed: No reading
2016-12-22 22:33:01: CPU Fan speed: No reading
2016-12-22 22:33:02: HD Fan speed: No reading
2016-12-22 22:33:13: CPU Fan speed: No reading
2016-12-22 22:33:26: CPU Fan speed: No reading
2016-12-22 22:33:38: CPU Fan speed: No reading
2016-12-22 22:33:49: CPU Fan speed: No reading
2016-12-22 22:34:00: CPU Fan speed: No reading
2016-12-22 22:34:11: CPU Fan speed: No reading
2016-12-22 22:34:23: CPU Fan speed: No reading
2016-12-22 22:34:36: CPU Fan speed: No reading
2016-12-22 22:34:48: CPU Fan speed: No reading
2016-12-22 22:34:48: Fan speeds are unreadable after 120 seconds, rebooting BMC
2016-12-22 22:34:48: Resetting BMC
hybrid2016-12-22 22:35:37: CPU Temp: 55.0 >= 55, CPU Fan going high.
2016-12-22 22:35:37: Maximum HD Temperature: 31
2016-12-22 22:35:38: CPU Temp: 48.0 >= 45, CPU Fan going med.
hybrid_fan_cotroler2016-12-22 22:35:49: CPU Fan speed: No reading
.p2016-12-22 22:35:50: HD Fan speed: No reading
^R
hybridhybrid_fan_cotroler.2016-12-22 22:36:01: CPU Fan speed: No reading
2016-12-22 22:36:01: HD Fan speed: No reading
^R
hybridhybrid_fan_cotroler.p2016-12-22 22:36:13: CPU Fan speed: No reading
l2016-12-22 22:36:13: HD Fan speed: No reading
2016-12-22 22:36:24: CPU Fan speed: No reading
screen
2016-12-22 22:36:35: CPU Fan speed: No reading
tmux
2016-12-22 22:36:48: CPU Fan speed: No reading
2016-12-22 22:37:00: CPU Fan speed: No reading
2016-12-22 22:37:12: CPU Fan speed: No reading
2016-12-22 22:37:24: CPU Fan speed: No reading
2016-12-22 22:37:36: CPU Fan speed: No reading
2016-12-22 22:37:47: CPU Fan speed: No reading
2016-12-22 22:37:58: CPU Fan speed: No reading
2016-12-22 22:37:59: Fan speeds are unreadable after 120 seconds, rebooting BMC
2016-12-22 22:37:59: Resetting BMC
2016-12-22 22:38:47: CPU Temp: 55.0 >= 55, CPU Fan going high.
2016-12-22 22:38:47: Maximum HD Temperature: 31
2016-12-22 22:38:48: CPU Temp: 51.0 >= 45, CPU Fan going med.
2016-12-22 22:38:59: CPU Fan speed: No reading
2016-12-22 22:39:00: HD Fan speed: No reading
2016-12-22 22:39:12: CPU Fan speed: No reading
2016-12-22 22:39:12: HD Fan speed: No reading
2016-12-22 22:39:23: CPU Fan speed: No reading
2016-12-22 22:39:23: HD Fan speed: No reading
 
Last edited:
Top