HP Major warning reg SCSI

[Jayraj]

Hi All,

My syslog, is filling up with these errors, regulary. Any Ideas where things went wrong..?

HP MAJORWARNING: (3) for Resource: /storage/events/disks/default/0_3_1_0.2.0 (Threshold: >= 3) Execute the following command to obtain event details: /opt/resmon/bin/resdata -R 185729032 -r /storage/events/disks/default/0_3_1_0.2.0 -n 185729276 -a


------ EMS Event Notification ------ Value: "MAJORWARNING (3)" for Resource: "/storage/e
vents/disks/default/0_3_1_0.5.0" (Threshold: >= " 3") Execute the following command to obtain event details: /opt/re
smon/bin/resdata -R 185729047 -r /storage/events/disks/default/0_3_1_0.5.0 -n 185729279 -a


EMS [2834]: ------ EMS Event Notification ------ Value: "MAJORWARNING (3)" for Resource: "/storage/e
vents/disks/default/0_3_1_0.0.0" (Threshold: >= " 3") Execute the following command to obtain event details: /opt/re
smon/bin/resdata -R 185729082 -r /storage/events/disks/default/0_3_1_0.0.0 -n 185729026 -a


------ EMS Event Notification ------ Value: "MAJORWARNING (3)" for Resource: "/storage/e
vents/disks/default/0_3_1_0.2.0" (Threshold: >= " 3") Execute the following command to obtain event details: /opt/re
smon/bin/resdata -R 185729032 -r /storage/events/disks/default/0_3_1_0.2.0 -n 185729027 -a

[TTr]

EMS can not see a bunch of devices
/0/3/1/0.2.0
/0/3/1/0.5.0
/0/3/1/0.0.0
They are probably disks. Run ioscan -fn and look at the above hw paths and check the status of those devices.

Did you remove any disks recently?
If not, either all those disks fails (highly unlikely) or the interface that all 3 disks are connected has failed.

[Jayraj]

Hi, Thank you for quick reply..

Here is the output of the path.

Class I H/W Path Driver S/W State H/W Type Description
=========================================================================
disk 0 0/0/2/0.0.0.0 sdisk CLAIMED DEVICE TEAC DV-28E-C
/dev/dsk/c0t0d0 /dev/rdsk/c0t0d0
disk 1 0/3/1/0.0.0 sdisk CLAIMED DEVICE HP 73.4GST373307LC
/dev/dsk/c4t0d0 /dev/rdsk/c4t0d0
disk 2 0/3/1/0.1.0 sdisk CLAIMED DEVICE HP 73.4GST373307LC
/dev/dsk/c4t1d0 /dev/rdsk/c4t1d0
disk 3 0/3/1/0.2.0 sdisk CLAIMED DEVICE HP 73.4GST373307LC
/dev/dsk/c4t2d0 /dev/rdsk/c4t2d0
disk 4 0/3/1/0.3.0 sdisk CLAIMED DEVICE HP 73.4GST373307LC
/dev/dsk/c4t3d0 /dev/rdsk/c4t3d0
disk 5 0/3/1/0.4.0 sdisk CLAIMED DEVICE HP 73.4GST373307LC
/dev/dsk/c4t4d0 /dev/rdsk/c4t4d0
disk 12 0/3/1/0.5.0 sdisk CLAIMED DEVICE HP 73.4GST373454LC
/dev/dsk/c4t5d0 /dev/rdsk/c4t5d0
disk 6 0/4/1/0.8.0 sdisk CLAIMED DEVICE HP 73.4GST373307LC
/dev/dsk/c5t8d0 /dev/rdsk/c5t8d0
disk 7 0/4/1/0.9.0 sdisk CLAIMED DEVICE HP 73.4GST373307LC
/dev/dsk/c5t9d0 /dev/rdsk/c5t9d0
disk 8 0/4/1/0.10.0 sdisk CLAIMED DEVICE HP 73.4GST373307LC
/dev/dsk/c5t10d0 /dev/rdsk/c5t10d0
disk 9 0/4/1/0.11.0 sdisk CLAIMED DEVICE HP 73.4GST373307LC
/dev/dsk/c5t11d0 /dev/rdsk/c5t11d0
disk 10 0/4/1/0.12.0 sdisk CLAIMED DEVICE HP 73.4GST373307LC
/dev/dsk/c5t12d0 /dev/rdsk/c5t12d0
disk 11 0/4/1/0.13.0 sdisk CLAIMED DEVICE HP 73.4GST373307LC
/dev/dsk/c5t13d0 /dev/rdsk/c5t13d0

[Jayraj]

Here is the pvdisplay output.. I see all are available and no pvs are stale..

:/wdroot# pvdisplay /dev/dsk/c4t1d0
--- Physical volumes ---
PV Name /dev/dsk/c4t1d0
VG Name /dev/vg01
PV Status available
Allocatable yes
VGDA 2
Cur LV 2
PE Size (Mbytes) 4
Total PE 17499
Free PE 10249
Allocated PE 7250
Stale PE 0
IO Timeout (Seconds) default
Autoswitch On

:/wdroot# pvdisplay /dev/dsk/c4t0d0
--- Physical volumes ---
PV Name /dev/dsk/c4t0d0
VG Name /dev/vg00
PV Status available
Allocatable yes
VGDA 2
Cur LV 12
PE Size (Mbytes) 16
Total PE 4374
Free PE 2225
Allocated PE 2149
Stale PE 0
IO Timeout (Seconds) default
Autoswitch On

:/wdroot# pvdisplay /dev/dsk/c4t2d0
--- Physical volumes ---
PV Name /dev/dsk/c4t2d0
VG Name /dev/vg02
PV Status available
Allocatable yes
VGDA 2
Cur LV 5
PE Size (Mbytes) 4
Total PE 17499
Free PE 0
Allocated PE 17499
Stale PE 0
IO Timeout (Seconds) default
Autoswitch On

:/wdroot# pvdisplay /dev/dsk/c4t3d0
--- Physical volumes ---
PV Name /dev/dsk/c4t3d0
VG Name /dev/vg02
PV Status available
Allocatable yes
VGDA 2
Cur LV 2
PE Size (Mbytes) 4
Total PE 17499
Free PE 1999
Allocated PE 15500
Stale PE 0
IO Timeout (Seconds) default
Autoswitch On

:/wdroot# pvdisplay /dev/dsk/c4t4d0
--- Physical volumes ---
PV Name /dev/dsk/c4t4d0
VG Name /dev/vg04
PV Status available
Allocatable yes
VGDA 2
Cur LV 23
PE Size (Mbytes) 4
Total PE 17499
Free PE 6224
Allocated PE 11275
Stale PE 0
IO Timeout (Seconds) default
Autoswitch On

:/wdroot# pvdisplay /dev/dsk/c4t5d0
--- Physical volumes ---
PV Name /dev/dsk/c4t5d0
VG Name /dev/vg03
PV Status available
Allocatable yes
VGDA 2
Cur LV 24
PE Size (Mbytes) 4
Total PE 17499
Free PE 15999
Allocated PE 1500
Stale PE 0
IO Timeout (Seconds) default
Autoswitch On

[TTr]

If you are positive these disks don't flake out once in a while then most likely either EMS is very old and needs patching or it needs to be restarted. Check the ems version with "swlist -l fileset | grep EMS" and look at the version number. Another thing to try is /etc/opt/resmon/lbin/monconfig and restart the monitoring.
How often do you get these messages?

[Jayraj]

Here is the EMS version..

EVENT MONITORING IS CURRENTLY ENABLED.
EMS Version : A.04.00.02
STM Version : A.45.00

from apr16(its reboot) almost every day I am getting this messages in my syslog

How to restart the monitoring..?

[TTr]

What happened on or before apr16? Anything changed regarding the disks? Any patches? It seems to me that EMS does not know how to "talk" to the disks and it thinks they are failed. Check for an EMS update or EMS patches for your OS version.

[Matti_Kurkela]

Please run the commands listed in the error messages in the first post. Each of the "resdata" commands should produce a detailed description of the problem, possibly with suggestions on how to solve it included.

/opt/resmon/bin/resdata -R 185729032 -r /storage/events/disks/default/0_3_1_0.2.0 -n 185729276 -a

/opt/resmon/bin/resdata -R 185729047 -r /storage/events/disks/default/0_3_1_0.5.0 -n 185729279 -a

/opt/resmon/bin/resdata -R 185729082 -r /storage/events/disks/default/0_3_1_0.0.0 -n 185729026 -a

/opt/resmon/bin/resdata -R 185729032 -r /storage/events/disks/default/0_3_1_0.2.0 -n 185729027 -a

This might be a SMART notification about a possible failure in the near future. Or if EMS was updated in April 16, the system may be trying to tell you that your disks need a firmware upgrade. Or maybe something else entirely.

Without reading the event details, we can only guess at the real problem.

MK

[Jayraj]

Hi...
Here I have run, the below commands, and attached the reports Here
/opt/resmon/bin/resdata -R 185729082 -r /storage/events/disks/default/0_3_1_0.0.0 -n 185729280 -a


/opt/resmon/bin/resdata -R 185729027 -r /storage/events/disks/default/0_3_1_0.1.0 -n 185729282 -a


/opt/resmon/bin/resdata -R 185729032 -r /storage/events/disks/default/0_3_1_0.2.0 -n 185729281 -a

/opt/resmon/bin/resdata -R 185729037 -r /storage/events/disks/default/0_3_1_0.3.0 -n 185729256 -a

Jul 1:/opt/resmon/bin/resdata -R 185729042 -r /storage/events/disks/default/0_3_1_0.4.0 -n 185729284 -a

[Jayraj]

Seond one