VxVM confused by SDS?

UNIX Solaris
1

I have an old V490 running an old version of Soalris 10 and an old version of VxVM.

The system disks are configured using metathis and metathat, the remaining disks

Because of the brain-damaged way engineering run things here, I cannot change this. I cannot upgrade nor patch the OS. I cannot upgrade nor patch VxVM.

I recently successfully replaced the root disk, and rebuilt the root mirror. But consequently vxdisk list complains about the replaced device.

# vxdisk list
DEVICE       TYPE            DISK         GROUP        STATUS
c0t0d0s2     auto            -            -            error
c0t1d0s2     auto:none       -            -            online invalid

How can I get c0t0d0s2 to transition to "online invalid"?

# uname -a
SunOS zus15d-4403 5.10 Generic_127111-02 sun4u sparc SUNW,Sun-Fire-V490

# pkginfo -l VRTSvxvm
   PKGINST:  VRTSvxvm
      NAME:  VERITAS Volume Manager, Binaries
  CATEGORY:  system
      ARCH:  sparc
   VERSION:  4.1,REV=02.17.2005.21.28
   BASEDIR:  /
    VENDOR:  VERITAS Software
      DESC:  Virtual Disk Subsystem
    PSTAMP:  VERITAS-4.1_MP2_RP2_HF1:2007-09-29
  INSTDATE:  Feb 26 2008 19:21
   HOTLINE:  800-342-0652
     EMAIL:  support@veritas.com
    STATUS:  completely installed
     FILES:      847 installed pathnames
                  17 partially installed pathnames
                  35 shared pathnames
                  18 linked files
                  98 directories
                 429 executables
              301445 blocks used (approx)
2

Why would you need to do that??:confused:
Btw, did you try vxdiskconfig or vxdisk online cxtxdxsx

3

I managed to solve the problem eventually. There is a recipe you can follow somewhere in sun.com. But, as is often the case with Sun's recipes, there is some ambiguity that can cause one to really foul it up the first time. Which I did. I repeated the procedure, and avoided the SNAFU second time around.

Because those disks are managed by SDS.

I sure did. To no avail. The basic problem is the way that old V490 deals with its internal FCAL disks, wedded to the fact that the version of VxVM doesn't offline the disks as far as the OS is concerned.