Replacing a disk drive in the 7063-CR1 system

Learn how to replace a disk drive in the IBM 7063-CR1 Hardware Management Console systems.

Procedure

Ensure that you have the electrostatic discharge (ESD) wrist strap on and that the ESD clip is plugged into a ground jack or connected to an unpainted metal surface. If not, do so now.
Install a disk drive into the drive tray.
Orient the disk drive such that the connectors are pointing to the rear of the disk drive as shown in Figure 1. Fasten the disk drive to the sides of the drive tray with the screws (two or three screws on each side), depending on the number of threaded holes present on the drive. If the number of threaded holes is greater than the number of screws that are available, use the threaded holes that are closest to each end of the drive.
Figure 1. Mounting the 3.5-inch disk drive in the drive tray
Support the disk drive by the bottom as you position the disk drive, and insert it into the disk drive slot.

Important: Ensure that the disk drive is fully seated and is all the way into the system.
Lock the drive bay handle (A) by pushing in the handle release until it locks at (B) as shown in Figure 2.
Figure 2. Disk drive lock detail
Note: The mvcli utility targets adapter ID 0 by default. However, some 7063-CR1 systems do not show any disks under the adapter ID 0 and it will be shown under the adapter ID 1. To switch to adapter ID 1, run the following command on the mvcli utility:
```
adapter -i 1
```
If both drives are being replaced, repeat steps from 1 to 4 for the second drive and continue with step 5.a. Otherwise, go to step 6.
1. List the currently defined virtual disks by running the following command:
```
info -o vd
```
2. Delete all existing virtual disks by running the following command:
```
delete -o vd -i 0
```
```
delete -o vd -i 1
```
3. Recreate virtual disk 0. See Creating the virtual disk on the 7063-CR1 system.
  This ends the procedure.
If only one physical disk was replaced, initiate the rebuild operation manually on the virtual disk that was replaced.
1. To see if the rebuild operation has started automatically, run the following command from the mvcli command line:
```
info -o vd 
```
  If the rebuild operation has started, which is indicated by a line similar to the following:
```
BGA progress: rebuilding is 1% done
```
  the procedure is complete and the HMC operating system can be started. The rebuild process continues in the background. If not, continue with the next step.
2. Verify that the newly installed drive is blank.
  Run the following command:
```
info -o vd
```
  Select one of the following options:
  - If only one virtual disk is listed, go to step 6.c.
  - If two virtual disks are listed, identify the one that contains the physical disk that was replaced by inspecting the output of info -o vd and observing the PD Raid setup line which lists the slot numbers contained in that virtual disk.
    
    If the physical disk that was replaced shows as being part of virtual disk 0, run the following command:
    delete -o vd -i 0
    When asked Are you sure you want to delete this virtual disk? (y or n), answer y.
    
    If the physical disk that was replaced shows as being part of virtual disk 1, run the following command:
    delete -o vd -i 1
    When asked Are you sure you want to delete this virtual disk? (y or n), answer y.
  Continue with step 6.c.
3. Start the virtual disk rebuild operation.
  - If the virtual disk in the first bay was replaced, run the following command from the mvcli command line:
```
rebuild -a start -l <vd ID> -d 0
```
    , where vd ID is the virtual disk that is identified in step 6.b.
  - If the virtual disk in the second bay was replaced, run the following command from the mvcli command line:
```
rebuild -a start -l <vd ID> -d 1
```
    , where vd ID is the virtual disk that is identified in step 6.b.
4. The rebuild operation can take several hours.
  Check the status of the rebuild operation by running the following command from the mvcli command line:
```
info -o vd
```
  If the status of the rebuild operation is in progress, the HMC operating system can be started and the rebuild process continues in the background.
  If the status of the rebuild is paused, restart the rebuild operation by running the following command for a virtual disk in the first drive bay:
```
rebuild -a resume -l <vd ID> -d 1
```
  , where vd ID is the virtual disk that is identified in step 6.b.
  Or by running the following command for a virtual disk in the second drive bay:
```
rebuild -a resume -l <vd ID> -d 0
```
  , where vd ID is the virtual disk that is identified in step 6.b.
5. Check the name of the virtual disk by running the following command:
```
info -o vd
```
  If the name is not "HMC Disk" and shows one or more [D] (a letter D in enclosed brackets), correct the name by running the following command:
```
set -o vd -i <vd ID> -n "HMC Disk"
```
  , where vd ID is the virtual disk that is identified in step 6.b.
  For example, if the name of the virtual disk 0 is "[D]HMC disk", run the following command:
```
set -o vd -i 0 -n "HMC Disk"
```