HP-UX EMS Disk Event critical warning

[Alexander Mironov]

Hello everyone!
I got a message marked as a HP-UX EMS Disk Event. It constantly spoolling in system and seems to be critical.
Does anybode know how to fix it?
Many thanx.!!!!



100776520071021122808
IndicationTime Sun, 10/21/2007, 4:28 PM MSD
Description The device was unsuccessful in processing the current request message because the message contained an invalid field in the command data block. The request was not processed.
AlertType Unknown
PerceivedSeverity Critical
ProbableCause Unknown
ProbableCauseDescription The error most likely indicates that the device is not fully supported by the current driver. This may or may not cause a problem in the operation of the device.
EventID 100776
EventTime Mon, 10/22/2007, 4:28 AM MSD
SystemCreationClassName CIM_ComputerSystem
SystemName rx2660-node2
ProviderName DiskIndicationProvider
Summary Disk at hardware path 64000/0xfa00/0x0 : Software configuration error
EventCategory 0
EventSubCategory 0
ActualEventThreshold 1
ActualEventTimeWindow 0
ClusterWideEvent false
ProviderVersion C.01.00.29
InformationURL http://docs.hp.com/hpux/content/hardware/ems/scsi.htm#100776
OSType 8
OSVersion B.11.31
SystemModel ia64 hp server rx2660
AlertingElementFormat CIMObjectPath
HWManufacturer HP
DeviceModel IR Volume
DevicePermanentNameFormat 2
NetworkAddresses 192.168.3.102
VariableNames OriginalProductNumber, CurrentProductNumber, SWID
VariableValues 60b613f6-2584-11dc-83fb-45ce7a568cd7
VariableTypes 1, 1, 1
HWFirmwareVersion HP01
HWLogicalLocation 64000/0xfa00/0x0
HWSerialNumber unavailable

[Torsten.]

First check the status of the controller, using for example:

# sasmgr get_info -D /dev/sasd0
# sasmgr get_info -D /dev/sasd0 -q lun=all
# sasmgr get_info -D /dev/sasd0 -q raid
# sasmgr get_info -D /dev/sasd0 -q phy=all


Check itrc.com for driver updates if needed.

[Thomas J. Harrold]

I am seeing the same error on an rx3600, patches were done about 2 months ago. I have sasd driver version B.11.23.04

I'll check for an update, but I'm skeptical...

All HW and RAID check out OK.

[Torsten.]

There are many items involved:

- controller firmware
- driver
- diagnostics

and between the internal controller and a smartarray (P400) the firmware and driver is even different.

On almost every item each update brings fixes, enhancements ...

example:
http://docs.hp.com/en/5992-0676/ar01s02.html

I would check this and ask HP support.

[Todd Stewart_1]

I had a similar EMS message using 11.31 on an rx3600.

Try upgrading to the latest Support Tools and the messages should go away.

[Andrew Merritt_2]

Hi Alexander,
I can confirm that this is a known problem, and upgrading to the current (D.02.00) version of the OnlineDiags will fix it.

From http://www.docs.hp.com/en/11827/emr_0709_1131.htm :
============
Disk Monitor (disk_em)

* JAGag28657
On the rx3600 and rx6600 systems, the disk_em monitor monitors the Logical Unit Numbers (LUNs) configured on the internal Serial-Attached SCSI (SAS) controller, although the device is not supported. This problem is fixed. The disk_em monitor does not monitor the LUNs configured on the internal SAS controller.
============

Although it only mentions rx3600 and rx6600, the same problem applies to rx2660, and the same fix applies.

If you get the same problem after upgrading, please report the problem to HP support.

Andrew

[Torsten.]

Andrew, the controller is monitored by dm_sas_adapter, right?

[Andrew Merritt_2]

Torsten,
Yes, that's correct, though not directly related to this problem.

Andrew