Storage Boards Cleanup
To make it easier to find information about HPE Storage products and solutions, we are doing spring cleaning. This includes consolidation of some older boards, and a simpler structure that more accurately reflects how people use HPE Storage.
Disk Arrays
cancel
Showing results for 
Search instead for 
Did you mean: 

Decoding SCSI lbolts from AutoRAID 12H

Mark Jones_1
Advisor

Decoding SCSI lbolts from AutoRAID 12H

I am getting SCSI lbolts in syslog reported thus:

vmunix: SCSI: First party detected bus hang -- lbolt: 6745401, bus: 0
vmunix: lbp->state: 3060
vmunix: lbp->offset: 40
vmunix: lbp->uPhysScript: f87be000
vmunix: From most recent interrupt:
vmunix: ISTAT: 29, SIST0: 00, SIST1: 00, DSTAT: 84, DSPS: 0000000a
vmunix: lsp: 0000000000000000
vmunix: lbp->owner: 000000004190a900
vmunix: bp->b_dev: cb001002
vmunix: scb->io_id: f8
vmunix: scb->cdb: 12 00 00 00 80 00
vmunix: lbolt_at_timeout: 6745301, lbolt_at_start: 6744801
vmunix: lsp->state: 5
vmunix: scratch_lsp: 000000004190a900
vmunix: Pre-DSP script dump [fffffffff87be020]:
vmunix: 00000000 00000000 41010000 f87be290
vmunix: 980dff00 0000000a 78351000 00000000
vmunix: Script dump [fffffffff87be040]:
vmunix: 0e000005 f87be540 e0100004 f87be7f8
vmunix: 870b0000 f87be2d8 98080000 00000005
vmunix: SCSI: Resetting SCSI -- lbolt: 6745501, bus: 0
vmunix: SCSI: Reset detected -- lbolt: 6745501, bus: 0
vmunix: SCSI: First party detected bus hang -- lbolt: 6746601, bus: 0
vmunix: lbp->state: 1060
vmunix: lbp->offset: f8
vmunix: lbp->uPhysScript: f87be000
vmunix: From most recent interrupt:
vmunix: ISTAT: 02, SIST0: 02, SIST1: 00, DSTAT: 80, DSPS: 00000000
vmunix: lsp: 0000000000000000
vmunix: lbp->owner: 000000004190a900
vmunix: bp->b_dev: cb001002
vmunix: scb->io_id: f8
vmunix: scb->cdb: 12 00 00 00 80 00
vmunix: lbolt_at_timeout: 6746501, lbolt_at_start: 6746001
vmunix: lsp->state: 5
vmunix: scratch_lsp: 000000004190a900
vmunix: Pre-DSP script dump [fffffffff87be020]:
vmunix: 00000000 00000000 41010000 f87be290
vmunix: 78342000 0000000a 78351000 00000000
vmunix: Script dump [fffffffff87be040]:
vmunix: 0e000005 f87be540 e0100004 f87be7f8
vmunix: 870b0000 f87be2d8 98080000 00000005



Plus other very similar messages.
How do I work out which disk is at fault?

Thanks in advance,
Mark
2 REPLIES
Mark Jones_1
Advisor

Re: Decoding SCSI lbolts from AutoRAID 12H

More information:

Now I've thought about this a bit more, I'm not even sure it's the 12H at fault.

I suppose the same question still applies though, I would expect the lbolt error to tell me some device information, and I can't spot it (I could be going blind of course!)

Thanks again
Mark
Mohanasundaram_1
Honored Contributor

Re: Decoding SCSI lbolts from AutoRAID 12H

Hi Mark,

vmunix: bp->b_dev: cb001002

is the device having the problem. This is c0t1d0 device.

cb ---> is the hex value of the device major number. 203 is the major number of the device giving this error.

001002 ---> c0t1d0 is the device file for that major number.

to confirm which device major classification 203 belongs to,

# lsdev | grep 203

With regards,
Mohan.
Attitude, Not aptitude, determines your altitude