EMS Disk errors in the syslog file

[Manoj P.U.]

Hi all

i am getting the disk errors in my n4000 box.the error is like this

Mar 10 08:54:39 radha : su : + tf hpadm-root
Mar 10 09:50:20 radha EMS [10651]: ------ EMS Event Notification ------ Value: "CRITICAL (5)" for Resource: "/storage/events/disks
/default/0_0_1_0.1.0" (Threshold: >= " 3") Execute the following command to obtain event details: /opt/resmon/bin/resdata
-R 698024033 -r /storage/events/disks/default/0_0_1_0.1.0 -n 698023953 -a
Mar 10 09:50:20 radha EMS [10651]: ------ EMS Event Notification ------ Value: "CRITICAL (5)" for Resource: "/storage/events/disks
/default/0_0_2_0.6.0" (Threshold: >= " 3") Execute the following command to obtain event details: /opt/resmon/bin/resdata
-R 698024037 -r /storage/events/disks/default/0_0_2_0.6.0 -n 698023954 -a
Mar 10 09:50:21 radha EMS [10651]: ------ EMS Event Notification ------ Value: "CRITICAL (5)" for Resource: "/storage/events/disks
/default/0_0_2_1.6.0" (Threshold: >= " 3") Execute the following command to obtain event details: /opt/resmon/bin/resdata
-R 698024041 -r /storage/events/disks/default/0_0_2_1.6.0 -n 698023955 -a
Mar 10 09:50:21 radha EMS [10651]: ------ EMS Event Notification ------ Value: "CRITICAL (5)" for Resource: "/storage/events/disks
/default/0_4_0_0.8.0.255.0.1.0" (Threshold: >= " 3") Execute the following command to obtain event details: /opt/resmon/bi
n/resdata -R 698024045 -r /storage/events/disks/default/0_4_0_0.8.0.255.0.1.0 -n 698023956 -a
Mar 10 10:03:31 radha : su : + console hpadm-root
Mar 10 10:15:46 radha : su : + tf hpadm-root

this error first came on my lock vg of MCSG

then it came on all the externel disks on Storage tek array and later iternel disks and DVD rom also. attached the ioscan output and error from the syslog, output of swlist, and explanation of error .

Can any one guiode me why this is cominng .any help will be grately apprecited

Hisham

[Roberto Martinez_6]

Hi,

We also have this kind of errors from time to time with our N4000 and a Hitachi Thunder 9200. Our provider has told us that these messages should be ignored (?). In fact, we have both machines in a production environment for more than a year working perfectly without errors or loose of information, despite these "critical" errors (in fact, our errors are with severity "SERIOUS", not "CRITICAL".
Maybe this won't solve your (nor our) problems, but it may help you sleep better...

[Michael Steele_2]

This is a patching issue and a disconnect between the O/S utility EMS and your STK disk array. Often times patching removes this problem but sometimes not. In this case you can disable the event message but I wouldn't recommend it. So try this first:

a) pdcinfo (* /usr/sbin/diag/contrib/pdcinfo *) You should be at 42.06 for a N4000. This patch will get you there: PHSS_26533. (* Note the reboot needed. *)

b) Load the latest diagnostics. Run STM to see where you're at. Here is the format : A.31. I not sure of the most recent version.

c) Latest from STK.

[Andrew Merritt_2]

I'd echo what M. Frederick said. From the attached information, you have
OnlineDiag B.11.00.13.16 HPUX 11.0 Support Tools Bundle
installed.

This is the A.21.00 release, IPR0006 (June 2000) which is pretty old as there is a new release each quarter. (http://www.docs.hp.com/hpux/onlinedocs/diag/stm/stm_upd.htm#table shows all the versions).

You should upgrade to a recent version of OnlineDiags (A.38.00, HWE0303 is the latest), and check any patch dependencies are met (see http://www.docs.hp.com/hpux/onlinedocs/diag/st/str_0212.htm for the latest release notes).

There are no known problems with the latest versions of OnlineDiag generating spurious Event 3. If after upgrading the OnlineDiags you still have a problem, you'll need to check the hardware connections.

Andrew