恳请老虾指点－在hp小型机上无法进行任何与阵列柜磁盘的操作

dsamsh

小型机hp4440 2台        1主机system灯呈 黄色  （？）
磁盘柜EVA4000+DL380     2控制器的第四灯呈 黄色 （？）－两个交叉椭圆 1为第四灯 从上至下

第一次ioscan -funC disk无法找到磁盘柜磁盘
/sbin/init.d/hparray start启动无效
后手工启动/opt/hparray/bin/ARMServer
reboot后ioscan能发现外置磁盘
# arraydsp -i
Arrays known to the ARMServer:
No arrays were found by the ARMServer
# armdsp -i
sh: armdsp:  not found.
备机# armdsp -i
Error logging in: TIMEOUT EXPIRED
＃vgchange -a y vgdata 出现僵死
＃vgscan 同样僵死
任何与外置磁盘柜的操作进程全部僵死 ctr+c无用 只有关闭窗口 恳请高手解决

[ 本帖最后由 dsamsh 于 2006-6-4 19:42 编辑 ]

dsamsh

两个交叉椭圆
如果该指示灯亮绿色，表示从存储到主机和管理服务器的link 正常。如不亮，请检查链路是否
有问题；黄？？？？

lu407

不知道lz都在做什么操作？？arraydsp??autoraid??armdsp??
把ioscan -fnCdisk的输出..string /etc/lvmtab的输出 打出来。。
你确认你的eva是正常的不？用dl380上的commandview EVA检查一下。。

aaaajack

arraydsp是针对AUTORAID 12H的AM60命令集,对VA(armdsp)EVA(commandview eva)不适用.
rp4440 system灯亮黄了,只能说明是attention灯亮了,MP有新LOG需要关注,
EVA4000 controller最底下的小灯也是attention灯,用command view eva去检查一吓吧.
DL380只是SMA SERVER,管理EVA用的.

ioscan -fnCdisk看到的EVA盘是CLAIMED吗?
diskinfo /dev/rdsk/c*t*d* 看EVA的盘是什么状态呢?

/dev/vgdata是什么卷组??是在cluster下激活的卷组么???vgdisplay -v /dev/vgdata显示的是什么状态??
主机连EVA4000应该还有SAN SWITCH吧??从SWITCH上看EVA状态呢??

能用rp4440+EVA4000也是企业重要的业务吧??建议楼主摸清楚了HPUX命令才去搞系统.

dsamsh

谢谢两位。

ioscan -fnCdisk看到的EVA盘是CLAIMED
cmruncl -v -f ...
然后vgdisplay -v /dev/vgdata
僵死......
SWITCH上如何看EVA状态？灯？

能提供EVA4000相关资料吗？感激ing    enable_d3@yahoo.com.cn

dsamsh

输出大概需要等待20至30分钟或更久
   
# pvdisplay /dev/dsk/c4t0d3              
pvdisplay: Warning: couldn't query physical volume "/dev/dsk/c4t0d3":
The specified path does not correspond to physical volume attached to
this volume group
pvdisplay: Warning: couldn't query physical volume "/dev/dsk/c8t0d3":
The specified path does not correspond to physical volume attached to
this volume group
pvdisplay: Warning: couldn't query physical volume "/dev/dsk/c10t0d3":
The specified path does not correspond to physical volume attached to
this volume group
pvdisplay: Warning: couldn't query physical volume "/dev/dsk/c12t0d3":
The specified path does not correspond to physical volume attached to
this volume group
pvdisplay: Warning: couldn't query all of the physical volumes.
pvdisplay: Couldn't retrieve the names of the physical volumes
belonging to volume group "/dev/vgdata".
pvdisplay: Cannot display physical volume "/dev/dsk/c4t0d3".

# vgchange -c n /dev/vgdata
vgchange: Warning: Couldn't attach to the volume group physical volume "/dev/dsk/c4t0d3":
The path of the physical volume refers to a device that does not exist, or is not configured into the kernel.
vgchange: Warning: Couldn't attach to the volume group physical volume "/dev/dsk/c8t0d3":
The path of the physical volume refers to a device that does not exist, or is not configured into the kernel.
vgchange: Warning: Couldn't attach to the volume group physical volume "/dev/dsk/c10t0d3":
The path of the physical volume refers to a device that does not exist, or is not configured into the kernel.
vgchange: Warning: Couldn't attach to the volume group physical volume "/dev/dsk/c12t0d3":
The path of the physical volume refers to a device that does not exist, or is not configured into the kernel.
vgchange: Could not attach to volume group "/dev/vgdata" all of its physical volumes.
vgchange: Warning: couldn't query physical volume "/dev/dsk/c4t0d3":
The specified path does not correspond to physical volume attached to this volume group
vgchange: Warning: couldn't query physical volume "/dev/dsk/c8t0d3":
The specified path does not correspond to physical volume attached to this volume group
vgchange: Warning: couldn't query physical volume "/dev/dsk/c10t0d3":
The specified path does not correspond to physical volume attached to this volume group
vgchange: Warning: couldn't query physical volume "/dev/dsk/c12t0d3":
The specified path does not correspond to physical volume attached to this volume group
vgchange: Warning: couldn't query all of the physical volumes.

# vgcfgrestore -n /dev/vgdata /dev/rdsk/c4t0d3
Warning: Cannot determine block size of Physical Volume "/dev/rdsk/c4t0d3".
Assuming a default value of 1024 bytes. Continuing.
vgcfgrestore: IO error on Physical Volume device /dev/rdsk/c4t0d3:

# diskinfo /dev/rdsk/c4t0d3
SCSI describe of /dev/rdsk/c4t0d3:
             vendor: HP      
         product id: HSV200         
               type: direct access
               size: 0 Kbytes
   bytes per sector: 0


感谢google

Disk Drive  



HotPlug Disk Drive Removal



The internal disk drives (up to four) are located at the front right side of the server (as you are facing it). When proper software and hardware procedures are followed, internal disk drives can be removed and replaced while the server is running.

The procedures in this section are in two parts, a HotSwap Software Procedure and a HotPlug Hardware Procedure for removing the disk from the server.

Before starting these procedures, you must have an up-to-date configuration backup file. Configuration backup is performed by default each time an LVM command changes the LVM configuration. The default backup files path is:

/etc/lvmconf/base_vg_name.conf.




The replacement disk drive must be the same product ID as the disk drive that is being replaced.


--------------------------------------------------------------------------------
HP often uses different manufacturers for disks that have the same product number. The HotSwap and HotPlug procedures will not update the disk drives internal information to that of the replaced disk drive.

--------------------------------------------------------------------------------

The replacement disk drive will have the same capacity and blocksize as the defective disk because they have the same product number. The only field the can be incorrect is the string specifying the vendor's name. This will not affect the behavior of the LVM. If you desire to update the manufacturer's name, the disks volume group must be deactivated and reactivated.

HotSwap Software Procedure

Perform these software procedural steps to replace a HotPlug disk drive device:

Step 1.  Determine whether the LVM found the physical volume to be defective when the volume group was activated.

If the volume was defective when the volume group was activated, vgchange would have generated the following message to the console:

WARNING

VGCHANGE: WARNING: COULDN'T ATTACH TO THE VOLUME GROUP PHYSICAL
VOLUME "/DEV/DSK/cXtXdX"

VGCHANGE: WARNING: COULDN'T ATTACH TO THE VOLUME GROUP PHYSICAL
VOLUME "/DEV/DSK/cXtXdX"

THE PATH OF THE PHYSICAL VOLUME REFERS TO A DEVICE THAT DOES NOT
EXIST, OR IS NOT CONFIGURED INTO THE KERNAL.


If you are unsure of the status of the vgchange, you may check if this occurred by doing a vgdisplay command:

#vgdisplay <VG name>

For example:

# vgdisplay /dev/vg00

If the disk was defective at vgchange time, the following message will be printed one or more times:

WARNING:

VGDISPLAY: WARNING: COULDN'T QUERY PHYSICAL VOLUME "/DEV/DSK/cXtXdX"
THE SPECIFIED PATH DOES NOT CORRESPOND TO PHYSICAL VOLUME ATTACHED TO THE
VOLUME GROUP.

VGDISPLAY: WARNING: COULDN'T QUERY ALL

dsamsh

......
For example:

# vgdisplay /dev/vg00

If the disk was defective at vgchange time, the following message will be printed one or more times:

WARNING:

VGDISPLAY: WARNING: COULDN'T QUERY PHYSICAL VOLUME "/DEV/DSK/cXtXdX"
THE SPECIFIED PATH DOES NOT CORRESPOND TO PHYSICAL VOLUME ATTACHED TO THE
VOLUME GROUP.

VGDISPLAY: WARNING: COULDN'T QUERY ALL OF THE PHYSICAL VOLUMES.


If you see these messages, the disk was defective at the time the volume group was activated. Remove the bad disk as described in step 9 of this procedure. Then follow the instructions in Disk Drive Replacement for replacing the disk and perform the HotSwap Procedure for Unattached Physical Volumes described there.

Otherwise, your disk drive became defective after the vgchange and you must continue with step 2 of this section.

......

link：http://avsfans.org/GARY/L_CLASS/lclasscd/content/02/210-con.html

zwt72

EVA是用 DL380上的commadview看啊    有没有报错  armdsp?那是 VA............