I/O Error

[Kwang-cheong , Seo]

HI!
what is it mean?
Jun 26 22:02:22 haksa vmunix: SCSI: Unhandled interrupt -- lbolt: 35117, dev: cb
010000
Jun 26 22:02:22 haksa vmunix: lbp->state: a0
Jun 26 22:02:22 haksa vmunix: lbp->offset: ffffffff
Jun 26 22:02:22 haksa vmunix: lbp->uPhysScript: 480000
Jun 26 22:02:22 haksa vmunix: From most recent interrupt:
Jun 26 22:02:22 haksa vmunix: ISTAT: 0a, SIST0: 81, SIST1: 00, DSTAT:
80, DSPS: 00680b80
Jun 26 22:02:22 haksa vmunix: NCR chip register access history (most recent la
st): 183 accesses
Jun 26 22:02:22 haksa vmunix: 1, DCMDDBC: 0f000001
Jun 26 22:02:22 haksa vmunix: 1, SBCL: a2
Jun 26 22:02:22 haksa vmunix: 1, DFIFO: 01
Jun 26 22:02:22 haksa vmunix: 1, SSTAT1: 00
Jun 26 22:02:22 haksa vmunix: 1, SSTAT2: 02
Jun 26 22:02:22 haksa vmunix: 3, DSP<-00480058
Jun 26 22:02:22 haksa vmunix: 18, ISTAT: 09
Jun 26 22:02:22 haksa vmunix: 2, DSTAT: 84
Jun 26 22:02:22 haksa vmunix: 2, DSPS: 00000001
Jun 26 22:02:22 haksa vmunix: 1, SCRATCH: ff001000
Jun 26 22:02:22 haksa vmunix: 2, DSP<-00480080
Jun 26 22:02:22 haksa vmunix: 3413, ISTAT: 0a
Jun 26 22:02:22 haksa vmunix: 2, SSTAT0: 81
Jun 26 22:02:22 haksa vmunix: 04: SOCL: 01 SODL: 00 SXFER:
08 SCID: 80
Jun 26 22:02:22 haksa vmunix: 08: SBCL: a3 SBDL: 00 SIDL:
08 SFBR: 00
Jun 26 22:02:22 haksa vmunix: 0c: SSTAT2: 03 SSTAT1: 01 SSTAT0:
00 DSTAT: 80
Jun 26 22:02:22 haksa vmunix: 10: DSA: 00000000
Jun 26 22:02:22 haksa vmunix: 14: CTEST3: 02 CTEST2: 21 CTEST1:
f0 CTEST0: 51
Jun 26 22:02:22 haksa vmunix: 18: CTEST7: 00 CTEST6: 3c CTEST5:
00 CTEST4: 00
Jun 26 22:02:22 haksa vmunix: 1c: TEMP: 00400000
Jun 26 22:02:22 haksa vmunix: 20: LCRC: 53 CTEST8: 20 ISTAT:
0a DFIFO: 55
Jun 26 22:02:22 haksa vmunix: 24: DCMDDBC: 09000055
Jun 26 22:02:22 haksa vmunix: 28: DNAD: 00680bab
Jun 26 22:02:22 haksa vmunix: 2c: DSP: 00500008
Jun 26 22:02:22 haksa vmunix: 30: DSPS: 00680b80
Jun 26 22:02:22 haksa vmunix: 34: SCRATCH: ff001000
Jun 26 22:02:22 haksa vmunix: 38: DCNTL: 01 DWT: 00 DIEN:
7f DMODE: c0
Jun 26 22:02:22 haksa vmunix: 3c: ADDER: 00b80b88
Jun 26 22:02:22 haksa vmunix:
Jun 26 22:04:22 haksa vmunix: NCR chip register access history (most recent la
st): 130 accesses
Jun 26 22:04:22 haksa vmunix: 1, SBCL: a2
Jun 26 22:04:22 haksa vmunix: 1, DFIFO: 01
Jun 26 22:04:22 haksa vmunix: 1, SSTAT1: 00
Jun 26 22:04:22 haksa vmunix: 1, SSTAT2: 02
Jun 26 22:04:22 haksa vmunix: 9, DSP<-00480058
Jun 26 22:04:22 haksa vmunix: 19, ISTAT: 09
Jun 26 22:04:22 haksa vmunix: 3, DSTAT: 84
Jun 26 22:04:22 haksa vmunix: 2, DSPS: 00000001
Jun 26 22:04:22 haksa vmunix: 1, SCRATCH: ff001020
Jun 26 22:04:22 haksa vmunix: 4, DSP<-00480080
Jun 26 22:04:22 haksa vmunix: 17, ISTAT<-20
Jun 26 22:04:22 haksa vmunix: 3387, ISTAT: 2a
Jun 26 22:04:22 haksa vmunix: 2, SSTAT0: 01
Jun 26 22:04:22 haksa vmunix: 3, DSTAT: 80
Jun 26 22:04:22 haksa vmunix: 1, DSPS: 07f80f00
Jun 26 22:04:22 haksa vmunix: 2, SCRATCH: ff001020
Jun 26 22:04:22 haksa vmunix: lsp: 2759000
Jun 26 22:04:22 haksa vmunix: bp->b_dev: cb011000
Jun 26 22:04:22 haksa vmunix: scb->io_id: 10000e0
Jun 26 22:04:22 haksa vmunix: scb->cdb: 12 00 00 00 80 00

I'm serious...
Please... I wait your answer

Thank you.

[Stefan Farrelly · Accepted solution]

Youve had a hardware/SCSI error to some remote disk or tape device. Its nothing too serious - unless youre getting more of them logged all the time ?

Anyway, its very difficult from your output to find the device which probably caused it. The best tool to use is LOGTOOL which you run from xstm (OnlineDiag diagnostic software - which you should have installed). Run xstm then go to tool -> utility -> logtool and from logtool display the formatted log or raw log and this will show all errors and which devices logged them which should uncover your troublesome device. Diagnosing hardware problems like this is a specialist task, you should probably get HP to dialin to view the logs (if possible) or save the raw log from logtool above and email it to HP (response centre) to get an expert to analyse for you.

[Ceesjan van Hattum]

Hi, you might have a look at the latest patches for your OS.
Secondly, read http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0xbfdffef4d250d611abdb0090277a778c,00.html
of Stephen, who had a similar problem, i think..

Regards,
Ceesjan

[barrett cooper]

I agree about it being a timeout on a disk. Looking at dev=cb010000 it looks like the disk at /dev/dsk/c1t0d0 caused the lbolt. I would try the following:
1: Do a diskinfo on the disk to make sure it is reporting size and firmware revision correctly.
2: Change the timeout on the disk to 180 using pvchange -t 180
3: Verify termination on the path.
4: If the problem doesn't change check the disk and controller for bus 1 (c1) for errors in logtool through the utilities in mstm. If there are many you may have a failing disk or controller and will want to call for service.

[Sanjay_6]

Hi,

Looks like a scsi disk problem,

dev cb010000 --> c1t0d0

Hope this helps.

Regds

[Kwang-cheong , Seo]

Thanks your answer.
This problem is Terminator.

Thank you.