HP 9000
cancel
Showing results for 
Search instead for 
Did you mean: 

Rp 3410 Not booting - IPL error: bad IPL checksum.

Nedved
Frequent Advisor

Rp 3410 Not booting - IPL error: bad IPL checksum.

Dear all ,

Today i booted my rp3410 hp-ux11.11 server. But it's shows the error

" IPL error: bad IPL checksum. "

I tried to boot from both from pri, and alt but same error.

So i booted from the CD then i went to recovery console to install the boot lif files.

But when while installing the boot lif i got the following mesage.


DIAGNOSTIC SYSTEM WARNING:
The diagnostic logging facility has started receiving excessive
errors from the I/O subsystem. I/O error entries will be lost
until the cause of the excessive I/O logging is corrected.
If the diaglogd daemon is not active, use the Daemon Startup command
in stm to start it.
If the diaglogd daemon is active, use the logtool utility in stm
to determine which I/O subsystem is logging excessive errors.

I tried to boot from both make_tape-recovery but only i got IPl Check sum error.
Can some one tell me how to solve this.

Thanks.
7 REPLIES
Nedved
Frequent Advisor

Re: Rp 3410 Not booting - IPL error: bad IPL checksum.

and write now my system is not booting so i could not run the STM utility to check which IO system causing problems.
Lijeesh N G_1
Respected Contributor

Re: Rp 3410 Not booting - IPL error: bad IPL checksum.

Hi,

Check the the available boot devices with sea command. Boot with alternate boot disk if you have mirrored disk.

Regards,
LIJEESH N G
Nedved
Frequent Advisor

Re: Rp 3410 Not booting - IPL error: bad IPL checksum.

Hi Lijeesh N G,

I tried to boot from both disks but same error. From the ignite backup also i tried to boot but same error.

if i gave sea ipl it's showing both disks as well as tape drive.
Nedved
Frequent Advisor

Re: Rp 3410 Not booting - IPL error: bad IPL checksum.

When i again try to boot from the cd i got this following error.

HARD Booted.

ISL Revision A.00.43 Apr 12, 2000

ISL booting hpux (;0):INSTALL

Boot
: disk(0/0/2/0.0.0.0.0.0.0;0):WINSTALL
12005376 + 2187352 + 2631504 start 0x201568




alloc_pdc_pages: Relocating PDC from 0xfffffff0f0c00000 to 0x3f900000.



Firmware Version 45.44

Duplex Console IO Dependent Code (IODC) revision 1



Stored message buffer up to panic:
IEN1: 97 SIEN0: 8f
44: GPCNTL: 2f MACNTL: 00 SWIDE: 00 SLPAR: 00
48: RESPID1: 00 RESPID0: 80 STIME1: 00 STIME0: fc
4c: STEST3: 80 STEST2: 00 STEST1: 0c STEST0: 06
50: RESV50: 00 RESV51: c0 SIDL1: 00 SIDL0: 1f
54: CCNTL1: 01 CCNTL0: 01 SODL1: 00 SODL0: 00
58: RESV58: 00 RESV59: 00 SBDL1: cf SBDL0: 0a
5c: SCRATCHB: 00030001
60: SCRATCHC: c0ffffff
64: SCRATCHD: 00061000
68: SCRATCHE: 90010c00
6c: SCRATCHF: 00060000
70: SCRATCHG: 0c01031f
74: SCRATCHH: 00065600
78: SCRATCHI: 0c05bf1f
7c: SCRATCHJ: 01005840
bc: SCNTL4: 00
PCI configuration register dump:
Command: 0157
Latency Timer: c0
Cache Line Size: 20

SCSI: Resetting SCSI -- lbolt: 30304, bus: 3 path: 0/1/1/1

SCSI: Reset detected -- lbolt: 30304, bus: 3 path: 0/1/1/1
SCSI: isrEscape Controller at 0/1/1/1.

SCSI: First party detected bus hang (HTH) -- lbolt: 31780, dev: cb033002
lbp->state: 30008
lbp->offset: ffffffff
lbp->nominalOffset: 450
lbp->Cmdindex: 1
lbp->last_nexus_index: 2
lbp->nexus_index: 0
uCmdSent: 1005840 uNexus_offset: 0
last lbp->puStatus [0000000041625600]:
00000000 00000000 00000000 00000000
next lbp->puStatus [00000000416257f0]:
00000000 00000000 00000000 00000000
From most recent interrupt:
ISTAT: 0a, SIST0: 40, SIST1: 01, DSTAT: 80, DSPS: 00000000
lsp: 0x0000000044f0e220
bp->b_dev: cb033002
scb->io_id: 3000006
scb->cdb: 12 00 00 00 24 00
lbolt_at_timeout: 33609, lbolt_at_start: 30609
lsp->state: 4205
Jump Table entry [0000000041620300]: 00001300 90010288
lsp->puScript [0000000041621000]:
09000010 39227980 0045c000 09000014
39227900 0045c000 78370000 00000000
DSAtbl->host_iocb_index: 1
DSAtbl->host_iocb_addr: 65840
stored scratcha: 0xff031300
scratch_lsp: 0x0000000044f0e220
c8xx_iocb [ffffffff90010b00]:
01005840 ff007300 00061000 b7031f00
00000005 00065820 00000006 00065828
Pre-DSP script dump [0000000041621000]: 09000010
Script dump [0000000041621004]:
39227980 0045c000 09000014 39227900
0045c000 78370000 00000000 80080000
NCR chip register dump for: 0x400200a
00: SCNTL3: b7 SCNTL2: 80 SCNTL1: 10 SCNTL0: da
04: GPREG: 0e SDID: 03 SXFER: 1f SCID: 47
08: SBCL: 21 SSID: 00 SOCL: 01 SFBR: 04
0c: SSTAT2: 08 SSTAT1: 01 SSTAT0: 01 DSTAT: 80
10: DSA: 90010b00
14: MBOX1: 00 MBOX0: 00 ISTAT1: 00 ISTAT: 08
1c: TEMP: 00061000
24: DCMDDBC: 0900000a
28: DNAD: 39227988
2c: DSP: 0006100c
30: DSPS: 39227980
34: SCRATCHA: ff031300
38: DCNTL: a1 DWT: 00 DIEN: 7f DMODE: 4c
3c: ADDER: 0028898c
40: SIST1: 00 SIST0: 00 SIEN1: 97 SIEN0: 8f
44: GPCNTL: 2f MACNTL: 00 SWIDE: 00 SLPAR: 00
48: RESPID1: 00 RESPID0: 80 STIME1: 00 STIME0: fc
4c: STEST3: 80 STEST2: 00 STEST1: 0c STEST0: 06
50: RESV50: 00 RESV51: c0 SIDL1: 00 SIDL0: 1f
54: CCNTL1: 01 CCNTL0: 01 SODL1: 00 SODL0: 00
58: RESV58: 00 RESV59: 00 SBDL1: cf SBDL0: 0a
5c: SCRATCHB: 00030001
60: SCRATCHC: c0ffffff
64: SCRATCHD: 00061000
68: SCRATCHE: 90010c00
6c: SCRATCHF: 00060000
70: SCRATCHG: 0c01031f
74: SCRATCHH: 00065600
78: SCRATCHI: 0c05b71f
7c: SCRATCHJ: 01005840
bc: SCNTL4: 00
PCI configuration register dump:
Command: 0157
Latency Timer: c0
Cache Line Size: 20

SCSI: Resetting SCSI -- lbolt: 31880, bus: 3 path: 0/1/1/1

SCSI: Reset detected -- lbolt: 31880, bus: 3 path: 0/1/1/1
I/O hardware probe timed out at path 0/1/1/1.

System Panic:

linkstamp: Wed Aug 17 15:28:53 MDT 2005
_release_version: @(#) $Revision: vmunix: vw: -proj selectors: CUPI80_BL2000_1108 -c 'Vw for CUPI80_BL2000_1108 build' -- cupi80_bl2000_1108 'CUPI80_BL2000_1108' Wed Nov 8 19:24:56 PST 2000 $
panic: I/O system hang

PC-Offset Stack Trace (read across, top of stack is 1st):
0x00212630 0x0039e958 0x00a02364
0x0003fc40 0x00267358 0x0016703c
0x004205f0 0x00178ad8 0x00176b24
End Of Stack



*** A system crash has occurred. (See the above messages for details.)
*** The system is now preparing to dump physical memory to disk, for use
*** in debugging the crash.

ERROR: Your system crashed before I/O and dump configuration was complete.
A crash dump cannot be taken under these circumstances without
special configuration. Contact your HP support representative.

Ganesan R
Honored Contributor

Re: Rp 3410 Not booting - IPL error: bad IPL checksum.

Hi Nedved,

You have some hardware issue. Check the device at hardware path 0/1/1/1 which generates scsi resets. Suspected device is c3t3d0.

I recommend you to log a case with HP to fix the hardware issue.
Best wishes,

Ganesh.
Andrew Rutter
Honored Contributor

Re: Rp 3410 Not booting - IPL error: bad IPL checksum.

hi,

sounds like the disk is bad - has died

the disk will need to be replaced and then try your restore again

Andy
SoorajCleris
HPE Pro

Re: Rp 3410 Not booting - IPL error: bad IPL checksum.

Hi,

As your all devices giving same error, it may be some other problem also?

is you all devices with ipl connected to the same scsi card?
"UNIX is basically a simple operating system, but you have to be a genius to understand the simplicity" - Dennis Ritchie