topic Query: My ProLiant DL180 Gen9 server powers on but doesn't display an image and doesn't - Prolaint server - DL180 Gen9 in ProLiant Servers (ML,DL,SL)

My ProLiant DL180 Gen9 server powers on but doesn't display an image and doesn't

emmanuel1 — Fri, 02 Feb 2024 07:16:02 GMT

Mi servidor ProLiant DL180 Gen9 se enciende, pero no aparece ninguna pantalla. Intenté acceder a iLO y en el campo Estado del sistema aparece "Crítico". Cuando busco más información, indica que BIOS/Hardware Health está en "Error". Al ingresar, muestra un mensaje: "(Nota de mantenimiento. iLO realizó una operación de RESTAURACIÓN automática)". ¿Qué debo hacer en este caso? ¿Qué pasos debo seguir o qué componente debo reemplazar para restaurar la funcionalidad normal?

Desde iLO, ¿podría realizar algún procedimiento para ayudar a resolver este problema?

Google Translated:

My ProLiant DL180 Gen9 server turns on, but no screen appears. I tried to access iLO and the System Status field shows "Critical". When I look for more information, it says BIOS/Hardware Health is in "Error". Upon entering, it displays a message: "(Maintenance note. iLO performed an automatic RESTORE operation)". What should I do in this case? What steps should I take or what component should I replace to restore normal functionality?

From iLO, could you perform any procedures to help resolve this issue?

Query: My ProLiant DL180 Gen9 server powers on but doesn't display an image and doesn't - Prolaint server - DL180 Gen9

support_s — Thu, 25 Jan 2024 17:04:41 GMT

System recommended content:

1. HPE ProLiant DL180 Gen9 Server-Server restarting with Bug check STOP: 0x00000133

2. HPE Integrated Lights-Out 4 (iLO 4) - UI Displays "Agentless Management service not available" Message on Software UI Page After VMWare ESXi Upgrade

Please click on "Thumbs Up/Kudo" icon to give a "Kudo".

Thank you for being a HPE valuable community member.

Re: Query: My ProLiant DL180 Gen9 server powers on but doesn't display an image and doesn'

emmanuel1 — Thu, 25 Jan 2024 22:45:18 GMT

Reviewing the links you shared with me, I would like to ask:

Where can I perform?

Check for HPS report and found memory dump file is generated.

And additionally, how can I analyze the dump file with the debugging tool?

NOMBRE_SÍMBOLO: hpqilo3chif+1d58

NOMBRE_MÓDULO: hpqilo3chif

NOMBRE_IMAGEN: hpqilo3chif.sys

Re: Query: My ProLiant DL180 Gen9 server powers on but doesn't display an image and doesn'

BPSingh — Tue, 30 Jan 2024 05:37:37 GMT

Greetings!

Please check for LED status on the server.

https://support.hpe.com/hpesc/public/docDisplay?docId=c05060599&docLocale=en_US

From the iLO page, please try booting from the redundant ROM and check. Refer below link to set redundant ROM from iLO page.

https://support.hpe.com/hpesc/public/docDisplay?docId=sd00001038en_us&docLocale=en_US&page=GUID-D7147C7F-2016-0901-06D0-000000001B4B.html

If the problem persists, conduct an AC power cycle and verify. Disconnect the power cable from the server, press the power button for 30 seconds, reconnect the power, and then check.

Also you may try clearing the NVRAM using S6 on the system board.

Page#104 https://support.hpe.com/hpesc/public/docDisplay?docId=c04422850&docLocale=en_US

 1. Clearing the NVRAM
 1.1 Please power down the server
 1.2 Please disconnect the power cable.
 1.3 Please press the power button for 10 seconds to power drain the server.
 1.4 Please open the access panel of the server.
 1.5 Please check the access panel for the system diagram.
 1.6 Please look for system maintenance switch.
 1.7 Please look for switch no. 6.
 1.8 Please set the switch on "ON" state.
 1.9 Please start the server
 1.10 Please wait for the message " system maintenance switch is On"
 1.11 Please power down the server.
 1.12 Please set the switch back to OFF state.
 1.13 Please restart the server and check if the server is powering on.

If the issue persists, proceed to test the server in a minimal hardware configuration, with a single DIMM, a single processor, and without any additional add-on cards or risers installed. This step aims to further isolate and identify the underlying issue.