Solaris

I think you cannot do option 11 first.

The right way is to do opt 4, remove/add disk then opt 5.

if I can recall correctly when you do opt11 then you later try to do opt 4/5 it may fail or give some error. I think you need to try to bring the disk back online before doing option 4.

But if you cannot do opt4/5 there is a workaround from sunsolve.

Solution 212645 : How to replace a root drive in Volume manager if vxdiskadm option4/option5 is not working

Btw I've never attempted this procedure before, so use at your own risk.

======================
Removing the Root disk
======================

1) # vxdg -g rootdg -k rmdisk

2) # vxprint -htg rootdg
remove the plexs associated with the original disk (disabled nodevice)

3) # vxplex dis opt-01 (run against all plexes associated with root disk)
- this is a standard plex that is creatd in encapsulation

4) # vxedit -r rm opt-01 (run against all plexes associated with root disk)

5) # vxedit rm

6) # vxdisk list
should no longer be listed as a removed entry

7) # vxdisk rm c#t#d#s2 (root disk)



=======================
Replacing the root disk
=======================

1) preform drive replacement steps per system requirements
if drive has already been replaced, skip this step

2) # format
Delete all partitions except for slice 2, and label the disk

3) # vxdctl enable

4) # vxdisksetup -i c#t#d# (rootdisk)

5) # vxdg -g rootdg adddisk rootdisk=c#t#d#

6) # vxdiskadm - opt6 to mirror
choose root mirror as the disk to mirror
root disk is destination disk
this should recognize that it should be a root disk and write a
bootblock onto it

7) # prtvtoc /dev/rdsk/c#t#d#s2 (rootdisk)
check to make sure that there are regular partitions


Product

VERITAS Volume Manager 3.2 for Solaris 9
VERITAS Volume Manager 4.0 Software
VERITAS Volume Manager 3.5 Software
VERITAS Volume Manager 3.2 Software
VERITAS Volume Manager 3.1.1 Software
VERITAS Volume Manager 3.1 Software
VERITAS Volume Manager 3.0.6 Software
VERITAS Volume Manager 3.0.4 Software
VERITAS Volume Manager 3.0.3 Software
VERITAS Volume Manager 3.0.2 Software



Keywords

volume manager, rootdisk replacement fails



Previously Published As

75082



Attachments

This solution has no attachment

Well, it turns out that the system needed to be patched.

After many unsuccessful attempts to add the disk to the mirror, Sun Support discovered that we were experiencing a problem with VxVM v4.1 patch level 171080-04 which could be fixed with patch 171080-07. The patch was installed and option 5 of vxdiskadm allowed the new disk to be added and re-synced.

Thanks for your assistance!

Here is what I would do (CLI - manual method):
Remove the old vx objects totally from the cfg (clean it out):
If disabled (vxedit -g rootdg -r rm rootdg01-0x)
if active (vxplex -o rm dis rootdg01-0x)
same as above for remaining plexes (see vxprint -thr & vxdisk list output)
vxdg -g rootdg rmdisk xxxxxxxxx
/etc/vx/bin/vxdiskunsetup -C cxtxdx
vxdisk rm cxtxdx

Run format - zero all partitions except slice 2
Label the new disk under format
run vxdctl enable

Find privite region lenght on existing disk (to match)
run vxprint -thr
TY NAME ASSOC KSTATE LENGTH
sd rootxxxxxxx - ENABLED 2743
(alt command) vxprint -thr | grep sliced
DM NAME DEVICE TYPE PRIVLEN PUBLEN STATE
dm rootmirror c1t1d0s2 sliced 2743 71681511 -

/etc/vx/bin/vxdisksetup -i cxtxdx puboffset=2744 (“rootdiskPriv” length + 1)
Note: Substitite the option old_layout for puboffset above for patch level 1 and above. (output: modinfo | grep vx = 3.2t_p1+)
So the command above would be (without puboffset statement):
vxdisksetup -i cxtxdx old_layout
vxdg -g rootdg adddisk rootdisk=cxtxdx
/etc/vx/bin/vxrootmir rootdisk
vxassist mirror swapvol rootdisk
vxassist mirror opt rootdisk
vxassist mirror usr rootdisk

I know that this works as I have used it many times in my env.
Please don't take my word for this - you need to test in your env.
Test on a test system by pulling a mirrored disk on a test box.
good luck