Firmware update interupted on HP DL380 G6 .. uh oh!

[LinuxGuy13]

Hey Everyone!

Today, we ran into a problem while upgrading the flash rom on one of our HP DL380 G6 machines.  The upgrade was done using the online linux ROM upgrade procedure, and it was performed over an SSH connection.  Unfortunately, the ssh connection was lost during the upgrade or the server crash / rebooted (we don’t know for sure, all we really know is that the SSH connection was terminated by something).  Okay, we know we shouldn't have been doing this over SSH, and next time we wont!  However, after this happened, the machine became unresponsive (no response to ping, ssh, etc.).  We powered cycled the machine via the ilO 2 interface, and even physically removed the power cables and put them back in, but the system refuses to boot up at all.   We are looking at the monitor display via the HP iLO2 remote cones,  and all we get is a grey screen.

We believe that this is due to the flash rom upgrade being interrupted.  We would like to recover the system from the backup rom.  According to the “HP Online ROM Flash User Guide” at this link, http://h20000.www2.hp.com/bc/docs/support/SupportManual/c00487453/c00487453.pdf, we should be able to the following:

 “If RBSU is inaccessible, switching ROM images can also be done by changing the switch settings on the system configuration switch. Refer to your server documentation for more information.”

However, we cannot find any documentation about what to set on the “system configuration switch” to switch to the backup rom.   According to page 85 of “HP ProLiant DL380 G6 Server Maintenance and Service Guide”, the “System maintenance switch” consists of 10 dip switches (S1 to S10).  However, the manual does not say which one (if any) of these would be used to access the redundant ROM.

If anyone could point me in the right direction of correct procedure to switch to the backup ROM image for a HP DL380 G6 machine, or suggest any other recovery path we might take that would be greatly appreciated.

Thanks alot!

Thank you very much,

[Torsten.]

From troubleshooting guide:

If the system ROM is corrupted, the system automatically switches to the redundant ROM in most cases. If the
system does not automatically switch to the redundant ROM, perform the following steps:
1.  Power down the server.
2.  Remove the server from the rack, if necessary.

3.  Remove the access panel.
4.  Change positions 1, 5, and 6 of the system maintenance switch to on.
5.  Install the access panel.
6.  Install the server into the rack.
7.  Power up the server.
8.  After the system beeps, repeat steps 1 through 3.
9.  Change positions 1, 5, and 6 of system maintenance switch to off.
10.  Repeat steps 5 and 6.
If both the current and backup versions of the ROM are corrupt, return the system board for a service
replacement.