VxVM vxdisksetup ERROR V-5-2-43 on newly replaced ...

David_Freer · ‎02-26-2008

Fresh HPUX install, now trying to configure VxVM:

# vxdisk list
DEVICE    TYPE DISK    GROUP STATUS
c4t0d0    auto:hpdisk    rootdisk01 rootdg    online
c4t1d0    auto:cdsdisk - - online
c4t2d0    auto:cdsdisk - - online
c4t3d0    auto:cdsdisk - - online
c4t5d0    auto:cdsdisk - - online
c4t6d0    auto:cdsdisk - - online
c5t8d0    auto:cdsdisk - - online
c5t9d0    auto:cdsdisk - - online
c6t1d0    auto:cdsdisk - - online
c6t2d0    auto:cdsdisk - - online
c6t3d0    auto:cdsdisk - - online
c6t4d0    auto:cdsdisk - - online
c6t5d0    auto:cdsdisk - - online
c6t6d0    auto:cdsdisk - - online
c7t8d0    auto:cdsdisk - - online
c7t9d0    auto:cdsdisk - - online
c7t10d0    auto:none    - - online invalid

Note that c4t4d0, c6t0d0 & c5t10d0 are all missing from vxdisk list.

# ioscan -fnC disk
Class    I H/W Path    Driver S/W State H/W Type    Description
=======================================================================
disk    0 0/0/2/1.2.0 sdisk CLAIMED    DEVICE    HP    DVD-ROM 305
   /dev/dsk/c3t2d0 /dev/dvd-rom    /dev/rdsk/c3t2d0
disk    1 0/10/0/0.0.0 sdisk CLAIMED    DEVICE    HP 36.4GST336607LC
   /dev/dsk/c4t0d0 /dev/rdsk/c4t0d0
disk    2 0/10/0/0.1.0 sdisk CLAIMED    DEVICE    HP 36.4GST336607LC
   /dev/dsk/c4t1d0 /dev/rdsk/c4t1d0
disk    3 0/10/0/0.2.0 sdisk CLAIMED    DEVICE    HP 36.4GST336607LC
   /dev/dsk/c4t2d0 /dev/rdsk/c4t2d0
disk    4 0/10/0/0.3.0 sdisk CLAIMED    DEVICE    FUJITSU MAW3073NC
   /dev/dsk/c4t3d0 /dev/rdsk/c4t3d0
disk    5 0/10/0/0.4.0 sdisk CLAIMED    DEVICE    FUJITSU MAW3073NC
   /dev/dsk/c4t4d0 /dev/rdsk/c4t4d0
disk    6 0/10/0/0.5.0 sdisk CLAIMED    DEVICE    HP 36.4GMAP3367NC
   /dev/dsk/c4t5d0 /dev/rdsk/c4t5d0
disk    7 0/10/0/0.6.0 sdisk CLAIMED    DEVICE    HP 36.4GST336607LC
   /dev/dsk/c4t6d0 /dev/rdsk/c4t6d0
disk    15 0/10/0/1.8.0 sdisk CLAIMED    DEVICE    HP 36.4GST336607LC
   /dev/dsk/c5t8d0 /dev/rdsk/c5t8d0
disk    16 0/10/0/1.9.0 sdisk CLAIMED    DEVICE    HP 36.4GST336607LC
   /dev/dsk/c5t9d0 /dev/rdsk/c5t9d0
disk    17 0/10/0/1.10.0 sdisk CLAIMED    DEVICE    FUJITSU MAW3073NC
   /dev/dsk/c5t10d0 /dev/rdsk/c5t10d0
disk    8 0/12/0/0.0.0 sdisk CLAIMED    DEVICE    FUJITSU MAW3073NC
   /dev/dsk/c6t0d0 /dev/rdsk/c6t0d0
disk    9 0/12/0/0.1.0 sdisk CLAIMED    DEVICE    HP 36.4GST336607LC
   /dev/dsk/c6t1d0 /dev/rdsk/c6t1d0
disk    10 0/12/0/0.2.0 sdisk CLAIMED    DEVICE    HP 36.4GST336607LC
   /dev/dsk/c6t2d0 /dev/rdsk/c6t2d0
disk    11 0/12/0/0.3.0 sdisk CLAIMED    DEVICE    HP 36.4GST336607LC
   /dev/dsk/c6t3d0 /dev/rdsk/c6t3d0
disk    12 0/12/0/0.4.0 sdisk CLAIMED    DEVICE    HP 36.4GST336607LC
   /dev/dsk/c6t4d0 /dev/rdsk/c6t4d0
disk    13 0/12/0/0.5.0 sdisk CLAIMED    DEVICE    HP 36.4GST336607LC
   /dev/dsk/c6t5d0 /dev/rdsk/c6t5d0
disk    14 0/12/0/0.6.0 sdisk CLAIMED    DEVICE    HP 36.4GST336607LC
   /dev/dsk/c6t6d0 /dev/rdsk/c6t6d0
disk    18 0/12/0/1.8.0 sdisk CLAIMED    DEVICE    HP 36.4GST336607LC
   /dev/dsk/c7t8d0 /dev/rdsk/c7t8d0
disk    19 0/12/0/1.9.0 sdisk CLAIMED    DEVICE    HP 36.4GST336607LC
   /dev/dsk/c7t9d0 /dev/rdsk/c7t9d0
disk    20 0/12/0/1.10.0 sdisk CLAIMED    DEVICE    HP 36.4GST336607LC
   /dev/dsk/c7t10d0 /dev/rdsk/c7t10d0

There are no /etc/vx/*.exclude files, and /etc/vx/disk.info does not list the missing drives. vxconfigd -k, vxdisk scandisks and vxdctl enable have all been attempted to sort this out but without success.

# /etc/vx/bin/vxdisksetup -i c4t4d0
VxVM vxdisksetup ERROR V-5-2-43 c4t4d0: Invalid disk device for vxdisksetup

Any suggestions?

Thanks,

David.

David_Freer · ‎02-26-2008

Found the problem, VxVM is seeing c4t3d0 as ALL of the replaced disks. How can this be undone?

# vxdisk list c4t3d0
Device:    c4t3d0
devicetag: c4t3d0
type:      auto
hostid:
disk:      name= id=1203411685.113.loopback
group:     name= id=1203410389.103.loopback
info:      format=cdsdisk,privoffset=128
flags:     online ready private autoconfig
pubpaths: block=/dev/vx/dmp/c4t3d0 char=/dev/vx/rdmp/c4t3d0
version:   3.1
iosize:    min=512 (bytes) max=256 (blocks)
public:    slice=0 offset=1152 len=71815272 disk_offset=0
private:   slice=0 offset=128 len=1024 disk_offset=0
update:    time=1203943437 seqno=0.14
ssb:       actual_seqno=0.1
headers:   0 120
configs:   count=1 len=640
logs:      count=1 len=96
Defined regions:
config   priv 000024-000119[000096]: copy=01 offset=000000 enabled
config   priv 000128-000671[000544]: copy=01 offset=000096 enabled
log      priv 000672-000767[000096]: copy=01 offset=000000 enabled
lockrgn priv 000768-000839[000072]: part=00 offset=000000
Multipathing information:
numpaths:   4
c4t3d0 state=enabled
c4t4d0 state=enabled
c5t10d0 state=enabled
c6t0d0 state=enabled

sunshine_2 · ‎03-17-2008

as seen in the # vxdisk list c4t3d0

Multipathing information:
numpaths:   4
c4t3d0 state=enabled   -   primary disk path
c4t4d0 state=enabled   -   secondary path for the c4t3d0 disk
c5t10d0 state=enabled   -   secondary path for the c4t3d0 disk
c6t0d0 state=enabled   -   secondary path for the c4t3d0 disk

you can also confirm by running

# vxdisk path or vxdisk -e list or

vxdmpadm getdmpnode enclosure=<enclosure name>

you can get the enclosure name from

vxdmpadm listctlr all

Jeffrey_S · ‎05-15-2008

I'm assuming you've fixed this, but did you try killing vxconfigd, removing /etc/vx/disk.info and then restarting vxconfigd to recreate the disk.info file?

VOX

VxVM vxdisksetup ERROR V-5-2-43 on newly replaced disks.