vxdisksetup error

Question

Hi,
I am having problem initializing the disk with "vxdisksetup".&nbsp; These are the LUNS which were removed from veritas &amp; storage , and&nbsp;have been re-allocated back to the same system.&nbsp; I can see the disks from OS and also in veritas but with "error" status.&nbsp;
vxdisksetup exits with the following error, but I can see the&nbsp;device in both /dev/vx/dmp and also in /dev/vx/rdmp.&nbsp; I tried removing the disk from veritas,&nbsp;remove the files from both /dev/vx/dmp and /dev/vx/rdmp, label the disk&nbsp;and then re-run "vxdctl enable" but seeing all the 3 disks in "error" status.&nbsp; I didn't move the file disk.info file &amp; run "vxconfigd -K".&nbsp; Its a cluster node (Sun cluster) so wondering if&nbsp;there is anything I can do without moving disk.info file.
# vxdisk list |grep error
	c2t5006048AD52F4106d14s2 auto&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; error
	c2t5006048AD52F4106d35s2 auto&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; error
	c2t5006048AD52F4106d36s2 auto&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; error
# vxdisksetup -i c2t5006048AD52F4106d14 format=sliced
	prtvtoc: /dev/vx/rdmp/c2t5006048AD52F4106d14s2: No such device or address
# prtvtoc /dev/vx/rdmp/c2t5006048AD52F4106d14s2
	prtvtoc: /dev/vx/rdmp/c2t5006048AD52F4106d14s2: No such device or address
# prtvtoc /dev/rdsk/c2t5006048AD52F4106d14s2
	* /dev/rdsk/c2t5006048AD52F4106d14s2 partition map
	*
	* Dimensions:
	*&nbsp;&nbsp;&nbsp;&nbsp; 512 bytes/sector
	*&nbsp;&nbsp;&nbsp;&nbsp; 533 sectors/track
	*&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 30 tracks/cylinder
	*&nbsp;&nbsp; 15990 sectors/cylinder
	*&nbsp;&nbsp; 65535 cylinders
	*&nbsp;&nbsp; 65533 accessible cylinders
	*
	* Flags:
	*&nbsp;&nbsp; 1: unmountable
	*&nbsp; 10: read-only
	*
	* Unallocated space:
	*&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; First&nbsp;&nbsp;&nbsp;&nbsp; Sector&nbsp;&nbsp;&nbsp; Last
	*&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Sector&nbsp;&nbsp;&nbsp;&nbsp; Count&nbsp;&nbsp;&nbsp; Sector
	*&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0 1047872670 1047872669
	*
	*&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; First&nbsp;&nbsp;&nbsp;&nbsp; Sector&nbsp;&nbsp;&nbsp; Last
	* Partition&nbsp; Tag&nbsp; Flags&nbsp;&nbsp;&nbsp; Sector&nbsp;&nbsp;&nbsp;&nbsp; Count&nbsp;&nbsp;&nbsp; Sector&nbsp; Mount Directory
	&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 2&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 5&nbsp;&nbsp;&nbsp; 01&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0 1047872670 1047872669
	#
	&nbsp;
Question on vxdiskunsetup:
I have also noticed the following error&nbsp;on some disks, when running "vxdiskunsetup".&nbsp;
#vxdiskunsetup c2t5006048AD52F4126d39
VxVM vxdiskunsetup ERROR V-5-2-3524 c2t5006048AD52F4126d39: No dmpnode is associated

Thanks,

gaurav_s · Answer

what about paths to those disks ? can you paste following:
vxdisk list c2t5006048AD52F4106d14s2
&amp; similar output for other disks ...
you are getting prtvtoc output from raw disk or DMP node ?
Can you also paste:
# modinfo | grep -i vx
# vxdmpadm listctlr all
# vxdmpadm listenclosure all
# vxdisk -e list | egrep 'cxtxdcx | cxtxdx'&nbsp;&nbsp; (put your errored disk devices here)
&nbsp;
Gaurav

nmcherla · Answer

Gaurav,
I am seeing error while&nbsp; running prtvtoc for DMP node and don't have any issue for getting disk geometry for rdsk.&nbsp; I have pasted the outputs also.
# prtvtoc /dev/vx/rdmp/c2t5006048AD52F4106d14s2
	prtvtoc: /dev/vx/rdmp/c2t5006048AD52F4106d14s2: No such device or address
# vxdisk list |grep error
	NONAMEs2&nbsp;&nbsp;&nbsp;&nbsp; auto&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; error
	c2t5006048AD52F4106d14s2 auto&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; error
	c2t5006048AD52F4106d35s2 auto&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; error
	c2t5006048AD52F4106d36s2 auto&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; error
	#
# vxdisk list c2t5006048AD52F4106d14s2
	Device:&nbsp;&nbsp;&nbsp; c2t5006048AD52F4106d14s2
	devicetag: c2t5006048AD52F4106d14
	type:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; auto
	flags:&nbsp;&nbsp;&nbsp;&nbsp; online error private autoconfig
	pubpaths:&nbsp; block=/dev/vx/dmp/c2t5006048AD52F4106d14s2 char=/dev/vx/rdmp/c2t5006048AD52F4106d14s2
	guid:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -
	udid:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; INVALID
	site:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -
	Multipathing information:
	numpaths:&nbsp;&nbsp; 1
	emcpower18c&nbsp;&nbsp;&nbsp;&nbsp; state=disabled
	#
	# vxdisk list c2t5006048AD52F4106d35s2
	Device:&nbsp;&nbsp;&nbsp; c2t5006048AD52F4106d35s2
	devicetag: c2t5006048AD52F4106d35
	type:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; auto
	flags:&nbsp;&nbsp;&nbsp;&nbsp; online error private autoconfig
	pubpaths:&nbsp; block=/dev/vx/dmp/c2t5006048AD52F4106d35s2
char=/dev/vx/rdmp/c2t5006048AD52F4106d35s2
	guid:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -
	udid:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; INVALID
	site:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -
	Multipathing information:
	numpaths:&nbsp;&nbsp; 1
	emcpower16c&nbsp;&nbsp;&nbsp;&nbsp; state=disabled
	#
	# vxdisk list c2t5006048AD52F4106d36s2
	Device:&nbsp;&nbsp;&nbsp; c2t5006048AD52F4106d36s2
	devicetag: c2t5006048AD52F4106d36
	type:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; auto
	flags:&nbsp;&nbsp;&nbsp;&nbsp; online error private autoconfig
	pubpaths:&nbsp; block=/dev/vx/dmp/c2t5006048AD52F4106d36s2 char=/dev/vx/rdmp/c2t5006048AD52F4106d36s2
	guid:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -
	udid:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; INVALID
	site:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -
	Multipathing information:
	numpaths:&nbsp;&nbsp; 1
	emcpower15c&nbsp;&nbsp;&nbsp;&nbsp; state=disabled
	#
# modinfo|grep -i vx
	&nbsp;50 7bec6000&nbsp; 3e4e0 308&nbsp;&nbsp; 1&nbsp; vxdmp (VxVM 5.0MP3: DMP Driver)
	&nbsp;52 7ba00000 209248 309&nbsp;&nbsp; 1&nbsp; vxio (VxVM 5.0MP3 I/O driver)
	&nbsp;54 7bbe90f0&nbsp;&nbsp;&nbsp; c78 310&nbsp;&nbsp; 1&nbsp; vxspec (VxVM 5.0MP3 control/status driv)
	244 7aa213c0&nbsp;&nbsp;&nbsp; cb0 311&nbsp;&nbsp; 1&nbsp; vxportal (VxFS 5.0_REV-5.0MP3A25_sol port)
	245 79e00000 1d89e0&nbsp; 21&nbsp;&nbsp; 1&nbsp; vxfs (VxFS 5.0_REV-5.0MP3A25_sol SunO)
	263 79fe4000&nbsp;&nbsp; a9e0 312&nbsp;&nbsp; 1&nbsp; fdd (VxQIO 5.0_REV-5.0MP3A25_sol Qui)
# vxdmpadm listctlr all
	CTLR-NAME&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ENCLR-TYPE&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; STATE&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ENCLR-NAME
	=====================================================
	emcp&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; PP_EMC&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ENABLED&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; pp_emc0
	c0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Disk&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ENABLED&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; disk
	c1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Disk&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ENABLED&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; disk
	&nbsp;
# vxdmpadm listenclosure all
ENCLR_NAME&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ENCLR_TYPE&nbsp;&nbsp;&nbsp;&nbsp; ENCLR_SNO&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; STATUS&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ARRAY_TYPE&nbsp;&nbsp;&nbsp;&nbsp; LUN_
	COUNT
	================================================================================
	===
	disk&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Disk&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; DISKS&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; CONNECTED&nbsp;&nbsp;&nbsp; Disk&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 4
	#
&nbsp;# vxdisk -e list | egrep 'c2t5006048AD52F4106d14s2|c2t5006048AD52F4106d35s2|c2t5006048AD52F4106d36s2'
	c2t5006048AD52F4106d14s2 auto&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; error&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; emcpower18c&nbsp; -
	c2t5006048AD52F4106d35s2 auto&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; error&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; emcpower16c&nbsp; -
	c2t5006048AD52F4106d36s2 auto&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; error&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; emcpower15c&nbsp; -
	&nbsp;
# vxdmpadm getsubpaths ctlr=emcp|grep -i disabled
	emcpower17c&nbsp; DISABLED&nbsp;&nbsp;&nbsp;&nbsp; -&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; PP_EMC&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; pp_emc0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -
	emcpower18c&nbsp; DISABLED&nbsp;&nbsp;&nbsp;&nbsp; -&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; c2t5006048AD52F4106d14s2 PP_EMC&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; pp_emc0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -
	emcpower16c&nbsp; DISABLED&nbsp;&nbsp;&nbsp;&nbsp; -&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; c2t5006048AD52F4106d35s2 PP_EMC&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; pp_emc0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -
	emcpower15c&nbsp; DISABLED&nbsp;&nbsp;&nbsp;&nbsp; -&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; c2t5006048AD52F4106d36s2 PP_EMC&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; pp_emc0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -
	&nbsp;

g_lee · Answer

nmcherla,
You mentioned prtvtoc of the disk works - are you using the cXtXdX device or the emcpower devices?
Could you also provide the following output for the powerpath devices, since VxVM is using the emcpower devices as the underlying path for the disks that you've indicated are in error
# /etc/powermt display dev=emcpower15c
	# /etc/powermt display dev=emcpower16c
	# /etc/powermt display dev=emcpower17c
	# /etc/powermt display dev=emcpower18c

nmcherla · Answer

I am using cxtxdx device not the emcpower device for prtvtoc.&nbsp; Powerpath doesn't list the emcpower devices that VxVM uses (emcpowerxxc).&nbsp;
The Pseduo name that EMC powerpath uses for the device C2t5006048AD52F4106d14s2 is "emcpower54a",( VXVM uses emcpower18c. ) &nbsp;And both the paths are active and alive. As I said these are the LUNS removed and re-assigned to the same system and these devices were under veritas control before.&nbsp; I think some how&nbsp;VxVM is using the previous information&nbsp;of the LUN as we can see the emcpower device used by Veritas is different from powerpath.
	&nbsp;
# vxdisk list c2t5006048AD52F4106d14s2
	Device:&nbsp;&nbsp;&nbsp; c2t5006048AD52F4106d14s2
	devicetag: c2t5006048AD52F4106d14
	type:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; auto
	flags:&nbsp;&nbsp;&nbsp;&nbsp; online error private autoconfig
	pubpaths:&nbsp; block=/dev/vx/dmp/c2t5006048AD52F4106d14s2 char=/dev/vx/rdmp/c2t5006048AD52F4106d14s2
	guid:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -
	udid:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; INVALID
	site:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -
	Multipathing information:
	numpaths:&nbsp;&nbsp; 1
	emcpower18c&nbsp;&nbsp;&nbsp;&nbsp; state=disabled
	&nbsp;
#&nbsp; powermt display dev=emcpower18c
	Bad dev value emcpower18c, or not under Powerpath control.
	#
	&nbsp;
# powermt display dev=c2t5006048AD52F4106d14s2
	Pseudo name=emcpower54a
	Symmetrix ID=000190102788
	Logical device ID=0AFB
	state=alive; policy=SymmOpt; priority=0; queued-IOs=0
	==============================================================================
	---------------- Host ---------------&nbsp;&nbsp; - Stor -&nbsp;&nbsp; -- I/O Path -&nbsp; -- Stats ---
	###&nbsp; HW Path&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; I/O Paths&nbsp;&nbsp;&nbsp; Interf.&nbsp;&nbsp; Mode&nbsp;&nbsp;&nbsp; State&nbsp; Q-IOs Errors
	==============================================================================
	3072 pci@3,700000/SUNW,emlxs@0/fp@0,0 c2t5006048AD52F4106d14s0 FA&nbsp; 7cA&nbsp;&nbsp; active&nbsp; alive&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0
	3073 pci@13,700000/SUNW,emlxs@0/fp@0,0 c4t5006048AD52F4109d14s0 FA 10cA&nbsp;&nbsp; active&nbsp; alive&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0
&nbsp;
# vxdisk list |grep error
DEVICE&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; TYPE&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; DISK&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; GROUP&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; STATUS
	NONAMEs2&nbsp;&nbsp;&nbsp;&nbsp; auto&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; error
	c2t5006048AD52F4106d14s2 auto&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; error
	c2t5006048AD52F4106d35s2 auto&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; error
	c2t5006048AD52F4106d36s2 auto&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; error
	&nbsp;
# prtvtoc /dev/rdsk/c2t5006048AD52F4106d14s2
	* /dev/rdsk/c2t5006048AD52F4106d14s2 partition map
	*
	* Dimensions:
	*&nbsp;&nbsp;&nbsp;&nbsp; 512 bytes/sector
	*&nbsp;&nbsp;&nbsp;&nbsp; 533 sectors/track
	*&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 30 tracks/cylinder
	*&nbsp;&nbsp; 15990 sectors/cylinder
	*&nbsp;&nbsp; 65535 cylinders
	*&nbsp;&nbsp; 65533 accessible cylinders
	*
	* Flags:
	*&nbsp;&nbsp; 1: unmountable
	*&nbsp; 10: read-only
	*
	* Unallocated space:
	*&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; First&nbsp;&nbsp;&nbsp;&nbsp; Sector&nbsp;&nbsp;&nbsp; Last
	*&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Sector&nbsp;&nbsp;&nbsp;&nbsp; Count&nbsp;&nbsp;&nbsp; Sector
	*&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0 1047872670 1047872669
	*
	*&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; First&nbsp;&nbsp;&nbsp;&nbsp; Sector&nbsp;&nbsp;&nbsp; Last
	* Partition&nbsp; Tag&nbsp; Flags&nbsp;&nbsp;&nbsp; Sector&nbsp;&nbsp;&nbsp;&nbsp; Count&nbsp;&nbsp;&nbsp; Sector&nbsp; Mount Directory
	&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 2&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 5&nbsp;&nbsp;&nbsp; 01&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0 1047872670 1047872669
	#
	&nbsp;

g_lee · Answer

If the devices were used by Veritas before, then removed and represented without updating/removing the disks cleanly from Veritas first, then this would explain why the entries are showing in error state, as the configuration hasn't been updated cleanly.
At this point, the best bet is to:
1. remove the devices in VxVM:
# vxdisk rm &lt;disk&gt; ### ie: the disks shown in error
2. Remove the entries for those disks under /dev/vx/dmp and /dev/vx/rdmp
3. Rebuild the dmp device tree
# vxdctl initdmp
4. Now rescan
# vxdisk scandisks
&nbsp;
NOTE: this still may not work as the devices were not removed cleanly, so the incorrect config may be stuck in the kernel. If the above does not work, I'd suggest scheduling a reboot rather than trying to remove the disk.info file, as this probably won't work either/may confuse the issue further.
To avoid this situation in future, ensure disks are removed from VxVM cleanly (ie: vxdisk rm, removing devices under /dev/vx/*dmp/, ensuring disks are not rescanned in after this point by stopping vxesd) PRIOR to cleaning up PowerPath and removing the disks from the OS.

Forum Discussion

vxdisksetup error

10 Replies

Related Content

Re: New disk "ERROR" in vxdisk list

Cannot vxdisksetup EMC disks

Client Error (25)

NBU error 58

Error Backup Snapshot Vmware

Recent Discussions

DataDomain To StoreOnce Migration

VCS ERROR V-16-1-10205 Group Mediation_NFS is faulted on system com1em03

vxprivutil

URGENT disk oublic region recover

super block corrupt