topic Re: SCSI Errors in Operating System - HP-UX

SCSI Errors

Vito Sarducci — Wed, 29 May 2002 21:26:47 GMT

scb->cdb: 28 00 02 13 a8 00 00 00 80 00
scb->cdb: 2a 00 00 07 0d c0 00 00 04 00
SCSI: Resetting SCSI -- lbolt: 20766441, bus: 5
SCSI: Reset detected -- lbolt: 20766441, bus: 5
DIAGNOSTIC SYSTEM WARNING:
The diagnostic logging facility has started receiving excessive
errors from the I/O subsystem. I/O error entries will be lost
until the cause of the excessive I/O logging is corrected.
If the diaglogd daemon is not active, use the Daemon Startup command
in stm to start it.
If the diaglogd daemon is active, use the logtool utility in stm
to determine which I/O subsystem is logging excessive errors

What might this be? Please advise?

Vito

Re: SCSI Errors

erics_1 — Wed, 29 May 2002 21:57:25 GMT

Vito,

Do you happen to have more information in syslog? Something like:

scsi: abort tag--lbolt: , dev:1f079000, io_id:7c9db5e

What I would be interested in is the hex address after the 'dev:' listing. This would point to a specific device. This may just be an issue of increasing the timeout on the disk with pvchange -t.

Let us know of any other information that you have.

Regards,
Eric

Re: SCSI Errors

S.K. Chan — Thu, 30 May 2002 01:46:25 GMT

It can only mean 3 things
1) Disk is failing
2) Low timeout value
3) SCSI termination and connection.

You just have to go through the process of elimination to determne your actual root cause. Check for IO error using STM..
# cstm
cstm>map
cstm>sel dev
cstm>info
cstm>infolog

If you don't see any error, double check connection, cable, termination,etc. If that is ok, then is it likely to be that the timeout value of the disk needs to be increased. For example ..
# pvchange -t 180 /dev/dsk/c0td0
increases it to 180 secs. Check man page of pvchange for details.

Of course you got to determine which device is giving the error message, typically what Eric had mentioned (eg: dev:1f079000 would be c7t9d0)