cancel
Showing results for 
Search instead for 
Did you mean: 

AIX: vxdisksetup error: invalid disk device for vxdisksetup

Chip_EMC
Level 2

Hello,

I have an issue on AIX 5.3 when running vxdisksetup and I've searched high and low but can't find a solution.

# /etc/vx/bin/vxdisksetup -i hdisk48

"VxVM vxdisksetup ERROR V-5-2-43 hdisk48: Invalid disk device for vxdisksetup"

I'm adding (4) new devices from a EMC CLARiiON array. I was able to successfully initilaize (3) of the devices but, for some reason, I can't initialize the 4th device.

I've ran:

vxdisk path

vxdmpadm getdmpnode enclosure=EMC_CLARiiON0

vxdmpadm getdmpnode nodename=hdisk48

So far, it looks like everything is in place so I'm not sure what's going on. I found this technote but it's for Solaris:

http://www.symantec.com/business/support/index?page=content&id=TECH9605

Is there a similar procedure for AIX? Or, does anyone have commands I could run.

If the information is too vague, let me know and I can provide additional information.

Thanks in advance

-Chip

3 REPLIES 3

Gaurav_S
Moderator
Moderator
   VIP    Certified

need more outputs

# vxdisk list

# lslpp -l |grep -i vxvm

# vxdisk list hdisk48

tried device tree cleaning ?

http://sfdoccentral.symantec.com/sf/5.1SP1/aix/html/dmp_admin/ch06s02s01.htm

 

G

Chip_EMC
Level 2
#vxdisk list

DEVICE       TYPE            DISK       GROUP    STATUS
hdisk0       auto:LVM        -          -        LVM
hdisk1       auto:LVM        -          -        LVM
hdisk2       auto:none       -          -        online invalid
hdisk3       auto:cdsdisk    dg04vg001  dg04vg   online
hdisk4       auto:cdsdisk    dg01vg001  dg01vg   online
hdisk5       auto:cdsdisk    dg01vg002  dg01vg   online
hdisk6       auto:cdsdisk    dg01vg003  dg01vg   online
hdisk7       auto:cdsdisk    dg01vg004  dg01vg   online
hdisk8       auto:cdsdisk    dg04vg002  dg04vg   online
hdisk9       auto:cdsdisk    dg04vg003  dg04vg   online
hdisk10      auto:cdsdisk    dg04vg004  dg04vg   online
hdisk11      auto:cdsdisk    loc1vg001  loc1vg   online
hdisk12      auto:cdsdisk    dg02vg001  dg02vg   online
hdisk24      auto:cdsdisk    dg04vg01   dg04vg   online
hdisk25      auto:cdsdisk    dg04vg02   dg04vg   online
hdisk45      auto:cdsdisk    -          -        online
hdisk46      auto:cdsdisk    -          -        online
hdisk47      auto:cdsdisk    -          -        online
hdisk48      auto:none       -          -        online invalid


#lslpp -l | grep -i vxvm
Enter NIS Password:

  VRTSvxvm                  5.0.1.50  COMMITTED  Veritas Volume Manager by
  VRTSvxvm                  5.0.1.50  COMMITTED  Veritas Volume Manager by

#xdisk list hdisk48
Device:    hdisk48
devicetag: hdisk48
type:      auto
info:      format=none
flags:     online ready private autoconfig invalid
pubpaths:  block=/dev/vx/dmp/hdisk48 char=/dev/vx/rdmp/hdisk48
guid:      -
udid:      DGC%5FRAID%205%5FAPM00064606993%5F6006016057531A0094F623AB5FAEE111
site:      -
Multipathing information:
numpaths:   4
hdisk8  state=enabled   type=secondary
hdisk12 state=enabled   type=primary
hdisk48 state=enabled   type=secondary
hdisk52 state=enabled   type=primary

-------

The (4) new devices are hdisk45-48. hdisk45-47 initialized without any issues. Only hdisk48 generates the vxdisksetup error.

 

I did not perform a device tree clean-up.

 

Thanks

-Chip

Gaurav_S
Moderator
Moderator
   VIP    Certified

Can u also paste a vxdisk list output of a good device ..

# vxdisk list hdisk47

# vxdisk -e list

also, are u using any cluster software ? specially VCS with IOfencing ? could be a remote chance that this device was provisioned to a cluster before which was using IOfencing , so can u check this command

# /sbin/vxfenadm -g /dev/vx/rdmp/hdisk48

 

If all above step looks clean, next I would recommend to double check from storage end if device is presented cleanly as other devices are, if yes, then would recommend for a device tree cleanup ....

http://www.symantec.com/docs/TECH184839

 

G