FUJITSU - Server fan control

bitboy0

bitboy0

Member
May 20, 2020
62
2
8
56
I am using Proxmox on a Primergy RX2540 M2 with 2 CPUs and 128GB RAM. Also HW RAID for the storage.

The server was running ESXI before and I had constant fan speeds at constant temperatures. At temperatures below 20°C the server was very quiet and from 25°C it became increasingly very unpleasant. We don't have a server room at the site and it is located in an office where there is air conditioning that is switched on as needed.

Since the server is running under PROXMOX, the behavior of the fans is significantly different. In completely irregular intervals the speed of the fans increases or decreases, although the room has no other temperature. The load of the server also does not correlate with the speed.

I got used to a relatively constant fan speed, but this spontaneous, irregular up and down at unpredictable intervals is annoying.

Is there any way to control this? Can you see what the system thinks might be necessary?

Translated with www.DeepL.com/Translator (free version)
 
hi,

what is your current workload like?

maybe checking htop, atop etc. similar tools for a while when the server is running is a good idea to pin the issue down.
 
The load-average is around 0.75 or 1.
But there is no apparent connection between the CPU load and the fan speed. It can be high at 5% CPU load and low at 50%. But other components are hardly load-dependent in terms of consumption and waste heat.

And while the speed used to increase in quite fine increments when the temperature increased (ESXI), it's now rather coarse increments.

I would like to know if there is a config file that can be adjusted. Or if I can see if the system gets meaningful values from the sensors at all.

Translated with www.DeepL.com/Translator (free version)
 
bitboy0 said:
Or if I can see if the system gets meaningful values from the sensors at all.
Click to expand...
you could install lm-sensors and run watch sensors
 
This is what it looks like all the time.

The CPU varies a bit and these "be2net" are fixed at exactly 59°C.


Code: 
Every 2.0s: sensors                                                                                                              pve1: Wed Jan 13 14:16:57 2021


power_meter-acpi-0
Adapter: ACPI interface
power1:      146.00 W  (interval =   1.00 s)


coretemp-isa-0001
Adapter: ISA adapter
Package id 1:  +35.0°C  (high = +80.0°C, crit = +90.0°C)
Core 0:        +27.0°C  (high = +80.0°C, crit = +90.0°C)
Core 1:        +28.0°C  (high = +80.0°C, crit = +90.0°C)
Core 2:        +27.0°C  (high = +80.0°C, crit = +90.0°C)
Core 3:        +27.0°C  (high = +80.0°C, crit = +90.0°C)


be2net-pci-0303
Adapter: PCI adapter
temp1:        +59.0°C


be2net-pci-0301
Adapter: PCI adapter
temp1:        +59.0°C


coretemp-isa-0000
Adapter: ISA adapter
Package id 0:  +38.0°C  (high = +80.0°C, crit = +90.0°C)
Core 0:        +33.0°C  (high = +80.0°C, crit = +90.0°C)
Core 1:        +32.0°C  (high = +80.0°C, crit = +90.0°C)
Core 2:        +32.0°C  (high = +80.0°C, crit = +90.0°C)
Core 3:        +30.0°C  (high = +80.0°C, crit = +90.0°C)


be2net-pci-0302
Adapter: PCI adapter
temp1:        +59.0°C


be2net-pci-0300
Adapter: PCI adapter
temp1:        +59.0°C
 
bitboy0 said:
The CPU varies a bit and these "be2net" are fixed at exactly 59°C.
Click to expand...
Did you run sensors-detect? I am missing the fan speeds in the output. Also you can check the data through IPMI, Fujitsu usually has a good load of sensor data there as well.
 
Yes, that's all he finds.

Code: 
root@pve1:/# sensors-detect
# sensors-detect revision $Revision$
# System: FUJITSU PRIMERGY RX2540 M2 [GS01]
# Board: FUJITSU D3289-B1
# Kernel: 5.4.78-2-pve x86_64
# Processor: Intel(R) Xeon(R) CPU E5-2623 v4 @ 2.60GHz (6/79/1)

This program will help you determine which kernel modules you need
to load to use lm_sensors most effectively. It is generally safe
and recommended to accept the default answers to all questions,
unless you know what you're doing.

Some south bridges, CPUs or memory controllers contain embedded sensors.
Do you want to scan for them? This is totally safe. (YES/no):
Module cpuid loaded successfully.
Silicon Integrated Systems SIS5595...                       No
VIA VT82C686 Integrated Sensors...                          No
VIA VT8231 Integrated Sensors...                            No
AMD K8 thermal sensors...                                   No
AMD Family 10h thermal sensors...                           No
AMD Family 11h thermal sensors...                           No
AMD Family 12h and 14h thermal sensors...                   No
AMD Family 15h thermal sensors...                           No
AMD Family 16h thermal sensors...                           No
AMD Family 17h thermal sensors...                           No
AMD Family 15h power sensors...                             No
AMD Family 16h power sensors...                             No
Intel digital thermal sensor...                             Success!
    (driver `coretemp')
Intel AMB FB-DIMM thermal sensor...                         No
Intel 5500/5520/X58 thermal sensor...                       No
VIA C7 thermal sensor...                                    No
VIA Nano thermal sensor...                                  No

Some Super I/O chips contain embedded sensors. We have to write to
standard I/O ports to probe them. This is usually safe.
Do you want to scan for Super I/O sensors? (YES/no):
Probing for Super-I/O at 0x2e/0x2f
Trying family `National Semiconductor/ITE'...               No
Trying family `SMSC'...                                     No
Trying family `VIA/Winbond/Nuvoton/Fintek'...               No
Trying family `ITE'...                                      No
Probing for Super-I/O at 0x4e/0x4f
Trying family `National Semiconductor/ITE'...               No
Trying family `SMSC'...                                     No
Trying family `VIA/Winbond/Nuvoton/Fintek'...               No
Trying family `ITE'...                                      No

Some systems (mainly servers) implement IPMI, a set of common interfaces
through which system health data may be retrieved, amongst other things.
We first try to get the information from SMBIOS. If we don't find it
there, we have to read from arbitrary I/O ports to probe for such
interfaces. This is normally safe. Do you want to scan for IPMI
interfaces? (YES/no):
Found `IPMI BMC KCS' at 0xca2...                            Success!
    (confidence 8, driver `to-be-written')

Some hardware monitoring chips are accessible through the ISA I/O ports.
We have to write to arbitrary I/O ports to probe them. This is usually
safe though. Yes, you do have ISA I/O ports even if you do not have any
ISA slots! Do you want to scan the ISA I/O ports? (YES/no):
Probing for `National Semiconductor LM78' at 0x290...       No
Probing for `National Semiconductor LM79' at 0x290...       No
Probing for `Winbond W83781D' at 0x290...                   No
Probing for `Winbond W83782D' at 0x290...                   No

Lastly, we can probe the I2C/SMBus adapters for connected hardware
monitoring devices. This is the most risky part, and while it works
reasonably well on most systems, it has been reported to cause trouble
on some systems.
Do you want to probe the I2C/SMBus adapters now? (YES/no):
Using driver `i2c-i801' for device 0000:00:1f.3: Wellsburg (PCH)

Next adapter: SMBus I801 adapter at 0580 (i2c-0)
Do you want to scan it? (YES/no/selectively):
Client found at address 0x48
Probing for `National Semiconductor LM75'...                No
Probing for `National Semiconductor LM75A'...               No
Probing for `Dallas Semiconductor DS75'...                  No
Probing for `National Semiconductor LM77'...                No
Probing for `Analog Devices ADT7410/ADT7420'...             No
Probing for `Analog Devices ADT7411'...                     No
Probing for `Maxim MAX6642'...                              No
Probing for `Texas Instruments TMP435'...                   No
Probing for `National Semiconductor LM73'...                No
Probing for `National Semiconductor LM92'...                No
Probing for `National Semiconductor LM76'...                No
Probing for `Maxim MAX6633/MAX6634/MAX6635'...              No
Probing for `NXP/Philips SA56004'...                        No
Probing for `SMSC EMC1023'...                               No
Probing for `SMSC EMC1043'...                               No
Probing for `SMSC EMC1053'...                               No
Probing for `SMSC EMC1063'...                               No

Next adapter: mga i2c (i2c-1)
Do you want to scan it? (yes/NO/selectively): yes


Now follows a summary of the probes I have just done.
Just press ENTER to continue:

Driver `coretemp':
  * Chip `Intel digital thermal sensor' (confidence: 9)

Driver `to-be-written':
  * ISA bus, address 0xca2
    Chip `IPMI BMC KCS' (confidence: 8)

Note: there is no driver for IPMI BMC KCS yet.
Check https://hwmon.wiki.kernel.org/device_support_status for updates.

To load everything that is needed, add this to /etc/modules:
#----cut here----
# Chip drivers
coretemp
#----cut here----
If you have some drivers built into your kernel, the list above will
contain too many modules. Skip the appropriate ones!

"Found `IPMI BMC KCS' at 0xca2... Success!
(confidence 8, driver `to-be-written')"

LOL?!
 
Last edited:
bitboy0 said:
"Found `IPMI BMC KCS' at 0xca2... Success!
(confidence 8, driver `to-be-written')"
Click to expand...
Yup, there seems to be no module for that one in the kernel. The ipmi interface (openipmi) should still provide some additional data. But Fujitsu also has its own software and plugins, maybe these may help.
https://download.ts.fujitsu.com/prim_supportcd/SVSSoftware/

Otherwise you can disable the C/P-states and run the server in full power, that provides no sound variation. ;)
 
Well, I was already there when the server tested its fans.
I prefer not to be around when the server gives the impression of launching straight from the rack into space.

I'll see what software they have and see if that helps me ;)
 
bitboy0 said:
This sounds like an adventure, which is way out of my league.
Click to expand...
Well, then you may look into the openipmi and query the values from there.
 
You must log in or register to reply here.

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom
Back