SCSI Gross Error - Reset Detected

[ITeam]

Hi,

We have an rx4640 running 11:23
keep getting the following error message:

SCSI: Reset detected -- lbolt: 140364379, bus: 4 path: 0/2/1/0

This path points to:

ext_bus 4 0/2/1/0 c8xx CLAIMED INTERFACE SCSI C1010 Ultra160Wide LVD A6828-60101

I've checked the interface/disks attched via this device and all appears to be ok; however we see this message every night - I've looked to see if there are any patches for SCSIU160 I can't find anything for an 11:23 system,(there are patches for 11.11/.00/.22). I've found a cumulative kernel SCSI patch for 11.23 (PHKL_33361) does anyone know if this will fix the SCSI reset errors, or is there something else out there that will? Has anyone else seen this?

Many thanks in advance, AW

[D Block 2]

ignore the lbolt (or kernel clock tick time, might even wrap to a negative number).
The Reset scsi might be coming from a device on the hardware path.

Is there a DDS being used ? Most likely it is the DDS that needs to be either: (1) reseated or (2) replace by HP H/W support.

I don't think it cabling, you checked. But, you might want to check again.

I don't think this is software, you are most likely patched up to date, or near to date for SCSI patches.

This appears to be Hardware related.

It might help by sending back an full listing of h/w on this path: ioscan -fnH 0/2/1/0

good luck

[ITeam]

Hi again,

I've just checked the cables again and all looks ok, there isn't a tape device on this h/w path, just a disk array - I am able to access all disks ok, there aren't any stale extents or anything which would indicate a disk failure/hw problem. Below is a paste of ioscan -fnH0/2/1/0

Class I H/W Path Driver S/W State H/W Type Description
======================================================================
ext_bus 4 0/2/1/0 c8xx CLAIMED INTERFACE SCSI C1010 Ultra160 Wi
de LVD A6828-60101
target 3 0/2/1/0.0 tgt CLAIMED DEVICE
disk 2 0/2/1/0.0.0 sdisk CLAIMED DEVICE HP 73.4GMAS3735NC
/dev/dsk/c4t0d0 /dev/rdsk/c4t0d0
target 5 0/2/1/0.1 tgt CLAIMED DEVICE
disk 4 0/2/1/0.1.0 sdisk CLAIMED DEVICE HP 73.4GMAS3735NC
/dev/dsk/c4t1d0 /dev/rdsk/c4t1d0
target 6 0/2/1/0.2 tgt CLAIMED DEVICE
disk 5 0/2/1/0.2.0 sdisk CLAIMED DEVICE HP 73.4GST373454LC
/dev/dsk/c4t2d0 /dev/rdsk/c4t2d0
target 7 0/2/1/0.3 tgt CLAIMED DEVICE
disk 6 0/2/1/0.3.0 sdisk CLAIMED DEVICE HP 73.4GMAS3735NC
/dev/dsk/c4t3d0 /dev/rdsk/c4t3d0
target 8 0/2/1/0.4 tgt CLAIMED DEVICE
disk 7 0/2/1/0.4.0 sdisk CLAIMED DEVICE HP 73.4GMAS3735NC
/dev/dsk/c4t4d0 /dev/rdsk/c4t4d0
target 9 0/2/1/0.5 tgt CLAIMED DEVICE
disk 8 0/2/1/0.5.0 sdisk CLAIMED DEVICE HP 36.4GST336753LC
/dev/dsk/c4t5d0 /dev/rdsk/c4t5d0
/dev/dsk/c4t5d0s1 /dev/rdsk/c4t5d0s1
/dev/dsk/c4t5d0s2 /dev/rdsk/c4t5d0s2
target 11 0/2/1/0.7 tgt CLAIMED DEVICE
ctl 2 0/2/1/0.7.0 sctl CLAIMED DEVICE Initiator
/dev/rscsi/c4t7d0
target 16 0/2/1/0.15 tgt CLAIMED DEVICE
ctl 6 0/2/1/0.15.0 sctl CLAIMED DEVICE HP A6491A
/dev/rscsi/c4t15d0

the only thing that I am aware of that happened recently was that one of the disks was faulty and was replaced. But all disks look to be ok.