RP7410鎖盤(pán)報(bào)錯(cuò)，請(qǐng)幫忙分析下，多謝！

tonybud

syslog報(bào)錯(cuò)：
Jan 26 03:07:33 dbserver1 cmcld: Unable to query the health of cluster lock disk /dev/dsk/c7t0d0: Device busy
Jan 26 03:07:33 dbserver1 cmcld: Check device, power, and cables.
Jan 26 03:48:48 dbserver1 EMS [3103]: ------ EMS Event Notification ------   Value: "SERIOUS (4)" for Resource: "/storage/events/disks/default/1_0_12_0_0.0.0"     (Threshold:  >= " 3")    Execute the following command to obtain event details:   /opt/resmon/bin/resdata -R 203358216 -r /storage/events/disks/default/1_0_12_0_0.0.0 -n 203358239 -a
Jan 26 04:08:48 dbserver1 cmcld: Unable to query the health of cluster lock disk /dev/dsk/c7t0d0: Device busy
Jan 26 04:08:48 dbserver1 cmcld: Check device, power, and cables.

dbserver1#[</>]/opt/resmon/bin/resdata -R 203358216 -r /storage/events/disks/default/1_0_12_0_0.0.0 -n 203358239 -a

CURRENT MONITOR DATA:

Event Time..........: Tue Jan 26 03:48:48 2010
Severity............: SERIOUS
Monitor.............: disk_em
Event #.............: 100172              
System..............: dbserver1

Summary:
     Disk at hardware path 1/0/12/0/0.0.0 : Device connectivity or hardware
     failure


Description of Error:

     The device was not ready to process requests, but the cause is not
     reportable.

Probable Cause / Recommended Action:

     If the device is a removable medium, this message is informational,
     indicating that I/O was attempted when a diskette was not inserted in the
     drive. Place a diskette in the drive before trying to use it.

     Alternatively, the device may be in a state where it could not process
     this, or any, request. Cycle power to the device.

     Alternatively, there could be more than one device having the same address
     on the SCSI bus. Make all the addresses on the SCSI bus unique.

     Alternatively, one or both of the terminators on the SCSI bus may be
     missing. Install the terminators in their proper locations at the ends of
     the SCSI bus.

     Alternatively, the SCSI cable may have become detached from the device.
     Re-attach the cable.

     Alternatively, the SCSI cable may have failed. Replace it.

     Alternatively, if another entry corresponding to this condition appears in
     the log for this device, the device has experienced a hardware failure.
     Contact your HP support representative to have the device checked.

Additional Event Data:
     System IP Address...: 132.32.21.101
     Event Id............: 0x4b5df5a000000000
     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):
          None
     Additional System Data:
          System Model Number.............: 9000/800/rp7410  
          OS Version......................: B.11.11
          STM Version.....................: A.43.00
          EMS Version.....................: A.04.00
     Latest information on this event:
          http://docs.hp.com/hpux/content/hardware/ems/scsi.htm#100172

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/0/12/0/0.0.0
     Device Class...........: Disk
     Inquiry Vendor ID......: HP 36.4G
     Inquiry Product ID.....: ST336753LC      
     Firmware Version.......: HPC3
     Serial Number..........: 3HX101G400007349WPZ9

Product/Device Identification Information:

     Logger ID.........: disc30; sdisk
     Product Identifier: Disk
     Product Qualifier.: HP 36.4GST336753LC      
     SCSI Target ID....: 0x00
     SCSI LUN..........: 0x00

SCSI Command Data Block:

     Command Data Block Contents:
          0x0000: 00 00 00 00   00 00
     
     Command Data Block Fields (6-byte fmt):
          Command Operation Code...(0x00)..: TEST UNIT READY
          Logical Unit Number..............: 0

Hardware Status:  (not present in log record).
     
SCSI Sense Data:

     Undecoded Sense Data:
          0x0000: 70 00 02 00   00 00 00 0A   00 00 00 00   04 00 02 00
          0x0010: 00 00
     
     SCSI Sense Data Fields:
          Error Code                      : 0x70
          Segment Number                  : 0x00
          Bit Fields:      
               Filemark                   : 0
               End-of-Medium              : 0
               Incorrect Length Indicator : 0
          Sense Key                       : 0x02
          Information Field Valid         : FALSE               
          Information Field               : 0x00000000
          Additional Sense Length         : 10
          Command Specific                : 0x00000000
          Additional Sense Code           : 0x04
          Additional Sense Qualifier      : 0x00
          Field Replaceable Unit          : 0x02
          Sense Key Specific Data Valid   : FALSE               
          Sense Key Specific Data         : 0x00 0x00 0x00
                       
          Sense Key 0x02, NOT READY, indicates that the logical unit addressed
          cannot be accessed.  Operator intervention may be required to correct
          this condition.
                       
          The combination of Additional Sense Code and Sense Qualifier (0x0400)
          indicates: Logical unit not ready, cause not reportable.


dbserver1#[</>]ioscan -fnkCdisk
Class     I  H/W Path        Driver   S/W State   H/W Type     Description
===========================================================================
disk      0  1/0/0/3/0.6.0   sdisk    CLAIMED     DEVICE       HP 36.4GST336753LC
                            /dev/dsk/c0t6d0   /dev/rdsk/c0t6d0
disk      1  1/0/0/3/1.2.0   sdisk    CLAIMED     DEVICE       HP      DVD-ROM 305
                            /dev/dsk/c1t2d0   /dev/rdsk/c1t2d0
disk      2  1/0/1/0/0/1/1.6.0        sdisk    CLAIMED     DEVICE       HP 36.4GMAS3367NC
                            /dev/dsk/c3t6d0   /dev/rdsk/c3t6d0
disk      5  1/0/2/0/0.8.0.108.0.0.0  sdisk    CLAIMED     DEVICE       HP      A6189B
                            /dev/dsk/c5t0d0   /dev/rdsk/c5t0d0
disk      8  1/0/2/0/0.8.0.108.0.0.1  sdisk    CLAIMED     DEVICE       HP      A6189B
                            /dev/dsk/c5t0d1   /dev/rdsk/c5t0d1
disk      9  1/0/2/0/0.8.0.108.0.0.2  sdisk    CLAIMED     DEVICE       HP      A6189B
                            /dev/dsk/c5t0d2   /dev/rdsk/c5t0d2
disk      3  1/0/4/0/0.8.0.110.0.0.0  sdisk    CLAIMED     DEVICE       HP      A6189B
                            /dev/dsk/c4t0d0   /dev/rdsk/c4t0d0
disk      6  1/0/4/0/0.8.0.110.0.0.1  sdisk    CLAIMED     DEVICE       HP      A6189B
                            /dev/dsk/c4t0d1   /dev/rdsk/c4t0d1
disk      7  1/0/4/0/0.8.0.110.0.0.2  sdisk    CLAIMED     DEVICE       HP      A6189B
                            /dev/dsk/c4t0d2   /dev/rdsk/c4t0d2
disk      4  1/0/12/0/0.0.0  sdisk    CLAIMED     DEVICE       HP 36.4GST336753LC
                            /dev/dsk/c7t0d0   /dev/rdsk/c7t0d0

雙機(jī)另一節(jié)點(diǎn)dbserver2也有一樣的報(bào)錯(cuò)，麻煩各位幫忙分析下，多謝。

[ 本帖最后由 tonybud 于 2010-1-26 22:24 編輯 ]

楓葉無(wú)霜

沒(méi)分析出來(lái)。

sinemaw

ioscan -fnCdisk 看下

hbh231

看event log，應(yīng)該是那塊盤(pán)掛了,要換了

可以dd測(cè)試下那塊盤(pán).

ignite

c7t0d0應(yīng)該已經(jīng)壞了，你用diskinfo看看，如果容量為0，那就掛了，也可以用vgdisplay這塊盤(pán)所在的vg，估計(jì)其狀態(tài)已經(jīng)是不可用，這syslog中看，是塊集群鎖盤(pán)，更換時(shí)要小心。

[ 本帖最后由 ignite 于 2010-1-27 11:18 編輯 ]

leelangco

內(nèi)置盤(pán)壞了
檢查vg00吧
不是鎖盤(pán)

livlonhsu

硬件問(wèn)題，不是硬盤(pán)就是總線

tonybud

確認(rèn)了一下，c7t0d0不是本地盤(pán)也不是存儲(chǔ)上的盤(pán)，而是兩臺(tái)主機(jī)都連接了一小盤(pán)柜，盤(pán)柜里就一塊盤(pán)，做雙機(jī)鎖盤(pán)用的。ioscan -fnCdisk看是claimed，diskinfo看大小是0，已經(jīng)申請(qǐng)備件準(zhǔn)備換這塊盤(pán)了。謝謝各位的分析。