How to change a Disk with Veritas Volume Manager


You can detect what disk is with issues on the server

#vxprint -htr | more
dg rootdg       default      default  70000    1165523746.8.
dm disk01       -            -        -        -                  NODEVICE       <--- Disk Broken
dm rootdisk     c1t0d0s2     auto     20351    143328960 -


Just in case you can check to the devalias assigned to the disk failed


#eeprom |grep devalias
devalias vx-disk01 /pci@1f,700000/scsi@2/disk@1,0:a
devalias vx-rootdisk /pci@1f,700000/scsi@2/disk@0,


You can run a cfgadm in order to check if the disk is available


# cfgadm -avl
unavailable  unavailable  n  /devices/pci@1f,700000/scsi@2:scsi::dsk/c1t1d0    <---Disk With Issues
c1::dsk/c1t2d0                 connected    configured   unknown    HITACHI  HUS10733ASUN72G
We will proceed now to offline the disk a perform the remove to replace the disk (disk01)
#vxdisk offline disk01
#vxdisk rm disk01
Checking the disk status
#vxprint -htr | more
Disk group: rootdg
dg rootdg       default      default  70000    1165523746.8.spdwd585
dm disk01       -            -        -        -        REMOVED     <----Disk with removed status
dm rootdisk     c1t0d0s2     auto     20351    143328960 -

#vxdisk list
.
.
-            -         disk01       rootdg       removed was:c1t1d0s2  <-----Disk with remove status



Now we will execute vxdiskadm in order to proceed to replace the disk


# vxdiskadm     
Volume Manager Support Operations
Menu: VolumeManager/Disk
 1      Add or initialize one or more disks
 2      Encapsulate one or more disks
 3      Remove a disk
 4      Remove a disk for replacement
 5      Replace a failed or removed disk
 6      Mirror volumes on a disk
 7      Move volumes from a disk
 8      Enable access to (import) a disk group
 9      Remove access to (deport) a disk group
 10     Enable (online) a disk device
 11     Disable (offline) a disk device
 12     Mark a disk as a spare for a disk group
 13     Turn off the spare flag on a disk
 14     Unrelocate subdisks back to a disk
 15     Exclude a disk from hot-relocation use
 16     Make a disk available for hot-relocation use
 17     Prevent multipathing/Suppress devices from VxVM's view
 18     Allow multipathing/Unsuppress devices from VxVM's view
 19     List currently suppressed/non-multipathed devices
 20     Change the disk naming scheme
 21     Get the newly connected/zoned disks in VxVM view
 22     Change/Display the default disk layouts
 23     Mark a disk as allocator-reserved for a disk group
 24     Turn off the allocator-reserved flag on a disk
 list   List disk information
 ?      Display help about menu
 ??     Display help about the menuing system
 q      Exit from menus
Select an operation to perform: 5
Replace a failed or removed disk
Menu: VolumeManager/Disk/ReplaceDisk
  Use this menu operation to specify a replacement disk for a disk
  that you removed with the "Remove a disk for replacement" menu
  operation, or that failed during use.  You will be prompted for
  a disk name to replace and a disk device to use as a replacement.
  You can choose an uninitialized disk, in which case the disk will
  be initialized, or you can choose a disk that you have already
  initialized using the Add or initialize a disk menu operation.
Select a removed or failed disk [<disk>,list,q,?] list
Disk group: rootdg
DM NAME         DEVICE       TYPE     PRIVLEN  PUBLEN   STATE
dm disk01       -            -        -        -        REMOVED

Select a removed or failed disk [<disk>,list,q,?] disk01

Select a removed or failed disk [<disk>,list,q,?] disk01
  The following devices are available as possible replacements after being
  initialized (or reinitiliazed):
        c1t2d0 c1t3d0
  You can choose one of these devices to replace disk01.
  Choose "none" to abort the replacement of disk01.
Choose a device, or select "none"
[<device>,none,q,?] (default: c1t2d0) c1t2d0
 The following disk device has a valid VTOC, but does not appear to have
  been initialized for the Volume Manager.  If there is data on the disk
  that should NOT be destroyed you should encapsulate the existing disk
  partitions as volumes instead of adding the disk as a new disk.
  Output format: [Device_Name]
  c1t2d0
Encapsulate this device? [y,n,q,?] (default: y) n
  c1t2d0
Instead of encapsulating, initialize? [y,n,q,?] (default: n) y
  VxVM  INFO V-5-2-378
The requested operation is to initialize disk device c1t2d0 and
  to then use that device to replace the removed or failed disk
  disk01 in disk group rootdg.
Continue with operation? [y,n,q,?] (default: y) y


Checking the task in process for the vxrecover


# vxtask list
TASKID  PTID TYPE/STATE    PCT   PROGRESS
   160           PARENT/R  0.00% 8/0(1) VXRECOVER disk01 rootdg
   161   161     ATCOPY/R 29.69% 0/4194304/1245184 PLXATT vol vol-02 rootdg

Disk is totally sync, remember to perform the installboot in order to install the bootarchive


# vxprint -htr | more
Disk group: rootdg
DG NAME         NCONFIG      NLOG     MINORS   GROUP-ID
ST NAME         STATE        DM_CNT   SPARE_CNT         APPVOL_CNT
DM NAME         DEVICE       TYPE     PRIVLEN  PUBLEN   STATE
RV NAME         RLINK_CNT    KSTATE   STATE    PRIMARY  DATAVOLS  SRL
RL NAME         RVG          KSTATE   STATE    REM_HOST REM_DG    REM_RLNK
CO NAME         CACHEVOL     KSTATE   STATE
VT NAME         NVOLUME      KSTATE   STATE
V  NAME         RVG/VSET/CO  KSTATE   STATE    LENGTH   READPOL   PREFPLEX UTYPE
PL NAME         VOLUME       KSTATE   STATE    LENGTH   LAYOUT    NCOL/WID MODE
SD NAME         PLEX         DISK     DISKOFFS LENGTH   [COL/]OFF DEVICE   MODE
SV NAME         PLEX         VOLNAME  NVOLLAYR LENGTH   [COL/]OFF AM/NM    MODE
SC NAME         PLEX         CACHE    DISKOFFS LENGTH   [COL/]OFF DEVICE   MODE
DC NAME         PARENTVOL    LOGVOL
SP NAME         SNAPVOL      DCO
dg rootdg       default      default  70000    1165523746.8.
dm disk01       c1t2d0s2     auto     10175    143339136 -
dm rootdisk     c1t0d0s2     auto     20351    143328960 -

Regards
Roger

Comments