===== Symptoms =====

 

lsvg shows **STALED** partitions

<code>
lsvg rootvg
VOLUME GROUP:       rootvg                   VG IDENTIFIER:  00cf4dc300004c0000000127ba041eb4
VG STATE:           active                   PP SIZE:        32 megabyte(s)
VG PERMISSION:      read/write               TOTAL PPs:      1918 (61376 megabytes)
MAX LVs:            256                      FREE PPs:       850 (27200 megabytes)
LVs:                21                       USED PPs:       1068 (34176 megabytes)
OPEN LVs:           19                       QUORUM:         1 (Disabled)
TOTAL PVs:          2                        VG DESCRIPTORS: 3
STALE PVs:          1                        STALE PPs:      17
ACTIVE PVs:         2                        AUTO ON:        yes</code>



or 

lsvg shows disk **missing**

<code>
lsvg -p rootvg
rootvg:
PV_NAME           PV STATE          TOTAL PPs   FREE PPs    FREE DISTRIBUTION
hdisk0            missing           959         425         48..06..00..179..192
hdisk1            active            959         425         37..04..00..192..192
</code>

=====Solutions=====

varyonvg "vgname" 

**BUT**

====On rootvg====

If the missing disk contains an actif dump device you will get the following error message

<code>
0516-1774 varyonvg: Cannot varyon volume group with an active dump device on
        a missing physical volume. Use sysdumpdev to temporarily replace the
        dump device with /dev/sysdumpnull and try again.
</code>

In that case use **lsvg -p** to identify the missing disk and **sysdumpdev -l** to identify the configured dump devices. 

For each dump device, **lslv -l "dump device lv"** will show the corresponding disk.

<code>
lsvg -p rootvg
rootvg:
PV_NAME           PV STATE          TOTAL PPs   FREE PPs    FREE DISTRIBUTION
hdisk0            missing           959         425         48..06..00..179..192
hdisk1            active            959         425         37..04..00..192..192
</code>

<code>
sysdumpdev -l
primary              /dev/hd7
secondary            /dev/hd7mir
copy directory       /var/adm/ras
forced copy flag     TRUE
always allow dump    FALSE
dump compression     ON
type of dump         traditional
</code>

<code>
lslv -l hd7mir
hd7mir:N/A
PV                COPIES        IN BAND       DISTRIBUTION  
hdisk1            010:000:000   0%            010:000:000:000:000 
[root@labotest]/root# lslv -l hd7   
hd7:N/A
PV                COPIES        IN BAND       DISTRIBUTION  
hdisk0            010:000:000   100%          000:010:000:000:000 
</code> 

Disengage the dump device of the missing disk.

**Attention:** there are different options for primary and secondary dump devices **!!!**

For **primary** dump device

<code>
sysdumpdev -Pp /dev/sysdumpnull

primary              /dev/sysdumpnull
secondary            /dev/hd7mir
copy directory       /var/adm/ras
forced copy flag     TRUE
always allow dump    FALSE
dump compression     ON
type of dump         traditional
</code> 

For **secondary** dump device

<code>
sysdumpdev -Ps /dev/sysdumpnull

primary              /dev/hd7
secondary            /dev/sysdumpnull
copy directory       /var/adm/ras
forced copy flag     TRUE
always allow dump    FALSE
dump compression     ON
type of dump         traditional
</code> 
 
Now you can resynchronize the rootvg with :

**varyonvg rootvg** 

The progression can be shown with lsvg rootvg. The number of STALED PP should decrease til 0.

**Don't forget the reset the  the dump device to its former value !**
Again different options for primary (**-Pp**)and secondary (**-Ps**) dump devices have to be used with the sysdumpdev command.

<code>
sysdumpdev -Pp /dev/hd7

primary              /dev/hd7
secondary            /dev/hd7mir
copy directory       /var/adm/ras
forced copy flag     TRUE
always allow dump    FALSE
dump compression     ON
type of dump         traditional
</code>