L3000报错，各位大虾帮帮看看怎么回事？小弟初识hp设备。

Question

系统的syslog报错：
ay  3 07:23:15 hntest01 vmunix:    errors from the I/O subsystem.  I/O error entries will be lost
May  3 07:23:15 hntest01 vmunix:    to determine which I/O subsystem is logging excessive errors.
May  3 07:23:17 hntest01 vmunix:    errors from the I/O subsystem.  3 I/O error entries were lost.
May  3 15:59:08 hntest01 vmunix:    errors from the I/O subsystem.  I/O error entries will be lost
May  3 15:59:08 hntest01 vmunix:    to determine which I/O subsystem is logging excessive errors.
May  3 15:59:16 hntest01 vmunix:    errors from the I/O subsystem.  12 I/O error entries were lost.
May  4 06:33:51 hntest01 vmunix:    errors from the I/O subsystem.  I/O error entries will be lost
May  4 06:33:51 hntest01 vmunix:    to determine which I/O subsystem is logging excessive errors.
May  4 06:35:14 hntest01 vmunix:    errors from the I/O subsystem.  7 I/O error entries were lost.

dmesg也报错：
hntest01:/var/adm/syslog #more syslog.log|grep EMS
May  2 21:07:39 hntest01 EMS [7530]: ------ EMS Event Notification ------   Value: "CRITICAL (5)" for Resource: "/storage/events/disks/default/0_0_1_1.2.0"     (Threshold:  >= " 3"    Execute the following command to obtain event details:   /opt/resmon/bin/resdata -R 493486082 -r /storage/events/disks/default/0_0_1_1.2.0 -n 493486116 -a
May  2 21:08:51 hntest01 EMS [7530]: ------ EMS Event Notification ------   Value: "CRITICAL (5)" for Resource: "/storage/events/disks/default/0_0_1_1.2.0"     (Threshold:  >= " 3"    Execute the following command to obtain event details:   /opt/resmon/bin/resdata -R 493486082 -r /storage/events/disks/default/0_0_1_1.2.0 -n 493486117 -a
May  3 17:12:33 hntest01 EMS [7530]: ------ EMS Event Notification ------   Value: "CRITICAL (5)" for Resource: "/storage/events/disks/default/0_0_1_1.2.0"     (Threshold:  >= " 3"    Execute the following command to obtain event details:   /opt/resmon/bin/resdata -R 493486082 -r /storage/events/disks/default/0_0_1_1.2.0 -n 493486118 -a
May  3 18:05:34 hntest01 EMS [7530]: ------ EMS Event Notification ------   Value: "CRITICAL (5)" for Resource: "/storage/events/disks/default/0_0_1_1.2.0"     (Threshold:  >= " 3"    Execute the following command to obtain event details:   /opt/resmon/bin/resdata -R 493486082 -r /storage/events/disks/default/0_0_1_1.2.0 -n 493486119 -a
May  3 21:08:25 hntest01 EMS [7530]: ------ EMS Event Notification ------   Value: "CRITICAL (5)" for Resource: "/storage/events/disks/default/0_0_1_1.2.0"     (Threshold:  >= " 3"    Execute the following command to obtain event details:   /opt/resmon/bin/resdata -R 493486082 -r /storage/events/disks/default/0_0_1_1.2.0 -n 493486120 -a
May  3 21:11:27 hntest01 EMS [7530]: ------ EMS Event Notification ------   Value: "CRITICAL (5)" for Resource: "/storage/events/disks/default/0_0_1_1.2.0"     (Threshold:  >= " 3"    Execute the following command to obtain event details:   /opt/resmon/bin/resdata -R 493486082 -r /storage/events/disks/default/0_0_1_1.2.0 -n 493486121 -a
hntest01:/var/adm/syslog # /opt/resmon/bin/resdata -R 493486082 -r /storage/events/disks/default/0_0_1_1.2.0 -n 493486121 -a

CURRENT MONITOR DATA:

Event Time..........: Tue May  3 21:11:26 2011
Severity............: CRITICAL
Monitor.............: disk_em
Event #.............: 101137              
System..............: hntest01

Summary:
     Disk at hardware path 0/0/1/1.2.0 : Media failure

Description of Error:

     The device was unsuccessful in reading or writing data for the current I/O
     request due to an error on the medium. The data could not be recovered.

Probable Cause / Recommended Action:

     Reformatting the medium may fix the problem.

     Alternatively, the medium in the device is flawed. If the medium is
     removable, replace the medium with a fresh one.

     Alternatively, if the medium is not removable, the device has experienced
     a hardware failure. Repair or replace the device, as necessary.

Additional Event Data:
     System IP Address...: 130.76.1.90
     Event Id............: 0x4dbffefe00000000
     Monitor Version.....: B.01.00
     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):
          0x4dbffefe00000000
     Additional System Data:
          System Model Number.............: 9000/800/L3000-5x
          OS Version......................: B.11.11
          STM Version.....................: A.26.00
          EMS Version.....................: A.03.20
     Latest information on this event:
          http://docs.hp.com/hpux/content/hardware/ems/scsi.htm

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/0/1/1.2.0
     Device Class...........: Disk
     Inquiry Vendor ID......: SEAGATE
     Inquiry Product ID.....: ST336704LC      
     Firmware Version.......: HP03
     Serial Number..........: 3CD2ARRX00002206CG0T

Product/Device Identification Information:

     Logger ID.........: sdisk
     Product Identifier: SCSI Disk
     Product Qualifier.: SEAGATEST336704LC
     SCSI Target ID....: 0x02
     SCSI LUN..........: 0x00

I/O Log Event Data:

     Driver Status Code..................: 0x0000007C
     Length of Logged Hardware Status....: 22 bytes.
     Offset to Logged Manager Information: 24 bytes.
     Length of Logged Manager Information: 34 bytes.

Hardware Status:

     Raw H/W Status:
          0x0000: 00 00 00 02   F0 00 03 00   C1 98 08 0A   00 00 00 00
          0x0010: 03 00 10 80   00 18

     SCSI Status...: CHECK CONDITION (0x02)
          Indicates that a contingent allegiance condition has occurred.  Any
          error, exception, or abnormal condition that causes sense data to be
          set will produce the CHECK CONDITION status.
     
SCSI Sense Data:

     Undecoded Sense Data:
          0x0000: F0 00 03 00   C1 98 08 0A   00 00 00 00   03 00 10 80
          0x0010: 00 18
     
     SCSI Sense Data Fields:
          Error Code                      : 0x70
          Segment Number                  : 0x00
          Bit Fields:      
               Filemark                   : 0
               End-of-Medium              : 0
               Incorrect Length Indicator : 0
          Sense Key                       : 0x03
          Information Field Valid         : TRUE
          Information Field               : 0x00C19808
          Additional Sense Length         : 10
          Command Specific                : 0x00000000
          Additional Sense Code           : 0x03
          Additional Sense Qualifier      : 0x00
          Field Replaceable Unit          : 0x10
          Sense Key Specific Data Valid   : TRUE
          Sense Key Specific Data         : 0x80 0x00 0x18
                       
          Sense Key 0x03, MEDIUM ERROR, indicates that the command terminated
          with a nonrecovered error condition that was probably caused by a
          flaw in the medium or an error in the recorded data.  This sense key
          may also be returned if the device is unable to distinguish between a
          flaw in the medium and a specific hardware failure (sense key 0x04).
          For the RECOVERED ERROR, HARDWARE ERROR, or MEDIUM ERROR Sense Key,
          the Sense Key Specific data indicates that 24 retries were attempted.
                       
          The combination of Additional Sense Code and Sense Qualifier (0x0300)
          indicates: Peripheral device write fault.

SCSI Command Data Block:

     Command Data Block Contents:
          0x0000: 2A 00 00 C1   98 08 00 00   04 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............: 12687368 (0x00C1980
          Transfer Length..................: 4 (0x0004)

Manager-Specific Data Fields:
     Request ID.............: 0x01DF1166
     Data Residue...........: 0x00000000
     CDB status.............: 0x00000002
     Sense Status...........: 0x00000000
     Bus ID.................: 0x01
     Target ID..............: 0x02
     LUN ID.................: 0x00
     Sense Data Length......: 0x12
     Q Tag..................: 0x77
     Retry Count............: 0

event.log日志报错信息如下：
hntest01:/var/adm/syslog #cd /var/opt/resmon/log
hntest01:/var/opt/resmon/log #ll
total 1400
lrwxr-xr-x   1 bin        bin             27 Sep 14  2001 api.log -> /etc/opt/resmon/log/api.log
lrwxr-xr-x   1 bin        bin             30 Sep 14  2001 client.log -> /etc/opt/resmon/log/client.log
-rw-r--r--   1 root       root        195643 May  4 01:15 event.log
-r--r-----   1 root       root        503689 May  9  2010 event.log1
lrwxr-xr-x   1 bin        bin             33 Sep 14  2001 registrar.log -> /etc/opt/resmon/log/registrar.log
hntest01:/var/opt/resmon/log #tail -300 event.log
     Serial Number..........: 3CD2ARRX00002206CG0T

Product/Device Identification Information:

     Logger ID.........: sdisk
     Product Identifier: SCSI Disk
     Product Qualifier.: SEAGATEST336704LC
     SCSI Target ID....: 0x02
     SCSI LUN..........: 0x00

I/O Log Event Data:

     Driver Status Code..................: 0x00000000
     Length of Logged Hardware Status....: 4 bytes.
     Offset to Logged Manager Information: 8 bytes.
     Length of Logged Manager Information: 34 bytes.

Hardware Status:

     Raw H/W Status:
          0x0000: 00 00 00 00  

     SCSI Status...: GOOD (0x00)
          Indicates that the target has successfully completed the command.

SCSI Sense Data: (not present in log record)

SCSI Command Data Block:

     Command Data Block Contents:
          0x0000: 2A 00 00 C1   1A E2 00 00   02 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............: 12655330 (0x00C11AE2)
          Transfer Length..................: 2 (0x0002)

Manager-Specific Data Fields:
     Request ID.............: 0x01DF0B8B
     Data Residue...........: 0x00000000
     CDB status.............: 0x00000000
     Sense Status...........: 0x00000000
     Bus ID.................: 0x01
     Target ID..............: 0x02
     LUN ID.................: 0x00
     Sense Data Length......: 0x00
     Q Tag..................: 0x78
     Retry Count............: 2

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

但是查看设备面板灯硬盘正常，pvdisplay和diskinfo均正常啊？就是查看该硬盘i/o的时候发现有点高啊，具体如下：
ntest01:/var/opt/resmon/log #sar -d 1 10

HP-UX hntest01 B.11.11 U 9000/800    05/04/11

09:15:00   device   %busy   avque   r+w/s  blks/s  avwait  avserv
09:15:01   c1t2d0   69.31    0.50      46     194    5.41   32.17
           c2t2d0   23.76    0.50      42     178    5.49    7.69
09:15:02   c1t2d0  100.00    0.77      55     272    7.76   67.93
           c2t2d0   30.00    0.50      50     252    5.40   11.10
09:15:03   c1t2d0   62.00    0.50      32     168    5.86   24.27
           c2t2d0   19.00    0.50      26     144    5.69    7.16
09:15:04   c1t2d0   55.00    0.50      14     112    5.88  130.75
           c2t2d0    9.00    0.50      11     100    5.76   14.60
09:15:05   c1t2d0   20.79    0.50      15      59    5.47   37.52
           c2t2d0    7.92    0.50      13      51    5.23   18.08
09:15:06   c1t2d0   12.12    0.50       6      24    5.22   33.49
           c2t2d0    3.03    0.50       4      16    5.00    8.06
09:15:07   c1t2d0   21.00    0.50      12      44    6.39   47.43
           c2t2d0    4.00    0.50      10      36    6.86   12.78
09:15:08   c1t2d0   36.00    0.50      16     112    6.08   67.52
           c2t2d0   10.00    0.50      12      96    5.95   14.49
09:15:09   c1t2d0   14.00    0.50      10      52    4.31   42.27
           c2t2d0    4.00    0.50       8      44    3.75    8.04
09:15:10   c1t2d0   17.00    0.50      10      52    4.31   37.17
           c2t2d0    2.00    0.50       8      44    4.07    9.13
求大虾帮忙看看怎么回事啊？

Answer 1

用dd命令测试一下，应该是盘挂了

Answer 2

盘有问题喽