I recently encountered a problem while upgrading the iLO2 firmware on a HP DL360G5 server. It seems if you reopen the remote console window while remotely updating the iLO2 firmware you can corrupt the firmware upgrade process. Hmm. This caught me out. When I rebooted my server it sat there not beeping or doing anything for a couple of minutes. I thought I had toasted it. I started attempting ROM recovery process\u00a0(flipping dip switches on the motherboard btw) but this didn’t help. Removing the RAM caused the server to beep so it was obviously not totally dead.\u00a0During one of my “boot- nothing-google-retry” cycles I left the server running. After about 10 minutes the server beeped and continued booting up – BUT the POST results showed no iLO2. So I figured it was a iLO firmware problem (which until then I had thought it was a ROM problem) which changed my google terms. I eventually found HP document c01850906.<\/p>\n
The document outlines a process for recovering from a corrupt iLO2 firmware update.<\/p>\n
The document describes it better but the steps are pretty much the following:<\/p>\n
Boot off maintenance CD (have patience, the boot might take 10 or so minutes)<\/p>\n
run firmware update
\nctl-alt dbx<\/p>\n
alt-ctrl-1\u00a0 enter
\ncd \/mnt\/bootdevice\/compaq\/swpackages
\nrmmod hpilo
\nrmmon ilo
\nsh CP012108.scexe –direct<\/p>\n
Message about firmware 1.81 and programming flash<\/p>\n
reboot<\/p>\n
The full process is at:<\/p>\n