HP ProLiant Smart Array E200 User guide

HP ProLiant  Smart Array E200 User guide
HP Smart Array E200 Controller
User Guide
December 2005 (First Edition)
Part Number 408556-001
© Copyright 2005 Hewlett-Packard Development Company, L.P.
The information contained herein is subject to change without notice. The only warranties for HP products 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.
December 2005 (First Edition)
Part Number 408556-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.
Contents
Hardware features ........................................................................................................................ 5
Board components .................................................................................................................................... 5
Controller specifications ............................................................................................................................. 5
Overview of the installation procedure ............................................................................................ 7
Installing the controller in an unconfigured server .......................................................................................... 7
Installing the controller in a previously configured server ................................................................................ 7
Installing the controller hardware .................................................................................................... 9
Before beginning the installation ................................................................................................................. 9
Preparing the server................................................................................................................................... 9
Installing the controller board...................................................................................................................... 9
Connecting storage devices ...................................................................................................................... 10
Updating the firmware ................................................................................................................ 11
Methods for updating the firmware ............................................................................................................ 11
Configuring an array .................................................................................................................. 12
Introduction ............................................................................................................................................ 12
Comparing the utilities ............................................................................................................................. 12
Using ORCA........................................................................................................................................... 13
Using ACU ............................................................................................................................................. 14
Using CPQONLIN................................................................................................................................... 14
Setting drive rebuild, expand priority, and accelerator ratio................................................................ 14
Expanding an array....................................................................................................................... 15
Adding or configuring spare drives.................................................................................................. 15
Migrating RAID level and stripe size online ....................................................................................... 16
Setting the boot controller and controller order ............................................................................... 17
Setting a controller as the boot controller.................................................................................................... 17
Setting the controller order........................................................................................................................ 17
Installing device drivers and Management Agents .......................................................................... 18
Installing device drivers ............................................................................................................................ 18
Installing Management Agents .................................................................................................................. 18
Upgrading or replacing controller options ..................................................................................... 19
Replacing a battery ................................................................................................................................. 19
Upgrading the cache ............................................................................................................................... 20
Replacing, moving, or adding hard drives ..................................................................................... 22
Identifying the status of a hard drive .......................................................................................................... 22
Recognizing hard drive failure .................................................................................................................. 23
Effects of a hard drive failure .......................................................................................................... 24
Compromised fault tolerance .......................................................................................................... 24
Recovering from compromised fault tolerance.................................................................................... 24
Replacing hard drives .............................................................................................................................. 24
Hard drive replacement guidelines .................................................................................................. 25
Automatic data recovery (rebuild) .................................................................................................... 25
Upgrading hard drive capacity ....................................................................................................... 27
Moving drives and arrays ........................................................................................................................ 28
Adding drives ......................................................................................................................................... 28
Contents
3
Diagnosing array problems.......................................................................................................... 30
Controller board runtime LEDs................................................................................................................... 30
Battery pack LEDs.................................................................................................................................... 31
Diagnostic tools ...................................................................................................................................... 32
Electrostatic discharge ................................................................................................................. 33
Preventing electrostatic discharge .............................................................................................................. 33
Grounding methods to prevent electrostatic discharge .................................................................................. 33
Regulatory compliance notices ..................................................................................................... 34
European Union regulatory notice ............................................................................................................. 34
BSMI notice ............................................................................................................................................ 34
Korean class B notice............................................................................................................................... 35
Battery replacement notice........................................................................................................................ 35
Taiwan battery recycling notice................................................................................................................. 35
Acronyms and abbreviations........................................................................................................ 36
Index......................................................................................................................................... 37
Contents
4
Hardware features
In this section
Board components ................................................................................................................................... 5
Controller specifications ............................................................................................................................ 5
Board components
Item ID
Description
1
Runtime LEDs. To interpret the illumination pattern of these LEDs,
refer to "Controller board runtime LEDs (on page 30)".
2
SAS port 2I (internal), 4x wide.
3
SAS port 1I (internal), 4x wide.
4
Cache module (also known as array accelerator). To enable RAID
migration, stripe size migration, array expansion, or logical drive
capacity extension, upgrade the cache ("Upgrading the cache" on
page 20).
Controller specifications
Feature
Details
Card type
Full-size PCIe
Dimensions (excluding bracket)
31.2 cm × 11.1 cm × 1.5 cm (12.3 in × 4.4 in × 0.6 in)
Maximum power required
Approximately 8 W
Hardware features 5
Temperature range
Operating, 10°C to 55°C (50°F to 131°F)
Storage, -30°C to 60°C (-22°F to 140°F)
Relative humidity
(noncondensing)
Operating, 10% to 90%; storage, 5% to 90%
RAID levels supported
RAID 0 and 1+0; also RAID 5 if the cache is upgraded ("Upgrading
the cache" on page 20)
Type of edge connector
PCIe x8 (fits in slots that have a physical size of x8 or greater;
operates at the speed rating of the slot, up to a maximum of x4)
PCIe transfer rate
Up to 1.0 GB/s full duplex
Number of SAS ports
Two internal wide ports; each port has four 1x connectors
SAS transfer rate
Up to 1.2 GB/s per port in each direction
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).
Hardware features 6
Overview of the installation procedure
In this section
Installing the controller in an unconfigured server ......................................................................................... 7
Installing the controller in a previously configured server ............................................................................... 7
Installing the controller in an unconfigured server
New HP ProLiant server models self-configure when they are powered up for the first time. For more
information about the autoconfiguration process, refer to the server-specific setup and installation guide or
the HP ROM-Based Setup Utility User Guide. These guides are available on the server Documentation CD.
IMPORTANT: Do not power up the server until the hardware configuration is satisfactory, as described in
the procedure given in this section.
To install the controller in an unconfigured server:
1.
Install the controller hardware ("Installing the controller hardware" on page 9).
2.
If necessary, install physical drives.
The number of drives in the server determines the RAID level that is autoconfigured when the server is
powered up (next step). For details, refer to the server-specific setup and installation guide or the HP
ROM-Based Setup Utility User Guide.
3.
Power up the server. The autoconfiguration process runs.
4.
Update the system firmware ("Methods for updating the firmware" on page 11).
5.
Update the controller firmware ("Methods for updating the firmware" on page 11).
6.
Install the operating system and device drivers ("Installing device drivers" on page 18). Instructions
are provided with the CD that is supplied in the controller kit.
The server is now ready to use. If you want to create additional logical drives ("Configuring an array" on
page 12), you may now do so.
Installing the controller in a previously configured server
1.
Back up any data on the system.
2.
Update the server firmware ("Methods for updating the firmware" on page 11).
3.
If the new controller is to be the boot device, install the device drivers ("Installing device drivers" on
page 18). Otherwise, continue with step 4.
4.
Install the controller hardware ("Installing the controller hardware" on page 9).
5.
Connect storage devices to the controller ("Connecting storage devices" on page 10).
6.
Update the controller firmware ("Methods for updating the firmware" on page 11).
7.
Set the controller order, using either ORCA ("Setting a controller as the boot controller" on page 17)
or RBSU ("Setting the controller order" on page 17).
8.
If the controller is not going to be the boot device, install the device drivers ("Installing device
drivers" on page 18).
Overview of the installation procedure 7
9.
Update the Management Agents ("Installing Management Agents" on page 18) if new versions are
available.
The server is now ready to use. If you want to create additional logical drives, you may now do so.
Overview of the installation procedure 8
Installing the controller hardware
In this section
Before beginning the installation ................................................................................................................ 9
Preparing the server ................................................................................................................................. 9
Installing the controller board .................................................................................................................... 9
Connecting storage devices..................................................................................................................... 10
Before beginning the installation
Before beginning the installation procedure, visit the HP website (http://www.hp.com/support) to confirm
that you have the latest version of each driver and utility file needed. Compare the version numbers of the
files there with those of the same files on the software CD or DVD that is supplied in the controller kit.
Preparing the server
1.
Back up all data.
2.
Close all applications.
3.
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.
4.
Power down all peripheral devices that are attached to the server.
5.
Unplug the AC power cord from the outlet and then from the server.
6.
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 x8 or larger PCI Express slot.
3.
Remove the slot cover. Save the retaining screw if one is present.
Installing the controller hardware 9
4.
Slide the controller board along the slot alignment guide if applicable, and press the board firmly
into the slot so that the contacts on the board edge are properly seated in the system board
connector.
5.
Secure the controller board in place with the retaining screw. If there is a guide latch on the rear of
the board, close the latch.
6.
Connect storage devices to the controller. (For details of the procedure, see "Connecting storage
devices (on page 10).")
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.)
NOTE: Drives that are to be grouped in the same array should all have comparable capacity for efficient
use of total storage capacity.
7.
Close or replace the access panel, and secure it with thumbscrews, if any are present.
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.
Connecting storage devices
You can connect the controller ports to internal SAS backplanes that are connected to SAS or SATA
drives. For information about the supported drive models, refer to the controller-specific page on the HP
website (http://www.hp.com/products/smartarray).
1.
Power down the system.
2.
Install hard drives, if necessary.
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.)
NOTE: Drives that are to be grouped in the same array should all have comparable capacity for efficient
use of total storage capacity.
For additional information about drive installation, see the appropriate section in this guide
("Replacing, moving, or adding hard drives" on page 22) and consult the server documentation and
the documentation that accompanied the drives.
3.
4.
Use the internal wide SAS cable provided with the server to connect the controller to the drives.
•
If the drives are hot-pluggable, connect the internal connector of the controller to the SAS
connector on the hot-plug drive cage.
•
If the drives are not hot-pluggable, connect the internal connector of the controller to the non-hotpluggable hard drives.
Close or replace the access panel, and secure it with thumbscrews, if any are present.
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.
5.
If the added drives are not hot-pluggable, power up the system.
Installing the controller hardware 10
Updating the firmware
In this section
Methods for updating the firmware........................................................................................................... 11
Methods for updating the firmware
To update the firmware on the server, controller, or hard drives, use Smart Components. These
components are available on the Firmware Maintenance CD. A more recent version of a particular server
or controller component might be available on the support page of the HP website
(http://www.hp.com/support). Components for controller and hard drive firmware updates are also
available from the software and drivers page for storage products
(http://www.hp.com/support/proliantstorage).
1.
Find the most recent version of the component that you require. Components for controller firmware
updates are available in offline and online formats.
2.
Follow the instructions for installing the component on the server. These instructions are given with
the CD and are provided on the same Web page as the component.
3.
Follow the additional instructions that describe how to use the component to flash the ROM. These
instructions are provided with each component.
For more information about updating the firmware, refer to the HP ProLiant Storage Firmware
Maintenance User Guide (for controller and hard drive firmware) or the HP Online ROM Flash User
Guide (for server firmware).
Updating the firmware 11
Configuring an array
In this section
Introduction ........................................................................................................................................... 12
Comparing the utilities ............................................................................................................................ 12
Using ORCA.......................................................................................................................................... 13
Using ACU ............................................................................................................................................ 14
Using CPQONLIN.................................................................................................................................. 14
Introduction
HP provides four 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
•
ACU CLI—A command line version of ACU
•
CPQONLIN—A menu-based configuration utility specifically for servers using Novell NetWare
For more information about the features of these utilities, see "Comparing the Utilities (on page 12)."
Whichever utility you use, be aware of the following limitations:
•
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.
•
All drives in an array must be of the same type (for example, all SAS or all SATA).
•
The probability that an array will experience a drive failure increases with the number of physical
drives in the array.
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 is not supported.
Supported features
ACU
CPQONLIN
ORCA
Uses a graphical interface
+
--
--
Available in languages other than English
+
--
--
Executable at any time
+
+
Only during POST
Available on CD
+
+
CD not necessary;
located in ROM
Configuring an array
12
Supported features
ACU
CPQONLIN
ORCA
Uses a wizard to suggest the optimum configuration for
an unconfigured controller
+
+
--
Describes configuration errors
+
--
--
Supported procedures
ACU
CPQONLIN
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
+
+
--
Setting of boot controller
--
--
+
Using ORCA
1.
Power up the server.
POST runs, and all controllers in the server are initialized one at a time in the current boot order
sequence. If a controller is connected to one or more hard drives, an ORCA prompt message
appears during the initialization process for that controller.
2.
At the ORCA prompt for the controller that you want to configure, 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.
Configuring an array
13
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.
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 Documentation CD that is provided in the controller kit.
Using CPQONLIN
The NetWare Online Array Configuration Utility (CPQONLIN) is an NLM that enables you to configure
drive arrays on a NetWare server without powering down the server or storage system. CPQONLIN also
provides information about the status of drives attached to the controller.
NOTE: CPQONLIN can only be used while the server is online. If you want to configure an array when the
server is offline, you must use ACU instead.
To run CPQONLIN:
1.
Use the software CD provided with the controller to load the drivers (HPQCISS.HAM and
CPQSHD.CDM) and the executable (CPQONLIN.NLM) on the server. Detailed instructions are
provided with the CD.
2.
Enter cpqonlin at the console prompt.
3.
Use the arrow keys to highlight the Array Configuration Utility menu item, and then press the Enter
key.
4.
From the list of controllers that is presented, select the one that you want to configure.
5.
•
If there are no logical drives connected to the controller, an auto-configuration wizard opens and
prompts you for fault-tolerance information.
•
If the controller is connected to at least one logical drive, CPQONLIN continues in manual
configuration mode. Use the arrow and Enter keys to navigate around the screen and set up the
logical drive. To get online help at any time, press the F1 key.
When you have finished configuring the array, save the changes.
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.
The following sections provide details of some typical procedures.
Setting drive rebuild, expand priority, and accelerator ratio
1.
Go to the Main Configuration View screen.
2.
Highlight the controller.
Configuring an array
14
3.
Select the Controller Settings option below Controller Options. The Controller Settings screen
appears.
Drive rebuild
Drive rebuild occurs after a physical drive fails and is replaced. Only logical drives that are configured
with RAID 1+0 or RAID 5 can be rebuilt.
Priority settings
To set the drive rebuild priority:
1.
Highlight the controller.
2.
Select the controller settings:
•
If you choose low priority for drive rebuild, drive rebuilding occurs when I/O to the drive is
inactive.
•
If you choose high priority, drive rebuilding occurs faster, at the expense of normal I/O
operations.
Accelerator ratio
The controller has an onboard cache called an Array Accelerator, which performs both write-posting and
read-ahead caching. The setting in CPQONLIN determines the amount of memory allocated to the read
and write caches.
For example, if the accelerator ratio is set to Read 75%:Write 25%, 75% of Array Accelerator cache is
dedicated to read-ahead cache and 25% is dedicated to the write-posting cache. This option can be
modified from the Controller Settings menu.
Expanding an array
During an expand, performance might be slightly degraded. In most cases, however, any potential
degradation is offset by the addition of physical drives.
IMPORTANT: Be sure that the cache battery is connected and fully charged before beginning an array
expansion, RAID level migration, or stripe size migration.
Some tips for expanding include:
•
Perform the expand process during periods of low server use. If you must expand during peak
periods, CPQONLIN enables you to set the priority of the expand. Setting the priority to LOW
affects performance the least, but it takes longer for the new space to become available.
•
When expanding, always add drives with a capacity equal to or greater than the capacity of the
smallest drive in the array. Adding larger drives wastes space because only the space that is equal
to the smallest drive size can be used.
Adding or configuring spare drives
When adding a spare drive to an array, an unassigned drive must exist or a drive already assigned as a
spare must exist on another array. You can assign a single spare to any number of arrays or assign
separate spares.
When you select Assign Spare Drive, only drives that qualify appear (for example, only those spares
that are large enough appear). If drives that you expect to see do not appear, switch to the physical drive
view (Tab key), and check the size of the drives. The capacity of the spare must be equal to or greater
than the capacity of the smallest drive in the array.
Configuring an array
15
Migrating RAID level and stripe size online
Using CPQONLIN, you can modify both the RAID level and stripe size of an existing logical drive while
online.
IMPORTANT: Be sure that the cache battery is connected and fully charged before beginning an array
expansion, RAID level migration, or stripe size migration.
To migrate a drive:
1.
Select the drive setting option under the logical drive menu for the drive you intend to modify.
2.
Select the new RAID level, stripe size, or both from the choices presented. If the new settings are
valid, the migration begins when you save the changes.
Configuring an array
16
Setting the boot controller and controller order
In this section
Setting a controller as the boot controller .................................................................................................. 17
Setting the controller order ...................................................................................................................... 17
Setting a controller as the boot controller
The following procedure enables you only to set a controller as the boot controller. If you also want to
adjust the boot order settings of other controllers in the system, use RBSU instead ("Setting the controller
order" on page 17).
IMPORTANT: A controller that is to be set as the boot controller must be connected to a logical drive.
1.
Power up the server.
POST runs, and all controllers in the server are initialized one at a time in the current boot order
sequence. If a controller is connected to one or more hard drives, an ORCA prompt message
appears during the initialization process for that controller.
As soon as you see the ORCA prompt for the controller that you want to set as the boot controller,
continue with the next step.
2.
Press the F8 key.
The ORCA main menu appears. If the controller is configured with a logical drive, one of the menu
options is to set the controller as the boot controller.
3.
Select the appropriate menu option, and follow any subsequent on-screen instructions. If prompted to
save the settings, do so.
4.
If you want to configure or reconfigure an array on this controller, you can do this while you are still
in ORCA. For further information, see the ORCA procedure in the array configuration section
("Using ORCA" on page 13).
If you do not want to configure an array at this time or if you intend to use a different utility to
configure the array, exit from ORCA, and then restart the server for the new boot controller setting to
take effect.
Setting the controller order
1.
Power up the server.
The server runs the POST sequence and briefly displays an RBSU prompt.
2.
At the prompt, press the F9 key to start RBSU.
3.
Follow the on-screen instructions to set the boot order for the different controllers in the system.
4.
Save the settings.
5.
Exit from the utility.
For more information about using RBSU, refer to the HP ROM-Based Setup Utility User Guide or the server
setup and installation guide. These documents are both available on the Documentation CD supplied in
the server kit.
Setting the boot controller and controller order
17
Installing device drivers and Management
Agents
In this section
Installing device drivers........................................................................................................................... 18
Installing Management Agents ................................................................................................................. 18
Installing device drivers
The drivers for the controller are located on the Support Software CD or the SmartStart CD that is
provided in the controller kit. Updates are posted to the HP website (http://www.hp.com/support).
Using the Support Software CD: Instructions for installing the drivers from the Support Software CD
are given in the leaflet that is supplied with the CD.
Using the SmartStart CD: If you use the Assisted Installation path feature of SmartStart to install the
operating system on a new server, the drivers are automatically installed at the same time.
You can also use SmartStart to update the drivers manually on systems that are already configured. For
more information, refer to the SmartStart documentation.
Installing Management Agents
If you use the Assisted Installation path feature of SmartStart to install the operating system on a new
server, the Management Agents are automatically installed at the same time.
You can update the Management Agents by using the latest versions of the agents from the HP website
(http://www.hp.com/servers/manage). The procedure for updating the agents is provided on the same
Web page.
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).
Installing device drivers and Management Agents 18
Upgrading or replacing controller options
In this section
Replacing a battery ................................................................................................................................ 19
Upgrading the cache .............................................................................................................................. 20
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 35)" before installing or
removing any item that contains a battery pack.
The standard 64-MB cache module does not use a battery. Only the cache upgrade module uses a
battery.
1.
Close all applications, and then power down the server. This procedure flushes all data from the
cache.
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).
3.
Press the battery retainer tabs down, and push them through to the other side of the cache board (1).
Upgrading or replacing controller options 19
4.
Lift the battery off the cache board (2).
5.
Mount the new battery on the cache board by reversing the procedure used in steps 3 and 4.
6.
Reinstall the cache board and its battery on the controller by reversing the procedure used in step 2.
IMPORTANT: If the cache is not properly connected, the controller will not boot.
NOTE: After installing a battery pack, you might see a POST message during reboot indicating that the
array accelerator (cache) is temporarily disabled. This is normal, because the new battery pack is likely to
have a low charge. You do not need to take any action, because the recharge process begins automatically
when the battery pack is installed. The controller will operate properly while the battery pack recharges,
although the performance advantage of the array accelerator will be absent. When the battery pack has
been charged to a satisfactory level, the array accelerator will automatically be enabled.
Upgrading the cache
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 35)" before installing or
removing any item that contains a battery pack.
1.
Close all applications, and then power down the server. This procedure flushes all data from the
cache.
2.
Remove the existing cache module:
a. Open the ejector latches on each side of the DIMM connector (1).
Upgrading or replacing controller options 20
b. Pull the cache module out of the DIMM slot (2).
3.
Insert the cache upgrade module and its attached battery into the DIMM slot on the controller.
IMPORTANT: If the cache is not properly connected, the controller will not boot.
Upgrading or replacing controller options 21
Replacing, moving, or adding hard drives
In this section
Identifying the status of a hard drive ......................................................................................................... 22
Recognizing hard drive failure ................................................................................................................. 23
Replacing hard drives ............................................................................................................................. 24
Moving drives and arrays ....................................................................................................................... 28
Adding drives ........................................................................................................................................ 28
Identifying the status of a hard drive
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).
Item
Description
1
Fault/ID LED (amber/blue)
2
Online LED (green)
Online/Activity
LED (green)
Fault/UID LED
(amber/blue)
Interpretation
On, off, or flashing Alternating amber
and blue
The drive has failed, or a predictive failure alert has been
received for this drive; it also has been selected by a
management application.
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.
Replacing, moving, or adding hard drives 22
Online/Activity
LED (green)
Fault/UID LED
(amber/blue)
Interpretation
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 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.
Flashing irregularly Off
The drive is active, and it is operating normally.
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.
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 power-cycled 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.
Replacing, moving, or adding hard drives 23
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 can use 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 nonfault-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.
•
RAID 5 configurations can tolerate one drive failure.
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 24).
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.
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.
Replacing, moving, or adding hard drives 24
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-to-recover condition and the same POST message appears whenever the system is restarted.
Hard drive replacement guidelines
Before replacing a degraded drive, perform the following tasks:
•
Open HP 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, see the Systems Insight
Manager documentation on the Management CD.)
•
Be sure that the array has a current, valid backup.
•
Confirm that the replacement drive is of the same type (SAS or SATA) as the degraded drive.
•
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.
•
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.)
The following case is an exception:
•
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.
Fault tolerance is unavailable during a rebuild. If another drive in the array fails while a rebuild is in
progress, a fatal system error can occur, and all data on the array is then lost. In some 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)
Replacing, moving, or adding hard drives 25
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
•
The amount of unused capacity on the drives
•
For RAID 5, the number of drives in the array
Allow approximately 15 minutes per gigabyte for the rebuild process to be completed. This figure is
conservative, and the actual time required is usually less.
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
26)" to determine what action you must take.
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.
One of the drives in the array has
experienced an uncorrectable read error.
The replacement drive has an
illuminated amber Fault LED.
The replacement drive has failed.
One of the other drives in the array
has an illuminated amber Fault LED.
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.
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.
Replacing, moving, or adding hard drives 26
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:
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.
Replacing, moving, or adding hard drives 27
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.
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 12).
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 hot-pluggable 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.)
Replacing, moving, or adding hard drives 28
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.
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.
Replacing, moving, or adding hard drives 29
Diagnosing array problems
In this section
Controller board runtime LEDs.................................................................................................................. 30
Battery pack LEDs................................................................................................................................... 31
Diagnostic tools ..................................................................................................................................... 32
Controller board runtime LEDs
NOTE: During server power-up, each runtime LED illuminates randomly until POST has finished.
LED ID
Color
LED name and interpretation
1
Green
CR1: Idle Task LED. This LED, together with item 2, indicates the amount of
controller CPU activity. For details, see the following table.
2
Green
CR2: Gas Pedal LED. This LED, together with item 1, indicates the amount of
controller CPU activity. For details, see the following table.
3
Green
CR3: Heartbeat LED. This LED blinks every two seconds to indicate the controller
health.
4
Green
CR4: Command Outstanding LED. The controller is working on a command from
the host driver.
5
Green
CR5: DMA Activity LED.
6
Green
CR6: SAS Activity LED.
7
Amber
CR7: Drive Failure LED. A physical drive connected to the controller has failed.
Observe the Fault LED on each drive to determine which drive has failed.
8
Amber
CR8: Controller Lockup LED.
Diagnosing array problems 30
Idle task LED
status
Gas pedal LED
status
Controller CPU activity level
Blinking
Off
0–25%
Off
Blinking
25–50%
Off
On steadily
50–75%
On steadily
On steadily
75–100%
Battery pack LEDs
Only the cache upgrade module has a battery pack. The LEDs for the battery pack are viewable on the
cache board.
Item 1
(amber LED)
Item 2 (green
LED)
Interpretation
—
Steady glow
The cache batteries are being charged. (The
charging process takes less than three hours.)
—
Fast blink
The cache microcontroller is waiting for the host
controller to communicate.
Steady glow
—
One of the following situations is occurring:
Fast blink
—
•
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.
Diagnosing array problems 31
Item 1
(amber LED)
Item 2 (green
LED)
Interpretation
Slow blink
(once every
16 seconds)
—
This display pattern occurs after the system is
powered down if the cache contains data that
has not yet been written to the drives. Restore
system power as soon as possible to prevent
data loss. (A fully charged battery pack can
preserve cached data for up to three days.)
The life expectancy of a battery pack is
typically three years or more, depending on the
cache module size. For further information, see
the controller QuickSpecs on the HP website
(http://www.hp.com).
Diagnostic tools
Several diagnostic tools provide feedback about problems with arrays. The most important are:
•
ADU
This utility is available on both the SmartStart CD and the HP website (http://www.hp.com/support).
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.
•
Server Diagnostics
To use Server Diagnostics:
a. Insert the SmartStart CD into the server CD-ROM drive.
b. Click Agree when the license agreement appears, and click the Maintenance tab.
c. Click Server Diagnostics, and follow the on-screen prompts and instructions.
Diagnosing array problems 32
Electrostatic discharge
In this section
Preventing electrostatic discharge............................................................................................................. 33
Grounding methods to prevent electrostatic discharge ................................................................................ 33
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 static-sensitive 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.
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.
Electrostatic discharge 33
Regulatory compliance notices
In this section
European Union regulatory notice ............................................................................................................ 34
BSMI notice ........................................................................................................................................... 34
Korean class B notice.............................................................................................................................. 35
Battery replacement notice ...................................................................................................................... 35
Taiwan battery recycling notice................................................................................................................ 35
European Union regulatory notice
This product complies with the following EU Directives:
•
Low Voltage Directive 73/23/EEC
•
EMC Directive 89/336/EEC
Compliance with these directives implies conformity to applicable harmonized European standards
(European Norms) which are listed on the EU Declaration of Conformity issued by Hewlett-Packard for this
product or product family.
This compliance is indicated by the following conformity marking placed on the product:
This marking is valid for non-Telecom products and EU harmonized Telecom products (e.g. Bluetooth).
This marking is valid for EU non-harmonized Telecom products.
*Notified body number (used only if applicable—refer to the product label)
BSMI notice
Regulatory compliance notices
34
Korean class B notice
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:
• 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, please use
the public collection system or return them to HP, an authorized HP Partner, or 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.
Regulatory compliance notices
35
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
CPQONLIN
NetWare Online Array Configuration Utility
ORCA
Option ROM Configuration for Arrays
POST
Power-On Self Test
RBSU
ROM-Based Setup Utility
SA
Smart Array
SIM
Systems Insight Manager
Acronyms and abbreviations
36
Index
A
ACU (Array Configuration Utility) 14
adding drives 15, 28
ADU (Array Diagnostic Utility) 32
array capacity expansion 28
Array Configuration Utility (ACU) 14
array controller installation overview 7
Array Diagnostic Utility (ADU) 32
array, configuring 12, 15
array, moving 28
automatic data recovery (rebuild) 25
B
batteries, replacing 19
battery pack LEDs 31
battery replacement notice 35
board components 5
boot controller, setting 17
BSMI notice 34
C
cache, replacing 20
compromised fault tolerance 24
configuring an array 12
connectors 5
controller board, features of 5
controller board, installing 9
controller installation, overview of 7
controller LEDs 30
controller order, setting 17
CPQONLIN 14
drives, adding 28
drives, configuring 15
drives, moving 28
E
electrostatic discharge 33
environmental requirements 5
error messages 23, 32
European Union notice 34
expanding an array 28
extending logical drive capacity 28
F
failure of hard drive 23
fault tolerance, compromised 24
firmware, updating 11
G
grounding methods 33
H
hard
hard
hard
hard
hard
hard
hard
drive LEDs 22
drive, failure of 24
drive, replacing 24
drives, adding 28
drives, determining status of 22
drives, installing 10
drives, moving 28
I
installation overview 7
D
L
data recovery 24, 25
data transfer rate 5
device drivers, installing 18
diagnostic tools 32
drive capacity, upgrading 27
drive failure, detecting 23
drive LEDs 22
drivers 18
LEDs, battery pack 31
LEDs, controller 30
LEDs, hard drive 22
logical drive capacity extension 28
logical drive, creating 12
Index 37
M
Management Agents, updating 18
moving an array 28
O
Option ROM Configuration for Arrays (ORCA) 13
ORCA (Option ROM Configuration for Arrays) 13
overview of installation process 7
P
POST error messages 23, 32
power requirements 5
R
rebuild, abnormal termination of 26
rebuild, description of 25
rebuild, time required for 26
regulatory compliance notices 34
replacing hard drives 22
replacing the batteries 19
ROM, updating 11
runtime LEDs 30
S
Server Diagnostics utility 32
specifications, controller 5
static electricity 33
status lights, battery pack 31
status lights, controller 30
status lights, hard drive 22
storage capacity, increasing 27
storage devices, connecting 10
T
Taiwan battery recycling notice 35
temperature requirements 5
troubleshooting 32
U
updating the firmware 11
upgrading drive capacity 27
Index 38
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertisement