Operating System - HP-UX
1847022 Members
4049 Online
110258 Solutions
New Discussion

SCSI: Parity error -- lbolt: 9039249, dev: cb023000

 
David_711
Frequent Advisor

SCSI: Parity error -- lbolt: 9039249, dev: cb023000

Hi,
I have a rp7405 sever with hpux 11.11, dmp 3.5 and veritas net backup 6 mp3. I have 4 scsi tapes units; 2 ultrium 460, 1 sun dds4 and 1 sun DLT7000, every unit is conected to scsi card separately.
Frecuentely my backups sessions with netbackup are down and present the following messages:

SCSI: isrEscape Controller at 0/0/8/0/0/1/0.
Sep 5 13:56:38 hp00pb01 vmunix:
Sep 5 13:56:38 hp00pb01 vmunix: SCSI: Parity error -- lbolt: 9039249, dev: cb023000
Sep 5 13:56:38 hp00pb01 vmunix: lbp->state: 30008
Sep 5 13:56:38 hp00pb01 vmunix: lbp->offset: ffffffff
Sep 5 13:56:38 hp00pb01 vmunix: lbp->nominalOffset: 270
Sep 5 13:56:38 hp00pb01 vmunix: lbp->Cmdindex: 3
Sep 5 13:56:38 hp00pb01 vmunix: lbp->last_nexus_index: 1
Sep 5 13:56:38 hp00pb01 vmunix: lbp->nexus_index: 2
Sep 5 13:56:38 hp00pb01 vmunix: uCmdSent: 30058c0 uNexus_offset: 11205608
Sep 5 13:56:38 hp00pb01 vmunix: last lbp->puStatus [0000000049235600]:
Sep 5 13:56:38 hp00pb01 vmunix: ff031300 ff031300 00000000 00000000
Sep 5 13:56:38 hp00pb01 vmunix: next lbp->puStatus [00000000492357f0]:
Sep 5 13:56:38 hp00pb01 vmunix: 00031300 00031300 00031300 00031300
Sep 5 13:56:38 hp00pb01 vmunix: From most recent interrupt:
Sep 5 13:56:38 hp00pb01 vmunix: ISTAT: 0a, SIST0: 41, SIST1: 00, DSTAT: 80, DSPS: 00000000
Sep 5 13:56:38 hp00pb01 vmunix: lsp: 0x0000000057bbb800
Sep 5 13:56:38 hp00pb01 vmunix: bp->b_dev: cb023000
Sep 5 13:56:38 hp00pb01 vmunix: scb->io_id: 20f8e27
Sep 5 13:56:38 hp00pb01 vmunix: scb->cdb: 4d 00 6e 00 00 00 00 01 44 00
Sep 5 13:56:38 hp00pb01 vmunix: lbolt_at_timeout: 0, lbolt_at_start: 0
Sep 5 13:56:38 hp00pb01 vmunix: lsp->state: 4005
Sep 5 13:56:38 hp00pb01 vmunix: Jump Table entry [0000000049230300]: ff001300 c7fec288
Sep 5 13:56:38 hp00pb01 vmunix: lsp->puScript [0000000049231000]:
Sep 5 13:56:38 hp00pb01 vmunix: 09000028 f62b5100 00754001 09000100
Sep 5 13:56:38 hp00pb01 vmunix: 316dcac0 004dc002 0900001c f62b5200
Sep 5 13:56:38 hp00pb01 vmunix: DSAtbl->host_iocb_index: 3
Sep 5 13:56:38 hp00pb01 vmunix: DSAtbl->host_iocb_addr: 112058c0
Sep 5 13:56:38 hp00pb01 vmunix: stored scratcha: 0xff031300
Sep 5 13:56:38 hp00pb01 vmunix: scratch_lsp: 0x0000000057bbb800
Sep 5 13:56:38 hp00pb01 vmunix: c8xx_iocb [fffffff407fecb00]:
Sep 5 13:56:38 hp00pb01 vmunix: 030058c0 ff001300 11201000 9f033e80
Sep 5 13:56:38 hp00pb01 vmunix: 00000001 112058a0 0000000a 112058a8
Sep 5 13:56:38 hp00pb01 vmunix: Pre-DSP script dump [0000000049231000]:
Sep 5 13:56:38 hp00pb01 vmunix: 09000028 f62b5100 00754001 09000100
Sep 5 13:56:38 hp00pb01 vmunix: 316dcac0 004dc002 0900001c
Sep 5 13:56:38 hp00pb01 vmunix: Script dump [000000004923101c]:
Sep 5 13:56:38 hp00pb01 vmunix: f62b5200 00754001 78370000 00000000
Sep 5 13:56:38 hp00pb01 vmunix: 80080000 c7fec288 00000000 00000000
Sep 5 13:56:38 hp00pb01 vmunix: NCR chip register dump for: 0x400200a
Sep 5 13:56:38 hp00pb01 vmunix: 00: SCNTL3: 9f SCNTL2: 80 SCNTL1: 10 SCNTL0: da
Sep 5 13:56:38 hp00pb01 vmunix: 04: GPREG: 0a SDID: 03 SXFER: 3e SCID: 47
Sep 5 13:56:38 hp00pb01 vmunix: 08: SBCL: ae SSID: 83 SOCL: 0d SFBR: 00
Sep 5 13:56:38 hp00pb01 vmunix: 0c: SSTAT2: 01 SSTAT1: 0e SSTAT0: 01 DSTAT: 80
Sep 5 13:56:38 hp00pb01 vmunix: 10: DSA: c7fecb00
Sep 5 13:56:38 hp00pb01 vmunix: 14: MBOX1: 00 MBOX0: 00 ISTAT1: 00 ISTAT: 08
Sep 5 13:56:38 hp00pb01 vmunix: 1c: TEMP: 11201000
Sep 5 13:56:38 hp00pb01 vmunix: 24: DCMDDBC: 0d000000
Sep 5 13:56:38 hp00pb01 vmunix: 28: DNAD: f62b5220
Sep 5 13:56:38 hp00pb01 vmunix: 2c: DSP: 11201024
Sep 5 13:56:38 hp00pb01 vmunix: 30: DSPS: f62b5200
Sep 5 13:56:38 hp00pb01 vmunix: 34: SCRATCHA: ff031300
Sep 5 13:56:38 hp00pb01 vmunix: 38: DCNTL: a1 DWT: 00 DIEN: 7f DMODE: 4c
Sep 5 13:56:38 hp00pb01 vmunix: 3c: ADDER: 114b6224
Sep 5 13:56:38 hp00pb01 vmunix: 40: SIST1: 00 SIST0: 00 SIEN1: 97 SIEN0: 8f
Sep 5 13:56:38 hp00pb01 vmunix: 44: GPCNTL: 2f MACNTL: 00 SWIDE: 00 SLPAR: 00
Sep 5 13:56:38 hp00pb01 vmunix: 48: RESPID1: 00 RESPID0: 80 STIME1: 00 STIME0: fc
Sep 5 13:56:38 hp00pb01 vmunix: 4c: STEST3: 80 STEST2: 00 STEST1: 0c STEST0: 76
Sep 5 13:56:38 hp00pb01 vmunix: 50: RESV50: 00 RESV51: c0 SIDL1: 00 SIDL0: 00
Sep 5 13:56:38 hp00pb01 vmunix: 54: CCNTL1: 01 CCNTL0: 01 SODL1: 00 SODL0: 00
Sep 5 13:56:38 hp00pb01 vmunix: 58: RESV58: 00 RESV59: 00 SBDL1: 00 SBDL0: 00
Sep 5 13:56:38 hp00pb01 vmunix: 5c: SCRATCHB: 00030001
Sep 5 13:56:38 hp00pb01 vmunix: 60: SCRATCHC: c0ffffff
Sep 5 13:56:38 hp00pb01 vmunix: 64: SCRATCHD: 11201000
Sep 5 13:56:38 hp00pb01 vmunix: 68: SCRATCHE: c7fecc00
Sep 5 13:56:38 hp00pb01 vmunix: 6c: SCRATCHF: 11200300
Sep 5 13:56:38 hp00pb01 vmunix: 70: SCRATCHG: 9f033e80
Sep 5 13:56:38 hp00pb01 vmunix: 74: SCRATCHH: 11205608
Sep 5 13:56:38 hp00pb01 vmunix: 78: SCRATCHI: 09819f3e
Sep 5 13:56:38 hp00pb01 vmunix: 7c: SCRATCHJ: 030058c0
Sep 5 13:56:38 hp00pb01 vmunix: bc: SCNTL4: 80
Sep 5 13:56:38 hp00pb01 vmunix: PCI configuration register dump:
Sep 5 13:56:38 hp00pb01 vmunix: Command: 0157
Sep 5 13:56:38 hp00pb01 vmunix: Latency Timer: ff
Sep 5 13:56:38 hp00pb01 vmunix: Cache Line Size: 10
Sep 5 13:56:39 hp00pb01 vmunix:
Sep 5 13:56:39 hp00pb01 vmunix: SCSI: Resetting SCSI -- lbolt: 9039349, bus: 2 path: 0/0/8/0/0/1/0
Sep 5 13:56:39 hp00pb01 vmunix: SCSI: Reset detected -- lbolt: 9039349, bus: 2 path: 0/0/8/0/0/1/0
Sep 5 13:56:42 hp00pb01 VERITAS: A registered PBX service NB_18989_702354824 has shutdown.
Sep 5 13:56:42 hp00pb01 VERITAS: V-103-9 Removing server: NB_18989_702354824

This problem only happen with the ultrium tapes. I have check the scsi cables, change the scsi cables, i have used new terminator and change the tape ultrium and i do the firmware upgrade.

But, the problem is sometimes present again.
Somebody know about this class of problem and what could be the problem?
Please help!
Thanks
2 REPLIES 2
NMory
Respected Contributor

Re: SCSI: Parity error -- lbolt: 9039249, dev: cb023000

These errors can be due
to:

1. The IO timeout setting for the physical disk
being set too low
2. A problem with the SCSI connector for that
device
3. Not having the latest SCSI patches
installed

Sandman!
Honored Contributor

Re: SCSI: Parity error -- lbolt: 9039249, dev: cb023000

Well your error message clearly shows that it's a bad SCSI controller.

> SCSI: isrEscape Controller at 0/0/8/0/0/1/0

You can further verify by looking at the controller attached to "/dev/dsk/c2t3d0"

cheers!