RP7410锁盘报错,请帮忙分析下,多谢!

发布于 2022-08-24 05:49:40 字数 13705 浏览 9 评论 7

syslog报错:
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

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

双机另一节点dbserver2也有一样的报错,麻烦各位帮忙分析下,多谢。

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

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(7

半世蒼涼 2022-09-04 13:38:37

确认了一下,c7t0d0不是本地盘也不是存储上的盘,而是两台主机都连接了一小盘柜,盘柜里就一块盘,做双机锁盘用的。ioscan -fnCdisk看是claimed,diskinfo看大小是0,已经申请备件准备换这块盘了。谢谢各位的分析。

清音悠歌 2022-09-04 13:34:37

硬件问题,不是硬盘就是总线

窗影残 2022-09-04 13:24:29

内置盘坏了
检查vg00吧
不是锁盘

女中豪杰 2022-09-04 11:30:16

c7t0d0应该已经坏了,你用diskinfo看看,如果容量为0,那就挂了,也可以用vgdisplay这块盘所在的vg,估计其状态已经是不可用,这syslog中看,是块集群锁盘,更换时要小心。

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

执手闯天涯 2022-09-04 09:23:22

看event log,应该是那块盘挂了,要换了

可以dd测试下那块盘.

不知所踪 2022-09-04 05:58:47

ioscan -fnCdisk 看下

贵在坚持 2022-09-03 14:41:07

没分析出来。

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文