SCSI Reset

[ROUCHON_1]

Hi all,

I have some trouble with scsi reset on my N4000 server.
I read into some of these forums that is due to disk failure, or tape device failure, but I didn't find anything wrong, NO_HW msg in ioscan (dat tape device had been changed, end-scsi too, sc10 disk checked).

You will find the syslog.log attached with tis case.

I know that dev :cb09d002 means

cb : 203(sctl)
09 : is the 9th scsi bus
d0 : means t13d0 ?

but in the syslog there is more than one scsi interface msg
cf :
lbolt: 5684, dev: cb056002, io_id: 5000007
...
lbolt: 11418, dev: cb08b002, io_id: 800000b
lbolt: 11418, dev: cb08c002, io_id: 800000c
...
lbolt: 13247, dev: cb091002, io_id: 9000002
lbolt: 13247, dev: cb092002, io_id: 9000003

Here is the results of ioscan -funC ctl

Class I H/W Path Driver S/W State H/W Type Description
=================================================================================
ctl 0 0/0/1/0.7.0 sctl CLAIMED DEVICE Initiator
/dev/rscsi/c0t7d0
ctl 1 0/0/2/0.7.0 sctl CLAIMED DEVICE Initiator
/dev/rscsi/c1t7d0
ctl 2 0/0/2/1.7.0 sctl CLAIMED DEVICE Initiator
/dev/rscsi/c2t7d0
ctl 13 0/2/0/0.1.0.255.0.0.0 sctl CLAIMED DEVICE EMC SYMMETRIX
/dev/rscsi/c14t0d0
ctl 7 0/4/0/0.7.0 sctl CLAIMED DEVICE Initiator
/dev/rscsi/c5t7d0
ctl 8 0/8/0/0.7.0 sctl CLAIMED DEVICE Initiator
/dev/rscsi/c6t7d0
ctl 9 0/8/0/1.7.0 sctl CLAIMED DEVICE Initiator
/dev/rscsi/c7t7d0
ctl 3 0/12/0/0.7.0 sctl CLAIMED DEVICE Initiator
/dev/rscsi/c3t7d0
ctl 4 0/12/0/0.15.0 sctl CLAIMED DEVICE HP A5272A
/dev/rscsi/c3t15d0
ctl 12 1/0/0/0.11.0.255.0.0.0 sctl CLAIMED DEVICE EMC SYMMETRIX
/dev/rscsi/c12t0d0
ctl 5 1/4/0/0.7.0 sctl CLAIMED DEVICE Initiator
/dev/rscsi/c4t7d0
ctl 6 1/4/0/0.15.0 sctl CLAIMED DEVICE HP A5272A
/dev/rscsi/c4t15d0
ctl 10 1/10/0/0.7.0 sctl CLAIMED DEVICE Initiator
/dev/rscsi/c8t7d0
ctl 11 1/12/0/0.7.0 sctl CLAIMED DEVICE Initiator
/dev/rscsi/c9t7d0

How can i find what's wrong ?

Many thanks for your help

[Steven E. Protter]

Shalom,

It can be caused by swapping out a hot swap disk. That would be cleared by the next reboot.

It could also be caused by a problem with a scsi cable, an unterminated scsi device, or bad drive cage if your system has a drive cage.

If its paragraph 2, you will see all disks present and accounted for. For now.

Any disks missing? If now, take a look and see if everything is terminated.

SEP

[ROUCHON_1]

I change any of the scsi cable, and terminator but it didn't change anything ...
We upgrade scsi driver with the last one, nothing change too.

[Steven E. Protter]

Shalom,

What server type is it. This could be a drive cage problem that you can't fix on your own. You may need to contact HP hardware for this.

Have there been intermittant problems for a while? Have there been a number of unexplained drive failures?

Perhaps run cstm mstm or xstm and test the various system components with the excercize function.

SEP