ioscan does not respond

[brian_31]

I have a strange issue. no specific error in syslog or dmesg except the following....

vmunix: DIAGNOSTIC SYSTEM WARNING:
vmunix: The diagnostic logging facility has started receiving excessive
vmunix: errors from the I/O subsystem. I/O error entries will be lost
vmunix: until the cause of the excessive I/O logging is corrected.
vmunix: If the diaglogd daemon is not active, use the Daemon Startup command
vmunix: in stm to start it.
vmunix: If the diaglogd daemon is active, use the logtool utility in stm
vmunix: to determine which I/O subsystem is logging excessive errors.

but ioscan command hangs. any thoughts?

Thanks

brian

[D Block 2]

Brian,
I'm not the expert here.. but might I suggest the following:

1. run IOSCAN in a terminal window
2. in a new window, at the same time, run a TAIL -f /var/adm/syslog/syslog.log

This way, you can see the logging messages

question: Do you see any thing that says Probe TimeOut ? is there also a H/W path related to this TimeOut ?

Of course, some background concerns might be: (1) is your system current on both the Diags and the IOSCAN patches ??


Just another thought, you can also classify your IOSCAN by using the -C option. Example:

ioscan -fnC tape
ioscan -fnC disk
ioscan -fnC fc

if the ioscan returns in a few minutes, then you know there is not issue. But, if the ioscan thens to hang for longs periods, say 20 minutes or 1/2 hour, then you just identifed the CLASS type. Good to know.

so try it and have some fun..

Think about it... the ioscan is like Probing your H/W during Boot-Up.. it times time.. and believe me.. a complicate task.. which can TimeOut and cause some Panic' Traps..

so Patch Up on the IOSCAN and your Diags..

Hey Brain, the ITRC guys will help you here.. but you need to supply possibly more details from your Syslog.log(file).

best in 07'

T.

[Raj D.]

Brian,
Check dmesg and syslog for any specific error, also check /var/opt/resmon/events/event.log file for error details,

Also check:
# cat /var/adm/syslog/syslog.log | grep EMS

Cheers,
Raj.

[Mridul Shrivastava]

Hi Brian,

I would rather suggest you to run cstm as suggested and then find which subsystem is causing issues.

If you are not familiar with cstm commands then you can execute the following command and then check the cstm.txt for any issues:

# echo "map selall info;wait infolog" | cstm > /tmp/cstm.txt

[Andrew Young_2]

Hi Brian

Knowing which class is giving the problem would be helpful.

The only times I have had this problem is with SCSI devices, usually either a device is not responding or partially responding, or with the SCSI termination. A quick first step would be to check all you connectors are in properly, do this when your system is down or idle, it is not unknown for a short on a SCSI cable to reboot a server.

Also if cstm is a bit too confusing you could use mstm which is a bit more intuitive.

HTH

Andrew Y