I/O Subsystem Error Message

[paula hawk_2]

Does anyone know what the following error indicates?? It is a D Class Server running 10.20. The DEMLOG daemon is not running and i can not get it started.

Apr 17 18:42:19 hp0089 vmunix: 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 DEMLOG daemon is not active, use the DIAGSYSTEM command in SYSDIAG to start it. If the DEMLOG daemon is active, use the LOGTOOL utility in SYSDIAG to determine which I/O subsystem is logging excessive errors.
Apr 17 18:42:19 hp0089 vmunix: SCSI: Request Timeout -- lbolt: 2659802, dev: 1f004000
Apr 17 18:42:19 hp0089 vmunix: lbp->state: 40c0
Apr 17 18:42:19 hp0089 vmunix: lbp->offset: ffffffff
Apr 17 18:42:19 hp0089 vmunix: lbp->uPhysScript: 1298000
Apr 17 18:42:19 hp0089 vmunix: From most recent interrupt:
Apr 17 18:42:19 hp0089 vmunix: ISTAT: 22, SIST0: 00, SIST1: 04, DSTAT:
00, DSPS: 012983c0
Apr 17 18:42:19 hp0089 vmunix: NCR chip register access history (most recent la
st): 289640 accesses

[Domenico_5]

hi paula

it means that
that the driver could not complete the
I/O in the specified amount of time. The default time is 30 seconds.


this error is on c0t4d0

[Jeff Schussele]

Hi Paula,

Sounds like the system is detecing an error on a SCSI disk - specifically c0t4d0.

Try a diskinfo command on it
diskinfo /dev/rdsk/c0t4d0 or run stm diags against it.

You can determine the disk from the dev: 1f0040000 indication.

HTH,
Jeff

[Paula J Frazer-Campbell]

Paula

You have a disk with a problem.

Full backup and replace it ASAP.


HTH

Paula

[S.K. Chan]

Confirm the disk problem in cstm .. (only do this if the disk seems to respond to diskinfo query and can be seen in ioscan)

# cstm
cstm>map
===> take note of "dev" number of the disk
cstm>sel dev 14
===> assuming disk has device 14 assigned to it
cstm>exercise
===> run exerciser tool on it, it take a while to complete
cstm>map
===> check status of exerciser until it's 100% completed
cstm>infolog

[Sandip Ghosh]

Look for the c0t4d0. Find out through STM whether there is a problem or not. If not look that disk is how much busy. If you find it is too much busy just increase the SCSI time delay. Do it by
pvchange -t 60 for 60 sec . by default it is 30 sec.

Sandip

[pap]

Hi PAula,
It is better to check the SCSI time out parameter.If it is low, try to increase it.

But it seems thast you have a disk problem and hence you need to check the disk at highest priority. Check the disk by using support tools manager utilities stm, cstm or xstm etc...
Simply u can try dd to check the disk functionality about read and write.

dd if=/dev/dsk/cxtydz of=/dev/null
(Specify approprite block size)


this will show an error if it will occurs.

Thanks,
-pap

[S.K. Chan]

.. the last bit should be ..
cstm>exeractlog
===> exerciser activity log display
cstm>exerfaillog
===> exerciser fail log display