Error Message

Replacement of disk bootdisk in group newrootdg with device c1t0d0
  failed.
  VxVM vxdg ERROR V-5-1-10127 associating disk-media bootdisk with c1t0d0s2:
        Disk public region is too small

- Found Technote: TECH15318, as per which the error occurs when using a non-default disk name for the rootdisk. It also mentions about a stale SubDisk in the rootdg config “User had an encapsulated rootdisk named "ps01" which had its private region taken out of swap, thus it had a subdisk named "ps01Priv" to protect the private region.”

Following the article, checked the vxprint output, found there is a stale SD lying :

dg newrootdg     default       default   43000     1258956205.24.javahab

dm altboot       c1t1d0s2      auto      66446     71060733 -

dm bootdisk      -              -         -         -         REMOVED    <<<<<<<<<<<<

sd rootdskPriv   -             bootdisk 12584484 66446     PRIVATE    c1t0d0s2 ENA    <<<<<<<<<<

v   rootdsk6vol   -             ENABLED   ACTIVE    10388844 ROUND      -         fsgen

pl rootdsk6vol-01 rootdsk6vol DISABLED REMOVED 10388844 CONCAT     -         RW

sd rootdsk-04    rootdsk6vol-01 bootdisk 50337935 10388844 0        -         RMOV   <<<<<<<<<

pl rootdsk6vol-02 rootdsk6vol ENABLED ACTIVE    10388844 CONCAT     -         RW

sd altboot-04    rootdsk6vol-02 altboot 50271489 10388844 0         c1t1d0    ENA

v   rootdsk7vol   -             ENABLED   ACTIVE    10388844 ROUND      -         fsgen

pl rootdsk7vol-01 rootdsk7vol DISABLED REMOVED 10388844 CONCAT     -         RW

sd rootdsk-03    rootdsk7vol-01 bootdisk 60726779 10388844 0        -         RMOV <<<<<<<<<

pl rootdsk7vol-02 rootdsk7vol ENABLED ACTIVE    10388844 CONCAT     -         RW

sd altboot-05    rootdsk7vol-02 altboot 60660333 10388844 0         c1t1d0    ENA

v   rootvol       -             ENABLED   ACTIVE    12584484 ROUND      -         root

pl rootvol-01    rootvol       DISABLED REMOVED   12584484 CONCAT     -         RW

sd rootdsk-B0    rootvol-01    bootdisk 12584483 1         0          -         RMOV     <<<<<<<<<

sd rootdsk-02    rootvol-01    bootdisk 0         12584483 1           -         RMOV

pl rootvol-02    rootvol       ENABLED   ACTIVE    12584484 CONCAT     -         RW

sd altboot-01    rootvol-02    altboot   0         12584484 0          c1t1d0    ENA

v   swapvol       -             ENABLED   ACTIVE    16712865 ROUND      -         swap

pl swapvol-01    swapvol       DISABLED REMOVED   16712865 CONCAT     -         RW

sd rootdsk-01    swapvol-01    bootdisk 12650930 16712865 0          -         RMOV     <<<<<<<<<

pl swapvol-02    swapvol       ENABLED   ACTIVE    16712865 CONCAT     -         RW

sd altboot-02    swapvol-02    altboot   12584484 16712865 0          c1t1d0    ENA

v   var           -             ENABLED   ACTIVE    20974140 ROUND      -         fsgen

pl var-01        var            DISABLED REMOVED   20974140 CONCAT     -         RW

sd rootdsk-05    var-01        bootdisk 29363795 20974140 0          -         RLOC    <<<<<<<<<<<

pl var-02        var           ENABLED   ACTIVE    20974140 CONCAT     -         RW

sd altboot-03    var-02         altboot   29297349 20974140 0          c1t1d0    ENA

- Here we can see that the SubDisk names for the DISABLED/REMOVED plexes were indicating to some other name ( rootdsk ) , however, the removed DM was " bootdisk ". (The subdisk of the removed plexes should ideally show the name as bootdisk-01 )

- The name of the removed disk from rootdg was changed and due to mismatch in the subdisk name and the DM name, it created PRIVATE subdisk ( rootdskPriv ).

- Renamed the DM name of the removed disk back to the previous one (as there in the SD names):

(Command: vxedit -g rename )

# vxedit -g newrootdg rename bootdisk rootdsk

- Now the vxdiskadm > option – 5, attached the disk back.