How to Replace a Failed Disk in an A5X00 array which is under Veritas Volume Manager Control

Asset ID:	1-71-1011782.1
Update Date:	2016-10-24
Keywords:

Solution Type Technical Instruction Sure

Solution 1011782.1 : How to Replace a Failed Disk in an A5X00 array which is under Veritas Volume Manager Control

Applies to:

Veritas Volume Manager (VxVM) Software
All Platforms

Goal

This document provides a working example of how to replace a failed
disk in an A5x00 array which is also under Veritas Volume Manager
control. Please note there are many approaches to type of replacement.
The one provided herein exclusively uses cli. Caveats to this procedure,
as well as alternatives are provided, but for simplicity, those working
examples are omitted.

Fix

In this working example, we will replace "Front Disk 2" in an
array named "PHOTON". The following commands let us see how the
working disk appears prior to its failure. The disk is viewed from
both a A5x00 and Veritas perspective. This disk participates as 1/2
of a mirror in a Veritas Volume. All outputs are PARSED for clarity!

# luxadm display PHOTON
               DISK STATUS
    SLOT   FRONT DISKS       (Node WWN)          
    0      On (O.K.)         20000020370f441b    
    1      Not Installed                        
    2      On (O.K.)         2000002037269c13    
    3      Not Installed                         
    4      On (O.K.)         20000020370f3c05    
    5      On (O.K.)         20000020370f4166    
    6      On (O.K.)         20000020370f46c5    
    7      On (O.K.)         20000020370f452a    
    8      On (O.K.)         20000020370f384b    
    9      Not Installed                         
    10     On (O.K.)         20000020370f46f2   

# vxdisk list
    DEVICE       TYPE            DISK         GROUP        STATUS
    c2t0d0s2     auto:sliced     disk01       testdf       online
    c2t2d0s2     auto:sliced     disk02       testdf       online

# vxprint -ht
    dm disk01       c2t0d0s2     auto     67972    17610256 -
    dm disk02       c2t2d0s2     auto     67972    17610256 -

    v  vol01        -            ENABLED  ACTIVE   1048576  SELECT    -        fsgen
    pl vol01-01     vol01        ENABLED  ACTIVE   1048576  CONCAT    -        RW
    sd disk01-01    vol01-01     disk01   0        1048576  0         c2t0d0   ENA
    pl vol01-02     vol01        ENABLED  ACTIVE   1048576  CONCAT    -        RW
    sd disk02-01    vol01-02     disk02   0        1048576  0         c2t2d0   ENA

The disk "PHOTON, FRONT DISK 2" fails. This is device c2t2d0 with
a wwpn of 2000002037269c13. Notice how the outputs from the previous
commands have changed.

# luxadm display PHOTON
               DISK STATUS
    SLOT   FRONT DISKS       (Node WWN)          
    0      On (O.K.)         20000020370f441b    
    1      Not Installed   
    2      On (Bypassed:AB)                             
    3      Not Installed                         
    4      On (O.K.)         20000020370f3c05    
    5      On (O.K.)         20000020370f4166    
    6      On (O.K.)         20000020370f46c5    
    7      On (O.K.)         20000020370f452a    
    8      On (O.K.)         20000020370f384b    
    9      Not Installed                         
    10     On (O.K.)         20000020370f46f2

# vxdisk list DEVICE TYPE DISK GROUP STATUS c2t0d0s2 auto:sliced disk01 testdf online c2t2d0s2 auto - - error - - disk02 testdf failed was:c2t2d0s2 # vxprint -ht dm disk01 c2t0d0s2 auto 67972 17610256 - dm disk02 - - - - NODEVICE v vol01 - ENABLED ACTIVE 1048576 SELECT - fsgen pl vol01-01 vol01 ENABLED ACTIVE 1048576 CONCAT - RW sd disk01-01 vol01-01 disk01 0 1048576 0 c2t0d0 ENA pl vol01-02 vol01 DISABLED NODEVICE 1048576 CONCAT - RW sd disk02-01 vol01-02 disk02 0 1048576 0 - RLOC

NEXT, WE WILL REPLACE THE DISK IN THE A5X00

# luxadm -e offline /dev/rdsk/c2t2d0s2
# luxadm remove_device -F PHOTON,f2
    Al alternative command to removing the device
    by "Enclosure name / slot location" is
    # luxadm remove_device -F /dev/rdsk/c2t2d0s2 
            The list of devices which will be removed is:
            1: Box Name:    "PHOTON" front slot 2
            Node WWN:    2000002037269c13
            Device Type:Disk device
            Device Paths:
            /dev/rdsk/c2t2d0s2
            /dev/rdsk/c3t2d0s2
            stopping:  Drive in "PHOTON" front slot 2....Done
            offlining: Drive in "PHOTON" front slot 2....Done
            Hit <Return> after removing the device(s).
            Logical Nodes being removed under /dev/dsk/ and /dev/rdsk:
              c3t2d0s2
              c2t2d0s2

PHYSICALLY REPLACE THE DISK.
# luxadm insert_device PHOTON,f2
     As an alternative to specifying the enclosure name and slot, 
     you may also run... 
     # luxadm insert_device

           Notice: PHOTON,f2 may already be present.
           The list of devices which will be inserted is:
           1: Box Name:    "PHOTON" front slot 2
           Please verify the above list of devices and then enter
           'c' or <CR> to Continue or 'q' to Quit. [Default: c]:
           Hit <Return> after inserting the device(s).
           Drive in Box Name "PHOTON" front slot 2
           Logical Nodes under /dev/dsk and /dev/rdsk :
              c2t2d0s2
              c3t2d0s2

# luxadm display PHOTON 
                                   
           DISK STATUS
      SLOT   FRONT DISKS       (Node WWN)          
      0      On (O.K.)         20000020370f441b    
      1      Not Installed                        
      2      On (O.K.)         20000020370f426e    
      3      Not Installed                         
      4      On (O.K.)         20000020370f3c05    
      5      On (O.K.)         20000020370f4166    
      6      On (O.K.)         20000020370f46c5   
      7      On (O.K.)         20000020370f452a    
      8      On (O.K.)         20000020370f384b    
      9      Not Installed                         
      10     On (O.K.)         20000020370f46f2    

YOU CAN NOW LABEL THE DISK IN SOLARIS. MANY OPTIONS EXIST. 
  You may use a similar drive from the A5X00. 
# prtvtoc /dev/rdsk/c2t0d0s2 | fmthard -s - /dev/rdsk/c2t2d0s2
  Or you may use the format utility. 
# format c2t2d0 <CR>   label <CR>

LASTLY, REINTRODUCE THE DISK INTO VERITAS VOLUME MANAGER. 
# vxdctl enable 
  This next command will initialize the drive. There are many different
  initialization parameters (especially in later versions of veritas
  volume manager.) You must make sure the disk is initialized in the 
  exact same fashion as before. An excellent verification of this is 
  to compare the VTOC of the drive with other disks in the diskgroup.
  If your vtoc differs after initialization, see the man page on 
  vxdisksetup to re-initialize correctly.  # /usr/lib/vxvm/bin/vxdisksetup -i c2t2d0 format=sliced # vxdg -g testdf -k adddisk disk02=c2t2d0s2 # vxrecover -g testdf disk02

  As an alternative to the vxdisksetup, vxdg and vxrecover commands, 
  you may use the # vxdiskadm utility, option 5, to restore the disk into
  the diskgroup. 

# vxdisk list
     DEVICE       TYPE            DISK         GROUP        STATUS
     c2t0d0s2     auto:sliced     disk01       testdf       online
     c2t2d0s2     auto:sliced     disk02       testdf       online

# vxprint -ht
     dm disk01       c2t0d0s2     auto     67972    17610256 -
     dm disk02       c2t2d0s2     auto     67972    17610256 -

     v  vol01        -            ENABLED  ACTIVE   1048576  SELECT    -        fsgen
     pl vol01-01     vol01        ENABLED  ACTIVE   1048576  CONCAT    -        RW
     sd disk01-01    vol01-01     disk01   0        1048576  0         c2t0d0   ENA
     pl vol01-02     vol01        ENABLED  ACTIVE   1048576  CONCAT    -        RW
     sd disk02-01    vol01-02     disk02   0        1048576  0         c2t2d0   ENA

Previously Published As
17003

Attachments

This solution has no attachment