Re: 43P-260 firmware errors - boot fails
From: Dan Foster (dsf_at_globalcrossing.net)
Date: 05/13/03
- Next message: Markus Baertschi: "Re: Clone a disk to tape"
- Previous message: scriptOmatic: "Re: Automated memory monitoring"
- In reply to: Richard Brittain: "43P-260 firmware errors - boot fails"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Tue, 13 May 2003 18:16:41 +0000 (UTC)
In article <b9r58o$1u5$1@merrimack.Dartmouth.EDU>, Richard Brittain <richard@polaris.dartmouth.edu> wrote:
> We have a 43P-260 that crashed during power brownouts and now doesn't get
> very far at all in the boot process. It pauses for a long time at
> checkpoint E298 or E297 on the LEDs, then stops with code 40A00000.
> The service manuals list this as a firmware IPL failure. I've tried
No idea if same thing but we once had a 260 that wouldn't come back up
after a normal shutdown+reboot... we eventually (with IBM's assistance)
traced this to a firmware bug - I don't recall details other than the
firmware bug had corrupted the NVRAM but it's fixed in newer firmware.
IBM had to clear the NVRAM then do a firmware upgrade to get it to boot
correctly.
This was our fault for not having kept it up to date on firmware revs.
Since then, we've been real good about that ;) We usually try to upgrade
microcode on each system about once a year, usually coinciding with some
other scheduled maintenance (eg patching).
-Dan
- Next message: Markus Baertschi: "Re: Clone a disk to tape"
- Previous message: scriptOmatic: "Re: Automated memory monitoring"
- In reply to: Richard Brittain: "43P-260 firmware errors - boot fails"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
