I would say yes, it's pretty normal - those 1U HP servers make a lotta noise!
I have a Proliant DL360 in my server room (not the same as yours, but still 1U) and it is one of the noisiest (if not the noisiest) server in the room. I had reason to turn it off once, and the noise in the room went down a phenomenal amount when it was off.
You might want to see if there's any firmware updates available and apply them - they solve some weird and wonderful problems, as well as do your server some good. I've had them solve things like reports of overheating, as well as some fan issues before.
It might also be worth your while poking around the BIOS to see if there's any settings for the fans. I doubt it, as like I said, the 1U servers are noisy little things - but you never know.
Unbelievable...
I found the answer after a ton of research and comparing two HP Dl180 G6's, one with the fan noise issue and one without I discovered the problem.
So here is the issue.
On right hand side of the server behind the power button there is a temperature sensor. When the motherboard stops registering that temp it assumes the incoming air is hotter then acceptable and ramps up the fan noise to compensate. The really odd thing is that the absence of this sensor data doesn't raise any red flags in the system or ILO. It simply indicates no data for the front panel sensor.
When I swapped in the front panel from a known working server the problem went away. When I swapped in the bad sensor to a working server the problem followed the sensor to the new server.
The sensor is not a separate part number it is part of the drive bay.
I called HP and insisted they replace the drive bay so I could get a new sensor.
The first drive bay they sent me was like for like, it was an 8 bay hotswap with the DVD-ROM drive. Part # 507305-001. I swapped that in and the problem remained it still wasn't registering the temp sensor.
I called HP and had them replace it again and again same problem.
Third call to HP I insisted they send me the drive bay for the 12 3.5 inch hotswap unit. This matched the working server that I owned. When I received it I carefully moved the power button assembly to my 8 bay unit and plugged it in. It was magic. When it rebooted ILO reported the following:
Generic 01/01/2002 00:02:14 FAN4_INLET Lower Critical-going low Assertion
Generic 01/01/2002 00:03:34 FAN4_INLET Lower Critical-going low Assertion
Fan noise returned to normal and when I checked ILO and IPMI data front panel was registering temp.
The part number for the 12 bay unit is 507254-001
The individual temp sensor didn't have any identifying marks on it and in all respects looked very similar. However there were some marked differences surrounding the temperature sensor chip. On the 8 bay unit it was covered in epoxy. On the 12 bay unit it was free and open.
My guess is this is a manufacturing defect.
I notified HP Engineering about the issue and provided them the same details as I am listing here.
I hope this helps someone out.
Good Luck.
Best Answer
Are you receiving an error, or are you just concerned that there's no fan present in slot #2?
The HP ProLiant DL360 G6 server uses three or four dual-fan block modules, depending on if the system is equipped with dual CPUs or a single CPU. (The extra fan module comes in the kit with the single processor option kit). Do you have a full fan block in the slot or a blank? On single-CPU models, there's a plastic blank in fan location #2 (empty in the photo below).
Since these are Linux and you have the HP agents installed, quickly post the output of the following commands:
hplog -v
# This will show the HP IML log and the alerts tied to the fan failures.hplog -t
# This will show the temperature zones.hplog -f
# This will show the fan ID and status.I'd like to see if these are consistent with what you're seeing from
hpasmcli
.Post the server firmware and CPU configuration if you can. You can get a concise summary of both with:
dmidecode -t 1 | egrep '(Manufacturer|Product|Serial)'; dmidecode -t processor| egrep '(Socket|Version)'
e.g.
All else, if your firmware version (Release Date) is older than the output I posted above, update the firmware for the server.