How to replace the root disk or root mirror disk with Veritas Volume Manager (tm) 3.5 and above on HP-UX 11i

Article: 100010453
Last Published: 2022-02-23
Ratings: 1 0
Product(s): InfoScale & Storage Foundation

Problem

How to replace the root disk or root mirror disk with Veritas Volume Manager (tm) 3.5 and above on HP-UX 11i

Solution

1. Remove the disk with option 3 of vxdiskadm

Volume Manager SupportOperations
Menu: VolumeManager/Disk

1      Add orinitialize one or more disks
2      Remove a disk
3      Remove a disk for replacement
4      Replace a failed or removed disk
5      Mirror volumes on a disk
6      Movevolumes from a disk
7      Enable access to (import) a diskgroup
8      Remove access to (deport) a disk group
9      Enable (online) a disk device
10     Disable(offline) a disk device
11     Mark a disk as a spare for a diskgroup
12     Turn off the spare flag on a disk
13     Remove (deport) and destroy a disk group
14    Unrelocate subdisks back to a disk
15     Exclude a disk fromhot-relocation use
16     Make a disk available for hot-relocationuse
17     Prevent multipathing/Suppress devices from VxVM'sview
18     Allow multipathing/Unsuppress devices from VxVM'sview
19     List currently suppressed/non-multipathed devices
20     Change the disk naming scheme
list   List diskinformation

?      Display help about menu
??     Display help about the menuing system
q      Exit from menus

Select an operation to perform: 3

Remove a disk for replacement
Menu:VolumeManager/Disk/RemoveForReplace

 Use this menu operation toremove a physical disk from a disk
 group, while retaining the diskname.  This changes the state
 for the disk name to a "removed"disk.  If there are any
 initialized disks that are not part of adisk group, you will be
 given the option of using one of these disksas a replacement.

Enter disk name [<disk>,list,q,?]list

Disk group: rootdg

DM NAME        DEVICE       TYPE     PRIVLEN  PUBLEN  STATE

dm rootdisk01   c0t1d0       simple  1024     4188096  -
dm rootdisk02  c0t2d0       simple   1024    4188096  -

Enter disk name [<disk>,list,q,?] rootdisk01

The following volumes will lose mirrors as a result ofthis
 operation:

       rootvol standvolswapvol

 No data on these volumes will be lost.

 Thefollowing devices are available asreplacements:

       c0t3d0

 You canchoose one of these disks now, to replace rootdisk01.
 Select "none" ifyou do not wish to select a replacement disk.

Choose a device, or select"none"
[<device>,none,q,?] (default: c0t3d0) none


 The requested operation is to remove diskrootdisk01 from disk group
 rootdg.  The disk name will be kept,along with any volumes using
 the disk, allowing replacement of thedisk.

 Select "Replace a failed or removed disk" from the mainmenu
 when you wish to replace the disk.

Continue withoperation? [y,n,q,?] (default: y) y

Removal of disk rootdisk01 completedsuccessfully.

Remove another disk? [y,n,q,?] (default: n) n


2.Rescan the devices and initialize the replaceddisk:

#  vxdctlenable
# /etc/vx/bin/vxdiskunsetup -C<DISK>

For VxVM 3.5 onHP-UX 11iv1:

#/etc/vx/bin/vxdisksetup -iB<DISK>  

For VxVM4.1/5.0 on HP-UX 11iv2 and 11iv3:

# /etc/vx/bin/vxdisksetup-iB <DISK> format=hpdisk


Note: The -B option is necessary toinitialize the bootable Veritas Volume Manager (VxVM) disk. Refer to the vxdisksetup man page fordetails


3. Replace the failed disk with option 4 of vxdiskadm

Menu:VolumeManager/Disk

1      Add or initialize one or moredisks
2      Remove a disk
3      Remove adisk for replacement
4      Replace a failed or removeddisk
5      Mirror volumes on a disk
6      Move volumes from a disk
7      Enableaccess to (import) a disk group
8      Remove access to(deport) a disk group
9      Enable (online) a diskdevice
10     Disable (offline) a disk device
11    Mark a disk as a spare for a disk group
12     Turn off the spareflag on a disk
13     Remove (deport) and destroy a disk group
14     Unrelocate subdisks back to a disk
15     Excludea disk from hot-relocation use
16     Make a disk available forhot-relocation use
17     Prevent multipathing/Suppress devicesfrom VxVM's view
18     Allow multipathing/Unsuppress devices fromVxVM's view
19     List currently suppressed/non-multipatheddevices
20     Change the disk naming scheme
list   Listdisk information

?      Display help about menu
??     Display help about the menuing system
q      Exit from menus

Select an operation to perform: 4

Replace a failed or removed disk
Menu:VolumeManager/Disk/ReplaceDisk

 Use this menu operation to specifya replacement disk for a disk
 that you removed with the "Remove a diskfor replacement" menu
 operation, or that failed during use.  Youwill be prompted for
 a disk name to replace and a disk device to useas a replacement.
 You can choose an uninitialized disk, in which casethe disk will
 be initialized, or you can choose a disk that you havealready
 initialized using the Add or initialize a disk menuoperation.

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

Disk group: rootdg

DM NAME        DEVICE       TYPE     PRIVLEN  PUBLEN  STATE

dm rootdisk01  -            -        -        -        REMOVED

Selecta removed or failed disk [<disk>,list,q,?] rootdisk01

Thefollowing devices are available asreplacements:

       c0t1d0 c0t3d0

 Youcan choose one of these disks to replace rootdisk01.
 Choose "none" toinitialize another disk to replace rootdisk01.

Choose a device, or select"none"
[<device>,none,q,?] (default: c0t1d0) c0t1d0

Therequested operation is to use the initialized device c0t1d0
 to replacethe removed or failed disk rootdisk01 in disk group rootdg.

Continue withoperation? [y,n,q,?] (default: y) y

Use a default private region lengthfor the disk?
[y,n,q,?] (default: y) y

Replacement of disk rootdisk01in group rootdg with disk device
 c0t1d0 completedsuccessfully.

Replace another disk? [y,n,q,?] (default: n)n


Now vxrecover is in process...

You can find out theremaining   vxrecover run time withthe follow command:

# vxtask -llist

Task:      164RUNNING
Type:      PARENT
Operation:VXRECOVER DMrootdisk01
Started:   MonSep  2 12:59:242002
Progress:  0.00% (1 jobactive)

Task:      165RUNNING (Parent:164)
Type:      ATCOPY
Operation:PLXATT Vol rootvol Plexrootvol-01
Started:   MonSep  2 12:59:242002
Throttle:  0
Progress:  63.52%2182784 of 3436544 Blocks
Work time:20 minutes, 50 seconds (11:57 remaining)


4. Verify thestatus of all volumes:

# vxprint -g rootdg-ht

dm rootdisk01  c0t1d0       simple   1024    4188096  -
dm rootdisk02  c0t2d0       simple   1024    4188096  -

v  rootvol      -            ENABLED  ACTIVE  3436544  SELECT    -        root
plrootvol-01   rootvol      ENABLED  ACTIVE  3436544  CONCAT    -        RW
sdrootdisk01-03 rootvol-01  rootdisk01 7290883436544  0         c0t1d0  ENA
pl rootvol-02  rootvol      ENABLED  ACTIVE  3436544  CONCAT    -        RW
sdrootdisk02-03 rootvol-02  rootdisk02 7290883436544  0         c0t2d0  ENA

v  standvol    -            ENABLED  ACTIVE  204800  SELECT    -        fsgen
plstandvol-01  standvol     ENABLED  ACTIVE  204800  CONCAT    -        RW
sdrootdisk01-01 standvol-01 rootdisk01 0      204800  0         c0t1d0  ENA
plstandvol-02  standvol     ENABLED  ACTIVE  204800  CONCAT    -        RW
sdrootdisk02-01 standvol-02 rootdisk02 0      204800  0         c0t2d0  ENA

v  swapvol      -            ENABLED  ACTIVE  524288  SELECT    -        swap
plswapvol-01   swapvol      ENABLED  ACTIVE  524288  CONCAT    -        RW
sdrootdisk01-02 swapvol-01  rootdisk01 204800 524288  0         c0t1d0  ENA
pl swapvol-02  swapvol      ENABLED  ACTIVE   524288  CONCAT    -        RW
sdrootdisk02-02 swapvol-02  rootdisk02 204800 524288  0         c0t2d0   ENA


5. Verifythe Logical Interchange Format (LIF) and Volume Manager label information on thereplaced disk:

# lifls -l/dev/rdsk/c0t1d0
lifls: Can'tlist /dev/rdsk/c0t1d0; not a LIFvolume

# vxvmboot -v/dev/rdsk/c0t1d0
vxvmboot: Disk/dev/rdsk/c0t1d0 does not contain a valid LIF volume.


6.Write Volume Manager volume information to the LABELfile:

# /opt/VRTS/bin/vxbootsetuprootdisk01


7. Display the LIF and Volume Manager labelinformation:

# vxvmboot -v/dev/rdsk/c0t1d0

LIF Label File @(1k) block # 1178 on VxVM Disk/dev/rdsk/c0t1d0:
Label Entry: 0,Boot Volume start:     3168; length: 200MB
Label Entry: 1, Root Volumestart:   732256; length: 3356MB
Label Entry: 2, Swap Volumestart:   207968; length: 512MB
Label Entry: 3, Dump Volumestart:   207968; length: 512MB

# lifls -l/dev/rdsk/c0t1d0
volume ISL10 datasize 7984 directory size 8 02/05/1016:25:44
filename   type  start   size    implement  created
===============================================================
ODE        -12960584    848      0          02/07/0812:33:46
MAPFILE    -122771432    128      0          02/07/0812:33:46
SYSLIB     -122801560    353      0          02/07/0812:33:46
CONFIGDATA -122781920    235      0          02/07/0812:33:46
SLMOD2     -122762160    141      0          02/07/0812:33:46
SLDEV2     -122762304    135      0          02/07/0812:33:46
SLDRV2     -122762440    205      0          02/07/0812:33:46
SLSCSI2    -122762648    131      0          02/07/0812:33:46
MAPPER2    -122792784    142      0          02/07/0812:33:46
IOTEST2    -122792928    411      0          02/07/0812:33:46
PERFVER2   -122793344    124      0          02/07/0812:33:46
PVCU      -12801 3472    64      0          02/07/0812:33:46
SSINFO     -122863536    2        0          02/07/0812:33:46
ISL        -128003544    306      0          02/05/1016:25:44
HPUX      -129283856    848      0          02/05/1016:25:44
AUTO      -122894704    1        0          02/05/1016:25:44
LABEL      BIN    4712    8        0          02/09/0210:38:27


8. Boot the machine off the replaceddisk
 
 

 

Was this content helpful?