errpt报DISK OPERATION ERROR，但使用正常，需要怎样处理？

sygdwg

AIX5。2操作系统，POWERPATH4。2，CX700存储，最近在对LUN从一个storage group移动到另一个storage group后，在系统中做importvg等对磁盘的系统级操作时，errpt中会报DISK OPERATION ERROR的错误。有时候有几行错误，有时候有几十行错误，但是应用的运行一点问题没有，请问这是否为严重问题，该如何操作，可以使系统中不再报错？
errpt
DCB47997   0710093106 T H hdisk21        DISK OPERATION ERROR
DCB47997   0707155506 T H hdisk55        DISK OPERATION ERROR

errpt -a
---------------------------------------------------------------------------
LABEL:                SC_DISK_ERR4
IDENTIFIER:        DCB47997

Date/Time:       Mon Jul 10 09:31:12 BEIS
Sequence Number: 523
Machine Id:      
Node Id:         
Class:           H
Type:            TEMP
Resource Name:   hdisk21         
Resource Class:  disk
Resource Type:   CLAR_FC_raid10
Location:        U1.5-P1-I5/Q1-W5006016110602717-L11000000000000
VPD:            
        Manufacturer................DGC     
        Machine Type and Model......RAID 10         
        ROS Level and ID............0207
        Serial Number...............
        Device Specific.(SI)........CX700
        Device Specific.(PQ)........00
        Device Specific.(VS)........32000045D9CL
        Device Specific.(UI)........60060160F95411000D1F64532E48D911
        Device Specific.(FL)........0032
        Device Specific.(Z0)........10
        Device Specific.(Z1)........10

Description
DISK OPERATION ERROR

Probable Causes
MEDIA
DASD DEVICE

User Causes
MEDIA DEFECTIVE

        Recommended Actions
        FOR REMOVABLE MEDIA, CHANGE MEDIA AND RETRY
        PERFORM PROBLEM DETERMINATION PROCEDURES

Failure Causes
MEDIA
DISK DRIVE

        Recommended Actions
        FOR REMOVABLE MEDIA, CHANGE MEDIA AND RETRY
        PERFORM PROBLEM DETERMINATION PROCEDURES

Detail Data
PATH ID
           0
SENSE DATA
0A00 2A00 01EB E020 0000 1004 0000 0000 0000 0000 0000 0000 0200 0300 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0001 D9AE 0008 A080 0000 0006 0000 0000 0000 0000 0000 0000 0000
0000 0035 001D
---------------------------------------------------------------------------
LABEL:                SC_DISK_ERR4
IDENTIFIER:        DCB47997

Date/Time:       Fri Jul  7 15:55:07 BEIS
Sequence Number: 522
Machine Id:      
Node Id:         
Class:           H
Type:            TEMP
Resource Name:   hdisk55         
Resource Class:  disk
Resource Type:   CLAR_FC_raid10
Location:        U1.5-P2-I8/Q1-W5006016010602717-LF000000000000
VPD:            
        Manufacturer................DGC     
        Machine Type and Model......RAID 10         
        ROS Level and ID............0207
        Serial Number...............
        Device Specific.(SI)........CX700
        Device Specific.(PQ)........00
        Device Specific.(VS)........30000045C8CL
        Device Specific.(UI)........60060160F95411000B1F64532E48D911
        Device Specific.(FL)........0030
        Device Specific.(Z0)........10
        Device Specific.(Z1)........10

Description
DISK OPERATION ERROR

Probable Causes
MEDIA
DASD DEVICE

User Causes
MEDIA DEFECTIVE

        Recommended Actions
        FOR REMOVABLE MEDIA, CHANGE MEDIA AND RETRY
        PERFORM PROBLEM DETERMINATION PROCEDURES

Failure Causes
MEDIA
DISK DRIVE

        Recommended Actions
        FOR REMOVABLE MEDIA, CHANGE MEDIA AND RETRY
        PERFORM PROBLEM DETERMINATION PROCEDURES

Detail Data
PATH ID
           0
SENSE DATA
0A00 2A00 00B8 74E8 0000 1004 0000 0000 0000 0000 0000 0000 0200 0300 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 6471 0006 F9C0 0000 0006 0000 0000 0000 0000 0000 0000 0000
0000 0035 001D

zlg88

去问EMC的工程师，你得到的答复肯定是“不用管它，这是误报”

Jens

最好换掉硬盘。

mygod1997

是用raid做的吗？最好连根线进去看看

yddll

我们这儿从开始安装到现在,一直就有这个问题,EMC的人说是正常,不用管它.

我一直比较担心的是,如果有一天我们习惯这些报错了,真有一天真的有问题了,却以为是正常的,那就麻烦了.......

hgh25emus

我也遇到同样的问题，开始emc的工程师来，做了下修改，后来好了，最近又有这种报错，但对应用是不影响。
的。其实你会发现不一定importvg 会引发这种出错，我重启ha或数据库都会出这种错的。
我有个他们当初的处理文档给你不知道你敢不敢用？

hgh25emus

EMC Knowledgebase


"How to remove LUNZ devices"



                 



                                       

Knowledgebase Solution         
               
        Question:
How to remove LUNZ devices
Environment:
Product: CLARiiON
Environment:
EMC SW: Navisphere CLI
Environment:
EMC SW: Navisphere
Environment:
OS: IBM AIX
Problem:
Why do LUNZ devices appear on an AIX host even though storage is attached?
Problem:
LUNZ devices appear after running cfgmgr, but were not there previously.
Change:
The ALU (Array LUN Unit) associated with HLU (Host LUN Unit) 0 was removed from the Storage Group.
Change:
CLARiiON LUNs attached to host.
Fix:
Fix 1:
Disable arraycommpath using navicli:
1.        lsdev -Cc disk | grep LUNZ to get a list of the hdisk devices that are LUNZ devices.
2.        rmdev -dl hdiskn for every LUNZ device, where n is the hdisk number of the LUNZ
3.        navicli -h <SP_IP_address> storagegroup -sethost -host <hostname> -arraycommpath 0
4.        Run cfgmgr on the host.
5.        Run INQ to verify LUNZ devices are now gone.
Fix 2:
Create a new LUN:
1.        Bind a small LUN.
2.        Add the LUN to the Storage Group in question.
3.        Before applying the configuration scroll the "Selected LUNs" field to the right.
4.        Change the "Host ID" field to 0 by clicking the blank space and choosing from the drop down menu.
5.        Run cfgmgr on the host.
6.        Run INQ to verify LUNZ devices are now gone.

hgh25emus

这个问题最后的处理结果，希望能告知大家。

hgh25emus

Problem:
Why do LUNZ devices appear on an AIX host even though storage is attached?
Problem:
LUNZ devices appear after running cfgmgr, but were not there previously.
Change:
The ALU (Array LUN Unit) associated with HLU (Host LUN Unit) 0 was removed from the Storage Group.
Change:
CLARiiON LUNs attached to host.
这个就是问题产生的原因，所以要消除LUNZ devices

星海夜航

正常现象，但host中出现lunz设备本身就说明有问题