Getting lbolt errors. Which device is this?

[Ray Humpage]

I had a disk go bad. I removed it from the LV mirror. Still getting these messsages. Trying to determine if I have another disk failing.

Apr 15 12:52:39 nmhptprd vmunix: SCSI: Resetting SCSI -- lbolt: 387760, bus: 6
Apr 15 12:52:39 nmhptprd vmunix: SCSI: Reset detected -- lbolt: 387760, bus: 6
Apr 15 12:52:44 nmhptprd vmunix: SCSI: Parity Error -- lbolt: 388260, dev: cb061
000
Apr 15 12:52:44 nmhptprd vmunix: lbp->state: 60
Apr 15 12:52:44 nmhptprd vmunix: lbp->offset: ffffffff
Apr 15 12:52:44 nmhptprd vmunix: lbp->uPhysScript: 90042000
Apr 15 12:52:44 nmhptprd vmunix: From most recent interrupt:
Apr 15 12:52:44 nmhptprd vmunix: ISTAT: 0a, SIST0: 41, SIST1: 00,
DSTAT: 80, DSPS: 002a8200
Apr 15 12:52:44 nmhptprd vmunix: lsp: 00000000a2b9ab00
Apr 15 12:52:44 nmhptprd vmunix: bp->b_dev: cb061000
Apr 15 12:52:44 nmhptprd vmunix: scb->io_id: 60000ac
Apr 15 12:52:44 nmhptprd vmunix: scb->cdb: 12 00 00 00 80 00
Apr 15 12:52:44 nmhptprd vmunix: lbolt_at_timeout: 0, lbolt_at_st
art: 0
Apr 15 12:52:44 nmhptprd vmunix: lsp->state: 5
Apr 15 12:52:44 nmhptprd vmunix: lbp->owner: 0000000000000000
Apr 15 12:52:44 nmhptprd vmunix: scratch_lsp: 00000000a2b9ab00
Apr 15 12:52:44 nmhptprd vmunix: Script dump [0000000064851000]:
Apr 15 12:52:44 nmhptprd vmunix: 09000014 002a8200 09000040 002b0
9c0
Apr 15 12:52:44 nmhptprd vmunix: 0900002c 002b8080 e25c0004 90042
7f8

[Tim Nelson]

My guess..(only because I cannot remember off the top of my head). Check device with diag ( xstm > info ).

/dev/dsk/c6t1d0

b_dev: cb061000 is the line that gives it to you.

seach this forum using keyword lbolt. There are 100s of replies to this issue.

[James R. Ferguson]

Hi Ray:

Device cb061000

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

Regards!

...JRF...

[Ray Humpage]

I seemed to me it would be /dev/c6t1d0 also.

I don't have a disk device named that when I do an ioscan? Just a tape device which has no tape currently in it and no process running against it.


nmhptprd(/var/adm/syslog)# ioscan -fun|grep c6
/dev/rmt/1m /dev/rmt/c6t1d0BEST
/dev/rmt/1mb /dev/rmt/c6t1d0BESTb
/dev/rmt/1mn /dev/rmt/c6t1d0BESTn
/dev/rmt/1mnb /dev/rmt/c6t1d0BESTnb
/dev/dsk/c6t2d0 /dev/rdsk/c6t2d0
/dev/rscsi/c6t7d0

[Tim Nelson]

could you post an ioscan -fn please. Seems that the system things there is scsi ID 1 out there somewhere and hence the lbolt errors.

[Matti_Kurkela]

Check that all your SCSI cable connectors are properly plugged in. A loose connector or a bad cable may well cause lbolt errors.

If the bad disk is still physically present on the SCSI bus, some failure modes of the disk electronics may have an impact on the SCSI bus.

MK

[Sajjad Sahir]

what is u /var/adm/syslog/sylog.log contains

[Sajjad Sahir]

in syslog
u can see dev:if0.....
for example if033000
once u found it
do
#ll /dev/*dsk | grep 033000

this will give to find the disk for further investigation
please revert it