Check to make sure vxdctl is enabled by running the command # vxdctl mode If it is not enabled, then run the commands # vxiod set 10 # vxconfigd -d # vxdctl init # vxdctl enable If that doesn't work, do the following mv /etc/vx/disk.info /etc/vx/disk.info.backup rm /etc/vx/reconfig.d/state.d/install-db vxconfigd -k -x cleartempdir vxdctl init vxconfigd -k -x syslog vxdctl mode 2. If none of this solved your problem, why not just unencapsulate and start back at the beginning with encapsulating? Yes Rajesh, I have tried to create rootdg with vxinstall, showing below error # vxinstall Some licenses are already installed. Do you wish to review them y,n,q,? (default: y) y Do you wish to enter another license key y,n,q,? (default: n) n Volume Manager Installation Menu: VolumeManager/Install VxVM will use the following format to name disks on the host: In the above format, is the logical name of the enclosure to which the disk belongs. VxVM assigns default enclosure names which can be changed according to the user requirements.
How to resolve 'No more handles [gtk_init_check() failed]' launching IBM Installation Manager install gui? IBM WebSphere DataStage known problems and workarounds Source: IBM Public Library. The IBM Information Server Installation. Director, and Administrator) include a large number of UI components that cannot handle GB18030 character data. The unsupported character data is incorrectly mapped within these controls.
Some examples would be: hitachi02 - second disk detected in enclosure 'hitachi0' enggdept2 - second disk detected in enclosure 'enggdept' dgc11 - first disk detected in enclosure 'dgc1' jbod1 - first disk detected in the jbod category For non-public loop disks (Ex. FC disks directly connected to the host or through hubs), you could choose to use the c#t#d#s# naming format. Do you want to use enclosure based names for all disks? y,n,q,? (default: n) n -vxvm:vxconfigd: ERROR: enable failed: Configuration daemon error -1 No such file or directory; aborting Failure during execution of command: vxconfigd -k -m disable.
Could you please try the following steps?i got it from here 1) cp /etc/vfstab to other location 2) remove vx devices from /etc/vfstab and replace it with regular device path.(e.g /dev/dsk/c0t0d0s0.) 3) touch /etc/vx/reconfig.d/state.d/install-db 4) reboote the server. 5) run vxinstall and re-created the rootdg (added the same disk back in) and reboot the server again. 6) copy back /etc/vfstab back, reboot the server for last time.