General
cancel
Showing results for 
Search instead for 
Did you mean: 

need help to identify device causing lbolt errors

Dave Chamberlin
Trusted Contributor

need help to identify device causing lbolt errors

I am getting this lbolt error in the system logs. I can't find a disk missing - is this a controller issue? How do get identify the actual device with the problem? Thanks

Jul 13 08:56:23 mars vmunix: SCSI: Resetting SCSI -- lbolt: 25628054, bus: 0 Jul 13 08:56:23 mars vmunix: SCSI: Reset detected -- lbolt: 25628054, bus: 0 Jul 13 08:56:34 mars vmunix: SCSI: First party detected bus hang -- lbolt: 25629154, bus: 0
Jul 13 08:56:34 mars vmunix: lbp->state: 5060
Jul 13 08:56:34 mars vmunix: lbp->offset: f8
Jul 13 08:56:34 mars vmunix: lbp->uPhysScript: 81fbc000
Jul 13 08:56:34 mars vmunix: From most recent interrupt:
Jul 13 08:56:34 mars vmunix: ISTAT: 02, SIST0: 02, SIST1: 10, DSTAT: 80, DSPS: 00000000
Jul 13 08:56:34 mars vmunix: lsp: 0000000000000000
Jul 13 08:56:34 mars vmunix: lbp->owner: 000000004f3cdd00
Jul 13 08:56:34 mars vmunix: bp->b_dev: cb001002
Jul 13 08:56:34 mars vmunix: scb->io_id: 65
Jul 13 08:56:34 mars vmunix: scb->cdb: 12 00 00 00 80 00
Jul 13 08:56:34 mars vmunix: lbolt_at_timeout: 25629054, lbolt_at_start: 25628554
Jul 13 08:56:34 mars vmunix: lsp->state: 5
Jul 13 08:56:34 mars vmunix: scratch_lsp: 000000004f3cdd00
Jul 13 08:56:34 mars vmunix: Pre-DSP script dump [ffffffff81fbc020]:
Jul 13 08:56:34 mars vmunix: 00000000 00000000 41010000 81fbc290
Jul 13 08:56:34 mars vmunix: 78342000 0000000a 78351000 00000000
Jul 13 08:56:34 mars vmunix: Script dump [ffffffff81fbc040]:
Jul 13 08:56:34 mars vmunix: 0e000005 81fbc540 e0100004 81fbc7f8
Jul 13 08:56:34 mars vmunix: 870b0000 81fbc2d8 98080000 00000005
7 REPLIES
Sharma Sanjeev
Respected Contributor

Re: need help to identify device causing lbolt errors

Hi Dave

Please have a look on c98t8d0

Regards
Sanjeev
Everything is Possible as " IMPOSSIBLE" word itself says I M POSSIBLE
Patrick Wallek
Honored Contributor

Re: need help to identify device causing lbolt errors

>>c98t8d0????

That is highly doubtful!!!

The device is:

Jul 13 08:56:34 mars vmunix: bp->b_dev: cb001002


0xcb = 203 --> ctl [from 'lsdev']
0x00 = 0 --> bus number
0x1 = 1 --> target
0x0 = 0 --> lun
0x02 --> flags

So this is: c0t1d0
Sharma Sanjeev
Respected Contributor

Re: need help to identify device causing lbolt errors

Hi Patrick Wallek


Yes, you are 100% correct, sorry for understanding it wrong :-)

Regards
Sanjeev
Everything is Possible as " IMPOSSIBLE" word itself says I M POSSIBLE
Ganesan R
Honored Contributor

Re: need help to identify device causing lbolt errors

Hi Dave,

It looks scsi reset initiated by the controller itself. You could also check the device c0t1d0.

Normally you should find the device file like this..

b_dev: cb001002 --> middle 3 digits represents the device file. In this case 010 which is c0t1d0

Involve HP to analyse and replace the part.
Best wishes,

Ganesh.
Mel Burslan
Honored Contributor

Re: need help to identify device causing lbolt errors

If you have an automatic tape exchanger of some sort, usually found in a tape library of any kind, that would be the culprit to your woes I think.
________________________________
UNIX because I majored in cryptology...
Shiv007
Frequent Advisor

Re: need help to identify device causing lbolt errors

Hi,

Try running the disk information tool from cstm on the disks.

cstm/mstm/xstm.

or try diskinfo

Thanks
Shiv
Taifur
Respected Contributor

Re: need help to identify device causing lbolt errors

Hi,

So, far it tape library related issue. If your tape drive attached with SCSI cable, then reseating SCSI cable & terminator and check that issue.

Rgds//
Taifur