Getting SCSI errors. How do I tell what device?

[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

[Eric de Lange (MSE)]

Ray,

The device for which the resets are logged may be a robotics or changer device for a (virtual)tape library.

Major Number 203 is used for SCTL usually associated with these devices.

Looks like the command involved was a SCSI Inquiry command.

-Eric

[Andrew Rutter]

hi ray,

from the dev cb061000 we can see its a sctl device, not a disk.

cb = 203 major device file, so we can try and find out the device with

#cd /dev/sctl
#ls -la

you will see something like this

total 0
crw-r--r-- 1 root sys 203 0x000000 Jun 24 14:19 c0t0l0
crw-r--r-- 1 root sys 203 0x001000 Jun 24 14:20 c0t1l0


but likely to be a tape device or controller causing it

Andy