Smart array 6400 controller manual

If the new controller is to be the boot device, install the device drivers for the operating system "Installing device drivers" on page Otherwise, continue with step 4.

Taking this precaution ensures that the system does not erroneously mark the drives as failed when the server is powered 3. Page Connecting Storage Devices Installing the controller hardware 7. Replace the access panel, and secure it with screws if any are present. Operating the server without the access panel results in improper airflow and improper cooling that can lead to thermal damage.

If the drives are hot-pluggable, go to step 3. If the drives are not hot-pluggable, go to step 4. Attach the internal point-to-point SCSI cable provided with the server from the internal connector of the controller to the hot-plug drive cage. These components are available on the Firmware Maintenance CD.

NOTE: The 2-channel expansion module is a controller in its own right. This document is available on the Documentation CD that is provided in the controller kit. Power up the server. POST runs, and any array controllers that are in the server are initialized one at a time. 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.

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. To migrate a drive: 1.

Select the drive setting option under the logical drive menu for the drive you intend to modify. Refer to "Battery replacement notice on page 62 " Pull the cache module out of the DIMM slot 2. 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. 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.

Replace whichever battery is degraded. Reinstall the batteries on the cache board and the controller board. Secure the expansion module to the controller board by inserting and tightening the appropriate screw provided in the kit in the back of the controller board 4. Front panel components.

Front panel LEDs and buttons. UID button functionality. Front panel LED power fault codes. Rear panel components. Rear panel LEDs. System board components. System maintenance switch descriptions. DIMM label identification.

DIMM slot locations. HPE Persistent Memory module label identification. Processor, heatsink, and socket components. Fan bay numbering. Drive box identification. Drive bay numbering. Drive bay numbering: Smart Array controller. Drive bay numbering: SAS expander. Drive bay numbering: NVMe drives. Riser components. Checking the battery backup charge level. Power up the server. Power down the server. Extending the server from the rack. Removing the server from the rack.

Secure cables using the cable management arm. Release the cable management arm. Remove the access panel. Install the access panel. Removing the fan cage. Installing the fan cage. Removing the air baffle or midplane drive cage. Installing the air baffle. Removing a riser cage. Removing a riser slot blank. Removing the hard drive blank. Accessing the Systems Insight Display. HPE support services. Set up the server. Operational requirements. Space and airflow requirements. Temperature requirements.

Power requirements. Electrical grounding requirements. Connecting a DC power cable to a DC power source. Server warnings and cautions. Rack warnings. Electrostatic discharge. Server box contents. Installing hardware options. Additionally, note that the driver will not engage the SCSI core at init time. This is because at driver init time, the SCSI core may not yet be initialized because the driver is a block driver and attempting to register it with the SCSI core in such a case would cause a hang.

For example:. Once the SCSI core is engaged by the driver, it cannot be disengaged except by unloading the driver, if it happens to be linked as a module. Note also that if no sequential access devices or medium changers are detected, the SCSI core will not be engaged by the action of the above script.