
Chapter 7
Removing and Replacing Components
Individual Component Remove/Replace Instructions
144
HotPlug Disk Drive Removal
The internal disk drives (up to four) are located at the front right side of the server (as you are facing it).
When proper software and hardware procedures are followed, internal disk drives can be removed and
replaced while the server is running.
The procedures in this section are in two parts, a HotSwap Software Procedure and a HotPlug Hardware
Procedure, for removing the disk from the server.
Before starting these procedures, you must have an up-to-date configuration backup file. Configuration
backup is performed by default each time an LVM command changes the LVM configuration. The default
backup files path is:
/etc/lvmconf/base_vg_name.conf.
The replacement disk drive must be the same product ID as the disk drive that is being replaced.
NOTE
HP often uses different manufacturers for disks that have the same product number. The
HotSwap and HotPlug procedures will not update the disk drive’s internal information to that
of the replaced disk drive.
The replacement disk drive will have the same capacity and blocksize as the defective disk because they have
the same product number. The only field that can be incorrect is the string specifying the vendor’s name. This
will not affect the behavior of the LVM. If you desire to update the manufacturer’s name, the disks volume
group must be deactivated and reactivated.
HotSwap Software Procedure
Perform these software procedural steps to replace a HotPlug disk drive device:
Step 1.
Determine whether LVM found the physical volume to be defective when the volume group was
activated.
If the volume was defective when the volume group was activated,
vgchange
will generate the
following message to the console:
WARNING
VGCHANGE: WARNING: COULDN’T ATTACH TO THE VOLUME GROUP PHYSICAL
VOLUME “/DEV/DSK/cXtXdX”
VGCHANGE: WARNING: COULDN’T ATTACH TO THE VOLUME GROUP PHYSICAL
VOLUME “/DEV/DSK/cXtXdX”
THE PATH OF THE PHYSICAL VOLUME REFERS TO A DEVICE THAT DOES NOT
EXIST, OR IS NOT CONFIGURED INTO THE KERNAL.
If you are unsure of the status of
vgchange
, check it with the
vgdisplay
command:
#vgdisplay <VG name>
For example:
# vgdisplay /dev/vg00
If the disk was defective when the
vgchange
command was entered, the following message will be
printed one or more times:
Summary of Contents for L1000 - 9000 - 0 MB RAM
Page 7: ...Contents vii Typical Installation Schedule 207 Site Inspection 208 Delivery Survey 212 ...
Page 8: ...Contents viii ...
Page 10: ...Tables x ...
Page 12: ...Figures xii ...
Page 14: ...xiv ...
Page 16: ...Chapter 1 Server Overview 2 ...
Page 17: ...Chapter 2 3 2 Server Unpacking and Installation ...
Page 37: ...Chapter 3 23 3 Installing Additional Components ...
Page 60: ...Chapter 3 Installing Additional Components Installing Disk Drives 46 ...
Page 61: ...Chapter 4 47 4 Cable Connections ...
Page 91: ...Chapter 5 77 5 Utilities ...
Page 98: ...Chapter 5 Utilities Configuring the Rev B Guardian Service Processor GSP 84 ...
Page 99: ...Chapter 6 85 6 Troubleshooting ...
Page 134: ...Chapter 6 Troubleshooting Fan Power Supply and Disk LED States 120 ...
Page 189: ...Appendix A 175 A Parts and Accessories ...