03-28-2007 09:13 AM
Solved! Go to Solution.
11-14-2010 02:23 AM
Sunny posted this query on 28 March 2007 and last commented 2 years 37 weeks ago on this forum.....
vxdisksetup should NOT be used on current boot disk.
Disks should first be removed from SVM (Sunny asked for how-to info) then encapsulated using vxdiskadm.
11-13-2010 10:15 PM
First of all you got to take the mirror off in your machine.
After by using vxdisksetup you can get the disks under control of Veritas.
then create a disk group and add disks
then by using
# vxencap -g <diskgroupname> rootdisk=c0t0d0s2
You will then need to reboot your machine for the change to take effect.
Once the system is back up confirm all is well using vxprint -hrt. You shoud see something simmiliar to this
dg rootdg default default 0 1079622222.1025.hostname
dm rootdisk c0t0d0s2 sliced 3590 17678493 -
v home - ENABLED ACTIVE 12342267 ROUND - gen
pl home-01 home ENABLED ACTIVE 12342267 CONCAT - RW
sd rootdisk-03 home-01 rootdisk 5336226 12342267 0 c0t0d0 ENA
v rootvol - ENABLED ACTIVE 4287654 ROUND - root
pl rootvol-01 rootvol ENABLED ACTIVE 4287654 CONCAT - RW
sd rootdisk-02 rootvol-01 rootdisk 1048572 4287654 0 c0t0d0 ENA
v swapvol - ENABLED ACTIVE 1048572 ROUND - swap
pl swapvol-01 swapvol ENABLED ACTIVE 1048572 CONCAT - RW
sd rootdisk-01 swapvol-01 rootdisk 0 1048572 0 c0t0d0 ENA
11-14-2010 02:23 AM
Sunny posted this query on 28 March 2007 and last commented 2 years 37 weeks ago on this forum.....
vxdisksetup should NOT be used on current boot disk.
Disks should first be removed from SVM (Sunny asked for how-to info) then encapsulated using vxdiskadm.