syslog - IO error

[Clutier_1]

Hi,

in the syslog.log i have :

Jan 31 18:44:24 ciccoga vmunix: DIAGNOSTIC SYSTEM WARNING:
Jan 31 18:44:24 ciccoga vmunix: The diagnostic logging facility has started r
eceiving excessive
Jan 31 18:44:24 ciccoga vmunix: errors from the I/O subsystem. I/O error ent
ries will be lost
Jan 31 18:44:24 ciccoga vmunix: until the cause of the excessive I/O logging
is corrected.
Jan 31 18:44:24 ciccoga vmunix: If the diaglogd daemon is not active, use the
Daemon Startup command
Jan 31 18:44:24 ciccoga vmunix: in stm to start it.
Jan 31 18:44:24 ciccoga vmunix: If the diaglogd daemon is active, use the log
tool utility in stm
Jan 31 18:44:24 ciccoga vmunix: to determine which I/O subsystem is logging e
xcessive errors.

[Fabio Ettore]

Hi Clutier,

of course, it is an EMS event notification.
Anyway you should

'use the log tool utility in stm to determine which I/O subsystem is logging excessive errors.'

You will obtain more info.
Also: what is the STM version? Just launch

# /usr/sbin/mstm

and near of top you will see something like

A.30.00

What is about your system?

Best regards,
Ettore

[T G Manikandan]

First check whether you diaglogd is active/running.
If not start is using

/sbin/init.d/diaglogd start

if youre getting excessive I/O warnings from the online diags (STM) then you definitely have to look at the /var/adm/syslog/syslog.log file for any errors.

Usually these are hint messages for any hardware problem.

[Kent Ostby]

Also, you can look for messages in syslog and dmesg that mention a specific dev or bdev.

This would indicate it is a disk that is likely having issues.

If you see a message for bdev = 0x1f009000, that would be a major number of 31 (the 0x1f) and a minor number of 009000 which works out to be c0t9d0.

You can check for something like this by doing :

ll /dev/dsk | grep and it will tell you which device it is.

Best regards,

Kent M. Ostby

[Clutier_1]

In stm, i have this msg

[Steven E. Protter]

These errors tend to point to a bad disk or cable or unterminated scsi device.

I would start up xstm in X Windows and run some excersizes and see what comes up.

SEP