I screwed up with firmware patch

[Kenneth Tipper]

I tried my first firmware patch according to the instructions in the HP-UX 11i installation guide (almost). I was running as root, and had the patch in /distrib/hpux instead of /tmp. When I ran swinstall, it reported that it had no permission to create a log but proceeded very quickly. After the automatic reboot, the old version numvber was still displayed, and I interrupted the boot to verify with the FV command. I shouldn't have done that. I issued BO PRI and it screwed up. Now the firmware works for diagnostics etc, but booting the OS fails with a system alert. Any way to fix a messed up firmware upgrade??? This is my only HP system (an A400).

[Michael Steele_2]

Please list the exact error and alert. Refer to the GSP error logs.

[Michael Steele_2]

Also, what firmware patch?

[Michael Steele_2]

Doesn't look like it. From PF_CHAW4219:

CAUTION: FROM THIS POINT FORWARD, THIS PROCESS CANNOT BE INTERRUPTED UNTIL COMPLETION. INTERRUPTING THIS PROCESS WILL CAUSE YOUR SYSTEM TO BE INOPERATIVE.

[A. Clay Stephenson]

I think the technical term for your situation is 'toast'; frankly, I surprised that it will even work for diagnostics. If you are extremely lucky -- and have a tape drive - you might be able to load a firmware tape --- but I doubt it. It's time to call HP Mr. Goodwrench and they will probably replace your systemboard which will have the effect of updating your firmware.

Firmware installation is one of those things where it is really, really important that you read and follow the installation instructions --- and not just treat them as suggestions.

I've done this many, many of these and I've only had one to fail -- on a DEC Alpha workstation --. It was a board replacement and, thankfully, under maintenance.

[Kenneth Tipper]

Model A400
Attempted firmware: 42.19
Existing firmware: 40.32
-----
GSP Error log entry:
----------------
SYSTEM NAME: uninitialized
DATE: 10/22/2003 TIME: 11:43:50
ALERT LEVEL: 2 = Non-Urgent operator attention required

SOURCE: 8 = I/O
SOURCE DETAIL: 2 = system bus adapter SOURCE ID: 2
PROBLEM DETAIL: 3 = function failure

CALLER ACTIVITY: 6 = machine check STATUS: 3
CALLER SUBACTIVITY: 34 = implementation dependent
REPORTING ENTITY TYPE: 0 = system firmware REPORTING ENTITY ID: 00

0x7000002382026343 00000000 00070200 type 14 = Problem Detail
0x5800082382026343 00006709 160B2B32 type 11 = Timestamp 10/22/2003 11:43:50
------------------------

Console log (from just before it goes wrong):
------------------------
HARD Booted.

ISL Revision A.00.38 OCT 26, 1994

ISL booting hpux srvrflash

Boot
: disk(0/0/1/1.15.0.0.0.0.0;0)srvrflash
21240 + 8576 + 2098904 start 0x1e00240

************* SYSTEM ALERT **************
SYSTEM NAME: uninitialized
DATE: 10/21/2003 TIME: 19:30:46
ALERT LEVEL: 7 = reserved

REASON FOR ALERT
SOURCE: 0 = unknown, no source stated
SOURCE DETAIL: 0 = unknown, no source stated SOURCE ID: FF
PROBLEM DETAIL: 0 = no problem detail

LEDs: RUN ATTENTION FAULT REMOTE POWER
FLASH FLASH FLASH OFF ON
LED State: Unexpected Reboot. Running non-OS code. Non-critical error detected.
Check Chassis and Console Logs for error messages.

0x0000007000FF6292 00000000 00000000 - type 0 = Data Field Unused
0x5800087000FF6292 00006709 15131E2E - type 11 = Timestamp 10/21/2003 19:30:46
A: ack read of this entry - X: Disable all future alert messages
Anything else skip redisplay the log entry
->Choice:a

[Thayanidhi · Accepted solution]

Hi,

what you tried is OS installable firmware
patch. Which means, you install the firmware
path from OS. When system reboots it boots
with "srvrflash" which actually flashes the
firmware. If it is not happening, I see only
one work around. Interrupt the auto boot.
From BDC give bo pri and interact with ISL
"y". From ISL you boot your old kernel
instead of flash utility.

ISL>hpux (;0)/stand/vmunix

Before doing that you can also modify
autofile. use "lsautofl" to list the content.

After booting use mkboot -a to set auto file
string. Now check your firmware is correct
and indented for this system ...etc. also I suggest to redownload and follow the correct
procedure.( check the chsum - output and
compare with document).

TT