vmunix: errors from the I/O Subsystem. I/O error entries will be lost

[manish_csc]

DIAGNOSTIC SYSTEM WARNING:
The diagnostic logging facility is no longer receiving excessive
errors from the I/O subsystem. 1 I/O error entries were lost.
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.


Getting above error, checked diaglogd is running and checked through stm also but still problem repeating ...

Manish Kumar

[Steven E. Protter]

Shalom Manish,

You have an intermittant I/O problem with disk.

If its SAN/FC based, it could be a problem with the SAN, FC card or cables.

It its local disk, you may have a disk that is being over-taxed or is ready to fail. Use xstm or mstm or cstm to test local disk and make sure it is solid.

SEP

[IT_2007]

As Steve said it is very hard to find out exact problem. Check all Fibre cards status using fcmsutil command and check for any errors using cstm command.

[V.Manoharan]

Hi Manish Kumar,
This is known issue with older version of STM&EMS, Please install the latest STM(Version A.52.00),EMS( A.04.20 )and latest patch bundles you can overcome the errors.

Best is install Support-Plus CD June 2006 .

Thanks and regards
V.Manoharan

[Kevin Wright]

I would investigate with logtool, fcmsutil, and tddiag.

[Andrew Merritt_2]

Hi Manish,
This is not a 'known problem', it is normal behaviour when a hardware device reports too many I/O errors for diaglogd to handle in a short time, although there are some other possible causes. If you have a current version of the OnlineDiags, the most likely cause is a hardware error.

As the message says: "use the logtool utility in stm to determine which I/O subsystem is logging excessive errors." In logtool you should at least see the paths of the devices logging the I/O errors, which should give you a start on troubleshooting the problem. You say you did check in stm - what did you see?

It is a good idea to make sure you have a current version of the OnlineDiags, and you should upgrade if you don't.

Andrew

[Tonya Underwood]

Post the output of the following:

egrep 'DIAGNOSTIC|vmunix' /var/adm/syslog/syslog.log

Thanks.

[MohankumarK]

Disks Selection
_______________________________________________________________________________

Device MByte Hardware Path Usage Type VolGroup
_______________________________________________________________________________
c2t0d0 69952 0/1/1/0.0.0 Pri_Boot _Main_ vg00
c2t1d0 69952 0/1/1/0.1.0 _(free)_ ______ ______________
_______________________________________________________________________________
These are your Disks Selection to install HPUX on this system.
ATTENTION: The contents of selected disks will be permanent lost
Do you want CONTINUE?

Press [y] for yes, [n] for no or [q] to quit, then press [Enter] y

_______________________________________________________________________________

The procedure will operate unattended.
The procedure executed by a PA-RISC RP3410 will take:
20 minutes for operating system
+30 minutes to install and configure mirror
Don't worry if the machine reboots automatically.

Press [Enter] to continue...

=>Fri May 17 17:19:17 IST 2013
=>Initialize Boot physical volume on /dev/rdsk/c2t0d0 ...
64+0 records in
64+0 records out

=>Fri May 17 17:19:19 IST 2013
=>Creating Boot physical volume on /dev/rdsk/c2t0d0 for LVM use ...
Creating "/etc/lvmtab".
Physical volume "/dev/rdsk/c2t0d0" has been successfully created.

=>Fri May 17 17:19:21 IST 2013
=>Creating boot block on /dev/rdsk/c2t0d0

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.

Pls help ...me too facing this problem

[Robert_Jewell]

The answer hasnt changed.....you are having a problem with a disk or possibly a controller.  Since you are trying to install, the issue is likely with the disk you are trying to install to, although if you have other drives installed, especially on the same controller, the problem could be there.

if you have any other drives, remove them and restart the installation to see if that helps.  If that doesnt or you dont have other drives you can suspect the disk.  Replacing that with another is the easiest means to troubleshoot this. 

If you wanted to you can try to boot into a recovery shell from the installation media to see if you can get more details about the problem.

-Bob