and services are set forth in the express warranty statements accompanying such products and services.
Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for
technical or editorial errors or omissions contained herein.
Microsoft and Windows are U.S. registered trademarks of Microsoft Corporation. Linux is a U.S.
registered trademark of Linus Torvalds.
July 2005 (First Edition)
Part Number 398844-001
Audience assumptions
This document is for the person who installs, administers, and troubleshoots servers and storage
systems. HP assumes you are qualified in the servicing of computer equipment and trained in
recognizing hazards in products with hazardous energy levels.
2 Controller health LED (blinking green indicates board is OK,
amber indicates board has failed)
3 I/O activity LED (indicates total activity of all ports)
4* SAS port 1I (internal, shared), 4x wide
5 SAS port 2I (internal, dedicated), 4x wide
6 Cache module (also known as BBWC or array accelerator)
7 Secondary (lower) battery for cache module
6 HP Smart Array P600 Controller for Integrity Servers User Guide
*Ports 1E and 1I share electrical circuitry. Whenever the controller is reset, it searches for
devices connected to port 1E before searching on port 1I. If both these ports are
connected to storage devices, the controller discovers and uses only the devices attached
to port 1E. Devices connected to port 1I are not displayed in this case.
Controller specifications
Feature Details
Card type Full-length PCI-X 133
Dimensions (excluding bracket) 31.1 cm x 10.8 cm x 1.8 cm (12.3 in x 4.3 in x 0.7 in)
Power required Approximately 28 W
Temperature range Operating, 10° to 35°C (50° to 95°F); storage, -20° to 55°C (-4° to
Connector type Compatible with full-length 3.3-V, 64-bit PCI-X or PCI slot
Transfer rate Up to 1.0 GB/s at 133 MHz (64-bit)
Number of SAS ports 2 (1 internal, and 1 that can be used as internal or external)
SAS transfer rate Up to 1.2 GB/s per port in each direction
Operating, 10% to 70%; storage, 5% to 90%
For more information about the controller features and specifications, and for
information about system requirements, refer to the HP website
(http://www.hp.com/products/smartarray
).
7
Overview of the installation procedure
In this section
Quick installation procedure (Windows® or Linux®)...................................................................7
Quick installation procedure (Windows® or Linux®)
Before installing the controller, refer to the support matrix on the HP website
(http://www.hp.com/products1/serverconnectivity
operating system support the controller.
To install the controller:
1. Power down the server.
2. Install the controller hardware ("Installing the controller hardware" on page
).
9
) to confirm that the server and
3. If necessary, install additional physical drives.
The number of drives in the server determines the RAID level that is
autoconfigured when the server is powered up (next step).
4. Power up the server.
5. Update the controller firmware ("Updating the firmware" on page 13
When the firmware update process is complete, the server reboots and runs
through a POST procedure. This POST procedure halts briefly during
controller initialization and prompts you to open ORCA.
6. Open ORCA ("Configuring an array" on page 15
– If using a headless console, press the Esc+8 key combination.
– Otherwise, press the F8 key.
7. Configure the logical boot drive, and then exit from ORCA.
):
).
8 HP Smart Array P600 Controller for Integrity Servers User Guide
If the server is using Linux®, controller installation is complete. When the server
is next rebooted, the operating system detects the controller hardware and
automatically loads the required driver.
If the server is using Microsoft® Windows®, continue as follows:
1. Load the controller driver from EBSU on the Smart Setup media. (To load
the driver, select Load OEM Boot Drivers at the appropriate point in
EBSU. For more information about Smart Setup, refer to the HP Smart Setup Guide on the Smart Setup media.)
2. Run Express Setup.
3. When you have finished installing the operating system as directed during
the Express Setup procedure, remove the operating system CD and insert the
Smart Setup media.
4. Install the Integrity Support Pack ("Installing device drivers and
Management Agents" on page 19
).
Controller installation is complete.
9
Installing the controller hardware
In this section
Before beginning the installation....................................................................................................9
Preparing the server........................................................................................................................9
Installing the controller board.......................................................................................................10
SAS cable part numbers ...............................................................................................................11
Before beginning the installation
Before beginning the installation procedure, visit the HP website
(http://www.hp.com/support
driver and utility file needed. Compare the version numbers of the files there
with those of the same files on the Smart Setup media.
) to confirm that you have the latest version of each
Preparing the server
Before installing the controller in the server, back up all data.
If the server supports hot-pluggable devices, no further preparation is required.
Proceed to install the controller board as described ("Installing the controller
board" on page 10
If the server does not support hot-pluggable devices:
1. Close all applications.
2. Power down the server.
CAUTION: In systems that use external data storage, be sure that
the server is the first unit to be powered down and the last to be
powered back up. Taking this precaution ensures that the system does
not erroneously mark the drives as failed when the server is powered
up.
).
10 HP Smart Array P600 Controller for Integrity Servers User Guide
3. Power down all peripheral devices that are attached to the server.
4. Unplug the AC power cord from the outlet and then from the server.
5. Disconnect all peripheral devices from the server.
Installing the controller board
WARNING: To reduce the risk of personal injury or damage to
the equipment, consult the safety information and user
documentation provided with the server before attempting the
installation.
Many servers are capable of providing energy levels that are
considered hazardous and are intended to be serviced only by
qualified personnel who have been trained to deal with these
hazards. Do not remove enclosures or attempt to bypass any
interlocks that may be provided for the purpose of removing these
hazardous conditions.
1. Remove or open the access panel.
2. Select an available 3.3-V, 64-bit full-length PCI or PCI-X slot.
3. If the controller is being hot-plugged, power down the slot.
4. Remove the slot cover or open the hot-plug latch. Save the retaining screw if
one is present.
5. Slide the controller board along the slot alignment guide, and press the board
firmly into the slot so that the contacts on the board edge are properly seated
in the system board connector.
6. Secure the controller board in place with the hot-plug latch or retaining
screw. If there is a guide latch on the rear of the board, close the latch.
7. Connect storage devices to the controller. (For details of the procedure, refer
to "Connecting storage devices ("Connecting external storage" on page 11
NOTE: Drives that are to be grouped in the same array should all
have comparable capacity for efficient use of total storage capacity.
).")
8. Close or replace the access panel, and secure it with thumbscrews, if any are
present.
Installing the controller hardware 11
CAUTION: Do not operate the server for long periods with the
access panel open or removed. Operating the server in this manner
results in improper airflow and improper cooling that can lead to thermal
damage.
9. If the controller was hot-plugged, power up the slot.
Connecting external storage
1. Power down the server.
2. Connect an external SAS cable to the external port of the controller.
NOTE: You do not have to disconnect any internal drives on
shared internal port 1I because the controller preferentially discovers
devices attached to port 1E. However, drives on the shared internal port
are unavailable until you disconnect the external storage device.
3. Tighten the lock screws on the cable connector.
4. Attach the other end of the cable to the SAS input connector of the external
storage enclosure.
IMPORTANT: Drives that are to be used in the same array must
be of the same type, either all SAS or all SATA. (Parallel SCSI drives
cannot be used with this controller.)
5. Tighten the lock screws on the cable connector.
6. Power up the enclosure.
7. Power up the server.
SAS cable part numbers
NOTE: If you require additional cables, order them by the option kit
Cable length Option kit number Cable assembly number
1.0 m (3.3 ft) 389665-B21 361317-001
2.0 m (6.6 ft) 389668-B21 361317-002
4.0 m (13 ft) 389671-B21 361317-004
number.
12 HP Smart Array P600 Controller for Integrity Servers User Guide
Cable length Option kit number Cable assembly number
6.0 m (20 ft) 389674-B21 361317-006
13
Updating the firmware
In this section
Methods for updating the firmware (Windows® or Linux®) ......................................................13
Methods for updating the firmware (Windows® or
Linux®)
To update the firmware on the server, controller, or hard drives, use Smart
Components. The most recent version of a particular component is available on
the support page of the HP website (http://www.hp.com/support
components are also available on the Smart Setup media.
1. Find the most recent version of the component that you require.
2. Follow the instructions for installing the component on the server. These
instructions are provided on the same Web page as the component.
). Some
3. Follow the additional instructions that describe how to use the component to
flash the ROM. These instructions are provided with each component.
Comparing the utilities .................................................................................................................16
Using ORCA ................................................................................................................................17
Using ACU ...................................................................................................................................18
Introduction
HP provides two utilities for manually configuring an array on a Smart Array
controller:
• ORCA—A simple ROM-based configuration utility
• ACU—A versatile, browser-based utility that provides maximum control
over configuration parameters
NOTE: To copy a particular array configuration to several other
servers on the same network, use ACR or the scripting capability of
ACU. ACR is provided in the SmartStart Scripting Toolkit, available on
the HP website (http://www.hp.com/servers/sstoolkit
).
Whichever utility you use, the following limitations apply:
• For the most efficient use of drive space, do not mix drives of different
capacities within the same array. The configuration utility treats all physical
drives in an array as if they have the same capacity as the smallest drive in
the array. The excess capacity of any larger drives is wasted because it is
unavailable for data storage.
• The probability that an array will experience a drive failure increases with
the number of physical drives in the array. If you configure a logical drive
with RAID 5, keep the probability of failure low by using no more than 14
physical drives in the array.
16 HP Smart Array P600 Controller for Integrity Servers User Guide
For conceptual information about arrays, logical drives, and fault-tolerance
methods, and for information about default array configuration settings, refer to
the HP Array Configuration Utility User Guide. This document is available on
the Documentation CD that is provided in the controller kit.
Comparing the utilities
NOTE: A + in the appropriate column indicates that the feature or
procedure is supported, while -- indicates that the feature or procedure
Supported features ACU ORCA
Uses a graphical interface + --
Available in languages other than English + --
Available on CD + --
is not supported.
Uses a wizard to suggest the optimum configuration for an unconfigured
+ --
controller
Describes configuration errors + --
Suitable for configuration while online + --
Suitable for configuration while offline -- +
Supported procedures ACU ORCA
Creation and deletion of arrays and logical drives + +
Assignment of RAID level + +
Sharing of spare drives among several arrays + --
Assignment of multiple spare drives per array + --
Setting of stripe size + --
Migration of RAID level or stripe size + --
Configuration of controller settings + --
Expansion of an array + --
Creation of multiple logical drives per array + --
Configuring an array 17
Using ORCA
1. Power up the server. POST runs, and any array controllers that are in the
server are initialized one at a time. During each controller initialization
process, POST halts for several seconds while an ORCA prompt message
appears.
2. At the ORCA prompt:
– If you are connected using a headless console, press the Esc+8 key
combination.
– Otherwise, press the F8 key.
The ORCA main menu appears, enabling you to create, view, or delete a
logical drive.
To create a logical drive using ORCA:
1. Select Create Logical Drive.
The screen displays a list of all available (unconfigured) physical drives and
the valid RAID options for the system.
2. Use the Arrow keys, Spacebar, and Tab key to navigate around the screen
and set up the logical drive, including an online spare drive if one is required.
NOTE: You cannot use ORCA to configure one spare drive to be
shared among several arrays. Only ACU enables you to configure
shared spare drives.
3. Press the Enter key to accept the settings.
18 HP Smart Array P600 Controller for Integrity Servers User Guide
4. Press the F8 key to confirm the settings and save the new configuration.
After several seconds, the Configuration Saved screen appears.
5. Press the Enter key to continue.
You can now create another logical drive by repeating the previous steps.
NOTE: Newly created logical drives are invisible to the operating
system. To make the new logical drives available for data storage,
format them using the instructions given in the operating system
documentation.
Using ACU
For detailed information about using ACU, refer to the HP Array Configuration
Utility User Guide. This document is available on the Smart Setup media or the Documentation CD provided in the controller kit.
19
Installing device drivers and Management
Agents
In this section
Systems using Microsoft® Windows® ........................................................................................19
Systems using Linux®..................................................................................................................20
Systems using Microsoft® Windows®
You can use the Integrity Support Pack to automatically install the device
drivers, Event Notification Service, and Management Agents, or you can install
these items manually.
The Integrity Support Pack is located on the Smart Setup media. To install the
Integrity Support Pack, launch Express Setup from EBSU and follow the onscreen instructions.
Installing device drivers
The drivers for the controller are located on the Smart Setup media. Updates are
posted to the support page of the HP website
(http://www.hp.com/support/itaniumservers
Installation instructions are provided with the drivers.
Installing the Event Notification Service
The HP Smart Array SAS/SATA Event Notification Service provides event
notification to the Microsoft® Windows® Server 2003 64-bit system event log
and the HP Integrated Management log.
).
20 HP Smart Array P600 Controller for Integrity Servers User Guide
The most recent version of the software component is available on the support
page of the HP website (http://www.hp.com/support/itaniumservers
instructions are provided with the component.
Installing Management Agents
The Management Agents are available on the Smart Setup media. The most
recent versions of the agents are available on the support page of the HP website
(http://www.hp.com/support/itaniumservers
). Installation instructions are
provided with the agents.
If the new agents do not function correctly, you might also need to update
Systems Insight Manager. The latest version of Systems Insight Manager is
available for download at the HP website (http://www.hp.com/servers/manage
Systems using Linux®
The drivers for the controller are bundled into the supported Red Hat and Novell
Linux distributions.
). Installation
).
In a system that does not yet have Linux installed:
1. Follow the standard controller installation procedure.
2. Reboot the server.
3. Follow the standard procedure for installing Linux. As Linux is installed, it
recognizes the controller and automatically loads the correct driver.
In a system that already has Linux installed:
1. Power down the system.
2. Follow the standard controller installation procedure.
3. Power up the system. As Linux boots, it recognizes the controller.
4. Enter one of the following commands as appropriate to ensure that the driver
is loaded correctly:
Red Hat: #mkinitrd -f /boot/efi/efi/redhat/initrd$(uname -r).img $(uname -r)
Installing device drivers and Management Agents 21
5. For Novell, enter the following command to confirm that the driver is active:
#lsmod | grep cciss
If the driver is active, the system responds by displaying cciss.
Installing Management Agents
The most recent versions of the agents are available on the support page of the
HP website (http://www.hp.com/support/itaniumservers
instructions, refer to the downloadable file HP Insight Management Agents for Linux on Integrity Servers provided with the agents.
If the new agents do not function correctly, you might also need to update
Systems Insight Manager. The latest version of Systems Insight Manager is
available for download at the HP website (http://www.hp.com/servers/manage
). For installation
).
23
Upgrading or replacing controller options
In this section
Replacing a battery .......................................................................................................................23
Replacing a battery
WARNING: There is a risk of explosion, fire, or personal injury
if the battery pack is not properly handled. Refer to "Battery
replacement notice (on page 52
item that contains a battery pack.
IMPORTANT: Whether you are replacing the main cache battery
or the secondary (lower) cache battery, remove both batteries so that
the board circuitry recognizes the new battery pack.
1. Close all applications, and then power down the server. This procedure
flushes all data from the cache.
)" before installing or removing any
2. Remove the cache module:
a. Open the ejector latches on each side of the DIMM connector (1).
b. Pull the cache module out of the DIMM slot (2).
24 HP Smart Array P600 Controller for Integrity Servers User Guide
3. If the main cache battery must be replaced:
a. Press the battery retainer tabs down, and push them through to the other
side of the cache board (1).
b. Lift the battery pack off the cache board (2).
4. Remove the secondary cache battery pack:
a. Unhook the wire retainer that holds the battery pack to the controller
board (1).
b. While holding the battery in one hand, pull the plastic retainer tabs up
and push them through to the other side of the controller board (2).
Upgrading or replacing controller options 25
5. Replace whichever battery is degraded.
6. Reinstall the batteries on the cache board and the controller board.
7. Reinstall the cache board and its battery on the controller.
27
Replacing, moving, or adding hard drives
In this section
Identifying the status of a hard drive............................................................................................27
Recognizing hard drive failure .....................................................................................................29
Replacing hard drives ...................................................................................................................31
Moving drives and arrays .............................................................................................................36
When a drive is configured as a part of an array and connected to a powered-up
controller, the condition of the drive can be determined from the illumination
pattern of the hard drive status lights (LEDs).
Online/Activity
LED (green)
On, off, or flashing Alternating amber
Fault/UID LED
(amber/blue)
and blue
Interpretation
The drive has failed, or a predictive failure alert has been
received for this drive; it also has been selected by a
management application.
28 HP Smart Array P600 Controller for Integrity Servers User Guide
Online/Activity
LED (green)
Fault/UID LED
(amber/blue)
Interpretation
On, off, or flashing Steadily blue The drive is operating normally, and it has been selected by a
management application.
On Amber, flashing
regularly (1 Hz)
A predictive failure alert has been received for this drive.
Replace the drive as soon as possible.
On Off The drive is online, but it is not active currently.
Flashing regularly
(1 Hz)
Amber, flashing
regularly (1 Hz)
Do not remove the drive. Removing a drive may terminate
the current operation and cause data loss.
The drive is part of an array that is undergoing capacity
expansion or stripe migration, but a predictive failure alert has
been received for this drive. To minimize the risk of data loss,
do not replace the drive until the expansion or migration is
complete.
Flashing regularly
(1 Hz)
Off
Do not remove the drive. Removing a drive may terminate
the current operation and cause data loss.
The drive is rebuilding, or it is part of an array that is undergoing
capacity expansion or stripe migration.
Flashing
irregularly
Flashing
Amber, flashing
regularly (1 Hz)
The drive is active, but a predictive failure alert has been
received for this drive. Replace the drive as soon as possible.
Off The drive is active, and it is operating normally.
irregularly
Off Steadily amber A critical fault condition has been identified for this drive, and
the controller has placed it offline. Replace the drive as soon as
possible.
Off Amber, flashing
regularly (1 Hz)
A predictive failure alert has been received for this drive.
Replace the drive as soon as possible.
Off Off The drive is offline, a spare, or not configured as part of an
array.
Replacing, moving, or adding hard drives 29
Recognizing hard drive failure
A steadily glowing Fault LED indicates that that drive has failed. Other means by
which hard drive failure is revealed are:
• The amber LED on the front of a storage system illuminates if failed drives
are inside. (However, this LED also illuminates when other problems occur,
such as when a fan fails, a redundant power supply fails, or the system
overheats.)
• A POST message lists failed drives whenever the system is restarted, as long
as the controller detects at least one functional drive.
• ACU represents failed drives with a distinctive icon.
• Systems Insight Manager can detect failed drives remotely across a network.
(For more information about Systems Insight Manager, refer to the
documentation on the Management CD.)
• ADU lists all failed drives.
For additional information about diagnosing hard drive problems, refer to the HP Servers Troubleshooting Guide.
CAUTION: Sometimes, a drive that has previously been failed by
the controller may seem to be operational after the system is powercycled or (for a hot-pluggable drive) after the drive has been removed
and reinserted. However, continued use of such marginal drives may
eventually result in data loss. Replace the marginal drive as soon as
possible.
Effects of a hard drive failure
When a hard drive fails, all logical drives that are in the same array are affected.
Each logical drive in an array may be using a different fault-tolerance method, so
each logical drive can be affected differently.
• RAID 0 configurations cannot tolerate drive failure. If any physical drive in
the array fails, all non-fault-tolerant (RAID 0) logical drives in the same
array will also fail.
• RAID 1+0 configurations can tolerate multiple drive failures as long as no
failed drives are mirrored to one another.
30 HP Smart Array P600 Controller for Integrity Servers User Guide
• RAID 5 configurations can tolerate one drive failure.
• RAID ADG configurations can tolerate simultaneous failure of two drives.
Compromised fault tolerance
If more hard drives fail than the fault-tolerance method allows, fault tolerance is
compromised, and the logical drive fails. In this case, all requests from the
operating system are rejected with unrecoverable errors. You are likely to lose
data, although it can sometimes be recovered (refer to "Recovering from
compromised fault tolerance" on page 30
One example of a situation in which compromised fault tolerance may occur is
when a drive in an array fails while another drive in the array is being rebuilt. If
the array has no online spare, any logical drives in this array that are configured
with RAID 5 fault tolerance will fail.
Compromised fault tolerance can also be caused by non-drive problems, such as
a faulty cable or temporary power loss to a storage system. In such cases, you do
not need to replace the physical drives. However, you may still have lost data,
especially if the system was busy at the time that the problem occurred.
).
Recovering from compromised fault tolerance
If fault tolerance is compromised, inserting replacement drives does not improve
the condition of the logical volume. Instead, if the screen displays unrecoverable
error messages, perform the following procedure to recover data:
1. Power down the entire system, and then power it back up. In some cases, a
marginal drive will work again for long enough to enable you to make copies
of important files.
If a 1779 POST message is displayed, press the F2 key to re-enable the
logical volumes. Remember that data loss has probably occurred and any
data on the logical volume is suspect.
2. Make copies of important data, if possible.
3. Replace any failed drives.
Replacing, moving, or adding hard drives 31
4. After you have replaced the failed drives, fault tolerance may again be
compromised. If so, cycle the power again. If the 1779 POST message is
displayed:
a. Press the F2 key to re-enable the logical drives.
b. Recreate the partitions.
c. Restore all data from backup.
To minimize the risk of data loss that is caused by compromised fault tolerance,
make frequent backups of all logical volumes.
Replacing hard drives
The most common reason for replacing a hard drive is that it has failed.
However, another reason is to gradually increase the storage capacity of the
entire system.
If you insert a hot-pluggable drive into a drive bay while the system power is on,
all disk activity in the array pauses for a second or two while the new drive is
spinning up. When the drive has achieved its normal spin rate, data recovery to
the replacement drive begins automatically (as indicated by the blinking
Online/Activity LED on the replacement drive) if the array is in a fault-tolerant
configuration.
If you replace a drive belonging to a fault-tolerant configuration while the system
power is off, a POST message appears when the system is next powered up. This
message prompts you to press the F1 key to start automatic data recovery. If you
do not enable automatic data recovery, the logical volume remains in a ready-torecover condition and the same POST message appears whenever the system is
restarted.
32 HP Smart Array P600 Controller for Integrity Servers User Guide
Factors to consider before replacing hard drives
Before replacing a degraded drive:
• Open Systems Insight Manager and inspect the Error Counter window for
each physical drive in the same array to confirm that no other drives have
any errors. (For details, refer to the Systems Insight Manager documentation
on the Management CD.)
• Be sure that the array has a current, valid backup.
• Use replacement drives that have a capacity at least as great as that of the
smallest drive in the array. The controller immediately fails drives that have
insufficient capacity.
In systems that use external data storage, be sure that the server is the first unit to
be powered down and the last to be powered back up. Taking this precaution
ensures that the system does not erroneously mark the drives as failed when the
server is powered up.
To minimize the likelihood of fatal system errors, take these precautions when
removing failed drives:
• Do not remove a degraded drive if any other drive in the array is offline (the
Online/Activity LED is off). In this situation, no other drive in the array can
be removed without data loss.
The following cases are exceptions:
– When RAID 1+0 is used, drives are mirrored in pairs. Several drives can
be in a failed condition simultaneously (and they can all be replaced
simultaneously) without data loss, as long as no two failed drives belong
to the same mirrored pair.
– When RAID ADG is used, two drives can fail simultaneously (and be
replaced simultaneously) without data loss.
– If the offline drive is a spare, the degraded drive can be replaced.
• Do not remove a second drive from an array until the first failed or missing
drive has been replaced and the rebuild process is complete. (The rebuild is
complete when the Online/Activity LED on the front of the drive stops
blinking.)
Replacing, moving, or adding hard drives 33
The following cases are exceptions:
– In RAID ADG configurations, any two drives in the array can be replaced
simultaneously.
– In RAID 1+0 configurations, any drives that are not mirrored to other
removed or failed drives can be simultaneously replaced offline without
data loss.
Automatic data recovery (rebuild)
When you replace a hard drive in an array, the controller uses the fault-tolerance
information on the remaining drives in the array to reconstruct the missing data
(the data that was originally on the replaced drive) and write it to the replacement
drive. This process is called automatic data recovery, or rebuild. If fault tolerance
is compromised, this data cannot be reconstructed and is likely to be permanently
lost.
If another drive in the array fails while fault tolerance is unavailable during
rebuild, a fatal system error may occur, and all data on the array is then lost. In
exceptional cases, however, failure of another drive need not lead to a fatal
system error. These exceptions include:
• Failure after activation of a spare drive
• Failure of a drive that is not mirrored to any other failed drives (in a RAID
1+0 configuration)
• Failure of a second drive in a RAID ADG configuration
Time required for a rebuild
The time required for a rebuild varies considerably, depending on several factors:
• The priority that the rebuild is given over normal I/O operations (you can
change the priority setting by using ACU)
• The amount of I/O activity during the rebuild operation
• The rotational speed of the hard drives
• The availability of drive cache
• The brand, model, and age of the drives
34 HP Smart Array P600 Controller for Integrity Servers User Guide
• The amount of unused capacity on the drives
• The number of drives in the array (for RAID 5 and RAID ADG)
Allow approximately 15 minutes per gigabyte for the rebuild process to be
completed. This figure is conservative; the actual time required is usually less
than this.
System performance is affected during the rebuild, and the system is unprotected
against further drive failure until the rebuild has finished. Therefore, replace
drives during periods of low activity when possible.
When automatic data recovery has finished, the Online/Activity LED of the
replacement drive stops blinking steadily at 1 Hz and begins to either glow
steadily (if the drive is inactive) or flash irregularly (if the drive is active).
CAUTION: If the Online/Activity LED on the replacement drive
does not light up while the corresponding LEDs on other drives in the
array are active, the rebuild process has abnormally terminated. The
amber Fault LED of one or more drives might also be illuminated. Refer
to "Abnormal termination of a rebuild (on page 34
action you must take.
)" to determine what
Abnormal termination of a rebuild
If the Online/Activity LED on the replacement drive permanently ceases to be
illuminated even while other drives in the array are active, the rebuild process
has abnormally terminated. The following table indicates the three possible
causes of abnormal termination of a rebuild.
Observation Cause of rebuild termination
None of the drives in the array have
an illuminated amber Fault LED.
The replacement drive has an
illuminated amber Fault LED.
One of the other drives in the array
has an illuminated amber Fault LED.
One of the drives in the array has
experienced an uncorrectable read error.
The replacement drive has failed.
The drive with the illuminated Fault LED
has now failed.
Each of these situations requires a different remedial action.
Case 1: An uncorrectable read error has occurred.
Replacing, moving, or adding hard drives 35
1. Back up as much data as possible from the logical drive.
CAUTION: Do not remove the drive that has the media error.
Doing so causes the logical drive to fail.
2. Restore data from backup. Writing data to the location of the unreadable
sector often eliminates the error.
3. Remove and reinsert the replacement drive. This action restarts the rebuild
process.
If the rebuild process still terminates abnormally:
1. Delete and recreate the logical drive.
2. Restore data from backup.
Case 2: The replacement drive has failed.
Verify that the replacement drive is of the correct capacity and is a supported
model. If these factors are not the cause of the problem, use a different drive as
the replacement.
Case 3: Another drive in the array has failed.
A drive that has recently failed can sometimes be made temporarily operational
again by cycling the server power.
1. Power down the server.
2. Remove the replacement physical drive (the one undergoing a rebuild), and
reinstall the drive that it is replacing.
3. Power up the server.
If the newly failed drive seems to be operational again:
1. Back up any unsaved data.
2. Remove the drive that was originally to be replaced, and reinsert the
replacement physical drive. The rebuild process automatically restarts.
3. When the rebuild process has finished, replace the newly failed drive.
However, if the newly failed drive has not recovered:
36 HP Smart Array P600 Controller for Integrity Servers User Guide
1. Remove the drive that was originally to be replaced, and reinsert the
replacement physical drive.
2. Replace the newly failed drive.
3. Restore data from backup.
Upgrading hard drive capacity
You can increase the storage capacity on a system even if there are no available
drive bays by swapping drives one at a time for higher capacity drives. This
method is viable as long as a fault-tolerance method is running.
CAUTION: Because it can take up to 15 minutes per gigabyte to
rebuild the data in the new configuration, the system is unprotected
against drive failure for many hours while a given drive is upgraded.
Perform drive capacity upgrades only during periods of minimal system
activity.
To upgrade hard drive capacity:
1. Back up all data.
2. Replace any drive. The data on the new drive is re-created from redundant
information on the remaining drives.
CAUTION: Do not replace any other drive until data rebuild on this
drive is complete.
When data rebuild on the new drive is complete, the Online/Activity LED
stops flashing steadily and either flashes irregularly or glows steadily.
3. Repeat the previous step for the other drives in the array, one at a time.
When you have replaced all drives, you can use the extra capacity to either create
new logical drives or extend existing logical drives. For more information about
these procedures, refer to the HP Array Configuration Utility User Guide.
Moving drives and arrays
You can move drives to other ID positions on the same array controller. You can
also move a complete array from one controller to another, even if the controllers
are on different servers.
Replacing, moving, or adding hard drives 37
Before you move drives, the following conditions must be met:
• The server must be powered down.
• If moving the drives to a different server, the new server must have enough
empty bays to accommodate all the drives simultaneously.
• The array has no failed or missing drives, and no spare drive in the array is
acting as a replacement for a failed drive.
• The controller is not running capacity expansion, capacity extension, or
RAID or stripe size migration.
• The controller is using the latest firmware version (recommended).
If you want to move an array to another controller, all drives in the array must be
moved at the same time.
When all the conditions have been met:
1. Back up all data before removing any drives or changing configuration. This
step is required if you are moving data-containing drives from a controller
that does not have a battery-backed cache.
2. Power down the system.
3. Move the drives.
4. Power up the system. If a 1724 POST message appears, drive positions were
changed successfully and the configuration was updated.
If a 1785 (Not Configured) POST message appears:
a. Power down the system immediately to prevent data loss.
b. Return the drives to their original locations.
c. Restore the data from backup, if necessary.
5. Verify the new drive configuration by running ORCA or ACU ("Configuring
an array" on page 15
).
38 HP Smart Array P600 Controller for Integrity Servers User Guide
Adding drives
You can add hard drives to a system at any time, as long as you do not exceed the
maximum number of drives that the controller supports. You can then either
build a new array from the added drives or use the extra storage capacity to
expand the capacity of an existing array.
To perform an array capacity expansion, use ACU. If the system is using hotpluggable drives, you can expand array capacity without shutting down the
operating system (that is, with the server online) if ACU is running in the same
environment as the normal server applications. (For more information, refer to
the HP Array Configuration Utility User Guide.)
The expansion process is illustrated in the following figure, in which the original
array (containing data) is shown with a dashed border and the newly added drives
(containing no data) are shown unshaded. The array controller adds the new
drives to the array and redistributes the original logical drives over the enlarged
array one logical drive at a time. This process liberates some storage capacity on
each of the physical drives in the array. During this procedure, the logical drives
each keep the same fault-tolerance method in the enlarged array that they had in
the smaller array.
Replacing, moving, or adding hard drives 39
When the expansion process has finished, you can use the liberated storage
capacity on the enlarged array to create new logical drives. Alternatively, you
can enlarge one of the original logical drives. This latter process is called logical drive capacity extension and is also carried out using ACU.
NOTE: During server power-up, each runtime LED illuminates
LED ID Color LED name and interpretation
0 Amber CR510: Controller Failure LED. The controller firmware has detected an error.
1 Amber CR511: Drive Failure LED. A physical drive connected to the controller has
2 Blue CR512: Activity LED for SAS port 2I.
3 Blue CR513: Activity LED for SAS port 1E and 1I.
randomly until POST has finished.
failed. Check the Fault LED on each drive to determine which drive has failed.
42 HP Smart Array P600 Controller for Integrity Servers User Guide
LED ID Color LED name and interpretation
4 Green CR514: Command Outstanding LED. The controller is working on a command
from the host driver.
5 Blue CR515: Heartbeat LED. This LED blinks every 2 seconds to indicate the
controller health.
6 Green CR516: Gas Pedal LED. This LED, together with item 7, indicates the amount of
controller CPU activity. For details, refer to the following table.
7 Green CR517: Idle Task LED. This LED, together with item 6, indicates the amount of
controller CPU activity. For details, refer to the following table.
8 Amber CR507: Battery Status LED. For interpretation, refer to "Cache module LEDs
(on page 43
9 Green CR508: Battery Charging LED. For interpretation, refer to "Cache module LEDs
(on page 43)."
10 Amber CR509: Controller Failure LED. The controller hardware has detected an error.
Controller CPU activity level Item 6 status Item 7 status
0–25% Off Blinking
25–50% Blinking Off
)."
50–75% On steadily Off
75–100% On steadily On steadily
Diagnosing array problems 43
Cache module LEDs
Item 1
(amber
LED)
-- Steady glow The cache batteries are being charged.
-- Fast blink The cache microcontroller is waiting for the
Steady glow -- One of the following situations is occurring:
Fast blink
Slow blink
(once every
16 seconds)
Item 2
(green LED)
Interpretation
host controller to communicate.
• There is a short circuit across the battery
terminals or within the battery pack.
• The host controller is updating the cache
microcontroller firmware.
There is an open circuit across the battery
terminals or within the battery pack.
This display pattern might occur after the
system is powered down. It indicates that the
cache contains data that has not yet been
written to the drives. Restore system power as
soon as possible to prevent data loss. (The
battery lifetime depends on the cache module
size. For further information, refer to the
controller QuickSpecs on the HP website
(http://www.hp.com
).)
44 HP Smart Array P600 Controller for Integrity Servers User Guide
Diagnostic tools
Several diagnostic tools provide feedback about problems with arrays. The most
important are:
•ADU
This utility is a Windows®-based diagnostic tool that sends an email to HP
Support when it detects any problems with the controllers and attached
storage in a system.
To install ADU, open the \contents\utilities\smartarray
directory on the Smart Setup media and double-click the cp00xxxx.exe
file. When installation is complete, run ADU by clicking Start and selecting
Programs>HP System Tools>HP Array Diagnostic Utility.
The meanings of the various ADU error messages are provided in the HP Servers Troubleshooting Guide.
•POST messages
Smart Array controllers produce diagnostic error messages at reboot. Many
of these POST messages are self-explanatory and suggest corrective actions.
For more information about POST messages, refer to the HP Servers Troubleshooting Guide.
Grounding methods to prevent electrostatic discharge.................................................................46
Preventing electrostatic discharge
To prevent damaging the system, be aware of the precautions you need to follow
when setting up the system or handling parts. A discharge of static electricity
from a finger or other conductor may damage system boards or other staticsensitive devices. This type of damage may reduce the life expectancy of the
device.
To prevent electrostatic damage:
• Avoid hand contact by transporting and storing products in static-safe
containers.
• Keep electrostatic-sensitive parts in their containers until they arrive at static-
free workstations.
• Place parts on a grounded surface before removing them from their
containers.
• Avoid touching pins, leads, or circuitry.
• Always be properly grounded when touching a static-sensitive component or
assembly.
46 HP Smart Array P600 Controller for Integrity Servers User Guide
Grounding methods to prevent electrostatic
discharge
Several methods are used for grounding. Use one or more of the following
methods when handling or installing electrostatic-sensitive parts:
• Use a wrist strap connected by a ground cord to a grounded workstation or
computer chassis. Wrist straps are flexible straps with a minimum of
1 megohm ±10 percent resistance in the ground cords. To provide proper
ground, wear the strap snug against the skin.
• Use heel straps, toe straps, or boot straps at standing workstations. Wear the
straps on both feet when standing on conductive floors or dissipating floor
mats.
• Use conductive field service tools.
• Use a portable field service kit with a folding static-dissipating work mat.
If you do not have any of the suggested equipment for proper grounding, have an
authorized reseller install the part.
For more information on static electricity or assistance with product installation,
contact an authorized reseller.
47
Regulatory compliance notices
In this section
Federal Communications Commission notice..............................................................................47
Canadian notice (Avis Canadien).................................................................................................50
European Union regulatory notice................................................................................................50
Part 15 of the Federal Communications Commission (FCC) Rules and
Regulations has established Radio Frequency (RF) emission limits to provide an
interference-free radio frequency spectrum. Many electronic devices, including
computers, generate RF energy incidental to their intended function and are,
therefore, covered by these rules. These rules place computers and related
peripheral devices into two classes, A and B, depending upon their intended
installation. Class A devices are those that may reasonably be expected to be
installed in a business or commercial environment. Class B devices are those that
may reasonably be expected to be installed in a residential environment (for
example, personal computers). The FCC requires devices in both classes to bear
a label indicating the interference potential of the device as well as additional
operating instructions for the user.
FCC rating label
The FCC rating label on the device shows the classification (A or B) of the
equipment. Class B devices have an FCC logo or ID on the label. Class A
devices do not have an FCC logo or ID on the label. After you determine the
class of the device, refer to the corresponding statement.
48 HP Smart Array P600 Controller for Integrity Servers User Guide
Class A equipment
This equipment has been tested and found to comply with the limits for a Class A
digital device, pursuant to Part 15 of the FCC Rules. These limits are designed to
provide reasonable protection against harmful interference when the equipment is
operated in a commercial environment. This equipment generates, uses, and can
radiate radio frequency energy and, if not installed and used in accordance with
the instructions, may cause harmful interference to radio communications.
Operation of this equipment in a residential area is likely to cause harmful
interference, in which case the user will be required to correct the interference at
personal expense.
Class B equipment
This equipment has been tested and found to comply with the limits for a Class B
digital device, pursuant to Part 15 of the FCC Rules. These limits are designed to
provide reasonable protection against harmful interference in a residential
installation. This equipment generates, uses, and can radiate radio frequency
energy and, if not installed and used in accordance with the instructions, may
cause harmful interference to radio communications. However, there is no
guarantee that interference will not occur in a particular installation. If this
equipment does cause harmful interference to radio or television reception, which
can be determined by turning the equipment off and on, the user is encouraged to
try to correct the interference by one or more of the following measures:
• Reorient or relocate the receiving antenna.
• Increase the separation between the equipment and receiver.
• Connect the equipment into an outlet on a circuit that is different from that to
which the receiver is connected.
• Consult the dealer or an experienced radio or television technician for help.
Regulatory compliance notices 49
Declaration of conformity for products marked with the FCC
logo, United States only
This device complies with Part 15 of the FCC Rules. Operation is subject to the
following two conditions: (1) this device may not cause harmful interference, and
(2) this device must accept any interference received, including interference that
may cause undesired operation.
For questions regarding this product, contact us by mail or telephone:
• Hewlett-Packard Company
P. O. Box 692000, Mail Stop 530113
Houston, Texas 77269-2000
• 1-800-HP-INVENT (1-800-474-6836). (For continuous quality
improvement, calls may be recorded or monitored.)
For questions regarding this FCC declaration, contact us by mail or telephone:
• Hewlett-Packard Company
P. O. Box 692000, Mail Stop 510101
Houston, Texas 77269-2000
• 1-281-514-3333
To identify this product, refer to the part, series, or model number found on the
product.
Modifications
The FCC requires the user to be notified that any changes or modifications made
to this device that are not expressly approved by Hewlett-Packard Company may
void the user’s authority to operate the equipment.
Cables
Connections to this device must be made with shielded cables with metallic
RFI/EMI connector hoods in order to maintain compliance with FCC Rules and
Regulations.
50 HP Smart Array P600 Controller for Integrity Servers User Guide
Canadian notice (Avis Canadien)
Class A equipment
This Class A digital apparatus meets all requirements of the Canadian
Interference-Causing Equipment Regulations.
Cet appareil numérique de la classe A respecte toutes les exigences du
Règlement sur le matériel brouilleur du Canada.
Class B equipment
This Class B digital apparatus meets all requirements of the Canadian
Interference-Causing Equipment Regulations.
Cet appareil numérique de la classe B respecte toutes les exigences du Règlement
sur le matériel brouilleur du Canada.
European Union regulatory notice
This product complies with the following EU Directives:
• Low Voltage Directive 73/23/EEC
• EMC Directive 89/336/EEC
*For a notified body number refer to the product regulatory label.
Compliance with these directives implies conformity to harmonized European
standards (European Norms) which are listed on the EU Declaration of
Conformity issued by Hewlett-Packard for this product or product family.
Regulatory compliance notices 51
BSMI notice
Japanese notice
52 HP Smart Array P600 Controller for Integrity Servers User Guide
Korean notice A&B
Class A equipment
Class B equipment
Battery replacement notice
This component uses a nickel metal hydride (NiMH) battery pack.
WARNING: There is a risk of explosion, fire, or personal injury
if a battery pack is mishandled. To reduce this risk:
Regulatory compliance notices 53
• Do not attempt to recharge the batteries if they are
disconnected from the controller.
• Do not expose the battery pack to water, or to temperatures
higher than 60°C (140°F).
• Do not abuse, disassemble, crush, or puncture the battery
pack.
• Do not short the external contacts.
• Replace the battery pack only with the designated HP spare. Battery disposal should comply with local regulations.
Batteries, battery packs, and accumulators should not be
disposed of together with the general household waste. To
forward them to recycling or proper disposal, use the public
collection system or return them by established parts return
methods to HP, an authorized HP Partner, or one of their agents.
For more information about battery replacement or proper disposal, contact an
authorized reseller or an authorized service provider.
Taiwan battery recycling notice
The Taiwan EPA requires dry battery manufacturing or importing firms in
accordance with Article 15 of the Waste Disposal Act to indicate the recovery
marks on the batteries used in sales, giveaway or promotion. Contact a qualified
Taiwanese recycler for proper battery disposal.
55
Acronyms and abbreviations
ACR
Array Configuration Replicator
ACU
Array Configuration Utility
ADG
Advanced Data Guarding (also known as RAID 6)
ADU
Array Diagnostics Utility
BBWC
battery-backed write cache
EBSU
EFI-based setup utility
EFI
extensible firmware interface
ORCA
Option ROM Configuration for Arrays
56 HP Smart Array P600 Controller for Integrity Servers User Guide
POST
Power-On Self Test
RAID
redundant array of inexpensive (or independent) disks
cable part numbers 11
cables 49
cache batteries, replacing 23
cache module LEDs 43
cache, features of 43
Canadian notice 50
compatibility of parallel SCSI drives 11
compromised fault tolerance 30
configuring an array 15
connectors 5
controller board, features of 5
controller board, installing 9
controller installation, overview of 7
controller LEDs 41
D
data recovery 30, 33
data transfer rate 6
device drivers, installing 19
F
failure of hard drive 29
fault tolerance, compromised 30
Federal Communications Commission (FCC)
notice 47, 49
firmware, updating 13
G
grounding methods 46
H
hard drive LEDs 27
hard drive, failure of 29
hard drive, replacing 31
hard drives, adding 38
hard drives, determining status of 27
hard drives, moving 36
I
installation overview 7
58 HP Smart Array P600 Controller for Integrity Servers User Guide