adaptec_smarthba_smartraid_x200_iug_7_2021

Adaptec® SmartRAID 3200 and SmartHBA 2200 Installation
and User Guide
© 2021 Microchip Technology Inc. User Guide DS-00004037A-page 1

and its subsidiaries
Table of Contents
1. Regulatory Compliance Statements........................................................................................................5
2. About This Guide.................................................................................................................................... 8

2.1. What You Need to Know Before You Begin................................................................................. 8
2.2. Terminology Used in this Guide....................................................................................................8
2.3. How to Find More Information...................................................................................................... 8
3. Kit Contents and System Requirements................................................................................................. 9

3.1. Kit Contents..................................................................................................................................9
3.2. System Requirements.................................................................................................................. 9
4. About Your Host Bus Adapter............................................................................................................... 10

4.1. About Your SmartRAID 3200 Series Host Bus Adapter............................................................. 10
4.2. About Your SmartHBA 2200 Series Host Bus Adapter.............................................................. 15
5. Installing the Controller and Disk Drives............................................................................................... 18

5.1. Before You Begin........................................................................................................................18
5.2. Selecting Disk Drives and Cables.............................................................................................. 18
5.3. Installing the Host Bus Adapter.................................................................................................. 19
6. Installing the Driver and an Operating System......................................................................................21

6.1. Download the Driver Package....................................................................................................21
6.2. Creating a Driver Disk................................................................................................................ 21
6.3. Installing with Windows ............................................................................................................. 21
6.4. Installing with Red Hat Linux ..................................................................................................... 22
6.5. Installing with SuSE Linux Enterprise Server............................................................................. 23
6.6. Installing with Oracle Linux.........................................................................................................24
6.7. Installing with Ubuntu Linux........................................................................................................25
6.8. Installing with Debian Linux........................................................................................................25
6.9. Installing with FreeBSD.............................................................................................................. 26
6.10. Installing with Solaris..................................................................................................................28
6.11. Installing with Citrix XenServer ..................................................................................................30
6.12. Installing with VMware ...............................................................................................................30
7. Installing the Driver on an Existing Operating System.......................................................................... 32

7.1. Download the Driver Package....................................................................................................32
7.2. Creating a Driver Disk................................................................................................................ 32
7.3. Installing on Windows ................................................................................................................32
7.4. Installing on Red Hat.................................................................................................................. 32
7.5. Installing on SuSE Linux Enterprise Server............................................................................... 34
7.6. Installing on Oracle Linux........................................................................................................... 35
7.7. Installing on Ubuntu Linux.......................................................................................................... 36
7.8. Installing on Debian Linux.......................................................................................................... 37
7.9. Installing on FreeBSD................................................................................................................ 37
7.10. Installing on Solaris.................................................................................................................... 37
7.11. Installing on Citrix XenServer..................................................................................................... 39
7.12. Installing on VMware.................................................................................................................. 39

8. Solving Problems ................................................................................................................................. 40
8.1. Troubleshooting Checklist.......................................................................................................... 40
8.2. Resetting the Adapter ................................................................................................................40
9. Using the Microchip SAS/SATA HII Configuration Utility.......................................................................41

9.1. Running the Microchip SAS/SATA Configuration Utility: UEFI/HII..............................................41
9.2. Controller Information.................................................................................................................41
9.3. Creating an Array....................................................................................................................... 41
9.4. Creating a maxCache Array....................................................................................................... 42
9.5. Managing Arrays and Logical Drives..........................................................................................42
9.6. Modifying SmartHBA 2200/SmartRAID 3200 Controller Settings.............................................. 45
9.7. Clearing the Controller Configuration......................................................................................... 47
9.8. Backup Power Source................................................................................................................47
9.9. Managing Power Settings.......................................................................................................... 47
9.10. Out of Band Messaging Settings................................................................................................48
9.11. Using the Encryption Manager................................................................................................... 49
9.12. Configuring the Controller Port Mode.........................................................................................52
9.13. Device Information..................................................................................................................... 53
9.14. Identifying a Disk Drive...............................................................................................................53
9.15. Erasing a Disk Drive...................................................................................................................53
9.16. Updating Drive Firmware............................................................................................................53
9.17. Clearing Configuration Meta-data.............................................................................................. 54
9.18. Setting the Bootable Device(s) for Legacy Boot Mode...............................................................54
9.19. Updating the SmartHBA 2200 Firmware.................................................................................... 54
9.20. Creating a Support Archive........................................................................................................ 55
9.21. Resetting the Controller to Factory Defaults.............................................................................. 55
9.22. Extracting Controller Debug Token.............................................................................................55
10. Installing the SmartPQI Drivers from Source ....................................................................................... 56

10.1. Installation Instructions for Supported Linux OSes.................................................................... 56
10.2. Using the Installation DVD as the Repository............................................................................ 57
11. SmartRAID/SmartHBA Physical and Logical Device Support...............................................................59
12. Safety Information................................................................................................................................. 60

12.1. Electrostatic Discharge (ESD)....................................................................................................60
13. Technical Specifications........................................................................................................................ 61

13.1. Environmental Specifications..................................................................................................... 61
14. Revision History.................................................................................................................................... 62
The Microchip Website.................................................................................................................................63
Product Change Notification Service............................................................................................................63
Customer Support........................................................................................................................................ 63
Microchip Devices Code Protection Feature................................................................................................ 63
Legal Notice................................................................................................................................................. 64

Trademarks.................................................................................................................................................. 64
Quality Management System....................................................................................................................... 65
Worldwide Sales and Service.......................................................................................................................66

Regulatory Compliance Statements
1. Regulatory Compliance Statements

Federal Communications Commission Radio Frequency Interference Statement
Attention: Changes or modifications to this unit not expressly approved by the party responsible for
compliance could void the user's authority to operate the 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 instruction manual, may cause harmful interference to radio communications.
However, there is no guarantee that interference will not occur in a particular installation. However, if this equipment
does cause interference to radio or television equipment 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 equipment and receiver.
• Connect the equipment to an outlet on a circuit different from that to which the receiver is connected.
• Consult the dealer or an experienced radio/television technician for help.
• Use a shielded and properly grounded I/O cable and power cable to ensure compliance of this unit to the
specified limits of the rules.
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.
UL Compliance Statement—Pending
From Microchip Adaptec products are tested and listed by Underwriters Laboratories, Inc. to UL
60950-1 /IEC 62368-1 Second Edition and IEC-60950-1/IEC 62368-1 Second Edition standards, file
numbers E516387. Microchip Adaptec products are for use only with UL listed ITE.
Microchip Corporation Use only with the listed ITE:
SmartRAID Ultra 3258P-32i /e

SmartRAID 3258-16i /e
SmartRAID 3254-8i
SmartRAID 3204-8i
SmartHBA 2200-16i

European Union Compliance Statement—Pending
This Information Technology Equipment has been tested and found to comply with EMC Directive
2014/30/EU, in accordance with:
• EN55032 (2014) Emissions:
– Class B ITE radiated and conducted emissions
• EN55024 (2010) Immunity:
– EN61000-4-2 (2009) Electrostatic discharge: ±4 kV contact, ±8 kV air
– EN61000-4-3 (2010) Radiated immunity: 3V/m
– EN61000-4-4 (2012) Electrical fast transients/burst: ±1 kV AC, ±0.5 kV I/O
– EN61000-4-5 (2014) Surges: ±1 kV differential mode, ±2 kV common mode
– EN61000-4-6 (2014) Conducted immunity: 3 V
– EN61000-4-11 (2004) Supply dips and variations: 30% and 100%
• EN 63000:2018 Technical Documentation:
– For the assessment of electrical and electronic products with respect to the restriction of
hazardous substances
• EC 62368-1:2014 (EU)
• IEC 60950-1:2005 (US)
In addition, all equipment requiring U.L. listing has been found to comply with EMC Directive 2014/35/EU,
in accordance with EN 62368 with amendments A1, A2, A3, A4, A11, A12.
The Restriction of the Use of Certain Hazardous Substances in Electrical and Electronic Equipment
Regulations 2012 – SI 2012 No. 3032.
Electromagnetic Compatibility Regulations 2016 – SI 2008 No. 1597.
The Electrical Equipment (Safety) Regulations 2016 – SI 2016 No. 1101.
Australian/New Zealand Compliance Statement—Pending
This device has been tested and found to comply with the limits for a Class B digital device, pursuant to the
Australian/New Zealand standard AS/NZS 3548 set out by the Spectrum Management Agency.
Canadian Compliance Statement—Pending
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.
Japanese Compliance (Voluntary Control Council Initiative)—Pending
This equipment complies to class B Information Technology equipment based on VCCI (Voluntary Control
Council for Interface). This equipment is designed for home use but it may causes radio frequency
interference problem if used too near to a television or radio. Please handle it correctly per this
documentation.

Korean Compliance (KCC) Statement—Pending

®
Microchip Adaptec products are tested and certified by KCC:
Korean Compliance (KCC) Statement:
R-R-M5P-3258P-32i
The above certification covers the following series:
SmartRAID Ultra 3258P-32i /e

R-R-M5P-3254-16e
SmartRAID Ultra 3254-16e /e

R-R-M5P-3258P-16i
SmartRAID Ultra 3258P-16i/e
R-R-M5P-3258-16i
SmartRAID 3254-8i
Smart HBA 2200-16i
This equipment is home use (Class B) electromagnetic wave suitability equipment and to be used mainly at
home and it can be used in all areas.

About This Guide
2. About This Guide

This Installation and User's Guide explains how to install and setup your SmartRAID 3200 or SmartHBA 2200 Series
Host Bus Adapter, including driver installation, BIOS operations, troubleshooting tips, and instructions for flashing the
adapter firmware.
These SmartRAID 3200 Series adapter models are described in this guide:
• Adaptec SmartRAID Ultra 3258P-32i /e
• Adaptec SmartRAID 3258-16i /e
• Adaptec SmartRAID 3254-16i /e
• Adaptec SmartRAID 3254-8i
• Adaptec SmartRAID 3204-8i
These SmartHBA 2200 Series adapter models are described in this guide:
• Adaptec SmartHBA 2200-16i
2.1 What You Need to Know Before You Begin

This guide is written for data storage and IT professionals who are responsible for installing, configuring, and
maintaining SmartHBA 2200/SmartRAID 3200 Series Host Bus Adapters in computers or servers in a "cloud" or data
center environment. You should be familiar with computer hardware, operating system administration, data storage
devices, and SAS and Serial ATA (SATA) technology.
If you are responsible for configuring the storage resources on the SmartRAID and SmartHBA adapters, you should
be familiar with RAID technology and creating bootable volumes.
2.2 Terminology Used in this Guide

Many of the terms and concepts referred to in this guide are known to computer users by multiple names. This guide
uses these terms:
• Host Bus Adapter or HBA (also known as controller, adapter, or I/O card)
• Disk drive (also known as hard disk, hard drive, or hard disk drive)
• Solid State Drive (also known as SSD or non-rotating storage media)
• Enclosure (also known as a storage enclosure, disk drive enclosure, or JBOD)
2.3 How to Find More Information

You can find more information about your SmartHBA 2200/SmartRAID 3200 Series Host Bus Adapter by referring to
these documents, available for download at start.adaptec.com.
• ARCCONF Command Line Utility User's Guide for Adaptec Smart Storage Controllers—Describes how to use
the ARCCONF utility to perform configuration and storage management tasks from an interactive command line.
(ESC-2161615)
• SmartRAID 3200 Series and SmartHBA 2200 Series Host Bus Adapters Installation and User's Guide (this
manual)—Describes how to install SmartRAID 3200 and SmartHBA 2200 Series adapters in a computer or
server, install drivers, and configure the adapter for initial use. (DS-00004037A)
• Adaptec Flash Backup Module ASCM-35 and ASCM-40 Installation Instructions (ESC-2170352)—Describes
how to install the ASCM-35 and ASCM-40 Flash Backup module using the mounting plate method.

Kit Contents and System Requirements
3. Kit Contents and System Requirements

This section lists the contents of your SmartHBA 2200/SmartRAID 3200 Series kit and the system requirements for
successfully installing and using your adapter.
3.1 Kit Contents

SmartRAID 3200 Series kits:
• SmartRAID 3200 Series adapter
• Full-height ("FH") and Low-profile ("LP") brackets, with mounting screws
• ASCM-40F or ASCM-35F Supercap Module, including:
– Supercap module extension cable
– Full-height and Low-profile mounting plate, with mounting screws
– Supercap mounting clip
– Tie-wraps (nylon)
SmartHBA 2200 Series kits:
• SmartHBA 2200 Series adapter
• Full-height ("FH") and Low-profile ("LP") brackets, with mounting screws
Note: The latest firmware, drivers, utilities software, and documentation can be downloaded at
storage.microsemi.com. For more information, see Downloading the Driver Package.
3.2 System Requirements

• PC-compatible computer with Intel Pentium, or equivalent, processor
• 4 GB of RAM minimum
• Available compatible PCIe slot (depending on your adapter model—see the descriptions in About Your Host Bus
Adapter)
• One of these operating systems:
• Microsoft® Windows® Server, Windows 10, Windows 8.1, Windows 7
• Red Hat® Enterprise Linux
• CentOS
• SuSE Linux Enterprise Server
• Ubuntu Linux
• Debian Linux
• Oracle Linux
• Citrix Xenserver
• Solaris
• FreeBSD
• VMware ESXi
See the Release Notes for a complete list of supported OS versions.
• USB flash drive or CD burner, for creating driver disks and bootable media

About Your Host Bus Adapter
4. About Your Host Bus Adapter
4.1 About Your SmartRAID 3200 Series Host Bus Adapter

This section provides an overview of the features of the SmartRAID 3200 Series adapter.
4.1.1 Standard Features

• Low profile, MD2 form factor on all boards with up to 16 ports, full-height, half-length form factor for 32 port
variants
• 8-lane (x8) or 16-lane (x16 “ultra”) PCIe Gen4 host interface
• Internal SlimSAS (SFF-8654) and external mini-SAS HD connectors using SFF-9402 pinout to support U.2 and
U.3)
• Secure Boot and Secure Debug
• maxCrypto CBE for SAS, SATA and NVMe devices
• Universal Backplane Management (UBM)
• Virtual Pin Port Management (VPP)
• SES (SAS expander-based backplanes), SGPIO (direct attached SAS/SATA backplanes)
• Dynamic adapter power management
• maxView tool suite support
• Support for 64 NVMe devices and up to 256 SAS/SATA and up to 64 LD/RAID arrays
• RAID 0, 1 Triple, 10 Triple, 5, 6, 50, 60
• RAID level migration and online capacity expansion
• Mixed mode and HBA mode support
• maxCache SSD caching (SmartRAID 325x only)
• Support for AMD x86 platform
• Zero Maintenance Cache Protection (ZMCP) integrated with all SmartRAID 325x products
Note: See the Product Brief for a complete list of supported features.
4.1.2 Mechanical Information
4.1.2.1 Board Dimensions

This table shows the board dimensions of the SmartRAID 3200 Series adapters, in inches.
Table 4-1. Full-Height (FH) Board Dimensions (32 port)
Dimension Measure
Height 4.376
Length 6.60
PCB thickness 0.062
Max. component height, top side Not to exceed 0.57 in.
Max. component height, bottom side Not to exceed 0.105 in.
Table 4-2. Low-Profile (LP) Board Dimensions (16 port, 8 port)
Dimension Measure
Height 2.731
Length 6.60

...........continued
Dimension Measure
PCB thickness 0.062
Max. component height, top side Not to exceed 0.57 in.
Max. component height, bottom side Not to exceed 0.105 in.
4.1.2.2 Heat Sink

SmartRAID 3200 Series adapters include a passive heat sink. The heat sink does not support an optional fan. The
heat sink has a minimum of four push-pins located at its four corners to ensure an even distribution of force across
the top of the ASIC. For airflow requirements, see 13.1 Environmental Specifications
4.1.3 Visual Indicators

LEDs on SmartRAID 3200 Series adapters provide a visual indication of the board hardware status and cache
backup system. The LED locations vary, and may be on the front of the board or back of the board. The LED states
are described in the following tables.
For LED locations, see the board images in 4.1.4 About the SmartRAID Ultra 3258P-32i /e Adapter, 4.1.5 About the
SmartRAID 3258-16i /e and 3254-16i /e Adapters, and 4.1.6 About the SmartRAID 3254-8i and 3204-8i Adapters.
Table 4-3. SmartRAID 3200 Series Status LEDs
LED Color Meaning

DDR_LED1 Yellow Cache backup error
DDR_LED2 Green Dirty cache
DDR_LED3 Green Charge status
HEARTBEAT Green Heartbeat (blinks once per/second
when firmware operating normally)
FAULT Yellow Hardware Lockup/Fault: OFF =
NORMAL OPERATION, ON =
FAULT
CRYPTO Green Cryptographic State: Off = NON-
ENCRYPTING, On = ENCRYPTING
PAL_DEBUG Yellow (8i adapters) Debug LED control signal
Red (16i adapters)

4.1.4 About the SmartRAID Ultra 3258P-32i /e Adapter

The SmartRAID Ultra 3258P-32i /e Adapter is a tri-mode (SAS/SATA/NVMe) Host Bus Adapter with these features:
Figure 4-1. SmartRAID Ultra 3258P-32i /e Adapters
Form Factor Full height PCI half length

Bus compatibility PCIe 4.0
PCIe bus width x16
Data transfer rate (SAS) 24 Gb/s per port
Phys (Unified Serial Ports) 32
Standard memory 10x 8 GB DDR4, 32 MB SPI Flash, 128 kB SAS FRU EEPROM
Connectors, internal 4x SlimSAS x8
Maximum number of disk drives 32 (SAS/SATA/NVMe)
Enclosure Support UBM, VPP, SGPIO
Controller-Based Encryption Yes
Thermal sensors Processor temperature, Ambient temperature

4.1.5 About the SmartRAID 3258-16i /e and 3254-16i /e Adapters

The SmartRAID 3258-16i /e and 3254-16i /e Adapters are tri-mode (SAS/SATA/NVMe) Host Bus Adapters with these
features:
Figure 4-2. SmartRAID 32xx-16i /e Adapters
Form Factor Half height; half length

PCIe bus width x8
PHYs (Unified Serial Ports) 16
Standard memory 5x 8 GB DDR4 used in standard configuration, 32 MB SPI Flash, 128
kb SAS FRU EEPROM
Controller-Based Encryption SmartRAID 3258-16i/e: Yes
SmartRAID 3254-16i /e: Yes

4.1.6 About the SmartRAID 3254-8i and 3204-8i Adapters

The SmartRAID 3254-8i and 3204-8i Adapters are tri-mode (SAS/SATA/NVMe) Host Bus Adapters with these
features:
Figure 4-3. SmartRAID 32x4-8i Adapters
Table 4-4. SmartRAID 3254-8i and 3204-8i Adapters

PCIe bus width x8
Standard memory 10x 8 GB DDR4, 32 MB SPI Flash, 128 kb SAS FRU EEPROM
Controller-Based Encryption SmartRAID 3254-8i: No
SmartRAID 3204-8i: No

4.2 About Your SmartHBA 2200 Series Host Bus Adapter

This section provides an overview of the features of the SmartHBA 2200 Series adapter.
4.2.1 Standard Features

• Low profile, MD2 form factor
• Fully tri-mode capable: 16 Gbps NVMe Gen 4, 24 Gbps SAS4 and 6 Gbps SATA
• 8-lane (x8) PCIe Gen 4 host interface
• Internal SlimSAS connector (using SFF-9402 pinout to support U.2 and U.3)
• Universal backplane management (UBM)
• Virtual Pin Port Management (VPP)
• SES (SAS expander-based backplanes), SGPIO (direct attached SAS/SATA backplanes)
• Secure Boot and Secure Debug
• Dynamic adapter power management
• arcconf/maxView support
• Support for 64 NVMe devices and up to 256 SAS/SATA devices
• Broad inbox OS coverage
• Comprehensive out-of-box driver support
• Multi-initiator support
• Support for AMD x86 platform
Note: See the Product Brief for a complete list of supported features.
4.2.2 Mechanical Information
4.2.2.1 Board Dimensions

See Table 4-2 for more information.
4.2.2.2 Heat Sink

SmartHBA 2200 Series adapters include a passive heat sink capable of bi-directional airflow. The heat sink does not
support an optional fan. The heat sink has a minimum of four push-pins located at its four corners to ensure an even
distribution of force across the top of the ASIC. For airflow requirements, see 13.1 Environmental Specifications
4.2.3 Visual Indicators

LEDs on the SmartHBA 2200 Series adapters provide a visual indication of the board hardware status. The LED are
located on the back of the board. The LED states are described in section 4.1.3 Visual Indicators.
For LED locations, see the board images in 4.2.4 About the SmartHBA 2200-16i Adapter.

4.2.4 About the SmartHBA 2200-16i Adapter

The SmartHBA 2200-16i Adapter is a tri-mode (SAS/SATA/NVMe) Host Bus Adapter with these features:
Figure 4-4. SmartHBA 2200-16i Adapter

PCIe bus width x8
Standard memory 10x 8 GB DDR4, 32 MB SPI Flash, 128 kb SAS FRU EEPROM
Maximum number of disk drives 16 (SAS/SATA)


Controller-Based Encryption No

Installing the Controller and Disk Drives
5. Installing the Controller and Disk Drives

This section explains how to install your SmartHBA 2200/SmartRAID 3200 Series adapter in a computer cabinet or
server and connect it to internal and external disk drives.
5.1 Before You Begin

• Read Safety Information.
• Familiarize yourself with your host bus adapter's physical features (for 3200 boards, see 4.1.1 Standard
Features; for 2200 boards, see 4.2.1 Standard Features).
• Ensure that you have the right number of disk drives for your application (see 5.2 Selecting Disk Drives and
Cables).
5.2 Selecting Disk Drives and Cables
5.2.1 Disk Drives

Your SmartHBA 2200/SmartRAID 3200 Series adapter supports SAS and SATA disk drives, Solid State Drives
(SSDs), and SAS tape drives. For more information about compatible disk drives, refer to www.microsemi.com/
products/storage/compatibility.
5.2.2 Cables
Depending on your application requirements, you can use any of the cables listed below (for typical applications;
list not exhaustive). For more information about cabling options for your SmartHBA 2200/SmartRAID 3200 Series
adapter, visit www.adaptec.com/cables
Note: We recommend using Microchip Adaptec SAS cables only.
SlimSAS Cables
SlimSAS x8 : SlimSAS x8
SFF-8654 to SFF-8654
SlimSAS x8 : miniSAS HD
SFF-8654 to SFF-8643

5.3 Installing the Host Bus Adapter

This section describes how to install your SmartHBA 2200/SmartRAID 3200 Series adapter in a computer cabinet or
server and connect internal and external storage devices. The SmartHBA 2200/SmartRAID 3200 Series adapters are
configured with Adapters with internal connectivity.
1. Turn off your computer and disconnect the power cord and any network cables. Open the cabinet, following
the manufacturer's instructions.
2. Select an available PCIe expansion slot that's compatible with your adapter model and remove the slot cover,
as shown in the figure below. (To check PCIe bus compatibility of your adapter, see 4. About Your Host Bus
Adapter.)
Note: For SmartRAID 3200 Series adapters with an external supercapacitor module, select a slot for the
adapter that's next to an empty slot in the backplane, ideally, a short.
Touch a grounded metal object before handling the adapter.

CAUTION
3. Insert the adapter into the expansion slot and press down gently but firmly until it clicks into place. When
installed properly, the adapter should appear level with the expansion slot.
Be sure to handle the adapter by its bracket or edges only. Apply pressure only on the edges when
CAUTION
inserting the card into expansion slot.

4. Secure the bracket in the expansion slot, using the retention device (for instance, a screw or lever) supplied
with your computer.
5. Connect SlimSAS cables between the adapter and internal disk drives or enclosures, as required:
6. Close your computer cabinet, reconnect the power cord and network cables, then power up the system.

Installing the Driver and an Operating System
6. Installing the Driver and an Operating System

This chapter explains how to install the SmartPQI controller driver and an operating system on a bootable volume. It
assumes that the SmartHBA 2200/SmartRAID 3200 is installed in a computer or server.
Note: For information about building the SmartPQI drivers from source, see 10. Installing the SmartPQI Drivers
from Source .
6.1 Download the Driver Package

Complete these steps to download the drivers for your operating system(s):
1. Open a browser window, then type start.adaptec.com in the address bar.
2. Enter your product or adapter model number, then select SmartRAID 3200 or SmartHBA 2200.
3. Select your operating system version, for instance, Microsoft Windows Server 2016 x64 or Red Hat Enterprise
Linux 7; then select the appropriate driver from the list.
4. Download the controller driver package (zip file archive).
5. When the download completes, extract the package contents to a temporary location on your machine. Each
driver is stored in a separate folder (\windows 2016, \rhel7, \rhel6, and so on).
Note: See the Release Notes for a complete list of available driver files.
6.2 Creating a Driver Disk

Create a driver disk by completing the steps below. You will need a USB flash drive to complete this task.
Note: For VMware, see 6.12 Installing with VMware .
1. Change to the driver directory for your operating system version.
2. Write the driver binary file to a USB flash drive.
For example, if the USB drive is /dev/sdc on the Linux system, type (where #.#.#-### is the build number):
Option Description
RHEL 7 dd if=smartpqi-#.#.#-###.rhel7u2.x86_64.dd of=/dev/sdc
SLES 12 dd if=smartpqi-#.#.#-###.sles12sp1.x86_64.dd of=/dev/sdc
Note: See the Release Notes for the latest build number.
3. Remove and label the driver disk.
4. Continue the installation with the instructions for your operating system.
6.3 Installing with Windows

Note:
Use the following procedure for all supported Windows versions. You will need your Windows Installation DVD (or
equivalent virtual media/iso image) to complete this task.
To install the controller SmartPQI driver while installing Windows:
1. Insert the Windows installation DVD, then restart the computer.
2. Follow the on-screen instructions to begin the Windows installation.
3. When prompted to specify a location for Windows, select Load Driver.
4. Insert the USB driver disk, browse to the driver location, then click Ok.
5. When prompted to select the driver to install, click Next.
6. Click Next again to accept the default partition configuration.
7. Follow the on-screen instructions to complete the installation.

6.4 Installing with Red Hat Linux

To install the controller SmartPQI driver while installing Red Hat Linux, follow the steps in the sections below.
RHEL7 Update 3 Installation and Above

To install the RHEL7 Update 3 driver with a Linux system:
1. Install the Linux system using the inbox smartpqi driver.
2. After the installation completes, install the latest smartpqi driver rpm by using the following command (where
#.#.#-### is the build number):
rpm –ivh kmod-smartpqi-#.#.#-###.rhel7u3.x86_64.rpm
RHEL7 Installation
Note: The following steps apply to all updates of RHEL 7 prior to Update 3. The example illustrated here represents
the steps for Update 2. Modify the filename of the installation archive to match the appropriate update version in the
appropriate fields.
To install the RHEL7 driver with a Linux system:
1. Copy the RHEL driver binary image to the USB key; see 6.2 Creating a Driver Disk.
2. Power-on the system.
3. Insert the RHEL7 DVD image from a media source.
4. Boot the RHEL installation.
5. Type "e" to edit the grub entry and append "modprobe.blacklist=aacraid inst.dd".
Note: This will cause the line to wrap. The editor adds the "\" automatically.
6. Insert the USB device, then type CTRL+X to boot.
Note: If the installer does not display the driver update media, type "r" and Enter on your keyboard to refresh
the list.
6.1. Select the device in the list with the label "OEMDRV":
The installer presents a driver (smartpqi rpm) to install.
6.2. Type "1" on your keyboard and Enter to select the driver update.
6.3. Type "c" and Enter to continue.
Note: It is recommended to remove the USB device once the driver update has been extracted, for
example:
DD: Extracting files....
RHEL6 Update 9 Installation and Above

To install the RHEL6 Update 9 driver with a Linux system:
#.#.#-### is the build number): rpm –ivh smartpqi-kmp-default-#.#.#-###.rehl6u9.x86_64.rpm
RHEL6 Installation
To install the RHEL6 driver with a Linux system:
1. Copy the RHEL driver binary image to the USB key; see 6.2 Creating a Driver Disk.
3. Insert the RHEL6 DVD image from a media source.
4. Boot the RHEL installation.
5. Press the Esc key when a grub entry appears with a countdown.
6. Type "e" to edit the grub entry
7. Type "e" again and append "blacklist=aacraid dd".
8. Press the Enter key and type "b".
9. Select Yes to specify that the driver disk is available.

10. Select the sd device.

Note: The device name of the driver update disk may vary.
11. Select No when the "More Driver Disks?" dialog appears.
Note: It is recommended to remove the USB device at this step.
12. Proceed with the normal installation.
6.5 Installing with SuSE Linux Enterprise Server

To install the controller SmartPQI driver while installing SuSE Linux, follow the steps in the sections below.
Installing with SLES 12 SP2 and Above

Follow these steps to install the driver while installing SLES 12 SP2:
rpm -ivh smartpqi-ueficert-#.#.#-###.sles12sp2.x86_64.rpm
rpm -ivh smartpqi-kmp-default-#.#.#-###.sles12sp2.x86_64.rpm
Installing with SLES 12

Follow these steps to install the driver while installing SLES 12:
1. Copy the SLES driver binary image to the USB key; see 6.2 Creating a Driver Disk.
3. Insert the SLES 12 DVD image from a media source.
4. Boot the SLES installation.
5. Type "e" to edit the grub entry when the SLES installation menu is displayed and append
"broken_modules=aacraid driverupdate=1".
6. Insert the USB device and type CTRL+X to boot.
The installation of the driver will start automatically.
7. Make sure that the controller is listed in the "Please choose the Driver Update medium" dialog box.
Note: If you do not see the controller, a driver installation error occurred. This can happen if the driver was
built against a different kernel version of the OS than the installed media.
Note: It is recommended to remove the driver update USB device.
8. Click Back and continue with the normal installation procedure.
Installing with SLES 11

Follow these steps to install the driver while installing SLES 11:
1. Copy the SLES driver binary image to the USB key; see 6.2 Creating a Driver Disk.
3. Insert the SLES 11 DVD image from a media source.
4. Boot the SLES installation.
5. Type "e" to edit the grub entry and append "broken_modules=aacraid driverupdate=1".
6. Insert the USB device and type CTRL+X to boot.
7. Make sure that the controller is listed in the "Please choose the Driver Update medium" dialog box.
Note: If you do not see the controller, a driver installation error occurred. This can happen if the driver was
built against a different kernel version of the OS than the installed media.
Note: It is recommended to remove the driver update USB device.

8. Click Back and continue with the normal installation procedure.
6.6 Installing with Oracle Linux

To install the controller SmartPQI driver while installing Oracle Linux, follow the steps in the sections below.
Installing with Oracle Linux 7.3 and Above

Notes:
1. The Oracle Linux 7.3 base kernel includes a smartpqi driver. The UEK kernel does not.
2. If using the UEK boot ISO for installation, you will need to use the driver update process described in the
Oracle Linux 7.2 installation section.
Follow these steps to install the driver while installing Oracle Linux 7.3:
2. On reboot, select the Oracle Linux 7.3 base kernel from the grub menu to boot. Grub will attempt to default to
the UEK kernel.
3. After the installation completes, install the latest smartpqi driver rpm for the kernel you intend to run (where
Base Kernel: rpm –ivh kmod-smartpqi-#.#.#-###.ol7u3.x86_64.rpm
UEK Kernel: rpm –ivh kmod-smartpqi-uek-#.#.#-###.ol7u3.x86_64.rpm
Installing with Oracle Linux 7.2

Follow these steps to install the driver while installing Oracle Linux 7.2:
1. Copy the Oracle Linux driver binary image to the USB key; see 6.2 Creating a Driver Disk.
3. Insert the Oracle Linux 7 DVD image from a media source.
4. Boot the Oracle installation.
5. Type "e" to edit the grub entry when the Oracle Linux installation menu is displayed and append
"modprobe.blacklist=aacraid inst.dd".
7. Complete the following steps:
7.1. Select the device in the list with the label "OEMDRV".
The installer will present a driver (smartpqi rpm) to install.
7.2. Type "1" on your keyboard, then press Enter to select the driver update.
7.3. Type "c", then press Enter to continue.
Note: We recommend that you remove the USB device once you see that the driver update has
been extracted; for example: "DD: Extracting files...".
7.4. Click Continue and follow the prompts for a normal install.
Note: The driver update will install the smartpqi driver for the Oracle Linux 7.2 base kernel only.
8. On reboot, select the Oracle Linux 7.2 base kernel from the grub menu to boot. Grub will attempt to default to
the UEK kernel.
9. After the installation completes, install the latest smartpqi driver rpm for the UEK kernel (where #.#.#-### is the
build number):
UEK Kernel: rpm –ivh kmod-smartpqi-uek-#.#.#-###.ol7u2.x86_64.rpm

6.7 Installing with Ubuntu Linux

To install the controller SmartPQI driver while installing Ubuntu Linux:
Note: The following instructions apply to Ubuntu Server only.
1. Copy the Ubuntu driver binary image to the USB key; see 6.2 Creating a Driver Disk.
3. Insert the Ubuntu CD/DVD image from a media source.
4. Boot the Ubuntu installation.
5. Type "e" to edit the grub entry when the Ubuntu installation menu is displayed.
6. Append "modprobe.blacklist=aacraid" after the “--“ on the line starting with “Linux”.
The driver installation will start automatically.
8. When the installer presents a dialog regarding detection of a virtual driver disk, select yes. Then proceed with
standard installation process.
Note: It is recommended to remove the driver update USB device when the installer reaches the “Configure
the network” screen.
9. At the "Finish the installation/Installation complete" screen, from a back terminal blacklist the aacraid
driver before rebooting using the following steps:
9.1. Press Alt + F2.
9.2. Type the following commands:
chroot /target
echo “blacklist aacraid” > /etc/modprobe.d/install-aacraid.conf
depmod ùname –r`
update-initramfs –u
exit
9.3. Press Alt + F1 to return to the installation screen.

10. Press Continue to reboot the system.
11. Install the smartpqi DKMS package (smartpqi-dkms_#.#.#-###_all.deb) by using the following
commands (where #.#.#-### is the build number):
Note: The smartpqi DKMS package rebuilds the smartpqi driver automatically whenever the kernel on the
system is updated. This ensures that you have a smartpqi driver to support the new kernel.
apt-get update
apt-get –f install build-essential dkms
dpkg -i smartpqi-dkms_#.#.#-###_all.deb
6.8 Installing with Debian Linux

To install the controller SmartPQI driver while installing Debian Linux:
1. Copy the Debian driver binary image (smartpqi.ko) to the USB key; see 6.2 Creating a Driver Disk.
2. Boot the Debian installation from the DVD or media source.
3. Type "e" to edit the boot entry when the Debian installation menu is displayed.
4. Append "modprobe.blacklist=aacraid" after the “--“ on the line starting with “Linux”.
5. Type CTRL+X to boot.
6. Proceed with standard installation process until the installer reaches the “Configure the network” screen.
7. Press CTRL+ALT+F2.
8. Insert the Debian driver USB key.
9. Assuming the USB drive is assigned to /dev/sda1, type the following commands to begin loading the driver:

Note: Type fdisk -l to determine the USB device assignment.
mkdir /SMARTPQI
mount -t vfat /dev/sda1 /mnt
cp -R /mnt/* /SMARTPQI
umount /mnt
10. Remove the Debian driver USB key.

11. Copy the driver to /lib/modules and load driver module:
Note: The following steps assume you are installing Debian 8.8 64-bit, using kernel 3.16.0-4.
mkdir -p /lib/modules/3.16.0-4-amd64/kernel/drivers/scsi/smartpqi
cp -f /SMARTPQI/smartpqi.ko
/lib/modules/3.16.0-4-amd64/kernel/drivers/scsi/smartpqi/smartpqi.ko
depmod -a ùname -r`
modprobe smartpqi
12. To return to the graphical install, press CTRL+ALT+F5; to return to a non-graphical install, press ALT+F1.
Note: Do not press Continue at the end of the installation until you
complete Step #unique_46/unique_46_Connect_42_debian_reboot_prompt and Step #unique_46/
unique_46_Connect_42_complete_driver_installation.
13. When prompted to reboot the system, press CTRL+ALT+F2 to switch to the console.
14. Type the following commands to complete the driver installation:
mkdir -p /target/lib/modules/3.16.0-4-amd64/kernel/drivers/scsi/smartpqi
cp -f /SMARTPQI/smartpqi.ko
/target/lib/modules/3.16.0-4-amd64/kernel/drivers/scsi/smartpqi/smartpqi.ko
chroot /target
depmod -a ùname -r`
echo “blacklist aacraid” > /etc/modprobe.d/aacraid-blacklist.conf
update-initramfs -u -v
exit
15. To return to a graphical install, press CTRL+ALT+F5; to return to a non-graphical install, press ALT+F1.
16. Reboot the system.
17. Install the smartpqi DKMS package (smartpqi-dkms_#.#.#-###_all.deb) by using the following
commands (where #.#.#-### is the build number):
Note: The smartpqi DKMS package rebuilds and activates the smartpqi driver automatically any time the
kernel on the system is updated. This insures you have a smartpqi driver to support the new kernel.
apt-get install build-essential dkms

6.9 Installing with FreeBSD

To install the controller SmartPQI driver while installing FreeBSD:
1. Copy the driver module (smartpqi.ko) to a USB drive.
Disk partition the USB key, using gpart on a unix system.
For example:
# gpart create -s GPT da1

# gpart add -t freebsd-ufs da1
# newfs /dev/da1p1
# mount /dev/da1p1 /mnt
# cp smartpqi.ko /mnt
2. Insert the USB driver disk.

3. Insert the FreeBSD Installation disk into the CD/DVD drive and boot from it.
4. From the FreeBSD boot menu, press Escape to launch the boot loader prompt.

5. Perform the following steps at the boot loader prompt:

5.1. Check all the present modules by executing following command.
# lsmod
Expected Output: It will show all the present modules.

5.2. Unload the kernel module by executing the following command:
# unload
5.3. Check whether the kernel is unloaded or not by executing the following command:
# lsmod
Expected Output: It will show all the present modules.

5.4. Check whether the USB drive is detected or not by executing the following command:
# lsdev
Expected Output:
part 0: ………….. (removable)
5.5. Load the kernel by executing the following command:
# load /boot/kernel/kernel
5.6. Load the driver module by executing the following command:
# load part< USB key location >:smartpqi.ko
For example: # load part2:smartpqi.ko

5.7. Continue the Installation procedure by typing the following command and pressing Enter.
# boot
5.8. After completing the kernel installation and before rebooting the system, add the driver to the new
system. Choose "YES" when it prompts the following message for the manual configuration.
"The installation is now finished. Before exiting the installer, would you like to open a shell in the new
system to make any final manual modifications?
5.9. Use the following commands to complete the manual configuration:
5.9.1. Mount the USB key by using the following command:
# mount /dev/da1p1 /media
5.9.2. Copy the driver to the boot directory by using the following command:
# cp /media/smartpqi.ko /boot/modules/smartpqi.ko
5.9.3. Ensure that the boot loader loads by using the following command:
# vi /boot/loader.conf
5.9.4. Add the following line:
smartpqi_load="YES"
# reboot

6. If the system halts at # mountroot>, check for the boot partition using the following command:
# mountroot> ?
Note: The boot partition is primarily present in P2, so use the following command:
# mountroot> ufs:/dev/<da0p2>
6.10 Installing with Solaris

To install the controller SmartPQI driver while installing Solaris, follow the steps in the sections below.
6.10.1 Installing with Solaris Live Media

To install the SmartPQI controller driver with Solaris Live Media:
1. Copy the smartpqi.pkg or iso file and adddriver.sh file to a USB flash drive and insert that drive into
the installation system (see 6.2 Creating a Driver Disk).
2. Boot to the Solaris 11 live media DVD in the installation system. Select the Solaris version and press Enter.
3. Select the keyboard (default is 27) and language (default is 3).
4. Enter your login credentials.
The GUI will appear.
5. Open the terminal and switch to the root user by using the following command:
# su
Use "solaris" as the root password.

6. Adaptec controllers are shipped with the inbox aac driver, so it is necessary to remove the driver. Use the
following command to remove the inbox aac driver:
# rem_drv aac
7. Open the "Device driver utility" from the desktop and enter the root password.
8. The DD utility scans and automatically highlights the controller or devices that are not claimed by the driver.
9. Click Browse to load the driver image from the USB flash drive.
10. Select smartpqi.pkg or iso file and click "OK".
11. Click Install.
The Installation Successful message gets displayed.
12. The DD utility rescans the devices.
13. The available disks are viewable in the terminal by typing the format command. Press CtrlL+C to return to the
command prompt.
14. Return to the desktop by typing exit at the ~# prompt.
15. Double click the Install Oracle Solaris icon for OS installation and follow the steps to complete the OS
installation.

Notes: After the OS is installed, perform following procedure:

1. Open the terminal and copy the adddriver.sh file to /tmp directory.
# cp /media/USB_DRIVE/adddriver.sh /tmp/
# cd /tmp
2. Execute the adddriver.sh script file with the parameter live as follows:
# chmod +x adddriver.sh
# ./adddriver.sh live
3. Reboot the system using the following command:
# reboot
6.10.2 Installing with Solaris Text Installer

To install the SmartPQI driver with Solaris Text Installer:
1. Copy the smartpqi.pkg or iso file and adddriver.sh files to a USB flash drive and plug that drive into the
installation system (see 6.2 Creating a Driver Disk).
2. Boot to the Solaris 11.3 or 11.4 text installer DVD in the installation system, and select the keyboard and
language.
3. After the DVD boots, select option 3 (Shell) from the list.
4. Remove the inbox aac driver and exit the shell using the following commands:
#rem_drv aac
#exit
5. Select option 2 (Install Additional Drivers) from the list. The Device Driver Utility screen appears.
6. Press the F4 key (Media) to search for the driver image file on your flash drive.
7. Select USB drive and press Enter.
8. Find the location of the smartpqi.pkg or iso file on the flash drive, highlight it, nd press the F2 key to select
it.
9. Press the F2 key again to install the driver.
10. If the installation succeeds, the following screen will appear:
11. Press the F9 key to exit to the Options menu.

12. Select option 3 (Shell ) from the list.

13. Type the format command in the terminal window to list the available disks. Press Ctrl+C to return to the
command prompt.
14. Type exit at the ~# prompt to go back to the Options menu.
15. Enter option 1 to Install Oracle Solaris.
The Welcome to Oracle Solaris screen appears.
16. Press the F2 key to continue.
17. Select the disk discovery method and press the F2 key to continue.
18. Follow installation steps accordingly.
19. At the installation summary, press the F2 key to install the Oracle package; or, press the F3 key to go back to
make changes.
20. After the OS has been installed, press F9 to go back to the Options menu.
21. Select Option 3 (Shell).
22. Open the terminal and copy the adddriver.sh file to /tmp directory using the following commands:
# cp /media/USB_DRIVE/adddriver.sh /tmp/
# cd /tmp
23. In the terminal, execute the adddriver.sh script file with the parameter text as follows:
# chmod +x adddriver.sh
# ./adddriver.sh text
#reboot
6.11 Installing with Citrix XenServer

Note: For XenServer 7.1 and later, a USB key is supported for the driver update ISO. On a Linux system, use the
dd command to write the SmartPQI driver ISO image to the USB key (see 6.2 Creating a Driver Disk). You need the
XenServer installation DVD (or equivalent virtual media/iso image) to complete this task. You must have administrator
privilege to install the driver image.
To install the controller SmartPQI driver while installing Citrix XenServer:
1. On the machine where you want to install the OS and SmartPQI driver, insert the XenServer installation DVD,
then restart your computer.
2. When prompted to add a driver, insert the driver USB key, press F9, then select local media.
Note: Leave the driver USB key inserted throughout the installation.
3. Verify the SmartPQI driver and “use”.
4. Continue the XenServer installation, following the on-screen instructions.
5. Remove the driver USB key, then reboot your computer.
6.12 Installing with VMware

Note:
You will need a writable CD or USB flash drive to complete this task. You must have administrator privileges to create
the driver disk and install the driver image.
To install the controller SmartPQI driver with VMware ESXi 6.0 or VMware ESXi 6.5, you must create a custom boot
image using the ESXi-Customizer tool. This tool automates the process of customizing the ESXi install-ISO and runs
as a script under Microsoft PowerShell.
You can download the ESXi-Customizer tool, ESXi-Customizer-PS-v2.5.ps1, from https://www.v-front.de/p/
esxi-customizer-ps.html and other locations on the Web.

Note:
Be sure to install the prerequisite software first, including Powershell and VMware POWERCLI, before you install
ESXi-Customizer.
To install the SmartPQI controller driver while installing VMware:
1. Download and install Microsoft PowerShell and VMware POWERCLI, as needed. You can download
PowerShell from the Microsoft Download Center at www.microsoft.com/download, and POWERCLI from
my.vmware.com.
Note:
PowerShell is pre-installed on many Windows systems, including Windows Server 2012 and Windows Server
2016.
2. Download the ESXi-Customizer tool from https://www.v-front.de/p/esxi-customizer-ps.html or other Web
location. Then, unpack the archive to a local directory on your Windows system; C:\ESXi-Customizer,
for instance.
3. Copy the VMware driver vib for your OS version to a temp directory, such as C:\temp\pkg. The driver vib
files (listed below, where xxxxxxx is the driver version/build number) should be in the driver download directory
on your Windows system (see 6.2 Creating a Driver Disk).
Option Description
ESXi 6.7 smartpqi-67.xxxx.0.xxx-1OEM.670.0.0xxxxxxx.x86_64
ESXi 6.5 smartpqi-65.xxxx.0.xxx-1OEM.650.0.0.xxxxxxx.x86_64
ESXi 6.0 smartpqi-60.xxxx.0.xxx-1OEM.600.0.0.xxxxxxx.x86_64
4. Run ESXi-Customizer from the installation directory:

C:\ESXi-Customizer>ESXi-Customizer.cmd
5. In PowerShell, enter the following command:

.\ESXi-Customizer-PS-v2.5.ps1 –Vxx -pkgDir C:\temp\pkg
where Vxx is the VMware OS version: V60 for VMmare 6.0, V65 for VMware 6.5.
PowerShell begins creating the custom ESXi install-ISO with embedded SmartPQI driver. It displays "All done"
when the ISO is ready.
6. Burn the custom ISO image to a writable CD or USB drive.
Note:
Use whatever tool you prefer to burn the CD or USB drive.
Remove the CD or USB drive after you finish burning the image.
7. On the VMware ESXi machine, insert the custom boot CD/USB, then restart your computer.
8. Follow the on-screen instructions to begin the VMware installation.
9. Complete the VMware installation, following the on-screen instructions.
10. Remove the custom boot CD or USB drive, then reboot your computer.

Installing the Driver on an Existing Operating Sys...
7. Installing the Driver on an Existing Operating System

This chapter explains how to install the SmartPQI controller driver on an existing operating system. It assumes that
the SmartHBA 2200/SmartRAID 3200 is installed in a computer or server and the OS is already installed.
Notes:
• To install the driver while you're installing an operating system, see Installing the Driver and an Operating
System.
• For information about building the SmartPQI drivers from source, see 10. Installing the SmartPQI Drivers from
Source .
7.1 Download the Driver Package

Complete these steps to download the drivers for your operating system(s):
1. Open a browser window, then type start.adaptec.com in the address bar.
2. Enter your product or adapter model number, then select SmartRAID 3200 or SmartHBA 2200.
3. Select your operating system version, for instance, Microsoft Windows Server 2016 x64 or Red Hat Enterprise
Linux 7; then select the appropriate driver from the list.
4. Download the controller driver package (zip file archive).
5. When the download completes, extract the package contents to a temporary location on your machine. Each
driver is stored in a separate folder (\windows 2016, \rhel7, \rhel6, and so on).
Note: See the Release Notes for a complete list of available driver files.
7.2 Creating a Driver Disk

Create a driver disk by completing the steps below. You will need a USB flash drive to complete this task.
1. Change to the driver directory for your operating system version.
2. Write the driver binary file to a USB flash drive.
3. Remove and label the driver disk.
4. Continue the installation with the instructions for your operating system.
7.3 Installing on Windows

Note:
The following instructions apply to all supported Windows operating systems.
To install the controller SmartPQI driver on Windows:
1. Start or restart Windows.
2. In the Control Panel, launch the Device Manager, right-click your Smart Storage Controller, then select Update
Driver Software.
3. Insert the driver disk, then select Browse my computer for driver software.
4. Browse to the driver disk location, then click Next.
5. Select the driver from the list, then click Next.
6. Specify the device type as a Storage controller and click Next.
7. Select the device driver you want to install.
8. Navigate to the disk location where the driver files are copied.
9. When the installation is complete, remove the driver disk and restart your computer.
7.4 Installing on Red Hat

To install the controller SmartPQI driver on Red Hat Linux, follow the steps in the sections below.

Note: The inbox aacraid driver is available in many of the Linux distributions that include basic support for Adaptec
Smart Storage Controllers, like the SmartHBA 2200. The preferred driver is smartpqi. The following instructions
show how to blacklist the aacraid driver or replace it.
Installing on RHEL7 Update 3 and Above

Note: RHEL7 Update 3 includes a version of the SmartPQI driver and an updated aacraid driver that does not
support the Adaptec SmartHBA 2200.
To install the RHEL7 Update 3 driver on a Linux system:
1. Install the latest smartpqi driver rpm by using the following command (where #.#.#-### is the build number):
Installing on RHEL 7
To install the RHEL7 driver on a Linux system:
1. Disable the aacraid support for the Smart Storage Controller using one of the following options:
– Using Blacklist Option:
Type the following command:
echo “blacklist aacraid” > /etc/modprobe.d/blacklist-aacraid.conf
– Update aacraid driver to allow Series 8 / HBA 1000 Controllers and SmartHBA 2200 to coexist:
1. Install an aacraid rpm version 1.2.1-53005 or higher using one of the following links:
https://storage.microsemi.com/en-us/support/series8/index.php
https://storage.microsemi.com/en-us/support/hba1000/index.php
2. Execute the following command:
rpm -Uvh kmod-aacraid-RHEL7.2-1.2.1-53005.x86_64.rpm
2. Install the latest smartpqi package by using the following command (where #.#.#-### is the build number):
Note: This command automatically rebuilds the initramfs with the updates, and avoids rebuilding it manually.
Installing on RHEL6 Update 9 and Above

Note: RHEL6 Update 9 includes a version of the SmartPQI driver and an updated aacraid driver that does not
support the Adaptec SmartHBA 2200.
To install the RHEL6 Update 9 driver on a Linux system:
Installing on RHEL 6
To install the RHEL6 driver on a Linux system:

rpm -Uvh kmod-aacraid-RHEL6.8-1.2.1-53005.x86_64.rpm
7.5 Installing on SuSE Linux Enterprise Server

To install the controller SmartPQI driver on SLES, follow the steps below.
Installing on SLES 12 SP2 and Above

Note: SLES 12 SP2 includes a version of the SmartPQI driver and an updated aacraid driver that does not support
the Adaptec SmartHBA 2200.
Follow these steps to install the driver on SLES 12 SP2:

Installing on SLES 12
Follow these steps to install the driver on SLES 12:
1. Disable the aacraid support for the Smart Storage Controller by using one of the following options:
Type echo “blacklist aacraid” > /etc/modprobe.d/blacklist-aacraid.conf
rpm -Uvh aacraid-kmp-default-SLES12-SP1-1.2.1-53005.x86_64.rpm

3. Run “mkinitrd” command with the root user privilege to ensure that the blacklisting and driver updates are
included.

Installing on SLES 11
Important:
By default, SuSE Linux uses the 'by-id' method to identify drives/partitions on the boot device. As a result,
upgrading from the aacraid driver to smartpqi on SLES 11 will fail due to a change in the boot drive ID.
(This issue is not seen on SLES 12.) To avoid this issue, switch to the "by-uuid" method, then perform the
upgrade, as described below.
Follow these steps to switch to the "by-uuid" method:

1. Use the 'blkid' command (built-in utility) or 'ls -l /dev/disk/by-uuid' to find the UUIDs of the file systems:
sles11sp3boot:~ # blkid
/dev/sda1: UUID="4512cf7d-4e22-4dfa-8991-4084dae41409" TYPE="swap"
/dev/sda2: UUID="b144a0a2-b7fc-47fd-8459-ba40d0f663cd" TYPE="ext3"
2. Change to the /etc directory: cd /etc, then:

2.1. Make a backup of the fstab file before modifying it.
2.2. Edit fstab.
2.3. Change the "by-id" names of the file systems to their corresponding "uuid" identifier found in Step 1.
3. Change to /boot/efi/efi/SuSE/ or /boot/grub: cd /boot/efi/efi/SuSE/, then:
3.1. Make a backup of elilo.conf/menu.lst file before modifying it.
3.2. Edit the elilo.conf or menu.lst file.
3.3. Change the "by-id" names of the file systems to their corresponding "uuid" identifier found in Step 1.
4. Upgrade the driver by following the instructions below.
Follow these steps to install the driver on SLES 11:
Note: The example below represents the steps for SLES 11 SP3. Modify the filename of the installation archive to
match the appropriate update version in the appropriate fields.
Type echo “blacklist aacraid” > /etc/modprobe.d/blacklist-aacraid.conf
rpm -Uvh aacraid-kmp-default-SLES11-SP3-1.2.1-53005.x86_64.rpm

3. Run “mkinitrd” command with the root user privilege to ensure that the blacklisting and driver updates are
included.
7.6 Installing on Oracle Linux

To install the controller SmartPQI driver on Oracle Linux, follow the steps in the sections below.

Installing on Oracle Linux 7.3 and Above Running the Base Kernel
Note: The Oracle Linux 7.3 base kernel includes a smartpqi and an aacraid driver. The smartpqi driver is
recommended.
To install the SmartPQI driver on an Oracle Linux system:
1. Install the smartpqi driver rpm by using the following command (where #.#.#-### is the build number):
rpm –ivh kmod-smartpqi-#.#.#-###.ol7u3.x86_64.rpm
Installing on Oracle Linux 7.2 running the Base or UEK Kernel and Oracle Linux 7.3 running the UEK Kernel
To install the SmartPQI driver on a Oracle Linux system:
2. Execute one of the following commands:
For Base Kernel: rpm -Uvh kmod-aacraid-OL7.2-1.2.1-53005.x86_64.rpm
For UEK Kernel: rpm -Uvh kmod-aacraid-UEK-OL7.2-1.2.1-53005.x86_64.rpm
For Base Kernel: rpm –ivh kmod-smartpqi-#.#.#-###.ol7u2.x86_64.rpm
For UEK Kernel: rpm –ivh kmod-smartpqi-uek-#.#.#-###.ol7u2.x86_64.rpm
7.7 Installing on Ubuntu Linux

Notes:
1. For driver installation on Ubuntu Linux, you may need to create the root account and password.
2. The SmartPQI driver is available as inbox for Ubuntu 16.04.3 Hardware Enablement kernel, and above.
To install the controller SmartPQI driver on Ubuntu:
1. Login to the system using the root user credentials.
2. Update the Ubuntu package index by using the following command:
sudo apt-get update
3. Load the Ubuntu unpacking tools:
sudo apt-get –f install build-essential dkms
1. Install an aacraid DEB driver package version 1.2.1-53005 or higher using one of the following
links:

dpkg -i aacraid -1.2.1-53005-Ubuntu16.04-x86_64.deb
5. Install the latest SmartPQI DKMS DEB driver package by using the following command (where #.#.#-### is
the build number):
7.8 Installing on Debian Linux

To install the controller SmartPQI driver on Debian:
1. Login to the system as root, or sudo to root.
2. Disable aacraid support for the Smart Storage Controller to avoid conflict with the SmartPQI driver:

update-initramfs -u -v
3. Install the supporting package for the SmartPQI DKMS deb package:
apt-get update
apt-get install build-essential dkms
4. Install the SmartPQI DKMS DEB driver package using the following command (where #.#.#-### is the build
number):
5. Reboot system.
7.9 Installing on FreeBSD

To install the controller SmartPQI driver on FreeBSD:
1. Check whether the driver package is installed or not.
# pkg info | grep smartpqi
2. Install the SmartPQI package by using the following command:
# pkg add smartpqi10x-amd64.txz
Note: Upgrade the package if it already exists, using the following command.
# pkg upgrade smartpqi10x-amd64.txz
3. Restart the system.
# reboot
7.10 Installing on Solaris

To install the controller SmartPQI driver on Solaris, follow the steps in the sections below.
1. Remove the inbox aac driver, since the Adaptec Smart Storage Controller is shipped with the inbox aac driver.
#rem_drv aac

2. Extract the SmartPQI driver package from a .zip or .tar file.

3. Perform the following instructions to load the driver package.
3.1. If "smartpqi.pkg" is present, execute the following command:
# pkgadd –d smartpqi.pkg
or,
3.2. Ensure that the MSCsmartpqi folder is present in the current directory. The dot (.) in following the
command will read this folder as a driver package:
# pkgadd –d .
In the terminal, the following messages will appear:
The following packages are available:

1 MSCsmartpqi Microsemi Smart PQI RAID Controller driver
(i386) 1.0.0-100,REV=2016.06.06.22.10
Select package(s) you wish to process (or 'all' to process

all packages). (default: all) [?,??,q]:
Enter "1" or "all".

The following prompt will appear:
Do you want to continue with the installation of <MSCsmartpqi> [y,n,?]
Enter "y".
The following message appears after a successful installation:
Installation of <MSCsmartpqi> was successful.
# reboot
5. Use the following command to confirm whether the driver is loaded or not:
# modinfo –c | grep smartpqi
6. Use the following command to identify the driver package information:
# pkginfo –l MSCsmartpqi
Removing the Driver Package

1. Remove the loaded driver package using the following command:
# pkgrm MSCsmartpqi
In the terminal, the following messages will appear:
The following package is currently installed:

MSCsmartpqi Microsemi Smart PQI RAID Controller driver
(i386) 1.0.0-100,REV=2016.06.06.22.10
The following prompt will appear:
Do you want to remove this package? [y,n,?,q]

Enter "y". Once the selection is made, the following prompt will appear:
Do you want to continue with the removal of this package [y,n,?,q]
Enter "y". The following message will appear to signify the successful removal of the driver package:
Removal of <MSCsmartpqi> was successful
# reboot
7.11 Installing on Citrix XenServer

Note: To copy the driver RPM file to XenServer (in Step 1 below), you must have access to a remote copy utility,
such as WinSCP, putty, or Linux scp. You must have root privilege to install the driver.
To install the controller SmartPQI driver on Citrix XenServer (where #.#.#-### is the build #):
1. Using a remote copy utility, copy the driver RPM file to a local directory on XenServer. This example uses
Linux scp to copy the driver to /tmp/smartpqi:
scp citrix-smartpqi-#.#.#-###.xen7.1.rpm root@<xen-server-ip>:/tmp/smartpqi
2. Install the driver module rpm:

rpm -ivh /tmp/smartpqi/citrix-smartpqi-#.#.#-###.xen7.1.rpm
3. Reboot your computer.
7.12 Installing on VMware

To install the controller SmartPQI driver on VMware:
Notes: The instructions in this section must be executed on the ESXi server’s command line. To access the
command line:
1. Enable ESXi system console login. At ESXi system console, press F2 and log in as root.
2. Select “Troubleshooting Options” and press ENTER.
3. Select “Enable ESXi shell”.
4. Press ESC to exit from the menus back to the ESXi splash screen.
5. Press ALT + F1 to get to the ESXi shell login screen.
6. Log in as root.
Now copy over the VIB file to the ESXi server and install it.
1. Using a remote copy utility, copy the downloaded driver VIB package onto the ESXi server’s temp directory
using the following command:
# scp smartpqi-67.xxxx.0.xxx-1OEM.670.0.0xxxxxxx.x86_64.vib <esxi_server_address>:/tmp
2. Install the driver package (.vib file):
# esxcli software vib install -v file:/tmp/

smartpqi-67.xxxx.0.xxx-1OEM.670.0.0xxxxxxx.x86_64 –maintenance-mode –no-sig-check
3. Restart the system.
# reboot
4. After rebooting the system, check whether the driver package is installed. Compare the driver vib version
shown by the command below with the version that was installed, to make sure they are the same.
# esxcli software vib list | grep smartpqi

Solving Problems
8. Solving Problems
This section provides basic troubleshooting information and solutions for solving problems with your SmartHBA 2200/
SmartRAID 3200 Series Host Bus Adapter.
8.1 Troubleshooting Checklist

If you encounter difficulties installing or using your SmartHBA 2200/SmartRAID 3200 Series Host Bus Adapter, check
these items first:
• With your computer powered off, check the connections to each disk drive, power supply, enclosure, and so on.
• Try disconnecting and reconnecting disk drives from the adapter.
• Check that your adapter is installed in a compatible PCIe expansion slot. To verify the bus compatibility of your
adapter, see 4. About Your Host Bus Adapter.
• Ensure that your adapter is firmly seated and secured in the PCIe expansion slot.
• If your adapter is not detected during system boot, try installing it in a different compatible expansion slot. (See
Installing the Host Bus Adapter for instructions.)
• Did the driver install correctly? It may need to be reloaded after a reboot or kernel update; see 6. Installing the
Driver and an Operating System.
• Check the Release Notes for compatibility issues and known problems.
If you are still unable to resolve a problem, contact Microchip Support.
8.2 Resetting the Adapter

You may need to reset your SmartHBA 2200/SmartRAID 3200 if it becomes inoperable or if a firmware upgrade
is unsuccessful. SmartHBA 2200/SmartRAID 3200 adapters support a reset protocol called Side Band Recovery.
For information about Side Band Recovery, contact your support representative. To locate the Side Band Recovery
jumper on your adapter, see the board illustrations in 4. About Your Host Bus Adapter.

Using the Microchip SAS/SATA HII Configuration...
9. Using the Microchip SAS/SATA HII Configuration Utility

The Microchip SAS/SATA Configuration Utility (MSCU) is a BIOS-based utility that you can use to manage your
SmartHBA 2200/SmartRAID 3200 adapters and the devices attached to them. It comprises a set of tools for creating
and managing arrays, viewing and modifying adapter properties, viewing disk drive properties, flashing the HBA
firmware, and managing disk drives and spares.
9.1 Running the Microchip SAS/SATA Configuration Utility: UEFI/HII

On servers that support the Unified Extensible Firmware Interface, or UEFI (version 2.10 or higher), the BIOS-level
configuration options are presented with a UEFI/HII interface (Human Interaction Infrastructure). UEFI/HII provides
an architecture-independent mechanism for initializing add-in cards, like the SmartHBA 2200/SmartRAID 3200, and
rendering contents.
In the UEFI/HII interface, the server's standard BIOS provides access to the SmartHBA 2200/SmartRAID 3200
configuration options. How you access the BIOS varies, depending on the server manufacturer, but typically it's
started by simply pressing DEL. Once you enter setup, navigate to the menu where forms of third-party vendors
are displayed. The menu location depends on server manufacturer. Select your controller from the list. Menus are
categorized for Controller Settings, Array Configuration, Disk Utilities, and Administration.
Menu-based instructions for completing tasks appear on-screen. Menus can be navigated using the arrows, ENTER,
ESC, and other keys on your keyboard or using mouse, depending on browser capability.
This appendix provides instructions for navigating and completing tasks with the UEFI/HII interface.
9.2 Controller Information

The Controller Information menu provides details about the controller, including the Board Id, firmware revision
number, operating mode, UEFI driver version, encryption support, and World Wide Name. It also provides a
configuration summary. To view the SmartHBA 2200 information, start the Microchip SAS/SATA HII Configuration
Utility and select Controller Information from the main menu.
9.3 Creating an Array

Use the Array Configuration option to create new arrays. You can select drives, specify the RAID level and encryption
options (if supported by your controller), and configure array settings, including stripe size and logical drive size.
To create an array:
1. Start the Microchip SAS/SATA Configuration Utility in UEFI mode.
2. Select your controller, then press Enter.
3. From the main menu, select Array Configuration, then select Create Array.
4. Select each drive you want to include in the array: use the arrow keys to select a drive, press Enter, then
Proceed.
Note: Be sure not to mix drive types! Select SATA drives or SAS drives only.
5. Select Proceed to next Form, then press Enter.
6. (For controllers with maxCrypto Controller-Based Encryption only) Select encryption options for the array:
encrypted volume or plaintext volume (not encrypted).
Note: You will be prompted for your account credentials (Admin or User) if you are not logged into the
Encryption Manager; see 9.11.1 Encryption Manager Full Setup.
7. Select the RAID level.
8. Select Proceed to next Form.
9. Configure array settings: select the stripe size (from 16KiB to 1024KiB, depending on the number of disks and
RAID level), logical drive size (default=all available space), the unit of measure (GiB, TiB, MiB), SSD Over
Provisioning Optimization (enable or disable over provisioning on solid state drives in the array, if applicable),
and caching (utilizing the controller's cache memory).

10. Select Submit Changes.
9.4 Creating a maxCache Array

Note: This option is available only in the UEFI/HII interface.
Use this option to create a maxCache array. The maxCache array supports read and redundant write caching, using
a reserved logical device comprised of SSDs only. You can select drives, specify the RAID level, and configure array
settings, such as the logical drive size and cache Write policy.
Note: When using maxCache in conjunction with an encrypted primary logical drive, the maxCache volume will also
be encrypted automatically.
To create a maxCache array:
1. From the main menu, select Array Configuration, then select Create maxCache Array.
2. Select each drive you want to include in the array: use the arrow keys to select a drive, press Enter, then
select Proceed to next Form.
3. Select the RAID level, then select Proceed to next Form.
4. Configure array settings: select the Cache Line size (64KiB or 256KiB), logical drive size (default=all available
space), unit of measure (GiB, TiB, MiB), and cache Write Policy (write-back, write-through).
6. Select the data logical drive associated with the maxCache device (16 GB minimum).
9.5 Managing Arrays and Logical Drives

Use the Array Configuration option to manage arrays and logical drives. You can view logical drive properties, create
and delete logical drives and spares, and delete logical drives and arrays.
9.5.1 Viewing Logical Drive Properties

To view logical drive properties:
1. From the main menu, select Array Configuration, then select Manage Arrays
2. Use the arrow keys the select an array, press Enter, then select List Logical Drives.
3. Use the arrow keys to select a logical drive, press Enter, then select Logical Drive Details.
9.5.2 Creating Logical Drives

Use the Create Logical Drive option to create new logical drives. This option creates a logical drive from the free
space on the selected array.
To create a logical drive:
1. From the main menu, select Array Configuration, then select Create Logical Drive.
2. Select each drive you want to include in the array: use the space bar to the select a drive, then press Enter.
Note: Be sure not to mix drive types! Select SATA drives or SAS drives only.
3. Select Proceed to next Form, then press Enter.
4. Select the RAID level, then select Proceed to next Form.
5. Configure array settings: select the stripe size (from 16KiB to 1024KiB, depending on the number of disks and
RAID level), logical drive size (default=all available space), the unit of measure (GiB, TiB, MiB), SSD Over
Provisioning Optimization (enable or disable over provisioning on solid state drives in the array, if applicable),
and caching (utilizing the controller's cache memory).
9.5.3 Enabling IO Bypass

Use this option to enable IO Bypass acceleration for logical drives comprised of SSDs only.
To adjust the IO Bypass settings:

1. From the main menu, select Array Configuration, then select Manage Arrays.
2. Use the arrow keys to the select an array, press Enter, then select IO Bypass Settings.
3. From the pop-up menu, select Enabled or Disabled, then press Enter.
9.5.4 Editing Logical Drive Properties

Use this option to edit logical drive properties, including acceleration method and logical drive label.
To edit logical drive properties:
2. Use the arrow keys to select an array, press Enter, then select List Logical Drives.
3. Use the arrow keys to select a logical drive, press Enter, then select Edit Logical Drive.
4. Select Acceleration Method, then select one of these options from the pop-up menu:
• IO Bypass (for logical drives comprised of SSDs)
• Controller Cache
• None (to disable acceleration)
5. Select Logical Drive Label, then type the new label.
9.5.5 Deleting a Logical Drive

Note: Use this procedure to delete an individual logical drive. To delete all logical drives on an array, see
9.5.9 Deleting an Array.
To delete a logical drive:
2. Use the arrow keys the select an array, press Enter, then select List Logical Drives.
3. Use the arrow keys to select a logical drive, press Enter, then select Delete LD.
Note: Be sure to delete logical drives from the bottom of the list and move up. If you delete a logical drive
from the middle of the list, the remaining logical drives move to the Transformation state. During that time, you
cannot delete any other logical drives until they all move to the Optimal state.
9.5.6 Assigning Spares

A spare is a disk drive that automatically replaces a failed drive in a logical drive. A spare drive must meet the
following criteria:
• It must be an unassigned drive or a spare for another array.
• It must be the same type as existing drives in the array (for example, SATA or SAS).
• The drive capacity must be greater than or equal to the smallest drive in the array.
To assign a spare to an array:
2. Use the arrow keys the select an array, press Enter, then select Manage Spare Drives.
3. Select the spare activation type:
– Assign Dedicated Spare: activate spare when drive fails
– Assign Auto Replace Spare: activate spare when drive reports a predictive failure (SMART) status
– Change Spare type to Dedicated: change assigned spare type from AutoReplace to Dedicated
– Change Spare type to AutoReplace: change assigned spare type from Dedicated to AutoReplace
4. Use the arrow keys to select the drive to assign as a spare.
Note: Only drives that meet the above criteria are displayed.
9.5.7 Deleting a Spare Drive

To delete a spare drive:

2. Use the arrow keys the select an array, then press Enter.
3. Select Manage Spare Drives, then select Delete.
4. If the array has more than one assigned spare, use the arrow keys to select a spare from the list, then press
Enter.
9.5.8 Identifying the Drives in an Array

Use this option to identify and locate the physical drives in an array by turning on their Identification LED.
To identify the physical drives in an array:
2. Use the arrow keys to select an array, then press Enter.
3. Select Identify Device.
4. Enter a value into Identification Duration (seconds). This value determines how long the LED on the device
will remain on.
5. Select Identify by Drive Configuration type, then select one of these options from the pop-up menu:
• Data Drive(s) only
• Spare Drive(s) only
• All Physical Drives (default)
6. Select Start, then press Enter.
7. To turn off the Identification LED(s), press Esc to return to the previous menu, then select Stop.
9.5.9 Deleting an Array

Note: Use this procedure to delete all logical drives on an array, and the array itself. To delete an individual logical
drive, see 9.5.5 Deleting a Logical Drive.
To delete an array:
1. From the main menu, select Array Configuration, then select Manage Array LD.
2. Use the arrow keys the select an array, press Enter, then select Delete Array.
9.5.10 Add Drives

Table 9-1. Add Drives
Option Definition
Expand array Expands the array by adding data drives.
Add drive to existing parity group Adds an equal number of drives to each parity group in
an array.
Add entire parity group Add drives by adding entire parity groups to array.
Auto expand Based on the parity group, it will auto expand.
9.5.11 Remove Drives

Enter a short description of your concept here (optional).
Table 9-2. Remove Drives
Option Definition
Shrink array Shrinks the array by removing the current data drives
from array.
Remove drive from existing parity group Removes an equal number of drives to each parity group
from array.

Option Definition
Remove entire parity group Removes drives by removing entire parity groups from
array.
Auto shrink Based on the parity group, it will auto shrink.
9.5.12 Move Drives

Use this option to replace one or more drives in the array with drives of the same type.
9.6 Modifying SmartHBA 2200/SmartRAID 3200 Controller Settings

To modify the SmartHBA 2200/SmartRAID 3200 settings, start the Microchip SAS/SATA Configuration Utility, select
Configure Controller Settings from the main menu, then select Modify Controller Settings, Modify Cache
Settings, or Advanced Controller Settings. You can set the options in the table below.
Option Description
Modify Controller Settings
Transformation Priority Sets the priority for array expansion:
• Low: normal system operations take priority over array expansion
• Medium: normal system operations and array expansion get equal priority
• High: expansion takes precedence over all other system operations
Rebuild Priority Sets the priority for rebuilding a failed logical drive:
• Low: normal system operations take priority over rebuilds
• Medium: normal system operations and rebuilds get equal priority
• Medium High: rebuilds get higher priority than normal system operations
• High: rebuilds take precedence over all other system operations
Surface Scan Analysis Priority Determines the time, in seconds, that a controller must be inactive before a surface scan
analysis is started on the physical drives connected to it. The scanning process checks physical
drives for bad sectors and, in fault-tolerant logical drives, such as RAID 5, it also verifies the
consistency of parity data. Delay value ranges from 1-30 seconds. Set the value to "0" to disable
the feature. Set the value at "31" to maintain high priority.
Current Parallel Surface Scan Sets the surface scan count for the controller. Set the value to "1" to disable the feature.
Count
Disabling Surface Scan Analysis is not recommended as it will prevent the controller
CAUTION
from proactively finding and correcting disk surface errors, which may lead to data
loss.
Unconfigured Physical Drive Write Enables and disables physical drive write cache for unconfigured drives on the controller.
Cache
HBA Physical Drive Write Cache Enables and disables physical drive write cache for HBA drives on the controller.
State
Configured Physical Drive Write Enables and disables physical drive write cache for configured drives on the controller.
Cache State
Modify Spare Activation Mode

Option Description
Spare Activation Mode Sets the spare activation mode to activate on failure or predictive failure activation.
The failure spare activation mode, activates the spare assigned for the Logical Drive when a
member of the Logical drive fails.
In Predictive Spare activation mode, activation is done when a drive reports a predictive failure.
Configure Controller Port Mode

Connector Mode (CN0:CN3 Configures the controller connectors to different operating modes:
• HBA: exposes physical drives to the operating system
• RAID: exposes only RAID volumes to the operating system
• Mixed: exposes RAID volumes and physical drives to the operating system
Modify Cache Settings

No Battery Write Cache Allows write caching to be enabled when a battery/supercapacitor is not present or fully charged.
This setting affects all logical drives on the controller.
Enabling write caching on a cache module without a fully charged battery/

CAUTION
supercapacitor may cause data loss in the event of a power failure.
Cache Ratio (Read) Sets the ratio of controller cache memory used for read-ahead cache versus write cache. Cache
ratio values range from 0–100, in increments of 5.
Write Cache Bypass Threshold All writes larger than the specified value will bypass the write cache and be written directly to the
disk for non-parity RAID volumes. A smaller value allows the controller to reserve write caching
to I/Os smaller than the threshold.
Advanced Controller Settings (RAID mode or Mixed mode only):
Degraded Mode Performance For degraded RAID 5 logical drives, enabling this setting directs the controller to attempt to
Optimization improve performance of large read requests by buffering physical drive requests. Disabling this
setting forces the controller to read from the same drives multiple times.
Physical Drive Request Elevator Sets the behavior of the drive's write Elevator sort algorithm, a scheduling optimization that
Sort prioritizes I/O requests such that disk arm and head motion continues in the same direction.
Enabling the elevator sort improves seek times and disabling the elevator sort improves
throughput.
Alternate Inconsistent Repair Sets the surface analysis inconsistency repair policy for RAID 5 when the controller detects that
Policy the parity information does not match the data on the drives. Disabling the repair policy directs
the controller to update the parity information, leaving the data untouched. Enabling the repair
policy directs the controller to update the data on the drives based on the parity information.
Max Drive Request Queue Depth Sets the queue depth for the controller. Valid values are Automatic, 2, 4, 8, 16, and 32.
Monitor and Performance Analysis Sets the Monitor and Performance Analysis delay for the controller, in minutes. Set the value to
Delay zero to disable Monitor and Performance Analysis. Default is 60 minutes.

Option Description
HDD Flexible Latency Enables flexible latency optimization for HDDs. When FLS is enabled, the controller detects
Optimization high-latency I/O requests and applies a cutoff, or threshold, value, after which it suspends
elevator sorting and services the request right away. Valid values are:
• Disable (default).
• Low
• Middle(100 ms)
• High
• Very high(30 ms)
• Very high(10 ms)
Configure Port Discovery Protocol This menu provides options to configure the protocols used by the controller to discover the
ports. A discovery protocol is the signal group/PHY mode protocol used to discover what's
attached.
Options are Auto-detect/UBM/SGPIO/VPP
This operation requires reboot.
Provide options to:
• View Current port Discovery Protocol
• View Pending port Discovery Protocol
• Set port Discovery Protocol
• Reset port Discovery Protocol to default
Modify Expander Minimum Scan This menu provides option to configure minimum scan duration for expanders. Entered value
Duration should be in seconds.
9.7 Clearing the Controller Configuration

Clearing the controller configuration destroys the controller meta-data, including partition information.
When you clear the controller configuration, all data on the attached media (SSD/HDD) will no longer
CAUTION
be accessible and cannot be recovered. Be sure you no longer need the data on the controller before
proceeding!
To clear the controller configuration:

1. From the main menu, select Configure Controller Settings, then select Clear Configuration.
2. Select Delete All Array Configurations or Delete Configuration Metadata on All Physical Drives.
9.8 Backup Power Source

Use the Backup Power Source option to check the status of the cache system's backup power supply, if applicable.
From the main menu, select Configure Controller Settings, then select Backup Power Source.
9.9 Managing Power Settings

Use the Manage Power Settings option to configure the controller's power modes. There are three available power
modes. You can also enable Survival mode.
• Maximum Performance (default): All settings are selected based on maximum performance. Power savings
options that affect performance are disabled.

• Balanced: You can use this setting to save power with minimal effects on performance. For large queue
depths, this setting affects throughput by 10% or less. At lower queue depths or infrequent I/O, impacts on
performance may be greater. This command is typically useful in environments using only hard drives, and is
not recommended when using SSDs. Settings are based on the user configuration, such as the number or types
of drives, the RAID level, storage topology, and so forth. Significant changes to the configuration may require a
reboot for optimal setting selection. If a reboot is required to change settings, UEFI HII prompts for a reboot to
reflect requested settings.
• Survival Mode: Allows the controller to throttle back dynamic power settings to their minimums when the
temperature exceeds the threshold. Enabling Survival Mode allows the server to continue running in more
situations, but may affect performance.
To change the power settings for a controller:
3. From the main menu, select Controller Configuration.
4. Select Manage Power Settings, then select Power Mode.
5. Press Tab to select the power mode.
6. Select Survival Mode, then press Tab to select Enabled or Disabled.
9.10 Out of Band Messaging Settings

Use this option to configure the Out of Band Messaging Interface to PBSI, MCTP, or Disable.
Note: This option is supported in the UEFI/HII interface only.
To change the Out of Band Messaging settings for a controller:
3. From the main menu, select Configure Controller Settings.
4. Select Out of Band Messaging Settings.
5. Select OOB Interface and press Enter.
6. From the pop-up menu, select PBSI, MCTP, or Disable OOB interface.
7. To configure Out of Band Messaging for PBSI, set these parameters:
PBSI Parameters Description

SMBus Slave Address Sets the SMBus (System Management Bus) slave address of the controller to a
valid hexadecimal address value.
SMBus Clock Speed Sets the SMBus clock speed:
• Feature Disabled (Default)
• SMBus clock speed 100 kHz
• SMBus clock speed 400 kHz
SMBus Clock Stretching Sets the SMBus Clock Stretching mode:

• Enable: Enables SMBus clock stretching
• Disable: Disables SMBus clock stretching
8. To configure Out of Band Messaging for MCTP, set these parameters:
MCTP Parameters Description

SMBus Slave Address Sets the SMBus (System Management Bus) slave address of the controller
to a valid hexadecimal address value. (For valid range, refer to the

MCTP Parameters Description

Management Component Transport Protocol (MCTP) SMBus/I2C Transport
Binding Specification document.)
SMBus Device Type Sets the SMBus Device Type:
• Default
• Fixed
• ARP (Address Resolution Protocol)
SMBus Physical Channel Sets the SMBus Channel mode:

• Enable: Enables SMBus channel
• Disable: Disables SMBus channel
Use Static EIDs during Sets the Static End Point Identifier (EID) mode:
Initialization • Enable: Enables Static EID
• Disable: Disables Static EID
VDM Discovery Notify Sets the Vendor Defined Message (VDM) discovery notification mode:
• Enable: Enables VDM discovery notification
• Disable: Disables VDM discovery notification
9.11 Using the Encryption Manager

Notes:
1. This option is available only in the UEFI/HII interface; UEFI version 2.4A or higher, recommended.
2. This option is available only for controllers that support maxCrypto Controller-Based Encryption. See
4.1 About Your SmartRAID 3200 Series Host Bus Adapter for more information.
The Encryption Manager allows you to configure the controller-based encryption options on your Smart Storage
controller. The Encryption Manager supports two roles for managing encryption services:
• A Crypto Officer (Admin) role that can perform all encryption operations
• A User role with reduced privileges
Once you configure the Encryption Manager, you can encrypt arrays and logical drives, and create storage spaces
with mixed encrypted and plaintext volumes. For more information about creating and managing encrypted volumes,
see 9.3 Creating an Array.
9.11.1 Encryption Manager Full Setup

Use the Full Setup option to configure the Encryption Manager for initial use. This option allows you to set the master
encryption key, configure the Crypto Officer account, and enable other basic encryption settings. It also allows you to
accept the Encryption Manager Terms of Use.
To configure the Encryption Manager:
3. From the main menu, select Configure Controller Settings, then select Encryption Manager.
4. Select Manage Encryption Settings, then select Full setup.
5. Using the arrow keys and Enter key, configure basic encryption settings:
a) In the Encryption Mode field, select one of these options:
• Enable and Allow future... to enable encryption and allow plaintext logical devices to be created
in addition to encrypted logical devices.
• Enable and Disallow future... to enable encryption and allow only encrypted logical devices to be
created.

• Disable to disable the Encryption Manager. If encryption is disabled, all encrypted logical drives
are set to offline and the data becomes inaccessible; newly created logical drives will not be
encrypted. (They will be created as plaintext logical drives.)
b) In the Enter new password field, enter the Crypto Officer password: press Enter, type the password in
the pop-up window, then press Enter to submit.
The password is a 8-16 character string, comprising all printable ASCII characters. It must include
at least one uppercase character, one lowercase character, one numeric, and one special character
(#,!,@,...).
c) In the Master Key field, enter the master encryption key: press Enter, type the key in the pop-up
window, then press Enter to submit.
The Master Key is a 10-32 character string, comprising all printable ASCII characters.
Be sure to record the master key and store in a safe place. Once set, the Master Key
CAUTION
cannot be displayed or recovered, only reset. Failure to provide the Master Key may result in
encrypted data being irretrievable.
6. Select Proceed to Next Form.

The Terms of Use form opens.
7. Select Accept to accept the Terms and Conditions.
9.11.2 Modifying the Encryption Manager Configuration

Use this option to modify the Encryption Manager configuration, including the master encryption key and other basic
encryption settings, and the Crypto Officer and User account settings.
Note: This option is available only after you complete the Encryption Manager Full setup; see 9.11.1 Encryption
Manager Full Setup.
To modify the Encryption Manager configuration:
4. Select Manage Encryption Settings, then select Crypto Officer Settings.
5. Using the arrow keys and Enter key, modify basic encryption settings, as needed (encryption enable/disable,
master encryption key, allow/disallow future plaintext volumes).
6. In the Firmware Update field, select Unlock to allow controller firmware upgrades. Select Lock to block
(prevent) firmware upgrades.
7. Using the arrow keys and Enter key, configure the Crypto Officer and User account settings:
a) Change the Crypto Officer password, as needed: press Enter, type the password in the pop-up
window, then press Enter to submit.
b) Enter the Password Recovery Question for a forgotten password: press Enter, type the recovery
question in the pop-up window, then press Enter to submit.
The recovery question is 16-255 characters, comprising all printable ASCII characters.
c) In the Password Recovery Answer field, enter the answer to the recovery question.
The recovery answer is 16-64 characters and is case sensitive, comprising all printable ASCII
characters.
Note: Password recovery is available only for the Crypto Officer account.
d) In the User Password field, enter the User account password: press Enter, type the password in the
pop-up window, then press Enter to submit.
The Terms of Use form opens.
9. Select Accept to accept the Terms and Conditions.

9.11.3 Modifying User Account Settings

Use this option to modify User account settings, including the account password and firmware upgrade options.
Note: This option is available only after you complete the Encryption Manager Full setup; see .
To modify the User Account Settings:
2. Select Manage Encryption Settings, then select User Settings.
3. Modify the User account password, as needed: press Enter; when the pop-up window opens, type the
password, then press Enter to submit.
The password is a 8-16 character string, comprising all printable ASCII characters. It must include at least one
uppercase character, one lowercase character, one numeric, and one special character (#,!,@,...).
4. In the Firmware Update field, select Unlock to allow the controller firmware to be upgraded. Select Lock to
prevent the controller firmware from being upgraded.
9.11.4 Resetting a Forgotten Password

Use this option to reset the Crypto Officer password by answering the recovery question.
Note: Password recovery is available only for the Crypto Officer account.
To reset a forgotten password:
2. Select Manage Encryption Settings, then select Forgot Crypto Officer Password.
3. Enter the answer to the password recovery question;
4. Enter the Crypto Officer's new password: press Enter; when the pop-up window opens, type the password,
then press Enter to submit..
9.11.5 Clearing the Encryption Manager Configuration

Clearing the Encryption Manager configuration resets all keys, passwords, and users, including the Crypto Officer
account and User account, and places the Encryption Manager in the factory-new state. If encrypted volumes are still
configured, this option is only available in the Microchip SAS/SATA Configuration Utility or by running the GUI/CLI
tools in offline mode.
Note: Clearing the configuration does not affect the encrypted logical drives in your storage space. However,
to continue accessing or managing encrypted volumes, you must reconfigure the basic encryption settings in the
Encryption Manager; see 9.11.1 Encryption Manager Full Setup.
To clear the Encryption Manager configuration:
4. Select Clear Configuration.
5. If your storage space includes encrypted volumes, enter the Encryption Master Key.
9.11.6 Re-Keying a Logical Drive

Use this option to re-key a logical drive for added security. The logical drive key is used with the master key to
encrypt the device.
To re-key a logical drive:

2. Select an array, then select List Logical Drives.
3. Select an encrypted logical drive, then select Volume key rekey.
4. Select your account type: Crypto Officer or User.
9.11.7 Converting Plaintext Data to Encrypted Data

Use this option to convert plaintext data to encrypted data. You can choose to preserve or discard the existing data
during conversion.
To convert plaintext data:
3. Select a plaintext logical drive, then select Convert Plaintext Data to Encrypted Data.
5. In the Convert Plaintext Data to Encrypted Data field, select discard existing data or preserve existing data
during conversion.
9.11.8 Erasing an Encrypted Logical Drive

Use this option to securely erase existing data on an encrypted logical drive. Secure erase completely destroys the
data on the logical drive; the data is completely and irretrievably eradicated.
To erase an encrypted logical drive:
3. Select an encrypted logical drive, then select Secure erase.
9.11.9 Importing a Foreign Master Key

When an encrypted logical drive is moved to another controller, the master key used to encrypt the logical drive is
needed to decrypt it. Use the Import Foreign Local Key option to import the master key so that the logical drive data
can be accessed and managed on the new controller.
Note: This option is available only if an encrypted logical device with a missing key is detected in the configuration.
To import a foreign master key:
2. Select Import Foreign Local Key.
3. Enter the master key used to encrypt the logical drive.
4. Enter the Crypto Officer password: press Enter; when the pop-up window opens, type the password, then
Enter.
9.12 Configuring the Controller Port Mode

You can set entire controller port mode or set independent port mode to:
• HBA: exposes physical drives to the operating system
• RAID: exposes only RAID volumes to the operating system and reserves all physical drives for array creation
• Mixed: exposes RAID volumes and unconfigured physical drives to the operating system
• Independent: Allows to set above options independently for each connector of the controller.

Notes:
1. Changing the port mode from Mixed or HBA to RAID mode removes access to physical drives from the
operating system.
2. HBA mode is not available if a port is already configured with logical drives.
To configure the port mode for a controller:
3. From the main menu, select Configure Controller Settings, then select Configure Controller Port Mode.
4. Select the controller port mode (HBA, RAID, Mixed).
9.13 Device Information

The Device Information menu provides details about the device, such as the Model, Serial Number, and Device Type.
To view the device information, start the Microchip Configuration Utility, select your controller, then press Enter.
From the main menu, select Disk Utilities, select the disk drive, then press Enter.
9.14 Identifying a Disk Drive

You can use the disk utilities to physically locate and identify a disk drive by turning on its Identification LED.
To identify a disk drive:
1. From the main menu, select Disk Utilities.
2. Select the disk drive you want to locate, then press ENTER.
3. Select Identify Device, then enter a value into Identification Duration (seconds). This value determines how
long the LED on the device will remain on.
4. Select Start, then press Enter.
5. To turn off the Identification LED, press ESC to return to the previous menu, select Stop and press Enter.
9.15 Erasing a Disk Drive

You can use the disk utilities to erase existing data on any unassigned disk drive. The erase operation destroys the
data by writing random patterns across the drive; it does not just write zeros.
To erase a disk drive:
2. Select the disk drive you want to erase, then press Enter.
3. Select Erase Disk, then select Continue.
9.16 Updating Drive Firmware

You can use the disk utilities to flash a hard drive with new firmware.
To update drive firmware:
1. Copy the firmware binary file to a USB flash drive, then connect the USB drive to the machine. Alternatively,
copy the firmware binary to a known location on your machine.
2. From the main menu, select Disk Utilities, then select Update Drive Firmware.
3. Select a disk drive, then enter the firmware update mode:
Option Description
Mode 5 Download and Activate

Option Description
Mode 7 Download in Multiple Transfers
Mode E Download in Multiple Transfers but Do Not Activate
Mode E+F (HBA Mode only) Download in Multiple Transfers and Activate
4. Enter the Transfer Size, in 512 byte-increments. The default transfer size is 32768 (32K) bytes. The maximum
transfer size is 262144 (256K) bytes.
Note: Transfer Size is not applicable for Mode 5.
5. Select Proceed.
6. Select the storage device where the firmware binary file is located (the USB drive, for instance), navigate the
folder hierarchy, then select the firmware binary file.
The firmware is sent to the hard drive.
7. When the update is complete, reboot the server.
9.17 Clearing Configuration Meta-data

You can use the disk utilities to clear the controller configuration meta-data from any drive that is not part of an array.
Note: This option is enabled only if the selected drive contains controller configuration meta-data. A drive may
contain configuration meta-data even if it is not part of an array.
To clear the configuration meta-data from a drive:
2. Select a disk drive with configuration meta-data, then press Enter.
3. Select Clear Configuration Metadata, then select Continue.
9.18 Setting the Bootable Device(s) for Legacy Boot Mode

Note: This option is applicable only for Legacy Boot Mode.
This option sets the primary and secondary physical boot device(s) for Legacy Boot Mode. The secondary boot
device acts as a failover to the primary boot device.
To set the physical boot device(s) for a controller:
1. From the menu, select Set Bootable Device(s) for Legacy Boot Mode, then select Select Bootable
Physical Drive.
2. To set the default bootable device, select a physical drive from the list, then select Set as Primary Bootable
Device.
3. To set the secondary bootable device, select a physical drive from the list, then select Set as Secondary
Bootable Device.
Note: To clear previously set boot devices, select Clear Bootable Device(s).
9.19 Updating the SmartHBA 2200 Firmware

To update the SmartHBA 2200 firmware:
1. Copy the firmware binary file (.bin) to a USB flash drive, then connect the USB drive to the machine.
Alternatively, copy the firmware binary to a known location on your machine.
2. From the main menu, select Administration, then select Flash Controller Firmware.
3. Select Continue with flashing Firmware.
4. Select the storage device where the firmware binary file is located (the USB drive, for instance), navigate the
folder hierarchy, then select the firmware binary file.
The firmware is sent to the controller.

5. When the update is complete, reboot the server.
9.20 Creating a Support Archive

Use this option to save configuration and status information to help Customer Support diagnose a problem with your
system. Saved information includes device logs, drive logs, event logs, error logs, controller logs, and statistics.
To create a support archive:
1. From the main menu, select Administration, then select Save Support Archive.
2. Select the device where the support archive information will be gathered and stored, then press Enter.
The system gathers the logs and statistics for the device and displays the path where the information is saved.
3. Press any key to complete the operation and exit.
9.21 Resetting the Controller to Factory Defaults
Use extreme caution when resetting the controller to factory defaults. This operation clears configured
CAUTION
arrays, controller configuration metadata on the drives, license keys, and encryption configuration, causing
all existing data and configuration settings to be irretrievably lost.
Use this option to reset the SmartHBA 2200 to factory default settings.
To reset the controller:
1. From the main menu, select Administration.
2. Select Reset controller settings to factory defaults.
9.22 Extracting Controller Debug Token

Note: For advanced users. Contact Microchip support for more information.
This option allows user to save the controller debug token to a selected storage device.
1. Start the Microchip SAS/SATA Configuration Utility in UEFI mode (See 9.1 Running the Microchip SAS/SATA
Configuration Utility: UEFI/HII.
2. Select your controller, then press ENTER.
3. Start the Microchip HII Configuration Utility, navigate to the Device Settings menu, then select your controller.
4. From the main menu, select Administration.
5. Select Extract Debug Token.
6. Select Storage Media.

Installing the SmartPQI Drivers from Source
10. Installing the SmartPQI Drivers from Source

This section explains how to build and install the SmartPQI drivers from source code for the supported Linux OSs,
including how to install the packages using the installation DVD as the repository.
10.1 Installation Instructions for Supported Linux OSes

This section explains how to install the driver from source for the following Linux OSes:
• RHEL OS images
• SuSE OS images
Use the following command to determine the type of OS installed on a Linux system:
# lsb_release -a
Note: The following instructions assume you are installing the packages from the RHEL or SuSE repositories; if not,
refer to 10.2 Using the Installation DVD as the Repository.
RHEL OS Images
The instructions below apply to the following RHEL OS images:
• Red Hat® Enterprise Linux 7.4, 7.3,7.2, 7.1, 7.0 (64-bit only)
• Red Hat® Enterprise Linux 6.9, 6.8, 6.7, 6.6 (64-bit only)
To install the SmartPQI driver from source for RHEL-based OS images:
1. Build the driver from the source using the following command:$ sudo su
Note: You must have administrator privileges to perform the installation steps.
2. Install the following driver dependency packages and reboot the system if necessary:#yum install
kernel kernel-devel kernel-headers gcc
3. Extract the driver source code from the source tar.bz2 file by using the following command:# tar –jxvf
smartpqi-1.1.2-125.tar.bz2
4. Compile the smartpqi.ko file by using the following command:
# cd smartpqi-1.1.2
# make -f Makefile.alt
Note: After the compilation you will get a smartpqi.ko driver file, which is the driver module.
5. Use the following command to backup the existing inbox driver:
# mv /lib/modules/ùname -r`/kernel/drivers/scsi/smartpqi/smartpqi.ko \
/lib/modules/ùname -r`/kernel/drivers/scsi/smartpqi/smartpqi.ko.org
6. Copy the smartpqi.ko driver file to the destination by using the following command:# cp ./
smartpqi.ko /lib/modules/ùname -r`/kernel/drivers/scsi/smartpqi
7. Use the following command to rebuild initramfs process with the newly installed smartpqi driver:# dracut -v
-f --add-drivers smartpqi
Note: RHEL provides dracut command to place the newly installed smartpqi.ko driver modules into the
initramfs file to include them in the Linux kernel.
8. Rebuild initramfs with the newly installed smartpqi driver by using the following command:# dracut -v -f
--add-drivers smartpqi
9. Reboot the system to load the new initramfs, which will contain the newly installed smartpqi.ko driver.
SuSE OS Images
The instructions below apply to the following SuSE OS images:
• SuSE Linux Enterprise Server 12, SuSE Linux Enterprise Server 12 SP1, SP2, SP3 (64-bit only)
• SuSE Linux Enterprise Server 11 SP3, SP4 (64-bit only)
To install the SmartPQI driver from source for SuSE OS images:

1. Build the driver from the source using the following command:$ sudo su
Note: You must have administrator privileges to perform the installation steps.
2. Install the following driver dependency packages and reboot the system if necessary:# zypper install
kernel-devel gcc make
3. Extract the driver source code from the source tgz file by using the following command:# tar –jxvf
smartpqi-1.1.2-125.tar.bz2
4. Compile the smartpqi.ko file by using the following command:
# cd smartpqi-1.1.2
# make -f Makefile.alt
Note: After the compilation you will get a smartpqi.ko driver file, which is the driver module.
5. Backup the already existing inbox driver.
# mv /lib/modules/ùname -r`/kernel/drivers/scsi/smartpqi/smartpqi.ko \
/lib/modules/ùname -r`/kernel/drivers/scsi/smartpqi/smartpqi.ko.org
6. Copy the kernel driver file to the destination by using the following command:# cp ./smartpqi.ko /lib/
modules/ùname -r`/kernel/drivers/scsi/smartpqi
7. Use the following command to rebuild initramfs process with the newly installed smartpqi driver:# mkinitrd
-v –m smartpqi
Note: SLES provides mkinitrd command to place the newly installed smartpqi.ko driver modules into the
initramfs file to include them in the Linux kernel.
8. Reboot the system to load the new initramfs, which will contain the newly installed smartpqi.ko driver.
10.2 Using the Installation DVD as the Repository

Follow the instructions in this section to install the packages required to compile the driver modules using the OS
installation DVD as the repository. In these procedures, the DVD is used as the package repository.
Installing Packages on a RHEL-based OS

The following steps install the packages required to compile the driver modules from source on a RHEL-based OS.
1. Execute the following command to become a super user to edit and make changes to various system files:
$ sudo -i
Note: Super user rights are required to edit and make changes in various system files.
2. Get the name of the installation DVD entry in /dev directory. The DVD is visible as /dev/srX. Use the
following command to list all the scsi devices on the system.
# lsscsi
3. Once the DVD name is confirmed, create a location to mount the DVD, for example:
# mkdir /media/iso
4. Mount the DVD to the /media/iso directory by using the following command:
/dev/srX /media/iso udf,iso9660 noauto,user,ro 0 0
5. Use the following command to mount the DVD, once the entry is placed in /etc/fstab:
# mount /dev/srX
6. Create a dvd.repo to use the packages from the mounted DVD location:
[dvd]
name=Red Hat Enterprise Linux Installation
DVD baseurl=file:///media/iso enabled=1
7. Import the GPG keys for YUM to authenticate the RPM packages in the DVD:
# rpm --import /media/iso/RPM-GPG*

8. Run the following commands to enable the DVD repository:
# yum repolist
# yum install
Installing Packages on a SuSE-based OS

The following steps install the packages required to compile the driver modules from source on a SuSE-based OS.
1. Execute the following command to become a super user:
$ sudo su
Note: Super user rights are required to edit and make changes in various system files.
2. Get the name of the installation DVD entry in /dev directory. The DVD is visible as /dev/srX. Use the
following command to list all the scsi devices on the system.
# lsscsi
3. Once the DVD name is confirmed, create a location to save the DVD image, for example:
# mkdir /var/iso
4. Create an ISO image from the installation disk. Once the DVD image is saved, zypper uses the ISO as an
installation service and install the packages from it by using the following command:
# dd if=/dev/srX of=/var/iso/sles.iso
5. Once the installation disk is saved as an ISO image, set it as an installation service by using the following
command:
# zypper sa “iso:/?iso=/var/iso/sles.iso” “SLES xy spz”
Where, xy z is the SLES distribution ID eg 10 sp1.
6. Run the following command after adding the ISO image as an installation service:
# zypper sl

SmartRAID/SmartHBA Physical and Logical Device Sup...
11. SmartRAID/SmartHBA Physical and Logical Device Support

Table 11-1. SmartRAID/SmartHBA Physical and Logical Device Support
Item SmartRAID SmartHBA Description

Adapters Adapters
Max single/dual devices 256 256 # of physical SAS/SATA devices supported.

supported Includes SEP devices, expanders. Results into
238 storage devices supported
Max # of RAID arrays 64 64 Maximum number of RAID arrays supported /
supported exposed to host OS
Max # of logical drives/ 64 64 Maximum number of logical drives (single or
single cached volumes RAID) exposed to host / OS
(single drive R0)
Multi-LUN Y Y Support for LUNs per SCSI ID available (for
RBODs, tape libraries)
# of LUNs supported per 256 256 # of SCSI LUNs supported per SCSI ID (other
SCSI ID than RAID LUNs)
RAID 0: max. devices per 128 drives per 128 drives max. Supported drive count in striping and mirroring
volume, RAID 1: 2 devices volume max. RAID arrays and the combination of both
per volume or 3 devices (RAID10)
with no plus hot spare,
RAID 10: max. devices per
volume
RAID 5: max devices per 128 128 Supported drive count in a RAID5
volume
RAID 50, 6, 60 max. 128 N/A Supported drive count in the named RAID
devices per volume arrays
maxCache 4.0 logical 32 N/A Max. 32 logical drives can be accelerated by

caching volumes maxCache. 32 LDs used for acceleration.
# of spare drives 4 / 32 4/32 Number per Array / number per adapter

supported

Safety Information
12. Safety Information

To ensure your personal safety and the safety of your equipment:
• Keep your work area and the computer clean and clear of debris.
• Before opening the system cabinet, unplug the power cord.
12.1 Electrostatic Discharge (ESD)
ESD can damage electronic components when they are improperly handled, and can result in total or
CAUTION
intermittent failures. Always follow ESD-prevention procedures when removing and replacing components.
To prevent ESD damage:

• Use an ESD wrist or ankle strap and ensure that it makes skin contact. Connect the equipment end of the strap
to an unpainted metal surface on the chassis.
• Avoid touching the adapter against your clothing. The wrist strap protects components from ESD on the body
only.
• Handle the adapter by its bracket or edges only. Avoid touching the printed circuit board or the connectors.
• Put the adapter down only on an antistatic surface such as the bag supplied in your kit.
• If you are returning the adapter to Microchip Product Support, put it back in its antistatic bag immediately.
If a wrist strap is not available, ground yourself by touching the metal chassis before handling the adapter or any
other part of the computer.

Technical Specifications
13. Technical Specifications
13.1 Environmental Specifications

Note: SmartRAID 3200 Series adapters and SmartHBA 2200 Series adapters require adequate airflow to operate
reliably. Forced airflow is required. See the Recommended Airflow table below for more information.
Ambient temperature with forced airflow 0 °C to 55 ° C

Relative humidity 20% to 80%, non-condensing
Altitude Up to 3,000 meters
Note: Ambient temperature is measured 1” from the HBA processor.

Table 13-1. Recommended Airflow
Controller Recommended Airflow/Linear Feet per Minute (LFM)

Adaptec SmartRAID 3204-8i 250 LFM
Adaptec SmartRAID 3254-8i 250 LFM
Adaptec SmartRAID 3254-16i /e 250 LFM
Adaptec SmartRAID 3258-16i /e 250 LFM
Adaptec SmartHBA 2200-16i 250 LFM
Adaptec SmartRAID Ultra 3258P-32i /e 200 LFM

Revision History
14. Revision History

Table 14-1. Revision History
Revision Date Description

A 06/2021 Document created.

The Microchip Website
Microchip provides online support via our website at www.microchip.com/. This website is used to make files and
information easily available to customers. Some of the content available includes:
• Product Support – Data sheets and errata, application notes and sample programs, design resources, user’s
guides and hardware support documents, latest software releases and archived software
• General Technical Support – Frequently Asked Questions (FAQs), technical support requests, online
discussion groups, Microchip design partner program member listing
• Business of Microchip – Product selector and ordering guides, latest Microchip press releases, listing of
seminars and events, listings of Microchip sales offices, distributors and factory representatives
Product Change Notification Service
Microchip’s product change notification service helps keep customers current on Microchip products. Subscribers will
receive email notification whenever there are changes, updates, revisions or errata related to a specified product
family or development tool of interest.
To register, go to www.microchip.com/pcn and follow the registration instructions.
Customer Support
Users of Microchip products can receive assistance through several channels:

• Distributor or Representative
• Local Sales Office
• Embedded Solutions Engineer (ESE)
• Technical Support
Customers should contact their distributor, representative or ESE for support. Local sales offices are also available to
help customers. A listing of sales offices and locations is included in this document.
Technical support is available through the website at: www.microchip.com/support
Microchip Devices Code Protection Feature
Note the following details of the code protection feature on Microchip devices:
• Microchip products meet the specifications contained in their particular Microchip Data Sheet.
• Microchip believes that its family of products is secure when used in the intended manner and under normal
conditions.
• There are dishonest and possibly illegal methods being used in attempts to breach the code protection features
of the Microchip devices. We believe that these methods require using the Microchip products in a manner
outside the operating specifications contained in Microchip’s Data Sheets. Attempts to breach these code
protection features, most likely, cannot be accomplished without violating Microchip’s intellectual property rights.
• Microchip is willing to work with any customer who is concerned about the integrity of its code.
• Neither Microchip nor any other semiconductor manufacturer can guarantee the security of its code. Code
protection does not mean that we are guaranteeing the product is “unbreakable.” Code protection is constantly
evolving. We at Microchip are committed to continuously improving the code protection features of our products.
Attempts to break Microchip’s code protection feature may be a violation of the Digital Millennium Copyright Act.
If such acts allow unauthorized access to your software or other copyrighted work, you may have a right to sue
for relief under that Act.

Legal Notice
Information contained in this publication is provided for the sole purpose of designing with and using Microchip
products. Information regarding device applications and the like is provided only for your convenience and may be
superseded by updates. It is your responsibility to ensure that your application meets with your specifications.
THIS INFORMATION IS PROVIDED BY MICROCHIP “AS IS”. MICROCHIP MAKES NO REPRESENTATIONS
OR WARRANTIES OF ANY KIND WHETHER EXPRESS OR IMPLIED, WRITTEN OR ORAL, STATUTORY
OR OTHERWISE, RELATED TO THE INFORMATION INCLUDING BUT NOT LIMITED TO ANY IMPLIED
WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY, AND FITNESS FOR A PARTICULAR PURPOSE
OR WARRANTIES RELATED TO ITS CONDITION, QUALITY, OR PERFORMANCE.
IN NO EVENT WILL MICROCHIP BE LIABLE FOR ANY INDIRECT, SPECIAL, PUNITIVE, INCIDENTAL OR
CONSEQUENTIAL LOSS, DAMAGE, COST OR EXPENSE OF ANY KIND WHATSOEVER RELATED TO THE
INFORMATION OR ITS USE, HOWEVER CAUSED, EVEN IF MICROCHIP HAS BEEN ADVISED OF THE
POSSIBILITY OR THE DAMAGES ARE FORESEEABLE. TO THE FULLEST EXTENT ALLOWED BY LAW,
MICROCHIP'S TOTAL LIABILITY ON ALL CLAIMS IN ANY WAY RELATED TO THE INFORMATION OR ITS USE
WILL NOT EXCEED THE AMOUNT OF FEES, IF ANY, THAT YOU HAVE PAID DIRECTLY TO MICROCHIP FOR
THE INFORMATION. Use of Microchip devices in life support and/or safety applications is entirely at the buyer’s risk,
and the buyer agrees to defend, indemnify and hold harmless Microchip from any and all damages, claims, suits, or
expenses resulting from such use. No licenses are conveyed, implicitly or otherwise, under any Microchip intellectual
property rights unless otherwise stated.
Trademarks
The Microchip name and logo, the Microchip logo, Adaptec, AnyRate, AVR, AVR logo, AVR Freaks, BesTime,
BitCloud, chipKIT, chipKIT logo, CryptoMemory, CryptoRF, dsPIC, FlashFlex, flexPWR, HELDO, IGLOO, JukeBlox,
KeeLoq, Kleer, LANCheck, LinkMD, maXStylus, maXTouch, MediaLB, megaAVR, Microsemi, Microsemi logo,
MOST, MOST logo, MPLAB, OptoLyzer, PackeTime, PIC, picoPower, PICSTART, PIC32 logo, PolarFire, Prochip
Designer, QTouch, SAM-BA, SenGenuity, SpyNIC, SST, SST Logo, SuperFlash, Symmetricom, SyncServer,
Tachyon, TimeSource, tinyAVR, UNI/O, Vectron, and XMEGA are registered trademarks of Microchip Technology
Incorporated in the U.S.A. and other countries.
AgileSwitch, APT, ClockWorks, The Embedded Control Solutions Company, EtherSynch, FlashTec, Hyper Speed
Control, HyperLight Load, IntelliMOS, Libero, motorBench, mTouch, Powermite 3, Precision Edge, ProASIC,
ProASIC Plus, ProASIC Plus logo, Quiet-Wire, SmartFusion, SyncWorld, Temux, TimeCesium, TimeHub, TimePictra,
TimeProvider, WinPath, and ZL are registered trademarks of Microchip Technology Incorporated in the U.S.A.
Adjacent Key Suppression, AKS, Analog-for-the-Digital Age, Any Capacitor, AnyIn, AnyOut, Augmented Switching,
BlueSky, BodyCom, CodeGuard, CryptoAuthentication, CryptoAutomotive, CryptoCompanion, CryptoController,
dsPICDEM, dsPICDEM.net, Dynamic Average Matching, DAM, ECAN, Espresso T1S, EtherGREEN, IdealBridge,
In-Circuit Serial Programming, ICSP, INICnet, Intelligent Paralleling, Inter-Chip Connectivity, JitterBlocker, maxCrypto,
maxView, memBrain, Mindi, MiWi, MPASM, MPF, MPLAB Certified logo, MPLIB, MPLINK, MultiTRAK, NetDetach,
Omniscient Code Generation, PICDEM, PICDEM.net, PICkit, PICtail, PowerSmart, PureSilicon, QMatrix, REAL ICE,
Ripple Blocker, RTAX, RTG4, SAM-ICE, Serial Quad I/O, simpleMAP, SimpliPHY, SmartBuffer, SMART-I.S., storClad,
SQI, SuperSwitcher, SuperSwitcher II, Switchtec, SynchroPHY, Total Endurance, TSHARC, USBCheck, VariSense,
VectorBlox, VeriPHY, ViewSpan, WiperLock, XpressConnect, and ZENA are trademarks of Microchip Technology
Incorporated in the U.S.A. and other countries.
SQTP is a service mark of Microchip Technology Incorporated in the U.S.A.
The Adaptec logo, Frequency on Demand, Silicon Storage Technology, and Symmcom are registered trademarks of
Microchip Technology Inc. in other countries.
GestIC is a registered trademark of Microchip Technology Germany II GmbH & Co. KG, a subsidiary of Microchip
Technology Inc., in other countries.
All other trademarks mentioned herein are property of their respective companies.
© 2021, Microchip Technology Incorporated, Printed in the U.S.A., All Rights Reserved.
ISBN: 978-1-5224-8317-5

Quality Management System
For information regarding Microchip’s Quality Management Systems, please visit www.microchip.com/quality.

Worldwide Sales and Service
AMERICAS ASIA/PACIFIC ASIA/PACIFIC EUROPE
Corporate Office Australia - Sydney India - Bangalore Austria - Wels
2355 West Chandler Blvd. Tel: 61-2-9868-6733 Tel: 91-80-3090-4444 Tel: 43-7242-2244-39
Chandler, AZ 85224-6199 China - Beijing India - New Delhi Fax: 43-7242-2244-393
Tel: 480-792-7200 Tel: 86-10-8569-7000 Tel: 91-11-4160-8631 Denmark - Copenhagen
Fax: 480-792-7277 China - Chengdu India - Pune Tel: 45-4485-5910
Technical Support: Tel: 86-28-8665-5511 Tel: 91-20-4121-0141 Fax: 45-4485-2829
www.microchip.com/support China - Chongqing Japan - Osaka Finland - Espoo
Web Address: Tel: 86-23-8980-9588 Tel: 81-6-6152-7160 Tel: 358-9-4520-820
www.microchip.com China - Dongguan Japan - Tokyo France - Paris
Atlanta Tel: 86-769-8702-9880 Tel: 81-3-6880- 3770 Tel: 33-1-69-53-63-20
Duluth, GA China - Guangzhou Korea - Daegu Fax: 33-1-69-30-90-79
Tel: 678-957-9614 Tel: 86-20-8755-8029 Tel: 82-53-744-4301 Germany - Garching
Fax: 678-957-1455 China - Hangzhou Korea - Seoul Tel: 49-8931-9700
Austin, TX Tel: 86-571-8792-8115 Tel: 82-2-554-7200 Germany - Haan
Tel: 512-257-3370 China - Hong Kong SAR Malaysia - Kuala Lumpur Tel: 49-2129-3766400
Boston Tel: 852-2943-5100 Tel: 60-3-7651-7906 Germany - Heilbronn
Westborough, MA China - Nanjing Malaysia - Penang Tel: 49-7131-72400
Tel: 774-760-0087 Tel: 86-25-8473-2460 Tel: 60-4-227-8870 Germany - Karlsruhe
Fax: 774-760-0088 China - Qingdao Philippines - Manila Tel: 49-721-625370
Chicago Tel: 86-532-8502-7355 Tel: 63-2-634-9065 Germany - Munich
Itasca, IL China - Shanghai Singapore Tel: 49-89-627-144-0
Tel: 630-285-0071 Tel: 86-21-3326-8000 Tel: 65-6334-8870 Fax: 49-89-627-144-44
Fax: 630-285-0075 China - Shenyang Taiwan - Hsin Chu Germany - Rosenheim
Dallas Tel: 86-24-2334-2829 Tel: 886-3-577-8366 Tel: 49-8031-354-560
Addison, TX China - Shenzhen Taiwan - Kaohsiung Israel - Ra’anana
Tel: 972-818-7423 Tel: 86-755-8864-2200 Tel: 886-7-213-7830 Tel: 972-9-744-7705
Fax: 972-818-2924 China - Suzhou Taiwan - Taipei Italy - Milan
Detroit Tel: 86-186-6233-1526 Tel: 886-2-2508-8600 Tel: 39-0331-742611
Novi, MI China - Wuhan Thailand - Bangkok Fax: 39-0331-466781
Tel: 248-848-4000 Tel: 86-27-5980-5300 Tel: 66-2-694-1351 Italy - Padova
Houston, TX China - Xian Vietnam - Ho Chi Minh Tel: 39-049-7625286
Tel: 281-894-5983 Tel: 86-29-8833-7252 Tel: 84-28-5448-2100 Netherlands - Drunen
Indianapolis China - Xiamen Tel: 31-416-690399
Noblesville, IN Tel: 86-592-2388138 Fax: 31-416-690340
Tel: 317-773-8323 China - Zhuhai Norway - Trondheim
Fax: 317-773-5453 Tel: 86-756-3210040 Tel: 47-72884388
Tel: 317-536-2380 Poland - Warsaw
Los Angeles Tel: 48-22-3325737
Mission Viejo, CA Romania - Bucharest
Tel: 949-462-9523 Tel: 40-21-407-87-50
Fax: 949-462-9608 Spain - Madrid
Tel: 951-273-7800 Tel: 34-91-708-08-90
Raleigh, NC Fax: 34-91-708-08-91
Tel: 919-844-7510 Sweden - Gothenberg
New York, NY Tel: 46-31-704-60-40
Tel: 631-435-6000 Sweden - Stockholm
San Jose, CA Tel: 46-8-5090-4654
Tel: 408-735-9110 UK - Wokingham
Tel: 408-436-4270 Tel: 44-118-921-5800
Canada - Toronto Fax: 44-118-921-5820
Tel: 905-695-1980
Fax: 905-695-2078


adaptec_smarthba_smartraid_x200_iug_7_2021

Uploaded by

Document Informationclick to expand document information

Copyright:

Available Formats

adaptec_smarthba_smartraid_x200_iug_7_2021

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

adaptec_smarthba_smartraid_x200_iug_7_2021

Uploaded by

Copyright:

Available Formats

Adaptec® SmartRAID 3200 and SmartHBA 2200 Installation

and User Guide

© 2021 Microchip Technology Inc. User Guide DS-00004037A-page 1

2. About This Guide.................................................................................................................................... 8

3. Kit Contents and System Requirements................................................................................................. 9

4. About Your Host Bus Adapter............................................................................................................... 10

5. Installing the Controller and Disk Drives............................................................................................... 18

6. Installing the Driver and an Operating System......................................................................................21

7. Installing the Driver on an Existing Operating System.......................................................................... 32

© 2021 Microchip Technology Inc. User Guide DS-00004037A-page 2

9. Using the Microchip SAS/SATA HII Configuration Utility.......................................................................41

10. Installing the SmartPQI Drivers from Source ....................................................................................... 56

11. SmartRAID/SmartHBA Physical and Logical Device Support...............................................................59

12. Safety Information................................................................................................................................. 60

13. Technical Specifications........................................................................................................................ 61

14. Revision History.................................................................................................................................... 62

The Microchip Website.................................................................................................................................63

Product Change Notification Service............................................................................................................63

Microchip Devices Code Protection Feature................................................................................................ 63

© 2021 Microchip Technology Inc. User Guide DS-00004037A-page 3

Quality Management System....................................................................................................................... 65

Worldwide Sales and Service.......................................................................................................................66

© 2021 Microchip Technology Inc. User Guide DS-00004037A-page 4

1. Regulatory Compliance Statements

Microchip Corporation Use only with the listed ITE:

SmartRAID Ultra 3258P-32i /e

© 2021 Microchip Technology Inc. User Guide DS-00004037A-page 5

European Union Compliance Statement—Pending

Australian/New Zealand Compliance Statement—Pending

Canadian Compliance Statement—Pending

Japanese Compliance (Voluntary Control Council Initiative)—Pending

© 2021 Microchip Technology Inc. User Guide DS-00004037A-page 6

Korean Compliance (KCC) Statement—Pending

SmartRAID Ultra 3258P-32i /e

Korean Compliance (KCC) Statement:

SmartRAID Ultra 3254-16e /e

Korean Compliance (KCC) Statement:

© 2021 Microchip Technology Inc. User Guide DS-00004037A-page 7

2. About This Guide

2.1 What You Need to Know Before You Begin

2.2 Terminology Used in this Guide

2.3 How to Find More Information

© 2021 Microchip Technology Inc. User Guide DS-00004037A-page 8

3. Kit Contents and System Requirements

3.1 Kit Contents

3.2 System Requirements

© 2021 Microchip Technology Inc. User Guide DS-00004037A-page 9

4. About Your Host Bus Adapter

4.1 About Your SmartRAID 3200 Series Host Bus Adapter

4.1.1 Standard Features

4.1.2 Mechanical Information

4.1.2.1 Board Dimensions

Table 4-2. Low-Profile (LP) Board Dimensions (16 port, 8 port)

© 2021 Microchip Technology Inc. User Guide DS-00004037A-page 10

4.1.2.2 Heat Sink

4.1.3 Visual Indicators

LED Color Meaning

© 2021 Microchip Technology Inc. User Guide DS-00004037A-page 11

4.1.4 About the SmartRAID Ultra 3258P-32i /e Adapter