High Fan Speed Issue on Lenovo ThinkSystem Servers
-
Weird but thanks a lot @rmaclachlan for the feedback!
-
We have exactly the same issue with a Lenovo ThinkSystem SR665 V3 (Model #7D9AA01SEA) running a single AMD EPYC 9354 32C. We are running currently the following latest firmwares on our system;
We installed xcp-ng-8.3.0-beta2 (due to the Mellanox ConnectX-6 Lx 10/25GbE SFP28 2-port OCP Ethernet Adapter which is by default not supported in XCP 8.2.1) and have exactly similar issues. When the server is turned on but not in XCP yet, we get the following temperature reading in Xclarity Controller 2 (having 2x 64 GB RAM MTC40F2046S1RC48BR);
However, when XCP is booted we get the following temperature reading;
This results indeed that the fans go to max power due to missing readings.The downgrade of Firmwares I haven't tried yet, but would be nice if this could be solved in XCP. We have another identical system in stock which we still need to install. I'm planning to try the installation on that server without upgrading the default factory firmwares and see if that works better.
-
I wonder what's missing exactly and where so we can bundle it (or not if it's not possible, but since it seems to work in a 4.18 kernelβ¦)
-
Adding @gduperrey in the conversation
-
@olivierlambert ; as it's a clean install I can see if I can provide you access to the server with Xclarity Controller 2 so you have full access to a system for testing? Would that help?
-
Hey,
Just wanted to provide an update from our end as well.
We've conducted tests with various versions of the xClarity Controller firmware / UEFI.
Lenovo seems to be onto something, as they recently released a new version with the following changelog: (XClarity Controller Firmware 2.40 KAX326G).They've also released a new UEFI in the meantime. However, the fan speed issue persists despite these updates.
We attempted to consolidate support from Lenovo, but they were unable to escalate the ticket due to XCP-ng being considered unsupported.
What seems to be working for us, as suggested by @rmaclachlan , is the UEFI version 1.41 (Build ID: KAE110K).
With this version, the fan speeds have decreased to around 9k RPMs, which, while still slightly high, is within acceptable sound levels.
That's really not the best option as they have adressed a few CVE's since this release, but at least we can start setting up the Server without getting angry calls all the time..
The XClarity Controller firmware doesn't have an impact on the fan speed at all as it seems. -
@RIX_IT said in High Fan Speed Issue on Lenovo ThinkSystem Servers:
XClarity Controller Firmware 2.40 KAX326G
On our system we are running XClarity Controller Firmware 2.40 KAX326G, having similar issues.
-
@LennertvdBerg As mentioned, XCC firmware doesn't seem to change anything regarding the fan speed. So we're sticking with the latest version for now. You could try rolling back to UEFI 1.41 (Build ID: KAE110K) as well and see if it makes a difference.
-
Please keep us posted, more details we have, more chances we can find what's missing in XCP-ng to make it work correctly
-
Could one of you try the
kernel-alt
package? It is not meant for production as it is not fully tested and supported, but if a higher patch level of the 4.19 helps, it could give us more idea of what's happening.EDIT: it should be updated to a new patch level soon-ish, so if current one does not fix, we should soon have another shot with a more recent update.
-
@bleader ; do you have somewhere the instructions how to do this procedure?
-
You can find information about
kernel-alt
here: https://docs.xcp-ng.org/installation/hardware/#-alternate-kernel -
Just did that on 8.2 (kernel-alt.x86_64 0:4.19.265-1.xcpng8.2), not the testing one yet.
Got a few errors on startup, not related afaik, but still fyi:
That didn't make a difference as it seems:
I'm on UEFI 1.41, could try the most recent somewhat later once people leave their offices.
-
@gduperrey said in High Fan Speed Issue on Lenovo ThinkSystem Servers:
https://docs.xcp-ng.org/installation/hardware/#-alternate-kernel
I tried installing the kernel-alt using
yum install kernel-alt
However I receive the following error;
python: can't open file '/opt/xensource/bin/updategrub.py': [Errno 2] No such file or directory warning: %postun(kernel-alt-4.19.227-5.xcpng8.3.x86_64) scriptlet failed, exit status 2
-
@RIX_IT I tried kernel-alt before rolling back the uefi and it didn't help. Also tried the new Xen beta stormi posted (4.19 was it?) in case something was added but that didn't fix it either.
Thanks for trying the new Lenovo fw - I saw it come out and was going to test when I had time but now I don't need to!
-
Did it come fully equipped?
Did you install Lenovo signed HDD in it? Or you have compatibles HDD.
If you have compatibility, try to put a HDD with (original) Lenovo firmware.
I had the same problem with an Lenovo ThinkSystem SR630, I had installed a Lenovo non-firmware HDD, all of them. I bought one with Lenovo firmware, I installed and the problem disappeared. -
@Gheppy Our SR635v3 are running factory installed Lenovo hardware, although I did test swapping out the Broadcom 57504 OCP NIC with Intel X710 but the fan issue persisted. Thanks for the suggestion!
-
@Gheppy I just installed Ubuntu 22.044 LTS with kernel 5.15.0-102-generic just to test if there could be anything like a 'vendor lock'. Using Ubuntu I just see my memory temperatures and all my fan speeds are around 6000 rpm. So it really seems to be something with XCP and Lenovo.
-
Try to install lm-sensors and see what it detects.
It seems to me that the kernel it does not have drivers for IPMI BMC KCS.
My fans have 8000 - 8100 rpmyum -y install lm_sensors sensors -v sensors-detect sensors
-
@Gheppy I've just reinstalled xcp-ng-8.3.0-beta2 after my Ubuntu experiment and installed lm_sensors. The output is indeed:
Driver `to-be-written': * ISA bus, address 0xcc0 Chip `IPMI BMC KCS' (confidence: 8) Note: there is no driver for IPMI BMC KCS yet. Check http://www.lm-sensors.org/wiki/Devices for updates. No modules to load, skipping modules configuration. Unloading i2c-dev... OK Unloading cpuid... OK
The complete output is:
What will be the solution for this?