topic Re: Syslog error message on rp4440 server in Operating System - HP-UX

Syslog error message on rp4440 server

Mahamudul Hassan — Thu, 07 Aug 2008 09:03:48 GMT

hi there, one of our rp4440 server shows the following output. can any one help me regarding the issue.

Thanks

wdkesc1 EMS [2015]: ------ EMS Event Notification ------ Value: "CRITICAL (5)" for Resource: "/storage/events/disks/default/

0_1_1_0.1.0" (Threshold: >= " 3") Execute the following command to obtain event details: /opt/resmon/bin/resdata -R 132055047 -r /st

orage/events/disks/default/0_1_1_0.1.0 -n 132055043 –a

root@wdkesc1 [/]

# /opt/resmon/bin/resdata -R 132055047 -r /storage/events/disks/default/0_1_1_0.1.0 -n 132055043 -a

CURRENT MONITOR DATA:

Event Time..........: Tue Aug 5 19:08:29 2008

Severity............: CRITICAL

Monitor.............: disk_em

Event #.............: 17

System..............: wdkesc1

Summary:

Disk at hardware path 0/1/1/0.1.0 : I/O request failed.

Description of Error:

The hardware responded to the initial query, but then it stopped

responding to more requests by the driver. The I/O request was not

completed.

Probable Cause / Recommended Action:

The bus device reset may have occurred or the device has failed. The bus

device reset could have occurred because the power was cycled or that the

device is a part of an enclosure and a device in that enclosure was pulled

out or put in, or that the interface card had a problem and it reset the

bus. If these errors continue, there may be a problem with the device or

the card.

Additional Event Data:

System IP Address...: 10.243.96.12

System IP Address...: 10.243.96.12

Event Id............: 0x489850cd00000000

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):

0x4898506300000001

Additional System Data:

System Model Number.............: 9000/800/rp4440

OS Version......................: B.11.23

STM Version.....................: C.53.00

EMS Version.....................: A.04.20

Latest information on this event:

http://docs.hp.com/hpux/content/hardware/ems/disk_em.htm#17

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.1.0

Device Class...........: Disk

Inquiry Vendor ID......: HP 146 G

Inquiry Product ID.....: ST3146707LC

Firmware Version.......: HPC2

Serial Number..........: 3KS47VEF00007701XFYF

Product/Device Identification Information:

Logger ID.........: sdisk

Product Identifier: SCSI Disk

Product Qualifier.: HP146

SCSI Target ID....: 0x01

SCSI LUN..........: 0x00

I/O Log Event Data:

Driver Status Code..................: 0x0000007E

Length of Logged Hardware Status....: 4 bytes.

Offset to Logged Manager Information: 8 bytes.

Length of Logged Manager Information: 34 bytes.

SCSI Command Data Block:

Command Data Block Contents:

0x0000: 2A 00 02 DA 17 60 00 00 10 00

Command Data Block Fields (10-byte fmt):

Command Operation Code...(0x2A)..: WRITE

Logical Unit Number..............: 0

DPO Bit..........................: 0

FUA Bit..........................: 0

Relative Address Bit.............: 0

Logical Block Address............: 47847264 (0x02DA1760)

Transfer Length..................: 16 (0x0010)

Manager-Specific Data Fields:

Request ID.............: 0x028AC6E7

Data Residue...........: 0x00002000

CDB status.............: 0x00000400

Sense Status...........: 0x00000000

Bus ID.................: 0x02

Target ID..............: 0x01

LUN ID.................: 0x00

Sense Data Length......: 0x00

Q Tag..................: 0xFC

Retry Count............: 1

root@wdkesc1 [/]

Re: Syslog error message on rp4440 server

Pete Randall — Thu, 07 Aug 2008 09:15:00 GMT

One of your disks had, or is having, a problem. Use "ioscan -kfnCdisk" to get the device file that matches up with hardware path 0/1/1/0.1.0. Then use dd to find out if that disk is accessible or not:

dd if=/dev/rdsk/cXtYdZ of=/dev/null bs=1024k

If you get errors from dd, most likely your disk is failed and needs to be replaced. Help with the replacement process can be found in this document:

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

Pete

Re: Syslog error message on rp4440 server

VK2COT — Thu, 07 Aug 2008 09:17:48 GMT

Hello,

You are very likely having a faulty disk
or it is in a state that will cause
trouble in the future:

Disk at hardware path 0/1/1/0.1.0

Run ioscan command and confirm it:

# ioscan -fnC disk

Look for NO_HW entries.

Then, organise the replacement part
from HP (if you have a maintenance
contract).

I hope your data on the disk is protected
by RAID-1 or tape backups?

Cheers,

VK2COT

Re: Syslog error message on rp4440 server

Anshumali — Thu, 07 Aug 2008 09:22:13 GMT

Was there any activity performed on the disk, 0/1/1/0.1.0 recently, it appears that it got a reset on the SCSI bus and event count being 0, it might be a pre-alarms of disk/card/bus going bad, if there was no activity performed,

Re: Syslog error message on rp4440 server

SUDHAKAR_18 — Thu, 07 Aug 2008 09:53:37 GMT

Hello,

Provide ioscan -fn output
also check ioscan -fn |grep -i no

Regards,

Re: Syslog error message on rp4440 server

Ganesan R — Thu, 07 Aug 2008 10:27:41 GMT

Hello,

Check the disk at h/w path 0/1/1/0.1.0. It is not able to handle I/O request means it could be due to bad media/disk failure/controller failure.

Check the disk status by diskinfo, ioscan, pvdisplay(if it is part of lvm) or dd

From my experience this event notification will end up with disk replacement. since it is critical event it is better to replace the disk.

Thanks

Re: Syslog error message on rp4440 server

Deepak Kr — Thu, 07 Aug 2008 11:30:13 GMT

Hi Hassan,

advisable to check the disk connected at h/w path 0/1/1/0.1.0.

System might be having issue while read/writing to this disk. so it may be due to bad media or controller issue.

run following to verify

diskinfo
ioscan
pvdisplay
lssf

Also log a case with HP as disk may be replaced if found bad.

Regds,
Deepak