Critical dm_ses_enclosure disk failure

[Chartier Jerome]

Hi all,

For two days, I've got this message from ems:
>------------ Event Monitoring Service Event Notification ------------<

Notification Time: Mon Feb 2 13:20:52 2004

Nemesis sent Event Monitor notification information:

/storage/events/enclosures/ses_enclosure/1_8_0_0.8.0.255.0.10.0
is >= 3.
Its current value is CRITICAL(5).



Event data from monitor:

Event Time..........: Mon Feb 2 13:20:51 2004
Severity............: CRITICAL
Monitor.............: dm_ses_enclosure
Event #.............: 111
System..............: nemesis.boulogne.com

Summary:
Enclosure at hardware path 1/8/0/0.8.0.255.0.10.0 : Hardware failure


Description of Error:

The disk device is indicating that it has faulted.

Probable Cause / Recommended Action:

The disk drive in slot 6 has failed. Check the connection, re-seat, or
inspect/verify the disk drive.

User Defined Annotation: .

Additional Event Data:
System IP Address...: 10.28.138.206
Event Id............: 0x401e4eb300000000
Monitor Version.....: B.01.00
Event Class.........: I/O
Client Configuration File...........:
/var/stm/config/tools/monitor/default_dm_ses_enclosure.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.............: 9000/800/N4000-75
OS Version......................: B.11.11
System Serial Number............: usm39292a8
System Software ID..............: 618329303
EMS Version.....................: A.04.00
STM Version.....................: A.41.00
Latest information on this event:
http://docs.hp.com/hpux/content/hardware/ems/dm_ses_enclosure.htm#111

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...: 1/8/0/0.8.0.255.0.10.0
Firmware Version.......: HP03
Serial Number..........: USSA06003211
Inquiry Product ID.....: A5236A
Inquiry Vendor ID......: HP


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

The disk doesn't seems to be broken ....
Are their some low level commands to check for this disk and its health?

Thanks in advance

Regards

Jérô

[Bernhard Mueller]

JJ,

to me this looks very much like an FC10 and target 10 is not a disk but the LCC (link controller card); product ID A5236 matches that, however I hope you have a support contract and can get HP to update controller firmware to HP10.

The disk in slot 6 should be target 5 so you can run a
dd if=/dev/rdsk/c#t5d0 of=/dev/null bs=1024k
to verify complete readability of this disk.

If it dd gives an I/O error, have the disk replaced.

However, I suspect the error due to the old controller firmware.

Regards,
Bernhard

[Steven E. Protter]

The disk array itself tends to be detected as LUN0 when none is assigned. EMS thinks its a disk, but it doesn't act like a disk and EMS gets confused.

It can be ignored


It can be eliminated by assigning a LUN0 to the Fiber connection.

SEP

[Bernhard Mueller]

JJ,

sorry, I just double-checked and saw the target ID of the disk would be 6 (for enclosure # 0).

Regards,
Bernhard

[Chartier Jerome]

Thanks all for your brilliant answers,

I've used the tool mstm which performs some exercise and so on test ....
With successfull issue ... so .... I'm happy with this result.
From my opinion, it should really be firmware issue ...

Thanks again for your help

Cheers

Jerome (without a french keyboard ... ;o)