1753797 Members
6908 Online
108799 Solutions
New Discussion юеВ

Re: EMS Log

 
SOLVED
Go to solution
mark.M
Frequent Advisor

EMS Log

i used rx2600(running 11.23).
i'm find record of EMS Log.
Disk Fault???? or low version of stm????

-web2 event.log -----

>------------ Event Monitoring Service Event Notification ------------<

Notification Time: Fri Sep 22 15:53:04 2006

web2 sent Event Monitor notification information:

/storage/events/disks/default/0_1_1_0.0.0 is >= 1.
Its current value is CRITICAL(5).



Event data from monitor:

Event Time..........: Fri Sep 22 15:53:02 2006
Severity............: CRITICAL
Monitor.............: disk_em
Event #.............: 3
System..............: web2

Summary:
Disk at hardware path 0/1/1/0.0.0 : Drive is not responding.


Description of Error:

As part of the polling functionality, the monitor periodically requests
data from the device. The monitor's request of Test Unit Ready command
failed.

Probable Cause / Recommended Action:

The I/O request that the monitor made to this device failed because the
device timed-out. Check cables, power supply, ensure the drive is powered
ON, and if needed contact your HP support representative.

Additional Event Data:
System IP Address...: 211.114.145.15
Event Id............: 0x4513884f00000000
Monitor Version.....: B.01.01
Event Class.........: I/O
Client Configuration File...........:
/var/stm/config/tools/monitor/default_disk_em.clcfg
Client Configuration File Version...: A.01.00
Qualification criteria met.
Number of events..: 1
Associated OS error log entry id(s):
None
Additional System Data:
System Model Number.............: ia64 hp server rx2600
OS Version......................: B.11.23
STM Version.....................: C.48.00
EMS Version.....................: A.04.11
Latest information on this event:
http://docs.hp.com/hpux/content/hardware/ems/disk_em.htm#3

v-v-v-v-v-v-v-v-v-v-v-v-v D E T A I L S v-v-v-v-v-v-v-v-v-v-v-v-v





Component Data:
Physical Device Path...: 0/1/1/0.0.0
Device Class...........: Disk
Inquiry Vendor ID......: HP 73.4G
Inquiry Product ID.....: ST373453LC
Firmware Version.......: HPC5
Serial Number..........: 3HW17EEN000074394173

Product/Device Identification Information:

Logger ID.........: disc30; sdisk
Product Identifier: Disk
Product Qualifier.: HP 73.4GST373453LC
SCSI Target ID....: 0x00
SCSI LUN..........: 0x00

SCSI Command Data Block: (not present in log record)

Hardware Status: (not present in log record).

SCSI Sense Data: (not present in log record)


>---------- End Event Monitoring Service Event Notification ----------<
3 REPLIES 3
Pete Randall
Outstanding Contributor
Solution

Re: EMS Log

Seems to be an issue with the disk at device path 0/1/1/0.0.0 . Use ioscan to find out the device file that matches up with address 0/1/1/0.0.0 , then run diskinfo against the raw device file:

# diskinfo /dev/rdsk/c3t5d0
SCSI describe of /dev/rdsk/c3t5d0:
vendor: SEAGATE
product id: ST39103LC
type: direct access
size: 8886762 Kbytes
bytes per sector: 512
#

If diskinfo is successful, try running dd against the disk:

#dd if=/dev/rdsk/c3t5d0 of=/dev/null bs=1024k

If that completes successfully, your disk is most likely OK. If it ends with an I/O error, you definitely have problems with your disk and should get it replaced.

A good guide to replacement procedures is available here:

http://docs.hp.com/en/5991-1236/When_Good_Disks_Go_Bad.pdf


Pete

Pete
Jaime Bolanos Rojas.
Honored Contributor

Re: EMS Log

Mark,

Also you might want to open a quick hardware call to HP if by any change you find out that the drive is ok, probably there is problem with some other part of your equipment.
And if it's the drive, then HP will be able to replace it.

Regards,

Jaime.
Work hard when the need comes out.
spex
Honored Contributor

Re: EMS Log

Hi,

0/1/1/0.0.0 is your root disk. Hopefully it's mirrored and you've got a current Ignite backup. Place a call to HP. They'll most likely have you replace it.

PCS