since I could not delete rootdg I added rootmirror disk to the group, reencapsulated rootdisk, mirrored with option 6, and then readded my other rootdg disks. I seem to be okay now
Hi
As you mention, 3.2 is a v.old version that is EOSL. Versions prior to 4.x (also EOSL) had a requirement that there must be a disk group named rootdg for vxvm to start.
In your output above, there seems to be a valid rootdg, with one disk (c3t0d0) and no volumes. VxVM appear to be functioning.
There are other disks that appear to have been in rootdg at some stage, but its likely that VxVM is using the most recently created one.
Q>Which disk (CTD name )is the boot disk and is your intent to encapsulate the boot disk into vxvm ?
Q>When you restored the data to create the new boot disk, did it place any original partitions that may indicate it was beloging to vxvm (prtvtoc output will help)
cheers
tony
