Intel® RAID Software User Guide • Intel® Embedded Server RAID Technology 2 • Intel® IT/IR RAID • Intel® Integrated Server RAID • Intel® RAID Software Stack 3 Revision 23.
DISCLAIMER IINFORMATION IN THIS DOCUMENT IS PROVIDED IN CONNECTION WITH INTEL PRODUCTS. NO LICENSE, EXPRESS OR IMPLIED, BY ESTOPPEL OR OTHERWISE, TO ANY INTELLECTUAL PROPERTY RIGHTS IS GRANTED BY THIS DOCUMENT.
Table of Contents 1 Overview ................................................................................................................ 1 1.1 1.2 1.3 2 Supported Hardware .....................................................................................................1 Software ........................................................................................................................ 4 RAID Terminology ................................................................................
3 RAID Utilities .......................................................................................................29 Intel® Embedded Server RAID Technology II BIOS Configuration Utility ................... 29 LSI MPT* SAS BIOS Configuration Utility .................................................................. 29 Intel® RAID BIOS Console 2 Configuration Utility for Intelligent RAID ....................... 30 Intel® RAID Web Console 2 Configuration and Monitoring Utility ..........................
6.2 Creating Mirrored Volumes .........................................................................................51 6.2.1 Mirrored Volume Configuration Overview ........................................................52 6.2.2 Creating Mirrored Volumes ..............................................................................52 6.2.3 Managing Hot Spare Disks ..............................................................................56 6.2.4 Other Configuration Tasks ............................
7.13.1 Viewing Controller Properties ........................................................................ 99 7.13.2 Modifying Controller Properties ..................................................................... 99 7.13.3 Viewing and Changing Virtual Drive Properties .......................................... 101 7.13.4 Deleting a Virtual Drive ............................................................................... 103 7.13.5 Deleting a Virtual Drive Group .................................
9.4 9.5 9.6 9.7 9.8 9.9 9.10 9.11 9.12 9.13 9.14 9.15 9.16 9.17 9.18 9.19 9.20 9.21 Hardware and Software Requirements .....................................................................149 Installing the Intel® RAID Web Console 2 on a Microsoft Windows* Operating System 149 Installing the Intel® RAID Web Console 2 on Linux or SuSE* Linux Enterprise Server . 151 Intel® RAID Web Console 2 Support and Installation on VMWare ...........................152 9.7.
9.21.8 Monitoring Rebuilds and Other Processes .................................................. 209 9.22 Maintaining and Managing Storage Configurations ............................................... 211 9.22.1 Initializing a Virtual Disk .............................................................................. 211 9.22.2 Running a Consistency Check .................................................................... 212 9.22.3 Scanning for New Drives ................................................
10.6.6 Setting the Cache Policy in a Virtual Drive ..................................................301 10.6.7 Showing Virtual Drive Information ...............................................................301 10.6.8 Deleting Virtual Drives .................................................................................302 10.6.9 Flashing Controller Firmware ......................................................................302 10.7 Unsupported StorCLI Commands .......................................
List of Figures Figure 1. RAID 0 – Data Striping ............................................................................................ Figure 2. RAID 1 – Disk Mirroring/Disk Duplexing .................................................................. Figure 3. RAID 5 – Data Striping with Striped Parity .............................................................. Figure 4. Example of Distributed Parity across Two Blocks in a Stripe (RAID 6) ................... Figure 5.
Figure 43. Virtual Drive Properties ........................................................................................ Figure 44. Create Virtual Drive – Advanced.......................................................................... Figure 45. Expand Virtual Drive ............................................................................................ Figure 46. Erase Virtual Drive ............................................................................................... Figure 47.
Figure 90. LDAP Login.......................................................................................................... Figure 91. Configure Host LDAP .......................................................................................... Figure 92. Intel® RAID Web Console 2 – Operations Tab.................................................... Figure 93. Intel® RAID Web Console 2 – Graphical Tab (Optional feature) ......................... Figure 94. Virtual Drive Creation Menu....................
Figure 137. Scan for Foreign Configuration .......................................................................... Figure 138. Preparing Drive for Removal.............................................................................. Figure 139. Check Controller Security status........................................................................ Figure 140. Check Drive Security status ............................................................................... Figure 141. Enable Drive Security......
Figure 184. Option to Close the Configuration Wizard .........................................................
List of Tables Table 1. RAID 0 Overview .......................................................................................................10 Table 2. RAID 1 Overview .......................................................................................................11 Table 3. RAID 5 Overview .......................................................................................................12 Table 4. RAID 6 Overview ...............................................................................
1 Overview The software described in this document is designed for use with Intel® RAID controllers, and with on-serverboard RAID solutions that use the Intel® RAID Software Stack 3 (driver package names begin with “ir3”), Embedded Server RAID Technology 2 (driver package names begin with ESRT2) or Intel® IT/IR RAID. 1.
— Intel® RAID Controller SASWT4I — Intel® RAID Controller SASUC8I — Intel® RAID SAS Riser Controller AFCSASRISER in Intel® Server System S7000FC4UR without Intel® SAS RAID Activation Key AXXRAKSAS2 installed — Intel® RAID SAS Riser Controller AFCSASRISER in Intel® Server System S7000FC4UR without Intel® SAS RAID Activation Key AXXRAKSAS2 installed — Intel® SAS Entry RAID Module AXX4SASMOD — Intel® 6G SAS PCIe Gen2 RAID Module RMS2LL080 and RMS2LL040 — Intel® Integrated RAID Module RMS25KB080, RMS25KB040, RM
RMS2AF040, RS2BL080, RS2BL040, RS2BL080DE, RS2BL080SNGL, RS2PI008, RS2PI008DE, RS2MB044, RS2WC080, RS2WC040, SROMBSASMR, SRCSATAWB, SRCSASRB, SRCSASJV, SRCSABB8I, SRCSASLS4I, SRCSASPH16I, SROMBSASFC, SROMBSASMP2, SROMBSAS18E, SRCSAS18E and SRCSAS144E.
backup strategy. It is highly recommended you back up data regularly through a tape drive or other backup strategy to guard against data loss. It is especially important to back up all data before working on any system components and before installing or changing the RAID controller or configuration. 1.2 Software Intel® Embedded Server RAID Technology II, Intel® IT/IR RAID and Intel® Integrated Server RAID controllers include a set of software tools to configure and manage RAID systems.
1.3 RAID Terminology RAID is a group of physical disks put together to provide increased I/O (Input/Output) performance (by allowing multiple, simultaneous disk access), fault tolerance, and reliability (by reconstructing failed drives from remaining data). The physical drive group is called an array, and the partitioned sets are called virtual disks. A virtual disk can consist of a part of one or more physical arrays, and one or more entire arrays.
for data storage in the array unless another drive fails. Upon failure of one of the array’s physical drives, the hot-spare drive is used to hold the recreated data and restore data redundancy. Hot-spare drives can be global (available to any array on a controller) or dedicated (only usable by one array). There can be more than one hot spare per array and the drive of the closest capacity is used. If both dedicated and global hot-spare drives are available, then the dedicated drive is used first.
“ABCsum”. When drive A fails, the controller uses the ABCsum to calculates what remains on drives B+C. The remainder must be recreated onto new drive A. Parity can be dedicated (all parity stripes are placed on the same drive) or distributed (parity stripes are spread across multiple drives). Calculating and writing parity slows the write process but provides redundancy in a much smaller space than mirroring.
1.3.3.1 Disk Striping Disk striping writes data across all of the physical disks in the array into fixed size partitions or stripes. In most cases, the stripe size is user-defined. Stripes do not provide redundancy but improve performance since striping allows multiple physical drives to be accessed at the same time. These stripes are interleaved in a repeated sequential manner and the controller knows where data is stored. The same stripe size should be kept across RAID arrays.
2 RAID Levels The RAID controller supports RAID levels 0, 1E, 5, 6, 10, 50, and 60. The supported RAID levels are summarized below. In addition, it supports independent drives (configured as RAID 0). This chapter describes the RAID levels in detail. 2.1 Summary of RAID Levels • RAID 0: Uses striping to provide high data throughput, especially for large files in an environment that does not require fault tolerance.
2.2 Selecting a RAID Level To ensure the best performance, select the optimal RAID level when the system drive is created. The optimal RAID level for a disk array depends on a number of factors: • • • • 2.2.1 The number of physical drives in the disk array The capacity of the physical drives in the array The need for data redundancy The disk performance requirements RAID 0 - Data Striping RAID 0 provides disk striping across all drives in the RAID array.
Weak Points 1 to 32 Drives 2.2.2 Does not provide fault tolerance or high bandwidth. If any drive fails, all data is lost. RAID 1 - Disk Mirroring/Disk Duplexing In RAID 1, the RAID controller duplicates all data from one drive to a second drive. RAID 1 provides complete data redundancy, but at the cost of doubling the required data storage capacity. Table 2 provides an overview of RAID 1. Table 2.
Table 3 provides an overview of RAID 5. Table 3. RAID 5 Overview Uses Provides high data throughput, especially for large files. Use RAID 5 for transaction processing applications because each drive can read and write independently. If a drive fails, the RAID controller uses the parity drive to recreate all missing information. Use also for office automation and online customer service that requires fault tolerance. Use for any application that has high read request rates but low write request rates.
Table 4. RAID 6 Overview Provides a high level of data protection through the use of a second parity block in each stripe. Use RAID 6 for data that requires a high level of protection from loss. In the case of a failure of one drive or two drives in a virtual disk, the RAID controller uses the parity blocks to recreate the missing information. If two drives in a RAID 6 virtual disk fail, two drive rebuilds are required, one for each drive. These rebuilds do not occur at the same time.
2.2.5 RAID IME An IME volume can be configured with up to ten mirrored disks (one or two global hot spares can also be added). Figure 5 shows the logical view and physical view of an Integrated Mirroring Enhanced (IME) volume with three mirrored disks. Each mirrored stripe is written to a disk and mirrored to an adjacent disk. This type of configuration is also called RAID 1E. Figure 5. Integrated Mirroring Enhanced with Three Disks Table 5.
Table 6. RAID 10 Overview Appropriate when used with data storage that requires 100 percent redundancy of mirrored arrays and that needs the enhanced I/O performance of RAID 0 (striped arrays). RAID 10 works well for medium-sized databases or any environment that requires a higher degree of fault tolerance and moderate to medium capacity. Uses Strong Points Provides both high data transfer rates and complete data redundancy.
Table 7. RAID 50 Overview Appropriate when used with data that requires high reliability, high request rates, high data transfer, and medium to large capacity. Uses Strong Points Weak Points Drives Provides high data throughput, data redundancy, and very good performance. Requires 2 to 8 times as many parity drives as RAID 5.
Table 8. RAID 60 Overview Provides a high level of data protection through the use of a second parity block in each stripe. Use RAID 60 for data that requires a very high level of protection from loss. Uses In the case of a failure of one drive or two drives in a RAID set in a virtual disk, the RAID controller uses the parity blocks to recreate all the missing information. If two drives in a RAID 6 set in a RAID 60 virtual disk fail, two drive rebuilds are required, one for each drive.
RAID 60 Figure 8. RAID 60 Level Virtual Drive Intel® RAID Software User Guide 18 Note: Parity (Q15-Q16) Segment 12 Segment 7 Parity (P1-P2) Parity is distributed across all drives in the array.
2.3 RAID Configuration Strategies The most important factors in RAID array configuration are: • • • Virtual disk availability (fault tolerance) Virtual disk performance Virtual disk capacity You cannot configure a virtual disk that optimizes all three factors, but it is easy to choose a virtual disk configuration that maximizes one factor at the expense of another factor. For example, RAID 1 (mirroring) provides excellent fault tolerance, but requires a redundant drive.
RAID Level 2.3.2 Fault Tolerance 5 Combines distributed parity with disk striping. Parity provides redundancy for one drive failure without duplicating the contents of entire disk drives. If a drive fails, the RAID controller uses the parity data to reconstruct all missing information. In RAID 5, this method is applied to the entire drive or stripes across all disk drives in an array. Using distributed parity, RAID 5 offers fault tolerance with limited overhead.
RAID Level 5 Performance RAID 5 provides high data throughput, especially for large files. Use this RAID level for any application that requires high read request rates, but low write request rates, such as transaction processing applications, because each drive can read and write independently. Since each drive contains both data and parity, numerous writes can take place concurrently.
2.3.3 Maximizing Storage Capacity Storage capacity is an important factor when selecting a RAID level. There are several variables to consider. Striping alone (RAID 0) requires less storage space than mirrored data (RAID 1 or IME) or distributed parity (RAID 5 or RAID 6). RAID 5, which provides redundancy for one drive failure without duplicating the contents of entire disk drives, requires less space then RAID 1. Table 11 explains the effects of the RAID levels on storage capacity. Table 11.
2.4 RAID Availability 2.4.1 RAID Availability Concept Data availability without downtime is essential for many types of data processing and storage systems. Businesses want to avoid the financial costs and customer frustration associated with failed servers. RAID helps you maintain data availability and avoid downtime for the servers that provide that data.
2.4.4 Drive in Foreign State When newly inserted drives are detected by the RAID controller, and are displayed in either RAID BIOS Console 2 or RAID Web Console 2, their state may show as (Foreign) Unconfigured Good, or (Foreign) Unconfigured Bad. The Foreign state indicates that the RAID controller finds existing RAID configuration on the new drives. Since these drives cannot be configured directly, avoid deleting data on the existing RAID by mistake.
— If you add a hot spare (assume a global hot spare) during a copyback operation, the copyback is aborted, and the rebuild operation starts on the hot spare. 2.4.6 Configuration Planning Factors to consider when planning a configuration are the number of physical disks the RAID controller can support, the purpose of the array, and the availability of spare drives. Each type of data stored in the disk subsystem has a different frequency of read and write activity.
2.4.9 UEFI 2.0 Support UEFI 2.0 provides MegaRAID customers with expanded platform support. The MegaRAID UEFI 2.0 driver, a boot service device driver, handles block IO requests and SCSI pass-through (SPT) commands, and offers the ability to launch pre-boot MegaRAID management applications through a driver configuration protocol (DCP). The UEFI driver also supports driver diagnostic protocol, which allows administrators to access pre-boot diagnostics. 2.4.
products, beginning with those designed to utilize the LSI 2208 and LSI2308 SAS products. Currently shipping Intel® RAID and SAS products will support 4K sector drives running in legacy 512b sector mode. 2.4.13 Larger than 2TB Drive Support The disk drive industry is in transition to support disk drives with volume size larger than 2 Terabytes. The Intel® 6G SAS PCIe Gen2 RAID Controllers can fully recognize and configure the volume of these disk drives.
• • • • • • • • 2.4.16 Online Hotspare Failed Rebuilding Unconfigured Bad Missing Offline None Array Purpose Important factors to consider when creating RAID arrays include availability, performance, and capacity.
3 RAID Utilities 3.1 Intel® Embedded Server RAID Technology II BIOS Configuration Utility With support for up to six SATA drives or eight SAS/SATA drives, depending on the server board or system, the embedded RAID BIOS has the following features: 3.2 • • Support for interrupt 13 and Int19h. • POST (Power On Self Test) and run-time BIOS support for device insertion and removal. • Support for a migration path from Intel® Embedded Server RAID Technology II to Intel Integrated Server RAID hardware.
Integrated Mirroring and Integrated Mirroring Enhanced support the following features: • Configurations of one or two IM or IME volumes on the same Intel® IT/IR RAID Controller. IM volumes have two mirrored disks; IME volumes have three to ten mirrored disks. Two volumes can have up to a total of 12 disks. • One or two global hot-spare disks per controller, to automatically replace failed disks in IM/IME volumes.
• • • • 3.4 Access controllers, virtual drives, and physical arrays to display their properties Create hot-spare drives Rebuild failed drives Verify data redundancy in RAID 1, 5, 6, 10, 50, or 60 virtual drives Intel® RAID Web Console 2 Configuration and Monitoring Utility The Intel® RAID Web Console 2 is an operating system-based, object-oriented GUI utility that configures and monitors RAID systems locally or over a network.
a time) during boot. With a RAID-level migration running, a boot can often take more than 15 minutes. 3.4.1 Drive Hierarchy within the RAID Firmware The Intel® Integrated RAID firmware is based on three fundamental levels. Virtual drives are created from drive arrays that are created from physical drives. • Level 1 consists of the physical drives (hard drives and removable hard disks). The firmware identifies each drive by its physical ID and maps it to a virtual address.
• If the system shuts down, the initialization or rebuild process automatically resumes on the next boot. Auto resume must be enabled prior to virtual drive creation. • Stripe size is user definable on a per drive basis and can be 8, 16, 32, 64, or 128 KB in size. The default is 256 KB, which is optimal for many data access types. • Hot spares can be set as global or dedicated. A global hot spare automatically comes online to replace the first drive to fail on any array or disk group on the controller.
memory that has not been written to disk, the LED signals that this operation needs to be completed. Upon reboot, the data in memory can then write to the hard disk drive. 3.5.3 • Although I/O performance may be lower, hard disk drive write-back cache is disabled by default because data can potentially be lost if a power outage occurs.
Caution: It is not recommended to increase the rebuild rate to over 50%. A higher rebuild rate can result in operating system requests not being serviced in a timely fashion and causing an operating system error. 3.5.5 3.5.6 • A consistency check scans the consistency of data on a fault-tolerant disk to determine if data has been corrupted. • Background initialization is a background check of consistency.
The silence alarm option in either the Intel® RAID BIOS Console 2 or the Intel® Web Console 2 management utilities will silence the alarm until a power cycle or another event occurs.
Intel® RAID Drivers 4 The drivers that Intel provides for Intel® RAID Controllers are not compatible with SCSI or SATA-only RAID controllers. The RAID driver files are available on the Resource CD that accompanies the RAID controllers. The driver files are also available at http://downloadcenter.intel.com. If you need to transfer the driver files to another system, you can copy them to a floppy disk or a USB key. Note: Intel updates software frequently and updated drivers may provide additional features.
4. When the system asks for the manufacturer-supplied hardware support disk, insert the Microsoft Windows* driver disk and press . 5. Select the appropriate Microsoft Windows* driver from the menu by highlighting it. Press to proceed. The driver is added to the registry and copied to the appropriate directory. 6. Continue with the Microsoft Windows* operating system installation procedure. 4.1.
2. Press at the boot prompt on the Welcome screen. 3. Copy the Linux driver image from the Resource CD to a disk or USB key. 4. Insert the disk with driver image. 5. Select Yes. 6. Scroll down to select Intel® RAID adapter driver. The utility locates and loads the driver for your device. 7. Follow the Red Hat* Linux installation procedure to complete the installation. 4.
3. Select Modify and press . 4. On the Storage Driver Support screen select Storage Adapters and press . 5. Delete any existing Intel® RAID adapter listings. 6. Press to add unlisted drivers. 7. Press again. A path is displayed. 8. Press . 9. Insert the driver disk into the floppy drive, and press . The system will locate the .HAM driver. 10. Press the key. 11. Select the Driver Summary screen, and press . 12.
Note: Drivers for Solaris* 10 are not available on the CD-ROM. The latest drivers are available at http://www.intel.com/support/motherboards/server/ or from your CDI account. Boot the target system from the Solaris* 10 OS DVD (starting with DVD #1). 1. Select Solaris from the GRUB menu. 2. After the initial kernel loads, select option 5 Apply driver updated. 3. Insert driver floppy or CD into USB floppy or DVD-ROM drive, respectively, on the target system. 4.5.
5 Intel® Embedded Server RAID BIOS Configuration Utility If the SATA RAID or SAS RAID options are enabled in the server BIOS, an option to enter the Intel® Embedded Server RAID BIOS Configuration utility displays during the server boot process. To enter the utility, press + when prompted.
Figure 9. Intel® Embedded Server RAID BIOS Configuration Utility Screen 5.1 Creating, Adding or Modifying a Virtual Drive Configuration To create, add, or modify a virtual drive configuration, follow these steps: 1. Boot the system. 2. Press + when prompted to start the Intel® Embedded Server RAID BIOS Configuration utility. 3. Select Configure from the Main Menu. 4. Select a configuration method: — Easy Configuration does not change existing configurations but allows new configurations.
For each configuration method, a list of available physical drives is displayed. These drives are in the READY state. If you select a physical drive in the list, information about each drive is displayed. 5. Use the arrow keys to move to a drive and press the space bar to add it to the array. Note: The utility limits each drive to the size of the smallest drive. The status for each selected drive that is added to an array changes status from READY to ONLIN A[array#]-[drive#].
16. Select Initialize and use the space bar to highlight the virtual drive to initialize. Caution: All data on the virtual drive is erased during an initialization. 17. Press the key. Select Yes at the prompt and press the key to begin the initialization. A graph shows the progress of the initialization. 18. After the initialization is complete, press the key to return to the previous menu. Pressing the key closes the current menu.
4. If asked to confirm the change, use the arrow key to select Yes. Press the key to change the cache setting. 5.3 Working with a Global Hot-spare Drive A global, but not dedicated, hot-spare drive can be created to automatically replace a failed drive in a RAID 1 or RAID 10 array. For new arrays, you should create the global hot-spare during the configuration process. See “Creating, Adding or Modifying a Virtual Drive Configuration” on page 43. 5.3.
3. Press the key and select Y to confirm. As the rebuild process begins, the drive indicator shows REBLD. 4. When the rebuild is complete, press any key to continue. 5.4.1 Auto Rebuild and Auto Resume To ensure data protection, enable Auto Rebuild and Auto Resume so that drives are automatically re-created to maintain redundancy. • In a pre-boot environment, auto rebuild starts only when you enter the BIOS utility. Note: Hot-plug support is not available in the pre-boot environment.
2. Choose Adapter, Virtual Drive, or Physical Drive. 3. Select the device from the list and view the properties. — For virtual drives, choose View | Update Parameters. — For physical drives, choose Drive Properties. The numeric values of the rates settings are the percentage of system resources. FGI and BGI are abbreviations for foreground and background initialization rates. 4. To change a value, highlight the property and press the key. Note: Some values cannot be changed. 5.
Note: You should also check the system BIOS Setup utility for the boot order setting. To access the BIOS Setup utility, press the key when prompted during POST. 5.9 Deleting (Clearing) a Storage Configuration Caution: Before you clear a storage configuration, back up all the data you want to keep. To clear a storage configuration, follow these steps: 1. On the Main Menu, select Configure | Clear Configuration. 2. When the message appears, select Yes to confirm.
6 Intel® IT/IR RAID Controller Configuration Utility This chapter explains how to create mirrored volumes and integrated striping volumes with the Intel SAS-3 BIOS Configuration Utility (SAS3 BIOS CU). 6.1 Overview This section provides an overview of Intel Integrated RAID features that support the creation of mirrored volumes and striped volumes. 6.1.
• • • • • Fusion-MPT architecture. Menu-driven, BIOS-based configuration utility. Error notification, in which the drivers update an OS-specific event log. Support for SCSI Enclosure Services (SES) status LED. Write journaling, which permits automatic synchronization of potentially inconsistent data after unexpected powerdown situations. • Use of metadata to store volume configuration on disks in a mirrored volume. • Automatic background resynchronization while host I/O transactions continue.
6.2.1 Mirrored Volume Configuration Overview The Intel SAS3 BIOS CU is a menu-driven utility program that enables you to easily configure and manage Integrated RAID volumes. You can use the SAS3 BIOS CU to create one or two mirrored volumes on each Intel SAS-3 controller, with up to two optional global hot spare disks. You must connect all disks in a mirrored volume to the same Intel SAS-3 controller.
Note: Intel strongly recommends that you create global hot spare disks for all mirrored volumes to increase the level of data protection. If a disk in a mirrored volume fails, the Integrated RAID firmware rebuilds it using one of the global hot spares, and the data is safe. If you create two mirrored volumes on an Intel SAS-3 controller, either of the volumes can use the global hot spares if a disk fails. 6.2.2.
This disk is the Secondary disk in the volume. 6. Press C to create the volume. A menu window appears. 7. From the menu options, select Save changes then exit this menu. A message appears briefly, and then the SAS3 BIOS CU returns to the Adapter Properties window. Initialization of the new volume continues in the background. Note: To create a second Integrated Mirroring volume, repeat these instructions starting with step 2.
Integrated Mirroring + Striping volume. As you add disks, the Volume Size field changes to reflect the size of the new volume. 6. Press C to create the volume. A menu window appears. 7. From the menu options, select Save changes then exit this menu. A message appears briefly, and then the SAS3 BIOS CU returns to the Adapter Properties window. Initialization of the new volume continues in the background.
8. Select Manage Volume. The Manage Volume window appears. 9. Select Online Capacity Expansion. A menu window appears with a warning message and with options to start the expansion process or quit. 10. Press Y to start the expansion. The RAID Properties window appears when the expansion process completes. 11. Run a commercial tool specific to the operating system to move or increase the size of the partition on the newly expanded RAID 1 volume. 6.2.
Figure 11. Manage Volume Window 5. Select Manage Hot Spares. The Manage Hot Spares window appears. 6. Identify a disk that is not part of a RAID volume (that is, the value in the Drive Status column is not RAID) and that is not already identified as a hot spare disk. A global hot spare disk must have 512-byte blocks and nonremovable media. The disk type must be either SATA with extended command set support or SAS with SMART support. 7.
3. Select Save changes then exit this menu to complete the deletion of the hot spare disk. The configuration utility pauses while it removes the global hot spare. 6.2.4 Other Configuration Tasks This section explains how to perform other configuration and maintenance tasks for mirrored volumes. 6.2.4.1 Viewing Volume Properties Follow these steps to view the RAID properties of a mirrored volume: 1. In the SAS3 BIOS CU, select an Intel SAS-3 adapter from the adapter list.
A menu window appears. 6. Press Y to start the consistency check. The consistency check runs in the background. If it encounters any data miscompares, it stores the information in a bad block table. 6.2.4.3 Activating a Volume A volume can become inactive if, for example, you remove it from one controller or computer and install it on a different one. The Activate Volume option permits you to reactivate an inactive volume. Follow these steps to activate a selected volume: 1.
4. Select Manage Volume. The Manage Volume window appears. 5. Select Delete Volume. A menu window appears. 6. Either press Y to delete the volume, or press N to cancel the deletion process. After a pause, the utility deletes the volume. If there is another remaining volume and one or two hot spare disks, the BIOS checks the hot spare disks to determine if they are compatible with the remaining volume. If they are not compatible (too small or wrong disk type), the BIOS deletes them also. 6.2.4.
1. In the SAS3 BIOS CU, select an adapter from the adapter list. 2. Select the SAS Topology option. If a device is currently designated as the boot device, the Device Info column on the SAS Topology window lists the word Boot, as shown in the following figure. Figure 12. Boot Device on SAS Topology Window If a device is currently designated as the alternative boot device, the Device Info column shows the word Alt. 3. To select the preferred boot disk, move the cursor to the disk, and press Alt + B. 4.
6.3.1 Integrated Striping Configuration Overview The Intel SAS3 BIOS CU is a menu-driven utility program that enables you to easily configure and manage Integrated RAID volumes. Use the SAS3 BIOS CU to create one or two Integrated Striping volumes on each Intel SAS-3 controller. Each volume contains two drives to ten drives. All disks in an Integrated Striping volume must be connected to the same Intel SAS-3 controller.
Follow these steps to configure an Integrated Striping volume with the SAS3 BIOS CU. The steps begin with the Adapter List window that appears when the SAS3 BIOS CU starts. 1. On the Adapter List window, select an Intel SAS-3 adapter, and press Enter. The Adapter Properties window appears, as the following figure shows. Figure 13. Adapter Properties Window 2. Select RAID Properties, and press Enter. The Select New Volume Type window appears. 3. Select Create RAID 0 Volume.
6.3.3 Other Configuration Tasks This section explains how to perform other configuration and maintenance tasks for Integrated Striping volumes. 6.3.3.1 Viewing Volume Properties Follow these steps to view the RAID properties of a volume: 1. In the SAS3 BIOS CU, select an Intel SAS-3 adapter from the adapter list. The Adapter Properties window appears. 2. Select RAID Properties. The Select New Volume Type window appears. 3. Select View Existing Volume.
6.3.3.3 Deleting a Volume Caution: Before you delete a volume, be sure to back up the data. Follow these steps to delete a selected volume: 1. In the Adapter List window, use the arrow keys to select an Intel SAS adapter. The Adapter Properties window appears. 2. Use the arrow keys to select RAID Properties, and then press Enter. The Select New Volume Type window appears. 3. Select View Existing Volume. The View Volume window appears.
Note: The LEDs on the disk drives flash, as previously described, if the firmware configuration is correct and the drives are in a disk enclosure. 6.3.3.5 Selecting a Boot Disk You select a boot disk in the SAS Topology window. The next time you boot the computer, the firmware moves this disk to scan ID 0, making it the new boot disk. This feature makes it easier to set BIOS boot device options and to keep the boot device constant during device additions and removals.
Note: To change the alternative boot device from one disk to another, follow step 4 and step 5 in this procedure, but press Alt + A instead of Alt + B.
7 12Gb/s Intel® RAID Controller Configuration Utility This chapter describes the Ctrl-R Utility, a BIOS configuration utility, that lets you create and manage RAID configurations on Intel SAS controllers. You can configure the drive groups and drives on the system before the operating system has been installed. 7.1 Overview The Ctrl-R Utility resides in the SAS controller BIOS and operates independently of the operating system. You can use the Ctrl-R Utility to perform tasks such as these: 7.
— If the system has only one SAS controller, the Ctrl-R Utility main menu screen appears. 7.3 Exiting the Ctrl-R Utility To exit the Ctrl-R Utility, perform these steps: 1. Perform one of these actions: — If you are not in a dialog, press Esc once. — If you are in a dialog, press Esc twice (once to exit the dialog, and the second time to exit the utility). A confirmation message box appears. 2. Press OK to exit the utility. 7.
Keystroke Action Lets you to select a menu item, a button, a check box, and values in a list box. Closes a screen or a window. Press Esc twice to exit from the Ctrl-R Utility. Up Arrow Moves the cursor to the next menu selection. Down Arrow Moves the cursor to the lower menu items or to a lower level menu. Right Arrow Opens a submenu, moves from a menu heading to the first submenu, or moves to the first item in a submenu. The right arrow also closes a menu list in a popup window.
Figure 15. VD Mgmt This screen shows information on the configuration of controllers, drive groups, and virtual drives. The right panel of the screen shows attributes of the selected device. In the Virtual Drive Management screen, you can perform tasks, such as creating and initializing virtual drives; performing a consistency check; deleting, expanding, and erasing virtual drives; importing or clearing foreign configurations; and creating CacheCade virtual drives.
Figure 16. Physical Drive Management The right panel of the screen shows additional attributes of the selected device. In the Drive Management screen, you can perform tasks, such as rebuilding a failed drive, making a drive offline, or making it a global hot spare drive. 7.5.3 Ctrl Mgmt Menu The Ctrl Mgmt menu lets you change the settings of the selected controller. The Ctrl Mgmt menu consists of two screens.
Figure 17. Controller Settings – First Screen In the second screen (as shown in the following figure), you can perform tasks, such as changing the link speed, the power save, and the battery settings of the controller. Figure 18. Controller Settings – Second Screen 7.5.4 Properties Menu The Properties menu shows all of the properties of the active controller. The Properties menu consists of two screens. The information shown in these screens is read only.
In the first screen (as shown in the following figure), you can view properties, such as controller status, firmware version, BIOS version, and metadata size. Figure 19. Properties To view additional properties, you can navigate to Next and press Enter. The second Properties screen shows information, such as maximum cache size, drive standby time, and power saving properties. To go back to the previous Properties screen, navigate to Prev, and press Enter. 7.5.
Figure 20. Foreign View Menu You can use the Foreign Config View screen to view information about the foreign configuration, such as drive groups, virtual drives, physical drives, and hot spares. The Foreign View menu lets you import foreign configurations to the RAID controller or clear the foreign configurations. 7.6 Controller Advanced Software Options 7.6.1 Advanced Software Options Perform the following steps to see the advanced software options that the controller supports. 1.
Figure 21. Advanced Software Options The Adv SW Option column shows the list of Advanced Software Options available in the controller. You can ignore License column, Safe ID and Serial No and Activation Key fields and Activate button. Intel RAID Controllers do not need software licenses to enable advanced software options. To enable some premium features present in the RAID controller, you need to install Intel RAID Premium Feature Keys on the controller.
7.6.2 RAID Premium Feature Key Below is a table listing all premium feature keys that are available now. For the latest support information, refer to the Tested Hardware and Operating System List (THOL) of each RAID product available at http://www.intel.com/support. For more details of premium feature key, refer to the Intel Raid Controller Configuration Guide at http://www.intel.com/support. Table 14.
7.7 Creating a Storage Configuration You can use the Ctrl-R Utility to configure RAID drive groups and virtual drives to create storage configurations on systems with Intel SAS controllers. 1. In the VD Mgmt screen, navigate to the controller and press the F2 key. 2. Press Enter. The Create New VD screen appears. Note: You can use the Create New VD dialog to create virtual drives for Unconfigured Good drives.
drives use less energy. The fan and the enclosure require less energy to cool and house the drives, respectively. Also, this technology helps avoid application time-outs caused by spin-up delays and drive wear caused by excessive spinup/down cycles. 5. You can encrypt data and use drive-based key management for your data security solution. This option protects the data in the event of theft or loss of drives. Select a value from the Secure VD field. The options available are Yes and No. 6.
Figure 24. Create Virtual Drive – Advanced 13. Select Initialize, and press OK. The new virtual drive is created and initialized. 7.7.1 Selecting Additional Virtual Drive Properties This section describes the following additional virtual drive properties that you can select while you create virtual drives. Change these parameters only if you have a specific reason for doing so. It is usually best to keep them at their default settings.
— Write Back with BBU – In this mode, the controller enables write back caching when the BBU is installed and charged. This option provides a good balance between data protection and performance. Note: The write policy depends on the status of the BBU. If the BBU is not present, is low, is failed, or is being charged, the current write policy switches to write through, which provides better data protection. • I/O Policy – The I/O policy applies to reads on a specific virtual drive.
Figure 25. Create CacheCade Virtual Drive 3. Enter a name for the CacheCade virtual drive in the Name field. 4. Select a SSD from the Select SSD box. The size of the SSD is reflected in the Size field (in the Basic Settings box). 5. Press OK. A message appears, stating that the CacheCade virtual drive has been created. 7.7.3 Modifying a CacheCade Virtual Drive You can modify an existing CacheCade virtual drive by renaming it. Perform the following steps to modify the CacheCade virtual drive: 1.
Figure 26. Modify CacheCade Virtual Drive 3. You can rename a CacheCade virtual drive in the CacheCade Virtual Drive Name field. 4. Press OK. 7.7.4 Creating a CacheCade Pro 2.0 Virtual Drive The MegaRAID CacheCade Pro 2.0 provides you with read and write capability. Perform the following steps to create a CacheCade Pro 2.0 virtual drive: 1. In the VD Mgmt screen, navigate to the controller, and press the F2 key. 2. Navigate to Create CacheCade Virtual Drive, and press Enter.
Figure 27. Create CacheCade Virtual Drive 3. Enter a name for the CacheCade virtual drive in the Name field. 4. Select a SSD from the Select SSD box. 5. Press OK. A message appears, stating that the CacheCade virtual drive has been created. 7.7.5 Modifying a CacheCade Pro 2.0 Virtual Drive You can modify the name and the write policy of an existing CacheCade virtual drive any time after a CacheCade virtual drive is created. Perform the following steps to modify the CacheCade virtual drive: 1.
Figure 28. Modify CacheCade Virtual Drive 3. You can rename a CacheCade virtual drive in the CacheCade Virtual Drive Name field. 4. You can also modify the write policy by selecting one from the Write Policy field. 5. Press OK. To view the virtual drives associated with this CacheCade virtual drive, click Associated VDs in the dialog above. The Associated Virtual Drives dialog appears. Figure 29.
You can view the ID, the name, and the size of the associated virtual drives. 7.7.6 Enabling SSD Caching on a Virtual Drive You can enable SSD caching on a virtual drive. When you enable SSD caching on a virtual drive, that virtual drive becomes associated with an existing or with a future CacheCade SSD Caching virtual drive. This option is only available when the virtual drive’s caching is currently disabled. Perform the following steps to enable SSD caching on a virtual drive: 1.
Figure 31. Message Box for Disabling SSD Caching 3. Click Yes to disable caching for that virtual drive. 7.7.8 Enabling or Disabling SSD Caching on Multiple Virtual Drives You can enable or disable SSD caching on multiple virtual drives at one go. Perform the follow steps to enable or disable SSD caching on multiple drives: 1. In the VD Mgmt screen, navigate to the controller, and press the F2 key. 2. Select Manage SSD Caching and press Enter. The Manage SSD Caching dialog appears. Figure 32.
7.7.9 Deleting a Virtual Drive with SSD Caching Enabled You can delete a virtual drive that has SSD caching enabled on it. Perform the following steps to delete the virtual drive: 1. In the VD Mgmt screen, navigate to a virtual drive, and press the F2 key. 2. Select Delete VD, and click Yes. The following message dialog appears. Figure 33.
Figure 34. Clear Configuration 3. Press Yes to delete all the virtual drives. 7.9 Intel SafeStore Encryption Services Intel SafeStore Encryption Services can encrypt data on the drives and use the drive-based key management to provide data security. This solution protects data in the event of theft or loss of physical drives.
3. Navigate to Enable Security, and press Enter. The Create Security Key dialog appears. Figure 35. Create Security Key 4. Either use the default security key identifier, or enter a new security key identifier. Note: After you create a security key, the Enable Security option is disabled. This option is reenabled only after you delete the existing key. 5. Either click Suggest to ask the system to create a security key, or you can enter a new security key. 6. Reenter the new security key to confirm it.
7.9.2 Changing Security Settings Perform the following steps to change the encryption settings for the security key identifier, security key, and password: 1. In the VD Mgmt screen, navigate to the controller, and press the F2 key. 2. Navigate to Drive Security, and press Enter. 3. Select Change Security Settings, and press Enter. The Change Security Key dialog appears. Figure 36. Change Security Key 4. Either keep the existing security key identifier, or enter a new security key identifier.
Note: Non-U.S. keyboard users must be careful not to enter DBCS characters in the Security Key field. The firmware works with the ASCII character set only. 7.9.3 Disabling Drive Security If you disable drive security, your existing data is not secure and you cannot create any new secure virtual drives. Disabling drive security does not affect data security on foreign drives. If you removed any drives that were previously secured, you still need to enter the password when you import them.
Verify whether any drives are left to import because the locked drives can use different security keys. If any drives remain, repeat the import process for the remaining drives. After all the drives are imported, there is no configuration to import. Note: When you create a new configuration, the Ctrl-R Utility shows only the unconfigured drives. Drives that have existing configurations, including foreign configurations, do not appear.
Figure 38. Foreign Configuration – Import 5. Press Yes to import the foreign configuration from all the foreign drives. Repeat the import process for any remaining drives. Because locked drives can use different security keys, you must verify whether there are any remaining drives to be imported. Note: When you create a new configuration, the Ctrl-R Utility shows only the unconfigured drives. Drives that have existing configurations, including foreign configurations, do not appear.
7.9.4.1 Foreign Configurations in Cable Pull and Drive Removal Scenarios If one or more drives are removed from a configuration, by a cable pull or drive removal, for example, the configuration on those drives is considered a foreign configuration by the RAID controller. The following scenarios can occur with cable pulls or drive removals. Note: To import the foreign configuration in any of the following scenarios, you must have all the drives in the enclosure before you perform the import operation.
Caution: If there are any foreign configurations, import the foreign configuration before you discard the preserved cache. Otherwise, you might lose data that belongs to the foreign configuration. Perform the following steps to discard the preserved cache: 1. In the VD Mgmt screen, navigate to the controller, and press the F2 key. 2. Navigate to Manage Preserved Cache, and press Enter. The Manage Preserved Cache dialog appears. Figure 40. Manage Preserved Cache 3.
The Convert JBOD to Unconfigured Good dialog appears, which shows all JBODs available in the system. Figure 41. Convert JBOD to Unconfigured Good 3. Select the JBODs which you want configured as Unconfigured Good drives. To select or deselect all the JBODs at one go, select the top most square brackets in the JBOD Drives box. 4. Press OK. The selected JBODS are converted to Unconfigured Good drives. Perform the following steps to convert a particular JBOD drive to an Unconfigured Good drive: 1.
Perform the following steps to convert multiple Unconfigured Good drives to JBOD drives: 1. In the VD Mgmt screen, navigate to the controller, and press the F2 key. 2. Navigate to Make JBOD, and press Enter. The Convert Unconfigured Good to JBOD dialog appears, which shows all Unconfigured Good drives available in the system. Figure 42. Convert Unconfigured Good to JBOD 3. Select the Unconfigured Good drives which you want configured as JBODs.
7.13 Viewing and Changing Device Properties This section explains how you can use the Ctrl-R Utility to view and change the properties for controllers, virtual drives, drive groups, physical drives, and BBUs. 7.13.1 Viewing Controller Properties The Ctrl-R Utility shows information for one Intel SAS controller at a time. If your system has multiple Intel SAS controllers, you can view information for a different controller by pressing the F12 key and selecting a controller from the list.
Option BIOS Mode Description Specifies the following options to set the BIOS boot mode: • • • • Stop on Error: Shows the errors encountered during boot up and waits for your input. The firmware does not proceed with the boot process till you take some action Ignore Error: Ignores errors and the firmware proceeds with boot. Pause on Error: The firmware may halt due to hardware faults. If the firmware encounters no hardware faults, then the boot up continues.
Option Description Enable Stop CC on Error Use this option to stop a consistency check when the controller BIOS encounters an error. Auto Enhanced Import Use this option to import automatically at boot time. Set Factory Defaults Use this option to load the default Ctrl-R Utility settings. Manage Link Speed Use this option to change the link speed between the controller and the expander, or between a controller and a drive that is directly connected to the controller.
Figure 43. Virtual Drive Properties The General box shows the virtual drive’s RAID level, name, state, size, and strip size. The Operations box lists any operation (performed on the virtual drive) in progress, along with its progress status and the time remaining for the operation to be completed. 3. You may change the settings for the fields that are enabled in this dialog. Caution: Before you change a virtual drive configuration, back up any data on the virtual drive that you want to save. 4.
Figure 44. Create Virtual Drive – Advanced You can view the virtual drive policies that were defined when the storage configuration was created. You can also select Initialize and/or Configure Hot Spare to initialize the newly created virtual drive or to configure the virtual drive as a hot spare, respectively.
Perform the following steps to delete a drive group: 1. In the VD Mgmt screen, navigate to a drive group, and press the F2 key. 2. Navigate to Delete Drive Group, and press Enter. The drive group is deleted and is removed from the VD Mgmt screen. 7.13.6 Expanding a Virtual Drive You can increase the size of a virtual drive to occupy the remaining capacity in a drive group. Perform the following steps to expand the size of a virtual drive: 1.
7.13.7 Erasing a Virtual Drive Virtual drive erase operates on a specified virtual drive and overwrites all user-accessible locations. It supports nonzero patterns and multiple passes. Virtual drive erase optionally deletes the virtual drive and erases the data within the virtual drive’s logical base address range. Virtual drive erase is a background operation that posts events to notify users of their progress. Perform the following steps to perform the virtual drive erase operation: 1.
5. Press Yes for the erase operation to start. Once the Drive Erase operation has started, the Simple, Normal, and Thorough options are disabled and the Stop Erase option is enabled. 7.13.8 Managing Link Speed The Managing Link Speed feature lets you change the link speed between the controller and an expander, or between the controller and a drive that is directly connected to the controller. All phys in a SAS port can have different link speeds or can have the same link speed.
— The Link Speed column shows the phy link speeds. 3. Select the desired link speed by using the drop-down list. The link speed values are Auto,1.5Gb/s, 3Gb/s, 6Gb/s, or 12Gb/s. Note: By default, the link speed in the controller is Auto or the value last saved by you. 4. Press OK. A message box appears, asking you to restart your system for the changes to take effect. 5. Press OK. The link speed value is now reset. The change takes place after you restart the system. 7.13.
4. Select the Spin down Hot Spares check box to let the controller enable the Hot spare drives to enter the Power-Save mode. 5. Select the drive standby time from the Drive Standby Time drop-down list. Note: The Drive Standby Time drop-down list is enabled only if any of the preceding check boxes are checked. The drive standby time can be 30 minutes, 1 hour, 90 minutes, or 2 hours through 24 hours. 6. Press OK. A message box appears, asking you to save the power-save settings. 7.
A learning cycle is a battery calibration operation that the controller performs periodically to determine the condition of the battery. Perform the following steps to view and change the battery settings: 1. Navigate to the second Controller Settings screen and select Manage Battery. The Battery Properties dialog appears. Most of the battery properties are read only. Figure 50.
— If the battery does not support transparent learn, the following values appear in the Learn Mode drop-down list: G Automatic – The firmware tracks the time since the last learning cycle and performs a learn cycle when due. Write caching need not be disabled. G Disabled – The firmware does not monitor or initiate a learning cycle. You can schedule learning cycles manually.
7.13.13 Securing a Drive Group If a drive group is created with FDE drives (security enabled drives) and at the time of creation, the security is set to No; later, you can secure that drive group using encryption. Perform the following steps to secure a drive group: 1. Navigate to the VD Mgmt screen, navigate to the drive group that you want to secure, and press the F2 key. 2. Navigate to Secure Drive Group, and press Enter. A message box appears asking for your confirmation. 3.
2. Navigate to Break Mirror, and press Enter. The following message box appears, asking for your confirmation. 3. Press Yes to proceed. 7.13.16 Performing a Join Mirror Operation You can perform a join mirror operation on a drive group to continue using the modified virtual drive or to reuse the original virtual drive. Perform the following steps to perform a join mirror operation: 1.
Figure 53. Confirmation Message If you select Join the mirror arm as a new virtual drive, the following confirmation dialog appears. Figure 54. Confirmation Message 4. Press Yes to proceed. The following dialog appears. Figure 55. Join Mirror – Choose Option 5. Select one of the options and press OK.
7.14 Managing Storage Configurations This section describes how to use the Ctrl-R Utility to maintain and manage storage configurations. 7.14.1 Initializing a Virtual Drive When you create a new virtual drive, the Ctrl-R Utility asks whether you would like to initialize the virtual drive. If you do not want to initialize the virtual drive at that stage, you can initialize the drive later. Perform the following steps to initialize a virtual drive: 1.
For example, in a system with parity, checking consistency means computing the data on one drive and comparing the results with the contents of the parity drive. You must run a consistency check if you suspect that the data on the virtual drive might be corrupted. Caution: Make sure to back up the data before you run a consistency check, if you think the data might be corrupted. Perform the following steps to run a consistency check: 1.
7.14.4 Performing a Copyback Operation You can perform a copyback operation on a selected drive. The copyback operation copies data from a source drive of a virtual drive to a destination drive that is not a part of the virtual drive. The copyback operation often creates or restores a specific physical configuration for a drive group (for example, a specific arrangement of drive group members on the device I/O buses). Perform the following steps to perform the copyback operation: 1.
If you change your mind and do not want to remove the drive, navigate to Undo Removal, and press Enter. 7.14.6 Creating Global Hot Spares A global hot spare is used to replace a failed physical drive in any redundant array, as long as the capacity of the global hot spare is equal to or larger than the coerced capacity of the failed physical drive. You can designate the hot spare to have enclosure affinity.
Caution: After you perform this step, the data on this drive is no longer valid. 7.14.9 Making a Drive Online You can change the state of a physical drive to online. In an online state, the physical drive works normally and is a part of a configured virtual drive. Perform the following steps to make a physical drive online: 1. Navigate to the Drive Management screen, select a physical drive, and press the F2 key. 2. Navigate to Place Drive Online, and press Enter.
— Normal: Specifies a three pass erase operation that first overwrites the physical drive content with random values, then overwrites it with pattern A and then overwrites it with pattern B. — Thorough: Specifies a nine pass erase operation that repeats Normal erase three times. — Stop Erase: This option is disabled. This option is disabled at first. Once the erase operation begins, this options is enabled. 3. Select a mode and press Enter.
8 6Gb/s Intel® RAID Controller Configuration Utility The Intel® RAID BIOS Console 2 utility provides a GUI utility to configure and manage RAID volumes. The utility configures disk groups and virtual drives. Because the utility resides in the RAID controller firmware, it is independent of the operating system.
6. Using the space in the arrays and disk groups, define the virtual drive(s). 7. Initialize the new virtual drives. 8.2 Detailed Configuration Steps using the Intel® RAID BIOS Console 2 8.2.1 Start the Intel® RAID BIOS Console 2 Utility 1. When the system boots, hold down the key and press the key when the following is displayed: Press to enter the RAID BIOS Console After you press +, the Controller Selection screen appears. 2.
Table 16. Intel® RAID BIOS Console 2 Toolbar Icon Descriptions (Cont.) Icon Description Exit the Intel® RAID BIOS Console 2 utility. Silence the alarm.
8.2.2.2 Main Screen From the main screen, you can scan the devices connected to the controller, select an Intel® RAID controller, and switch between the Physical Drives view and Virtual Drives view. The main screen also provides access to the following screens and tools: • • • • • • • • Controller Selection • Exit Controller Properties Scan Devices Virtual Drives Drives Configuration Wizard Physical View Events Figure 59.
8.2.2.3 Controller Selection This option allows you to choose an Intel® RAID controller installed in the system. Figure 60. Intel® RAID BIOS Console 2 – Controller Selection 8.2.2.4 Controller Properties Screen When you select the Controller Selection option on the main screen, the Intel® RAID BIOS Console 2 utility displays a list of the Intel RAID controllers in the system. The Controller Properties screen allows you to view and configure the software and hardware of the selected controller.
8.2.2.4.1 • • • Sub Vendor ID: The sub-vendor ID (identification) for the RAID controller. • • Max Stripe Size: The maximum stripe size. Port Count: Number of ports available. Memory Size: The memory size of the installed DIMM (Dual In-Line Memory Module). Physical Disk Count: The number of physical disks connected to the RAID controller. Additional Controller Properties To access the screen that displays the additional controller properties, click Next on the Controller Properties screen.
Enter a number between 0 and 100 to control the rate at which virtual drives are initialized in the background. • CC Rate (Check Consistency Rate): A consistency check scans the consistency of data on a fault-tolerant disk to determine if the data is corrupted. Enter a number between 0 and 100 to control the rate at which a consistency check is done. • Reconstruction Rate: Enter a number between 0 and 100 to control the rate at which the reconstruction of a virtual drive occurs.
8.2.2.5 Scan Devices Option When you select the Scan Devices option on the Main screen, the Intel® RAID BIOS Console 2 checks the physical and virtual drives for any changes of the drive status. The Intel® RAID BIOS Console 2 displays the results of the scan in the physical and virtual drive descriptions. 8.2.2.6 Virtual Drives Screen You can access the virtual drives screen by clicking on a virtual drive in the virtual drive list on the main screen.
8.2.2.8 Configuration Wizard Option This option enables you to clear a configuration, create a new configuration, or add a configuration. “Setting Up a RAID Array Using the Configuration Wizard” on page 128 provides detailed steps for using the Configuration Wizard. 8.2.2.9 Events Screen This option displays the events generated by physical drives, physical devices, enclosure, the Intel® Smart Battery, and SAS controller.
Figure 63. Intel® RAID BIOS Console 2 – Configuration Types 2. Select New Configuration and click Next. 3. Then select Virtual Drive Configuration and click Next. Figure 64.
4. Choose the configuration method and click Next. Figure 65. Intel® RAID BIOS Console 2 – Configuration Methods The following configuration methods options are provided: — Automatic Configuration There are two options in Redundancy. Redundancy When Possible or No Redundancy. Redundancy When Possible configures configures RAID 1 for systems with two drives or RAID 5 for systems with three or more drives, or RAID 6 for systems with three or more drives.
8.4 Creating RAID 0, 1, 5, or 6 using Intel® RAID BIOS Console 2 (detailed) This section describes the process to set up RAID modes using the custom configuration options. 1. When the server boots, hold the key and press the key when the following is displayed: Press to enter RAID BIOS Console The Controller Selection screen appears. 2. Select a controller and click Start to begin the configuration. 3. Choose Manual Configuration and click Next (see Figure 65). 4.
8. On the VD Definition window, select RAID 0, 1, 5, or 6 from the first dropdown box. 9. Enter the virtual drive size in the Select Size box. This example shows a specific size. Depending on the RAID level you choose , you may need to manually type in the expected volume size. The possible sizes for some RAID levels are listed on right panel of the screen for reference. 10.
Figure 68. Intel® RAID BIOS Console 2 – Confirm Configuration 13. Click Accept as necessary in the screens that follow. You are prompted to save the configuration and then to initialize the virtual drive. 14. Click Yes to initialize the new drive. 15. Click Initialize to begin the initialization process. — Fast initialization runs a quick preliminary initialization and then runs full initialization in the background after the operating system is booted.
Figure 69. Intel® RAID BIOS Console 2 – Initialization Speed Setting 16. Click Home to return to the main configuration screen. 17. Select an additional virtual drive to configure or exit the Intel® RAID BIOS Console 2 configuration utility and reboot the system.
8.5 Creating RAID 10, RAID 50, and RAID 60 using Intel® RAID BIOS Console 2 RAID 10, RAID 50, and RAID 60 require setting up multiple RAID arrays/disk groups. 1. When the server boots, hold the key and press the key when the following is displayed: Press to enter the RAID BIOS Console After you press +, the Controller Selection screen appears. 2. Select a controller and click Start to begin the configuration. 3. Select Custom Configuration and click Next (see Figure 65). 4.
Figure 70. Intel® RAID BIOS Console 2 – Multiple Disk Groups for RAID 10, 50, or 60 7. Select all arrays or disk groups that are to be spanned in the RAID 10, 50, or 60 array by holding down the key and selecting each array/disk group in the right pane. 8. Click Next. 9. In the next screen, click Add to SPAN to move all arrays from the left pane to the right pane. Use to select all SPANs on the right pane. 10. Click Next. 11.
Figure 71. Intel® RAID BIOS Console 2 – Spanning Multiple Arrays 14. Click Next if the application does not automatically progress to the next screen. The configuration preview screen displays the virtual drive as shown below. The configuration preview screen displays the virtual drive (RAID 1 for RAID 10, or RAID 50 or RAID 60). Figure 72. Intel® RAID BIOS Console 2 – Viewing Completed Settings 15. Click Accept to save the configuration.
16. When asked to save the configuration, click Yes. This will store the configuration in the RAID controller. 17. When asked to initialize the drive, click Yes. 18. Select Fast Initialize and click Go. The drives will initialize based on the RAID settings. Note: Slow Initialize initializes the entire drive and may take several hours to complete. Figure 73. Intel® RAID BIOS Console 2 – Initialization Settings 19. Click Home at the Intel® RAID BIOS Console 2 screen to return to the main screen.
Figure 74. Intel® RAID BIOS Console 2 – RAID 10 Final Screen 20. Under Virtual Drives, select Virtual Drive 0: RAID 10, or select Virtual Drive 0: RAID 50, or select Virtual Drive 0: RAID 60 to display the drive properties. Figure 75.
Figure 76.
8.
— Cached IO: All reads are buffered in cache memory. — Direct IO: Reads are not buffered in cache memory. Data is transferred to cache and to the host concurrently. If the same data block is read again, it comes from cache memory. • Disk Cache Policy: The cache policy applies to the cache on physical drives of the current array. — Enable: Enable disk cache. Enabling the disk cache in Write-back mode provides little or no performance enhancement, while the risk of data loss due to power failure increases.
3. Click one of the following: — Click Make Dedicated HSP to add the drive as a hot spare dedicated for certain virtual drives. — Click Make Global HSP if you want to create a global hot spare for all disk groups. Figure 78. Intel® RAID BIOS Console 2 – Setting a Hot Spare Drive 4. Click Go to create the hot spare. The Drive State changes to HOTSPARE, as shown below.
Figure 79. Intel® RAID BIOS Console 2 – Viewing Hot Spare 5. Click Home to return to the main screen. Figure 80.
8.8 Viewing Event Details Events contain information, warnings, and fatal events. Events can be captured on various RAID controller components, such as the battery, physical card, and within the configuration. You can view these using the following steps. 1. On the Main screen, select Events from the menu at the left. The Events screen appears. Figure 81. Intel® RAID BIOS Console 2 – Event Information Screen 2. Select the component to display from the Event Locale list. 3.
Figure 82. Intel® RAID BIOS Console 2 – Selecting Events to View 5. Click Go. In the following example, virtual drive events for informational messages were selected, starting with the event at sequence 120. The events screen displays the event information for sequence number 120 in the right pane. Note: In the following example, the Start Sequence# and the # of Events fields display 0. This is because when you click Go to display the events, these fields automatically reset to 0.
Figure 83. Intel® RAID BIOS Console 2 – Viewing an Event 6. Click Next to view the next message.
9 Intel® RAID Web Console 2 The Intel® RAID Web Console 2 enables you to configure, monitor, and maintain Intel® RAID controllers and the storage-related devices connected to the RAID controller. The Intel® RAID Web Console 2 graphical user interface (GUI) makes it easy to create and manage storage configurations. Note: Depending on different version of Intel® RAID Web Console 2, the actual screen displayed could be different from this section. This section is for reference only. 9.
9.3 Maintenance Functions Use the Intel® RAID Web Console 2 to perform system maintenance tasks such as running patrol read operations, updating firmware, and running consistency checks on arrays and disk groups that support redundancy. 9.4 Hardware and Software Requirements The hardware requirements for Intel® RAID Web Console 2 software are as follows.
Figure 84. Intel® RAID Web Console 2 – Customer Information Screen 4. Enter your user name and organization name. At the bottom of the screen, select an installation option: — If you select All users, any user with administrative privileges can view or change the RAID configurations. — If you select Only for current user (Administrator), only you can view or change the RAID configurations. 5. Click Next to continue. 6.
Figure 85. Setup Type Screen 7. Select one of the following setup options. — Select Complete if you are installing the Intel® RAID Web Console 2 on a system. — Select Custom Installation if you want to select or omit individual program components to install. When selected, more custom options are provided. Please read the instructions on the screen carefully to make sure you select the preferred setup type. 8. Click Next to proceed and then click Finish to complete the installation process. 9.
9.7 Intel® RAID Web Console 2 Support and Installation on VMWare This section documents the installation of Intel® RAID Web Console 2 on VMWare Classic (with console operating system) and on the VMWare ESX 3i operating system. 9.7.1 Installing Intel® RAID Web Console 2 for VMWare Classic VMWare does not support any graphics components. In order to install the server component of Intel® RAID Web Console 2 (Intel® RAID Web Console 2 without popup and client), run the script file ServerInstall.
The Linux installer of Intel® RAID Web Console 2 works under console with minimal changes. Hardware RAID is currently supported in ESX 3.x. Note: There is a known limitation that virtual drives that are created or deleted will not be reflected to the kernel. The workaround is to reboot the server or to run esxcfg-rescan from COS shell. The network communication is a key element for a proper setup. Therefore, we recommend that you install the management on a VM within the ESXi.
Edit your file C.\windows\system32\drivers\etc\hosts and add another entry: IP of the ESXi Host 192.19.221.186 FQDN of the ESXi Host local.lsi.com 5. Final Steps: Reboot the VM and start the Intel® RAID Web Console 2. The ESXi server should now appear in the list of the found hosts. You can now log in with the root account name and password of the ESXi Host. 9.7.3.1 Limitations The following are the limitations of this installation and configuration: • • • • • 9.7.3.
Full functionality support is available for the VMware ESXi operating system, but it works differently than the normal Intel® RAID Web Console 2 framework mode. The event logging feature for the Intel® RAID Web Console 2 Client connected to a VMware ESXi system behaves as follows: — There is no support for retrieving initial logs (the events that occurred before a client logs in). Only those events that occur after a client logs in appear in the event logger dialog. — System log does not display.
7. This is supported only on a full installation of Intel® RAID Web Console 2; standalone, client-only, and server-only modes do not support VMWare ESX3i management. 8. Supported on following guest operating systems: — Windows Server 2003* and Windows Server 2008* — Linux RHEL 4 and 5 9. The following describes the status of components related to VMWare ESX3i: — Intel® RAID Web Console 2 client GUI is supported. — There is no support for Monitor Configurator; you cannot configure the severity of the AENs.
There is no password by default for the shell. If you have set any password from the "yellow" screen (DCUI), use that password. You are prompted (#) next. 2. Enable ssh for remote copy. a. Type the following command. vi /etc/inetd.conf b. Search for ssh in the file. By default, the line that contains ssh has comments. c. Remove the comment by deleting the symbol # in front of the line. d. Save the file and exit. 3. Restart the inetd daemon for the changes to take effect. a.
9.8 Starting the Intel® RAID Web Console 2 Complete the following steps to start the Intel® RAID Web Console 2 (Different Operating Systems may have slighlty different directories): 9.9 • Microsoft Windows*: Select Start | All Programs | RAID Web Console 2 | StartupUI, or double-click the Intel® RAID Web Console 2 icon on the desktop. • Red Hat* Enterprise Linux 3 U6: Select Start | System Tools | RAID Web Console 2 StartupUI.
Note: To access systems on a different subnet, type in the box in middle-left side of the screen the IP address of a system in the desired subnet where Intel® RAID Web Console 2 is running and click Discover Host. If you check the Connect to remote framework box, you can also access a standalone server running Intel® RAID Web Console 2, if it has a network connection.
root and appropriate password to log on to Intel® RAID Web Console 2. If you do not know the password, contact the server system administrator to obtain the password. Figure 88. Intel® RAID Web console 2 dashboard The information displayed on this Dashboard screen provides an overview of the RAID ecosystem on the selected server system. Some frequently used functions are listed in the Dashboard tab, such as Create Virtual Drive and so on.
Figure 89. Intel® RAID Web Console 2 – Main Screen The information on the screen in Figure 89 shows the connected devices such as RAID controllers, physical devices, battery and so on. The following subsections describe this screen in more detail. 9.9.1 LDAP Support The Intel® RAID Web Console 2 application supports the discovery of remote Intel® RAID Web Console 2 servers using LDAP. To enable LDAP support, the Intel® RAID Web Console 2 servers must be registered with the LDAP server. Note: 1.
To register the Intel® RAID Web Console 2 servers with the LDAP server, define a new attribute on the machine on which the LDAP server is configured, and give this attribute the value MSM. This registration enables the discovery of only the Intel® RAID Web Console 2 servers that have been registered with the LDAP server. To use LDAP support, follow these steps: 1. Double-click the Intel® RAID Web Console 2 software shortcut icon on your desktop. The Select Server dialog appears. 2.
1. Enter the IP address of the LDAP server in the LDAP Server IP Address field. 2. Enter the LDAP server's user name and password in the User Name and Password fields, respectively. An example of a user name can be username@testldap.com. 3. Enter the name of the Domain Controller in the Distinguished Name field. As an example, the Domain Controller name can be dc= TESTLDAP, dc=com.
Figure 91. Configure Host LDAP 2. Select the Use LDAP Login as default login mode check box to always connect to the LDAP server. 3. Select the Do not prompt for credentials when connecting to LDAP check box if you do not want the LDAP Login dialog to appear when connecting to the LDAP server. 4. Enter the IP address of the LDAP server in the IP Address field. 5. Enter the port number in the Port field. 6. Enter the name of the Domain Controller in the Distinguished Name field. 7.
9.9.3 Physical/Virtual View Panel Depending on the tab selected, the left panel displays either the Physical View or the Virtual View of the system and the devices in it. Note: The word ‘Virtual’ may be displayed as ‘Logical’ depending on different versions of the utility. • The Physical View shows the hierarchy of physical devices in the system. At the top of the hierarchy is the system itself. Controllers are installed in the system, and each controller has one or more ports.
Figure 92. Intel® RAID Web Console 2 – Operations Tab The Operations tab lists the operations that can be performed on the device selected in the left panel. This tab is available only when you are logged in to Intel® RAID Web Console 2 in Full-access mode. Options available for controllers include: enabling or silencing the alarm, flashing the firmware, and so on. Some types of devices, such as arrays, disk groups, and ports, do not have operations associated with them.
Figure 93. Intel® RAID Web Console 2 – Graphical Tab (Optional feature) 9.9.5 Event Log Panel The lower part of the screen displays the event log entries for the system. New event log entries display during the session. Each entry has a time and date stamp, an Error Level that indicates the severity of the event, and a brief description of the event. For information about the event log entries, see Appendix B: “Events and Messages” on page 315 9.9.
Other options may include: Server option to discover and enter other server system's RAID configuration; Check Consistency; Initialize to initialize a RAID; Show progress. 9.9.7 Menu Bar/Go To Menu The Go To menu has sub-menus like Controller, Drive Group, Physical Drive, Virtual Drive, BBU, and so on. Each of above sub-menu may have some or all items greyed out, unless controller, physical, virtual drive, drive group, BBU or other storage object is selected.
9.10.1 • • “Removing a Drive or Changing the RAID Level of a Virtual Disk” on page 191 • • • “Changing Virtual Disk Properties” on page 193 “A Reconstruct operation begins on the virtual disk. You can monitor the progress of the reconstruction in the Group Show Progress window. Select Manage -> Show Progress.” on page 193 “Deleting a Virtual Disk” on page 194 “Managing Configurations” on page 195 Create Virtual Drive Use the Create Virtual Drive to create disk groups and virtual disks.
Figure 94. Virtual Drive Creation Menu The dialog box for the configuration mode (simple or advanced) appears, as shown in Figure 95.
Figure 95. Virtual Drive Creation Mode 2. Click Simple and press Next. The Create Virtual Drive screen appears, as shown in Figure 96.
Figure 96. Create Virtual Drive Screen 3. Select the RAID level desired for the virtual drive. When you use simple configuration, the RAID controller supports RAID levels 1, 5, and 6. In addition, it supports independent drives (configured as RAID 0). The screen text gives a brief description of the RAID level you select. The RAID levels you can choose depend on the number of drives available. To learn more about RAID levels, see Chapter-2 “RAID Levels” on page 9 4.
The Create Virtual Drive - Summary window appears, as shown in Figure 97. This window shows the selections you made for simple configuration. Figure 97. Create Virtual Drive – Summary Window 8. Click Back to return to the previous screen to change any selections or click Finish to accept and complete the configuration. The new storage configuration will be created and initialized.
Figure 99. Option to Close the Configuration Wizard If you select Yes, the configuration procedure closes. If you select No, the dialog box closes and you remain on the same page. 9.12 Creating a Virtual Drive Using Advanced Configuration The advanced configuration procedure provides an easy way to create a new storage configuration.
Figure 100. Virtual Drive Creation Menu The dialog box shown in Figure 101 appears.
Figure 101. Virtual Drive Creation Mode 2. Click Advanced and press Next. The Create Drive Group Settings screen appears, as shown in Figure 102.
Figure 102. Create Drive Group Settings Screen 3. Select the following items on the Create Drive Group Settings screen: a. Select the RAID level desired for the drive group from the drop-down menu. To make a spanned drive, select RAID 10, RAID 50, or RAID 60 in the RAID level field. Drive Group 0 and Span 0 appear in the Drive groups field when you select RAID 10, 50, or 60. The RAID controller supports RAID levels 1, 5, 6, 10, 50, and 60.
Figure 103. Span 0 of Drive Group 0 c. Click Create Span to create a second span in the drive group. d. Select unconfigured drives from the list of drives and click Add> to add them to the drive group. e.
Figure 104. Span 0 and Span 1 of Drive Group 0 f. Click Create Drive Group to make a drive group with the spans. g. Click Next to complete this step. The Virtual drive settings window appears, as shown in Figure 105. The drive group and the default virtual drive settings appear. The options to update the virtual drive or remove the virtual drive are grayed out until you create the virtual drive.
Figure 105. Virtual Drive Settings Window 4. Change any virtual drive settings, if desired. 5. Click Create Virtual Drive. The new virtual drive appears under the drive group, as shown in Figure 106. The options Update Virtual Drive and Remove Virtual Drive are now available. Update Virtual Drive allows you to change the virtual drive settings and Remove Virtual Drive allows you to delete the virtual drive.
Figure 106. New Virtual Drive 0 6. Click Next. The Create Virtual Drive - Summary window appears, as shown in Figure 107. This window shows the selections you made for advanced configuration. Figure 107. Create Virtual Drive Summary Window 7. Click Back to return to the previous screen to change any selections or click Finish to accept and complete the configuration. The new storage configuration will be created and initialized.
Note: If you create a large configuration using drives that are in powersave mode, it could take several minutes to spin up the drives. A progress bar appears as the drives spin up. If any of the selected unconfigured drives fail to spin up, a box appears to identify the drive or drives. 8. After the configuration is completed, a dialog box may or may not notify (depending on different utility version) you that the virtual drives were created successfully, as shown in Figure 108.
9.13 Creating a Spanned Disk Group Spanning allows you to configure multiple arrays as a single virtual disk. Spanned arrays provide additional levels of data redundancy and storage capacity.
9.14 Creating Hot Spares Hot spares are disk drives that are available to automatically replace failed drives in a virtual disk. There are two kinds of hot spares: 1) dedicated hot spares, which are available to one or more specified arrays or disk groups, and 2) global hot spares, which are available to any array or disk group defined on the controller. To create a global hot spare, follow these steps: 1.
You normally create a dedicated hot spare when you create a new configuration with the Manual Configuration option. To add a dedicated hot spare to an existing array or disk group, follow these steps: 1. In the left panel of the Intel® RAID Web Console 2 window, click the icon of a disk drive that is not assigned to a storage configuration. If it is assigned to a storage configuration, a check mark is displayed on the disk drive icon. 2.
Figure 112. Select Hotspare Drive 4. Click OK to create the dedicated hot spare. 9.15 Setting Adjustable Task Rates To change the Rebuild rate and other task rates for a controller, you must first log onto the system in All Access mode (versus View-Only mode). Complete the following steps to set the adjustable task rates: 1. Select a controller icon in the left panel, and select the Physical View tab. 2. In the Menu, select the Go To -> Controller tab and select Set Adjustable Task Rates.
Figure 113. Set Adjustable Task Rates 3. Enter changes as needed to any of the task rates: — Rebuild Rate. Enter a number from 0 to 100 to control the rate at which a rebuild is performed on a disk drive when one is necessary. The higher the number, the faster the rebuild will occur. However, if a higher number is selected, the system I/O rate may be slower. — Patrol Rate. Enter a number from 0 to 100 to control the rate at which patrol reads are performed.
— Background Initialization (BGI) Rate. Enter a number from 0 to 100 to control the rate at which virtual disks are initialized in the background. Background initialization makes the virtual disk immediately available for use, even while the initialization is occurring. The higher the number, the faster the initialization occurs. However, if a higher number is selected, the system I/O rate may be slower. — Check Consistency Rate.
Figure 114. Starting Modify Drive Group The Modify Drive Group window is displayed, as shown in Figure 115. Figure 115. Select RAID level to migrate 2. Click Add Drive.
Note: Depending on current RAID level, the targeted migrated RAID level and the available Unconfigured Good drive numbers, pop-up window may appear to allow selection among Add drives, Remove drives, and Migrate RAID level. The following screen appears: Figure 116. Selecting Drives to Add 3. In the panel, check the disk drives that you want to add to the virtual disk. 4. When you are finished adding disk drives, click Next.
Figure 117. Changing RAID Level 5. When everything is acceptable, click Finish to accept the new configuration. A Reconstruct operation begins on the virtual disk. You can monitor the progress of the reconstruction in the Group Show Progress window. Select Manage -> Show Progress. 9.17 Removing a Drive or Changing the RAID Level of a Virtual Disk You can use Intel® RAID Web Console 2 to remove a physical disk drive from a virtual disk.
Figure 118. Selecting Drives to Remove 3. In the panel, check the disk drives that you want to remove from the virtual disk. 4. When you are finished removing disk drives, click Next. The next screen displays, which allows you to review the summary and go back if you need to make corrections as shown in Figure 119.
Figure 119. Changing RAID Level 5. When everything is acceptable, click Finish to accept the new configuration. A Reconstruct operation begins on the virtual disk. You can monitor the progress of the reconstruction in the Group Show Progress window. Select Manage -> Show Progress. 9.18 Changing Virtual Disk Properties You can change a virtual disk’s Read Policy, Write Policy, and other properties after the disk is created. To do this, follow these steps: 1.
Figure 120. Set Virtual Disk Properties 2. As needed, change the properties in the pop-up window. 3. Click OK to accept the changes. 9.19 Deleting a Virtual Disk Warning: Before you delete a virtual disk, back up the data on it. You can delete one or more virtual disks. Before you can do this, you must be logged on to the system in All Access mode. To delete a virtual disk, follow these steps: 1. Back up all user data on the virtual disk you intend to delete. 2.
9.20 Managing Configurations You can use Intel® RAID Web Console 2 to manage the configurations that you create. For example, you can save a storage configuration that you have defined on a controller and load this configuration from the disk to another controller, after first clearing the existing configuration from that controller. In order to do this, you must be logged on to the system in All Access mode. This section explains how to do these tasks. 9.20.
The Save dialog box displays as shown in Figure 122. Figure 122. Save Configuration Dialog Box 3. In the dialog box, type a name for the configuration file. 4. Click Save to save the configuration file, or accept the default name: hostname.
9.20.2 Clearing a Configuration from a Controller If you want to manually create a new storage configuration on a controller, or load a configuration file on a controller, you must first clear the existing configuration. Warning: Before you clear a configuration, make sure to save any data you want to keep! Clearing a configuration deletes all data from the disks in the existing configuration. To clear a configuration from a controller, follow these steps: 1.
9.20.3 Adding a Configuration from a File When you replace a controller or when you want to duplicate an existing storage configuration on a new controller, you can add a saved configuration to the controller. Warning: When you add a saved configuration to a replacement controller, make sure that the number and size of the physical disks connected to the controller is exactly the same as it was when the configuration was saved. To add a saved configuration, follow these steps: 1.
9.21 Monitoring System Events and Devices The Intel® RAID Web Console 2 enables you to monitor the status of disk drives, virtual disks, enclosures, and other devices. You can monitor the following: 9.21.
Figure 125. Event Information Window Each event in the log includes an error level—Information, Warning, Critical, Fatal, or Dead—a date/time stamp, and a brief description. (For a list of all events, see Appendix B: “Events and Messages” on page 315) The status bar at the bottom of the screen indicates whether the log is a system log (as in Figure 125) or a log from a locally stored file. (This file could have been generated by a previous “Save Log” action.
When a system log displays, the Log menu has four options: • • • Save Log: Saves the current log to a .log file. • Load: Enables you to load a local .log file. Save as Text: Saves the current text to a .txt file. Clear: Clears the current log information, if you have full access (versus View-only access). When a local log is displayed, the status bar lists the name of the local log file, and the Log menu has an additional option, Rollback to Current Log, which enables you to retrieve the system log.
9.21.3 • The Rebuild rate, Patrol read rate, Reconstruction rate, Consistency check rate, and BGI rate (background initialization) are all user-selectable. For more information, see “Setting Adjustable Task Rates” on page 186. • • The BBU Present field indicates whether a battery backup unit is installed. The Alarm Present and Alarm Enabled fields indicate whether the controller has an alarm to alert the user with an audible tone when there is an error or problem on the controller.
If the physical drives are in a disk enclosure, you can identify which physical drive is represented by a disk icon on the left. To do this, follow these steps: 1. Click the physical disk icon in the left panel. 2. Click the Go To -> Physical Drive tab. 3. Click Start Locating Drive (see Figure 128). Figure 128. Locating a Physical Drive The LED on the physical disk drive in the enclosure starts blinking to show its location. Note: LEDs on global or dedicated hot-spare drives do not blink. 4.
9.21.3.1 Running a Patrol Read A Patrol Read periodically verifies all sectors of physical disks that are connected to a controller, including the system reserved area in the RAID configured drives. Patrol Read works for all RAID levels and for all hot-spare drives. A patrol read is initiated only when the controller is idle for a defined period and has no other background activities. To enable and configure Patrol Read, follow these steps: 1. Click a controller icon in the left panel. 2.
7. If Run Patrol Read non-stop check box is selected, Patrol Read will run continuously. 8. Click OK to enable these Patrol Read options. 9.21.4 Monitoring Virtual Disks When the Intel® RAID Web Console 2 is running, you can see the status of all virtual disks. If a virtual disk is operating normally, the icon looks like this: . If the virtual disk is running in degraded mode—for example, if a physical disk has failed—a small yellow circle is displayed to the right of the icon, which looks like this: .
9.21.5 Monitoring Enclosures When the Intel® RAID Web Console 2 is running, you can see the status of all enclosures that are operating normally. Information about the enclosure is displayed in the right panel. Figure 131 shows it. Figure 131. Enclosure Information The display in the Dashboard tab also includes enclosure information in the Properties part. 9.21.
Figure 132. Battery Backup Unit Information The BBU properties include the following: 9.21.
9.21.7.1 Setting Learn Cycle Properties To set the learn cycle properties, perform the following steps: 1. Click the Physical tab to open the physical view. 2. Select the BBU icon in the left panel. 3. Click the Go To -> BBU tab. The BBU operations appear, as shown in Figure 133 (Depending on different utility version, the BBU operation also may appear in a new pop-up window). Figure 133. Battery Backup Unit Operations 4. Select Set Learn Cycle Properties. The options appear in the right frame. 5.
9.21.7.2 Starting a Learn Cycle Manually To start the learn cycle properties manually, perform the following steps: 1. Click the Physical tab to open the physical view. 2. Select the BBU icon in the left panel. 3. Click the Go To -> BBU tab. The BBU operations appear, as shown in Figure 133 (Depending on different utility version, the BBU operation also may appear in a new pop-up window). 4. Click Start Learn Cycle and click OK.
• • Reconstruction (see “Adding a Drive to a Virtual Disk” on page 188). Consistency check (see “Running a Consistency Check” on page 212). Note: A Reconstruction process cannot be aborted. To abort any other ongoing process, click Abort next to the status indicator. Click Abort All to abort all ongoing processes. Click Close to close the window.
9.22 Maintaining and Managing Storage Configurations This section explains how to use Intel® RAID Web Console 2 to maintain and manage storage configurations. You must log on to the system in Full Access mode to complete these maintenance and management tasks. This following maintenance and management functions can be done: • • • • • 9.22.
Figure 135. Selecting Initialize The Group Initialize dialog box is displayed. 3. Select the virtual disk(s) to initialize. If you want to use this option, select Fast Initialization. Fast Initialization quickly formats the virtual disk by writing zeros to the first few sectors of the physical disks in the virtual disk. Depending on the number and size of the physical disks in the virtual disk, regular initialization takes longer. 4. Click Start to begin the initialization.
Figure 136. Group Consistency Check Window 2. Select the virtual disks you want to check, or click Select All to select all disks. 3. Click Start to begin. You can monitor the progress of the consistency check. For more information, see “Monitoring Rebuilds and Other Processes” on page 209. Note: You can also run a consistency check by selecting the virtual disk icon in the left panel and right-click the option Start Consistency Check.
9.22.3 Scanning for New Drives The Intel® RAID Web Console 2 normally detects newly installed disk drives and other storage devices and displays icons for them on the main screen. If the Intel® RAID Web Console 2 does not detect a new drive, you can use the Scan for Foreign Configuration option to find it. To do this, follow these steps: 1. Select a controller icon in the left panel. 2. Select Go To -> Controller -> Scan Foreign Configuration. Figure 137.
If you need to rebuild a physical drive, follow these steps: 1. Right click the icon of the failed drive and select Rebuild. 2. When the warning message displays, click Yes. If the drive is still good, a rebuild starts. You can monitor the progress of the rebuild in the Group Show Progress window by selecting Go To -> Show Progress. If the drive cannot be rebuilt, an error message is displayed, and you must replace the drive before a rebuild can occur. Continue with the next step. 3.
9.22.5 Removing a Drive You may sometimes need to remove a non-failed drive that is connected to the controller. For example, you may need to replace the drive with a larger drive. Follow these steps to remove a drive safely: 1. Click the icon of the drive in the left panel and right-click it. 2. Select Make Drive Offline. 3. Right-click again and select Mark Drive as Missing. 4. Right-click again and select Prepare for Removal. This will change drive status to Ready to Remove 5.
This feature enables authentication key management for data security protection for Self Encrypting Drives (SED), auto-lock, and instant erase of self-encrypting drives. • It transparently auto-locks Volumes; Volumes are automatically locked when powered down. • It provides secure data when a drive is misplaced, failed, experiencing drive theft, experiencing Server theft “Smash and Grab”. • It provides Instant Secure Erase: Before returning leased Drives; Before redeploying with the datacenter.
Figure 139. Check Controller Security status 2. Select the physical drive and choose Physical tab in the left panel of Intel® RAID Web Console 2. Check Drive Security Properties in the right panel to see whether the RAID controller is Full Disk Encryption capable.
Figure 140. Check Drive Security status 3. Right-click on the controller and select Enable Drive Security.
Figure 141. Enable Drive Security 4. In the Security Wizard, click Next.
Figure 142. Start Security Wizard 5. Create the required Security key Identifier. Use the default suggestion, or create your own, then click Next.
Figure 143. Enter Security Key Identifier 6. Create the required Security key. Use the default suggestion, or create your own, then click Next.
Figure 144. Enter Security Key 7. Create an optional Pass Phrase for additional security, then click Next.
Figure 145. Enter Pass Phrase 8. Accept the confirmation to complete the wizard and enable drive security, then click Finish.
Figure 146. Confirm Enable Drive Security 9. Controller properties now indicate Drive security enabled is Yes.
Figure 147. Check Drive Security Enabled status 10. Select Unconfigured Good drives and select Drive security method, here FDE to create the virtual drive.
Figure 148. Select Full Disk Encryption 11. Follow same steps for creating a RAID virtual drive. After a virtual drive is created, Selecting this virtual drive in left panel shows its secured status and Drive security method status in the Drive Security Properties part in the right panel. Log information at the bottom of the window also indicates the virtual drive security status. Full Disk Encryption feature has now been enabled.
Figure 149. Create RAID Virtual Drive with FDE enabled 12. (Optional) For Self-Encrypting Drives (SEDs) that need to have their data permanently erased for security reason, follow normal steps to delete the secured RAID virtual drive, and mark all SEDs as Unconfigured Good physical drives. Then select one SED, right-click it and select Instant Erase.
Figure 150. Instant Secure Erase 13. Accept confirmation to permanently erase disk drive.
Figure 151. Confirm Secure Erase 9.23.2 Enabling Snapshot feature This feature is supported by Intel® RAID RAID controller with Intel® RAID Premium Feature Key AXXRPFKSNSH or AXXRPFKSNSH2 installed. Refer to Intel® RAID Premium Feature Key AXXRPFKSSD, AXXRPFKDE, and AXXRPFKSNSH Installation Guide (E88588-00x), or Intel® RAID Premium Feature Keys AXXRPFKSSD2, AXXRPFKDE2, and AXXRPFKSNSH2 Installation Guide (G29824-00x) for physical installation of the Premium Feature Key.
Recovers lost data from disk in minutes, minimizing the downtime experienced by users and eliminating the lengthy process of restoring data from tape. Allows isolation of a server’s boot volume to a separate virtual drive; by enabling the Auto Snapshot feature, users are guaranteed that bootable snapshots exist, in case corruption of operating system occurs. Note: MegaRAID Recovery Snapshots are not a substitute for a tested backup strategy.
Figure 153. Enter the Capacity for Snapshot Respository 5. Choose whether to have a snapshot taken on reboot. To enable this option, check the box next to the Take snapshot on reboot field. If you select this option, a snapshot is taken on boot after every successful shutdown. You can use this snapshot of the boot virtual drive to restore the operating system on the virtual drive in case the virtual drive becomes corrupted.
Figure 154. Confirm Enable Snapshot 8. This virtual drive becomes a snapshot repository. Use it only for storing snapshotrelated data. Caution: After you enable snapshots on this virtual drive, you cannot change the allocated percentage of capacity or the snapshot repository without first disabling snapshots and losing any snapshot data.
Figure 155. Snapshot Base is shown 9. Following steps create Snapshots and Views, based on above configurations for Snapshot Base and Snapshot Repository. Note: You can create up to eight snapshots of a volume. snapshots are showed in chronological order from the oldest to the newest. Each snapshot is a PiT snapshot of the virtual drive that is the Snapshot Base. The snapshots appear on the timeline from the oldest on the left to the newest on the right.
Figure 156. Enter Snapshot Name 11. Enter the snapshot name in the Enter snapshot name field. Click Create Snapshot. 12. Repeat above step so that additional snapshots can be created. The snapshot you create appears in the snapshot timeline. The oldest snapshot is on the left end of the timeline. Figure 157. Create Snapshot 13. (Assuming you experience a file deletion or corruption, following steps create MegaRAID Recovery Views based on snapshots created previously, and can roll back snapshots.
frame (This screen shows the Snapshot Base details and any existing snapshots). Click Create View. Figure 158. Create View 14. Enter the name of the view in the Enter View name field and the capacity to set aside in the snapshot. Click OK. Note: The “View name” can be found in the snapshots screen view in the View Details information box after a snapshot has been created 15. Enter into “My computer”, and then you can see a new drive. 16. Copy the files in the new drive to the original drive and cover them.
20. Follow these steps to Set MegaRAID Recovery Properties: Click the Logical view on the main menu screen; Click the Snapshot Base virtual drive in the left frame; Click Go To -> Virtual Drive -> Set MegaRAID Recovery Properties on the menu bar; Check the box to the properties selections you desire and click OK. Figure 159. Set MegaRAID Recovery Properties 21.
Figure 160. Disable MegaRAID Recovery 22. A confirmation dialog box appears. It warns that any snapshot-related data that is on the associated Snapshot Repository virtual drives will be lost if you disable snapshots; Check the box next to the Confirm field and click Yes. The snapshots are disabled. Figure 161. Confirm Disable Snapshots 23. After snapshots are successfully created (in step 12, Figure 157), following steps roll back to a snapshot at a previous Point in Time (PiT).
Figure 162. Adapter Selection 25. In the home page, from the Logical View in the right panel, click the Snapshot Base which has the operating system installed. Figure 163. Selecting Snapshot Base 26. In the new screen, select Adv Opers (which means Advanced Operations), and click Go.
Figure 164. Selecting Advanced Operations 27. In the Advanced Operations screen, select Rollback.
Figure 165. Selecting Rollback 28. From the drop-down menu, select a previous created snapshot, and then click Go.
Figure 166. Selecting a snapshot 29. A Confirm Page should appear. Please read carefully the warning message. “You have chosen to restore a previous snapshot time line. Doing so will rollback to the snapshot to its state at the date and time you selected. You may lose any changes you have made subsequent to that date and time. Are you sure you want to restore snapshot
Figure 168. Rollback operation is done 9.23.3 Enabling Super Sized Cache This feature is supported by Intel® RAID Premium Feature Key AXXRPFKSSD or AXXRPFKSSD2 installed. Refer to Intel® RAID Premium Feature Key AXXRPFKSSD, AXXRPFKDE, and AXXRPFKSNSH Installation Guide (E88588-00x), or Intel® RAID Premium Feature Keys AXXRPFKSSD2, AXXRPFKDE2, and AXXRPFKSNSH2 Installation Guide (G29824-00x) for physical installation of the Premium Feature Key.
Figure 169. Create SSC from Dashboard 2. The Create Super Sized Cache Drive group screen appears. Select the unconfigured SSD drive. Click Add > -> Create SSC Drive Group -> Next. Figure 170.
3. The Create Super Sized Cache Drive screen appears. Click Create to create a SSC drive group. Click Next. Figure 171. Create SSCD name 4. Create Super Sized Cache screen appears. Click Finish to confirm the information and create the Super Sized Cache Disk (SSCD).
Figure 172. SSC Summary 5. You can see Super Sized Cache Drive Group in the logical view. Figure 173. SSCD status shown 6. Following steps delete a Super Sized Cache disk: Click the Logical view tab on the main menu screen; Click the SSCD virtual drive in the left frame; Click Go To -> Virtual Drive -> Delete Virtual Drive on the menu bar.
Figure 174. Delete SSCD 7. A confirmation dialog box appears. Check the box next to the Confirm field and click Yes. The SSCD is deleted.
10 StorCLI 10.1 Overview The Storage Command Line Tool (StorCLI) is the command line management software designed for the Intel® RAID Controller product line. The StorCLI is a command line interface that is designed to be easy to use, consistent, and easy to script. This chapter provides information on installing and using the StorCLI and explains the various features of the StorCLI. Note: The legacy commands are deprecated from this guide. 10.
• • • • • • • VMware* ESX 4.1 U2 VMware* ESXi 4.1 U2 VMware* ESXi 5.0 U1 Solaris* FreeBSD (32/64 bit) EFI Ubuntu* Note: The LSISAS2208 and LSISAS2108 controllers provide support for Microsoft Windows 8 and Microsoft Windows Server 2012 operating systems. 10.3.1 Installing StorCLI on Microsoft Windows Operating Systems The Windows StorCLI binary is provided in a binary format, and no separate installation is required. 1. Copy the binary file from the CD or from the Intel website. 2.
3. To uninstall the debian package, run the command sudo dpkg –r storcli. 10.3.4 Installing StorCLI on VMware Operating Systems To install StorCLI on VMware operating systems, run the following syntax from the command line: esxcli software vib install –v= Example: esxcli software vib install v=/vmfs/volumes/datastore1/StorCliMN/vmware-esx-StorCli1.01.04.vib 10.3.
10.4 StorCLI Command Syntax This chapter describes the StorCLI command syntax and the valid values for each parameter in the general command syntax. Note: To get the output in JSON format, add J at the end of the command syntax. Example: storcli /cx show | J Note: JSON format output is not supported in the EFI operating system. The EFI platform ignores the J when it is added at the end of the command syntax.
Object Identifier Description /cx/pall This object identifier is for all PHY operations on controller x. /cx/bbu This object identifier is for a bbu x on controller x. /cx/cv This object identifier is for a cache vault x on controller x. Note: If enclosures are not used to connect physical drives to the controller, you do not specify the enclosure ID in the command. The StorCLI tool supports the following verbs. Table 18.
• <[adverb | attributes | properties] > – Specifies what the verb modifies or displays. • 10.5 <[key=value]> – Specifies a value, if a value is required by the command. Working with the Storage Command Line Tool This section describes the commands supported by the Storage Command Line Tool. Note: The Storage Command Line Tool is not case sensitive. Caution: The order in which you specify the command options must be the same as in the User Guide; otherwise, the command will fail.
storcli -v This command shows the version of the Storage Command Line Tool. 10.5.2 Controller Commands Controller commands provide information and perform actions related to the specified controller, such as the /c0 controller. The Storage Command Line Tool supports the controller commands described in this section. 10.5.2.1 Show and Set Controller Properties Commands Table 19. Controller Commands Quick Reference Table Command Value Range Description show See Table 20.
storcli storcli storcli storcli storcli storcli storcli storcli storcli storcli storcli storcli storcli storcli storcli storcli storcli storcli storcli storcli storcli storcli storcli storcli storcli storcli storcli storcli storcli storcli storcli storcli storcli storcli storcli storcli storcli storcli storcli storcli 255 /cx /cx /cx /cx /cx /cx /cx /cx /cx /cx /cx /cx /cx /cx /cx /cx /cx /cx /cx /cx /cx /cx /cx /cx /cx /cx /cx /cx /cx /cx /cx /cx /cx /cx /cx /cx /cx /cx /cx /cx show show show show show
storcli /cx set = General example output: Status Code = 0 Status = Success Description = None Controller 0, new Property_name = Property_value The following commands are examples of the properties that can be set using the storcli /cx set = command: storcli /cx set abortcconerror= storcli /cx set termlog[=on|off|offthisboot] storcli /cx set activityforlocate= storcli /cx set alarm= storcli /cx set backplane= storcli /cx set battery
storcli storcli storcli storcli storcli storcli storcli storcli /cx /cx /cx /cx /cx /cx /cx /cx set set set set set set set set restorehotspare= smartpollinterval= spinupdelay= spinupdrivecount= stoponerror= usefdeonlyencrypt= time=yyyymmdd hh:mm:ss|systemtime usefdeonlyencrypt= The following table lists and describes the properties for the show and set commands. Table 20.
Property Name copyback Set Command Range on|off type = smartssd|smarthdd|all Description Enables/disables copy back for drive types. smartssd: Copy back enabled for SSD drives. smarthdd: Copy back enabled for HDD drives. all: Copy back enabled for both ssd drives and HDD drives. Example: storcli /cx set copyback=on type=all directpdmapping on|off Enables/disables direct physical drive mapping. When enclosures are used, this feature is disabled; otherwise it should be enabled.
Property Name Set Command Range Description loadbalancemode on|off Enables/disables automatic load balancing between SAS phys or ports in a wide port configuration. maintainpdfailhistory on|off Maintains the physical drive fail history. migraterate 0 to 100 Sets data migration rate in percentage. patrolread|pr See “Patrol Read” on page 261. See “Patrol Read” on page 261.
Property Name usefdeonlyencrypt 10.5.2.2 Set Command Range on|off Description Enables/disables FDE drivebased encryption. Controller Show Commands The Storage Command Line Tool supports the following show commands: storcli /cx show storcli /cx show all storcli /cx show freespace The detailed description for each command follows. storcli /cx show This command shows the summary of the controller information.
10.5.2.3 Controller Background Tasks Operation Commands 10.5.2.3.1 Rebuild Rate storcli /cx set rebuildrate= storcli /cx show rebuildrate The detailed description for each command follows. storcli /cx set rebuildrate= This command sets the rebuild task rate of the specified controller. The input value is in percentage. Input example: storcli /c0 set rebuildrate=30 Note: A high rebuild rate slows down I/O processing.
storcli /cx set patrolread {=on mode=}|{off} This command turns the patrol read scheduling on and sets the mode of the patrol read to automatic or manual. Input example: storcli /c0 set patrolread=on mode=manual storcli /cx set patrolread [starttime=] [maxconcurrentpd=] [includessds=] [uncfgareas=on|off] This command schedules a patrol read operation. You can use the following options for patrol read command. Table 21.
storcli /cx start patrolread This command starts the patrol read operation. This command starts a patrol read immediately. Input example: storcli /c0 start patrolread storcli /cx stop patrolread This command stops a running patrol read operation. Input example: storcli /c0 stop patrolread Note: You cannot resume a stopped patrol read. storcli /cx suspend patrolread This command pauses a running patrol read operation.
Option delay Value Range -1 and any integer value. Description Delays a scheduled consistency check. The value is in hours. A value of 0 makes the CC runs continuously with no delay (in a loop). Note: Only scheduled consistency checks can be delayed. starttime A valid date and hour in 24-hour format. Start time of a consistency check is in yyyy/mm/dd hh format. excludevd The range should be less than the number of virtual drives. Excludes virtual drives from the consistency checks.
storcli /cx set advancedsoftwareoptions(aso) key= [preview] This command activates advanced software options (ASO) for a controller. You can use the following options with the advanced software options command. Table 23. Set Advanced Software Options Input Options Option Value Range Description 40 alpha numeric characters. Key to activate ASO on the controller. deactivatetrialkey — Deactivates the trial key applied on the specified controller.
storcli /cx compare securitykey=ssssss This command compares and verifies the security key of the controller. storcli /cx delete securitykey This command deletes the security key of the controller. Input example: storcli /c0 delete securitykey storcli /cx set securitykey keyId=kkkk This command sets the key ID for the controller. The key ID is unique for every controller. storcli /cx set securitykey=sssss [passphrase=sssss][keyid=sssss] This command sets the security key for the controller.
10.5.2.6 Flashing Controller Firmware Command Note: The Flashing Controller Firmware command is not supported in Embedded Intel® RAID. The following command flash the controller firmware: storcli /cx download file=filepath [fwtype=] [nosigchk] [noverchk] [resetnow] This command flashes the firmware to the specified adapter from the given file location (filepath is the absolute file path). You can use the following options when you flash the firmware. Table 25.
10.5.3 Drive Commands This section describes the drive commands, which provide information and perform actions related to physical drives. The following table describes frequently used virtual drive commands. Table 26. Physical Drives Commands Quick Reference Table Command set Value Range missing: Sets the drive status as missing. Description Sets physical drive properties. good: Sets the drive status to unconfigured good. offline: Sets the drive status to offline.
storcli /cx[/ex]/sx|sall show all This command shows all information of a physical drive for the specified slot in the controller. If you use the all option, the command shows information for all slots on the controller. x stands for a number, a list of numbers, a range of numbers, or all numbers. Input examples: storcli /c0/e3/s0-3 show all storcli /c0/e35/sall show all Note: The storcli /cx/sx show all command shows tape drives information. 10.5.3.
10.5.3.3 Set Drive State Commands The Storage Command Line Tool supports the following commands to set the status of physical drives: storcli storcli storcli storcli storcli storcli /cx[/ex]/sx /cx[/ex]/sx /cx[/ex]/sx /cx[/ex]/sx /cx[/ex]/sx /cx[/ex]/sx set set set set set set jbod good [force] offline online missing bootdrive= The detailed description for each command follows. storcli /cx[/ex]/sx set jbod This command sets the drive state to JBOD.
Input example: storcli /c1/e56/s3 set bootmode=on 10.5.3.4 Drive Initialization Commands When you initialize drives, all the data from the drives is cleared. The Storage Command Line Tool supports the following commands to initialize drives: storcli /cx[/ex]/sx show initialization storcli /cx[/ex]/sx start initialization storcli /cx[/ex]/sx stop initialization The detailed description for each command follows.
10.5.3.6 Locate Drives Commands The Storage Command Line Tool supports the following commands to locate a drive and activate the physical disk activity LED: storcli /cx[/ex]/sx start locate storcli /cx[/ex]/sx stop locate The detailed description for each command follows. storcli /cx[/ex]/sx start locate This command locates a drive and activates the drive’s LED.
10.5.3.8 Drive Security Command The Storage Command Line Tool supports the following drive security command: storcli /cx[/ex]/sx show securitykey keyid storcli /cx[/ex]/sx show securitykey keyid This command shows the security key for secured physical drives. Input example: storcli /c0/e252/s1 show SecurityKey keyid 10.5.3.
Table 27. Drive Erase Command Options Option Value Range simple: Single pass, single pattern write erase Description Secure erase type. normal: Three pass, three pattern write thorough: Nine pass, repeats the normal write three times erasepatternA 8-bit value Erase pattern A to overwrite the data. erasepatternB 8-bit value Erase pattern B to overwrite the data. Input example: storcli /c0/e25/s1 start erase thorough erasepatternA=10010011 erasepatternB=11110000 10.5.3.
storcli /cx[/ex]/sx show rebuild This command shows the progress of the rebuild process in percentage. Input example: storcli /c0/s5 show rebuild storcli /cx[/ex]/sx start rebuild This command starts a rebuild operation for a drive. Input example: storcli /c0/s4 start rebuild storcli /cx[/ex]/sx stop rebuild This command stops a rebuild operation. You can run this command only for a drive that is currently rebuilt. Input example: storcli /c0/s4 stop rebuild 10.5.3.
Input example: storcli /c0/e25/s4 resume copyback storcli /cx[/ex]/sx show copyback This command shows the progress of the copyback operation in percentage. Input example: storcli /c0/e25/s4 show copyback storcli /cx[/ex]/sx start copyback target=eid:sid This command starts a copyback operation for a drive. Input example: storcli /c0/e25/s4 start copyback target=25:8 storcli /cx[/ex]/sx stop copyback This command stops a copyback operation.
Option Value Range Valid enclosure number enclaffinity Description Specifies the enclosure with which the hot spare is associated. If this option is specified, affinity is set; if it is not specified, there is no affinity. Affinity cannot be removed after it is set for a hot spare drive. nonrevertible — Sets the drive as a nonrevertible hot spare. Input example: storcli /c0/e3/s4,5 add hotsparedrive This command sets the drives /c0/e3/s4,5 as Global Hot spare.
10.5.4.1 Add Virtual Drives Commands The Storage Command Line Tool supports the following commands to add virtual drives: storcli /cx add vd type=raid[0|1|5|6|00|10|50|60][Size=,,..|all] [name=,..
Option Value Range Description name 15 characters of length Specifies the drive name for each virtual drive. drives Valid enclosure number and valid slot numbers for the enclosure In e:s|e:s-x|e:s-x,y: e specifies the enclosure ID. s represents the slot in the enclosure. e:s-x is the range convention used to represent slots s to x in the enclosure e. pdperarray 1-16 Specifies the number of physical drives per array. The default value is automatically chosen.
Option Value Range Description strip 8, 16, 32, 64, 128, 256, 512, 1024 Sets the strip size for the RAID configuration. aftervd Valid virtual drive number Creates the VD in the adjacent free slot next to the specified VD. spares Number of spare physical drives present Specifies the physical drives that are to be assigned to a disk group for spares. force — Forces a security-capable physical drive to be added to a drive group without security.
10.5.4.2 Delete Virtual Drives Commands The Storage Command Line Tool supports the following virtual drive delete commands: storcli /cx/vx|vall del storcli /cx/vx|vall del cachecade storcli /cx/vx|vall del force Note: If the virtual drive has user data, you must use the force option to delete the virtual drive. A virtual drive with a valid master boot record (MBR) and a partition table is considered to contain user data.
Note: This command deletes the virtual drive where the operating system is present. Data located on these drives and the operating system of the drive will no longer be accessible. 10.5.4.3 Virtual Drive Show Commands The Storage Command Line Tool supports the following virtual drive show commands: storcli /cx/vx show storcli /cx/vx show all The detailed description for each command follows. storcli /cx/vx show This command shows the summary of the virtual drive information.
10.5.4.
storcli /cx/vx set rdcache= This command sets the read cache policy on a virtual drive to read ahead, no read ahead, or adaptive read ahead. Input example: storcli /c0/v0 set rdcache=nora storcli /cx/vx|vall set ssdcaching= This command assigns CacheCade virtual drives. If ssdcaching=off, the CacheCade virtual drive is removed.
Input example: storcli /c0/v2 show init storcli /cx/vx start init [full] This command starts the initialization of a virtual drive. The default initialization type is fast initialization. If the fulloption is specified, full initialization of the virtual drive starts. Input example: storcli /cx/vx start init [full] storcli /cx/vx stop init This command stops the initialization of a virtual drive. A stopped initialization cannot be resumed. Input example: storcli /c0/v0 stop init 10.5.4.
The detailed description for each command follows. storcli /cx/vx show migrate This command shows the progress of the virtual drive migrate operation in percentage. Input example: storcli /c0/v0 show migrate storcli /cx/vx start migrate [option= disk= ] This command starts the reconstruction on a virtual drive to the specified RAID level by adding or removing disks from the existing virtual drive.
Initial RAID Level Migrated RAID Level RAID 5 RAID 6 RAID 6 RAID 0 RAID 6 RAID 5 Input example: storcli /c0/v3 start migrate type=r5 option=add disk=e5:s2,e5:s3 10.5.4.
storcli /cx/vx start cc force This command starts a consistency check operation for a virtual drive. Typically, a consistency check operation is run on an initialized virtual drive. Use the force option to run a consistency check on an uninitialized drive. Input example: storcli /c0/v4 start cc storcli /cx/vx stop cc This command stops a consistency check operation. You can run this command only for a virtual drive that has a consistency check operation running.
Input example: storcli /c0/v0 show autobgi storcli /cx/vx show bgi This command shows the background initialization progress on the specified virtual drive in percentage. Input example: storcli /c0/v0 show bgi storcli /cx/vx stop bgi This command stops a background initialization operation. You can run this command only for a virtual drive that is currently initialized. Input example: storcli /c0/v4 stop bgi storcli /cx/vx pause bgi This command suspends a background initialization operation.
10.5.5 Foreign Configurations Commands The Storage Command Line Tool supports the following commands to view, import, and delete foreign configurations: storcli /cx/fall|fall del|delete [ securitykey=sssssssssss ] storcli /cx/fall|fall import [preview][ securitykey=sssssssssss ] storcli /cx/fall|fall show [all] [ securitykey=sssssssssss ] Note: Provide the security key when importing a locked foreign configuration created in a different machine that is encrypted with a security key.
storcli /cx set autobootselect|abs= This command enables the BIOS to select the best logical drive as the boot drive. Input example: storcli /cx set autobootselect=on storcli /cx set bios= This command enables or disables the Intel® RAID Controller's BIOS. Note: The legacy BIOS can load a limited number of the PCI device's BIOS. Disable the Intel® RAID BIOS to avoid issues during POST.
storcli/cx/vx show bootdrive This command shows the boot drive for the controller. The boot drive can be a physical drive or a virtual drive. Input example: storcli /c0/v0 show bootdrive 10.5.7 Drive Group Commands This section describes the drive group commands. 10.5.7.
Input example: storcli /c0/dx show storcli /cx/dx show all This command shows the physical drive and the virtual drive information for the drive group. Input example: storcli /c0/dx show all storcli /cx/dx set security=on This command enables security on the specified drive group. Input example: storcli /c0/dx set security=on all 10.5.8 Dimmer Switch Commands 10.5.8.
Option Value Range 1: Unconfigured type 2: Hot spare 3: Virtual drive 4: All auto: Logical device power savings are managed by the firmware. defaultldtype none: No power saving policy. Description Specifies the type of drives that the dimmer switch feature is applicable. By default, it is activated for unconfigured drives, hot spare drives, and virtual drives. Specifies the default logical drive type that is created by the dimmer switch option; set to none automatically.
storcli storcli storcli storcli storcli /cx/bbu /cx/bbu /cx/bbu /cx/bbu /cx/bbu set writeaceess=sealed show modes show properties show status start learn The detailed description for each command follows. storcli /cx/bbu show This command shows the summary information for the BBU of a controller. Input example: storcli /c0/bbu show storcli /cx/bbu show all This command shows all the information of the BBU.
A. B. Indicates how long the battery can hold data in the controller’s memory in case of accidental system shutdown. The controller’s performance is not affected during the battery’s learn cycle. Input example: storcli /c0/bbu set bbuMode=2 Note: BBU modes are supported on any BBU8/9 bbu/controller combo and later-generation controllers. storcli /cx/bbu set learndelayinterval= This command sets the learn delay interval for the BBU in hours. The value must be between 0 to 168 hours (7 days).
Input example: storcli /c0/bbu show status storcli /cx/bbu start learn This command starts the BBU learning cycle. The battery learn cycle is immediately started and no other parameters are required for this command. Input example: storcli /c0/bbu start learn 10.5.
storcli /cx/ex show status This command shows the enclosure status and the status of all the enclosure elements. Input example: storcli /c0/e0 show status 10.5.11 PHY Commands The Storage Command Line Tool supports the following PHY commands: storcli /cx/px|pall set linkspeed=0(auto)|1.5|3|6|12 storcli /cx/px|pall show storcli /cx/px|pall show all The detailed description for each command follows. storcli /cx/px|pall set linkspeed=0(auto)|1.5|3|6|12 This command sets the PHY link speed.
storcli /cx delete events This command deletes all records in the event log. Input example: storcli /c0 delete events storcli /cx delete termlog This command clears the TTY (firmware log for issue troubleshooting) logs. Input example: storcli /c0 delete termlog storcli /cx show events file= This command prints the system log to a text file and saves the file in the specified location.
10.6 Frequently Used Tasks 10.6.1 Showing the Version of the Storage Command Line Tool The following command shows the version of the command line tool: Storcli -v 10.6.2 Showing StorCLI Help The following command shows the command line tool help: Storcli -h Help appears for all the StorCLI commands. 10.6.3 Showing System Summary Information The following command shows the summary of all the controller information: Storcli -show [all] 10.6.
• The drives that are used to create the virtual drives. drives = e:s|e:s-x|e:s-x,y Where: — e specifies the enclosure id. — s represents the slot in the enclosure. — e:s-x is the range conventions used to represents slots s to x in the enclosure e. • The physical drives per array. The physical drives per array can be set to a particular value. • • • • The SED option creates security-enabled drives. • • • • • The wt option disables write back.
storcli /cx show [all] 10.6.8 Deleting Virtual Drives The following command deletes virtual drives: storcli /cx/v(x|all) del [cc|cachecade] The following inputs are required when deleting a virtual drive: 10.6.9 • • The controller on which the virtual drive or virtual drives is present. • The cc or cachecade option to confirm that the deleted drive is a CacheCade drive. The virtual drives that must be deleted; or you can delete all the virtual drives on the controller using the vall option.
10.7 Unsupported StorCLI Commands The commands in the following table are not supported for the Intel® RAID Controllers such as Intel® RAID Controller RS3WC080. Table 37.
Command Group ASO Command storcli /cx(x|all) set aso key= preview storcli /cx(x|all) set aso key= storcli /cx(x|all) set aso transfertovault storcli /cx(x|all) set aso rehostcomplete storcli /cx(x|all) set aso deactivatetrialkey storcli /cx(x|all) show safeid storcli /cx(x|all) show rehostinfo storcli /c0 set time = storcli /c0 show cc|consistencycheck storcli /c0/vall show expansion storcli /c0 set jbod storcli /cx download src= [forceActivate] C
Command Group Secure ease Command storcli /cx/sx secureerase [force] storcli /cx/sx start erase [simple| normal| thorough][erasepatternA=] storcli /cx/sx stop erase storcli /cx/sx show erase 305 Consistency check storcli /cx show cc/ConsistencyCheck Controller storcli /cx show cc Intel® RAID Software User Guide
Appendix A: Creating a Virtual Drive Using Advanced Configuration The advanced configuration procedure provides an easy way to create a new storage configuration. Advanced configuration gives you greater flexibility than simple configuration because you can select the drives and the virtual drive parameters when you create a virtual drive. In addition, you can use the advanced configuration procedure to create spanned drive groups.
Figure 175. Virtual Drive Creation Menu The dialog box shown in Figure 176 appears.
Figure 176. Virtual Drive Creation Mode 2. Click Advanced and press Next. The Create Drive Group Settings screen appears, as shown in Figure 177.
Figure 177. Create Drive Group Settings Screen 3. Select the following items on the Create Drive Group Settings screen: a. Select the RAID level desired for the drive group from the drop-down menu. To make a spanned drive, select RAID 10, RAID 50, or RAID 60 in the RAID level field. Drive Group 0 and Span 0 appear in the Drive groups field when you select RAID 10, 50, or 60. The RAID controller supports RAID levels 1, 5, 6, 10, 50, and 60.
Figure 178. Span 0 of Drive Group 0 c. Click Create Span to create a second span in the drive group. d. Select unconfigured drives from the list of drives and click Add> to add them to the drive group. e.
Figure 179. Span 0 and Span 1 of Drive Group 0 f. Click Create Drive Group to make a drive group with the spans. g. Click Next to complete this step. The Virtual drive settings window appears, as shown in Figure 180. The drive group and the default virtual drive settings appear. The options to update the virtual drive or remove the virtual drive are grayed out until you create the virtual drive.
Figure 180. Virtual Drive Settings Window 4. Change any virtual drive settings, if desired. 5. Click Create Virtual Drive. The new virtual drive appears under the drive group, as shown in Figure 181. The options Update Virtual Drive and Remove Virtual Drive are now available. Update Virtual Drive allows you to change the virtual drive settings and Remove Virtual Drive allows you to delete the virtual drive.
Figure 181. New Virtual Drive 0 6. Click Next. The Create Virtual Drive - Summary window appears, as shown in Figure 182. This window shows the selections you made for advanced configuration. Figure 182.
7. Click Back to return to the previous screen to change any selections or click Finish to accept and complete the configuration. The new storage configuration will be created and initialized. Note: If you create a large configuration using drives that are in powersave mode, it could take several minutes to spin up the drives. A progress bar appears as the drives spin up. If any of the selected unconfigured drives fail to spin up, a box appears to identify the drive or drives. 8.
Appendix B: Events and Messages This appendix lists the Intel® RAID Web Console 2 events that may display in the event log. The Intel® RAID Web Console 2 monitors the activity and performance of all controllers in the server and the devices attached to them. When an “event” such as the completion of a consistency check or the removal of a physical drive occurs, an event message is displayed in the log displayed at the bottom of the Intel® RAID Web Console 2 screen.
Table 38.
Number 317 Type Description 30 Info Event log cleared 31 Info Event log wrapped 32 Dead Multi-bit ECC error: ECAR=%x 33 Warning Single-bit ECC error: ECAR=%x 34 Dead Not enough controller memory 35 Info Patrol Read complete 36 Info Patrol Read paused 37 Info Patrol Read Rate changed to %d%% 38 Info Patrol Read resumed 39 Info Patrol Read started 40 Info Rebuild rate changed to %d%% 41 Info Reconstruction rate changed to %d%% 42 Info Shutdown command received from ho
Number Type Description 60 Fatal Consistency Check detected uncorrectable double medium errors (%s at %lx on %s) 61 Critical Consistency Check failed on %s 62 Fatal Consistency Check failed with uncorrectable data on %s 63 Warning Consistency Check found inconsistent parity on %s at strip %lx 64 Warning Consistency Check inconsistency logging disabled on %s (too many inconsistencies) 65 Progress Consistency Check progress on %s is %s 66 Info Consistency Check started on %s 67 Warnin
Number 319 Type Description 89 Info Format started on %s 90 Critical Hot Spare SMART polling failed on %s (Error %02x) 91 Info PD inserted: %s 92 Warning PD %s is not supported 93 Warning Patrol Read corrected medium error on %s at %lx 94 Progress Patrol Read progress on %s is %s 95 Fatal Patrol Read found an uncorrectable medium error on %s at %lx 96 Critical Predictive failure: CDB: %s 97 Fatal Patrol Read puncturing bad block on %s at %lx 98 Info Rebuild aborted by user o
Number Type Description 120 Critical SAS topology error: Unaddressable device 121 Critical SAS topology error: Multiple ports to the same SAS address 122 Critical SAS topology error: Expander error 123 Critical SAS topology error: SMP timeout 124 Critical SAS topology error: Out of route entries 125 Critical SAS topology error: Index not found 126 Critical SAS topology error: SMP function failed 127 Critical SAS topology error: SMP CRC error 128 Critical SAS topology error: Mult
Number 321 Type Description 151 Info Battery relearn started 152 Info Battery relearn in progress 153 Info Battery relearn completed 154 Critical Battery relearn timed out 155 Info Battery relearn pending: Battery is under charge 156 Info Battery relearn postponed 157 Info Battery relearn will start in 4 days 158 Info Battery relearn will start in 2 day 159 Info Battery relearn will start in 1 day 160 Info Battery relearn will start in 5 hours 161 Info Battery removed 16
Number Type Description 182 Warning Enclosure %s not supported; too many enclosures connected to port 183 Critical Enclosure %s firmware mismatch 184 Warning Enclosure %s sensor %d bad 185 Critical Enclosure %s phy %d bad 186 Critical Enclosure %s is unstable 187 Critical Enclosure %s hardware error 188 Critical Enclosure %s not responding 189 Info SAS/SATA mixing not supported in enclosure; PD %s disabled 190 Info Enclosure (SES) hotplug on %s was detected, but is not supported
Number 323 Type Description 211 Critical BBU Retention test failed! 212 Info NVRAM Retention test was initiated on previous boot 213 Info NVRAM Retention test passed 214 Critical NVRAM Retention test failed! 215 Info %s test completed %d passes successfully 216 Critical %s test FAILED on %d pass.
Number Type Description 240 Info VDs missing at boot: %s 241 Info Previous configuration completely missing at boot 242 Info Battery charge complete 243 Info Enclosure %s fan %d speed changed 244 Info Dedicated spare %s imported as global due to missing arrays 245 Info %s rebuild not possible as SAS/SATA is not supported in an array 246 Info SEP %s has been rebooted as a part of enclosure firmware download. SEP will be unavailable until this process completes.
Number 325 Type Description 268 Warning PD %s reset (Type %02x) 269 Warning VD bad block table on %s is 80% full 270 Fatal VD bad block table on %s is full; unable to log block %lx (on %s at %lx) 271 Fatal Uncorrectable medium error logged for %s at %lx (on %s at %lx) 272 Info VD medium error corrected on %s at %lx 273 Warning Bad block table on PD %s is 100% full 274 Warning VD bad block table on PD %s is 100% full 275 Fatal Controller needs replacement, IOP is faulty 276 Info
Number Type Description 295 Warning Copyback aborted on PD %s from PD %s, as rebuild required in the array 296 Fatal Controller cache discarded for missing or offline VD %s When a VD with cached data goes offline or missing during runtime, the cache for the VD is discarded. Because the VD is offline, the cache cannot be saved.
Number 327 Type Description 321 Info PD %s security key changed 322 Fatal Security subsystem problems detected for PD %s 323 Fatal Controller cache pinned for missing or offline VD %s 324 Fatal Controller cache pinned for missing or offline VDs: %s 325 Info Controller cache discarded by user for VDs: %s 326 Info Controller cache destaged for VD %s 327 Warning Consistency Check started on an inconsistent VD %s 328 Warning Drive security key failure, cannot access secured configurat
Number Type Description 349 Info Snapshot rollback started on %s from snapshot at %s 350 Fatal Snapshot rollback on %s internally aborted for snapshot at %s 351 Info Snapshot rollback on %s completed for snapshot at %s 352 Info Snapshot rollback progress for snapshot at %s, on %s is %s 353 Warning Snapshot space for %s in snapshot repository %s, is 80%% full 354 Critical Snapshot space for %s in snapshot repository %s, is full 355 Warning View at %s to snapshot at %s, is 80%% full on
Number 329 Type Description 377 Info Snapshot scheduled action is due on %s 378 Info Performance Metrics: collection command 0x%lx 379 Info Premium feature %s key was transferred - %s 380 Info Premium feature serial number %s 381 Warning Premium feature serial number mismatched. Key-vault serial num - %s 382 Warning Battery cannot support data retention for more than %d hours.
Number Type Description 404 Info Consistency Check resumed on %s 405 Info Background Initialization suspended on %s 406 Info Background Initialization resumed on % 407 Info Reconstruction suspended on %s 408 Info Rebuild suspended on % 409 Info Copyback suspended on %s 410 Info Reminder: Consistency Check suspended on % 411 Info Reminder: Background Initialization suspended on %s 412 Info Reminder: Reconstruction suspended on %s 413 Info Reminder: Rebuild suspended on %s 414
Number 331 Type Description 433 Critical CacheCade disassociate failed on %s 434 Progress CacheCade disassociate progress on %s is %s 435 Info CacheCade disassociate aborted by user on %s 436 Info Link speed changed on SAS port %d and PHY %d 437 Warning Advanced Software Options was deactivated for - %s 438 Info %s is now accessible 439 Info %s is using CacheCade 440 Info %s is no longer using CacheCade 441 Info Patrol Read aborted on %s 61440 Info Monitor has shutdown succe
Glossary This chapter provides a glossary for terms used in this document. A Absolute state of charge Predicted remaining battery capacity expressed as a percentage of Design Capacity. Note that the Absolute State of Charge operation can return values greater than 100 percent. Access policy A virtual drive property indicating what kind of access is allowed for a particular virtual drive. The possible values are Read/Write, Read Only, or Blocked.
Battery status Operating status of the battery. Possible values are Missing, Optimal, Failed, Degraded (need attention), and Unknown. Battery type Possible values are intelligent Battery Backup Unit (BBU), intelligent Battery Backup Unit (iBBU), intelligent Transportable Battery Backup Unit (iTBBU), and ZCR Legacy. BBU present A controller property that indicates whether the controller has an on-board battery backup unit to provide power in case of a power failure.
Consistency check An operation that verifies that all stripes in a virtual drive with a redundant RAID level are consistent and that automatically fixes any errors. For RAID 1 drive groups, this operation verifies correct mirrored data for each stripe. Consistency check rate The rate at which consistency check operations are run on a computer system.
Design voltage Designed voltage capacity of the battery, measured in millivolts (mV). Device chemistry Possible values are NiMH (nickel metal hydride) and LiON (lithium ion). Device ID A controller or drive property indicating the manufacturer-assigned device ID. Device port count A controller property indicating the number of ports on the controller. Drive cache policy A virtual drive property indicating whether the virtual drive cache is enabled, disabled, or unchanged from its previous setting.
F Fast initialization A mode of initialization that quickly writes zeroes to the first and last sectors of the virtual drive. This allows you to immediately start writing data to the virtual drive while the initialization is running in the background. Fault tolerance The capability of the drive subsystem to undergo a single drive failure per drive group without compromising data integrity and processing capability.
Hot spare A standby drive that can automatically replace a failed drive in a virtual drive and prevent data from being lost. A hot spare can be dedicated to a single redundant drive group or it can be part of the global hot spare pool for all drive groups controlled by the controller. When a drive fails, the GUI management utility software automatically uses a hot spare to replace it and then rebuilds the data from the failed drive to the hot spare.
Max error Expected margin of error (percentage) in the state of charge calculation. For example, when Max Error returns 10 percent and Relative State of Charge returns 50 percent, the Relative State of Charge is more likely between 50 percent and 60 percent. The gas gauge sets Max Error to 100 percent on a full reset. The gas gauge sets Max Error to 2 percent on completion of a learn cycle, unless the gas gauge limits the learn cycle to the +512/–256-mAh maximum adjustment values.
O Offline A drive is offline when it is part of a virtual drive but its data is not accessible to the virtual drive. P Patrol read A process that checks the drives in a storage configuration for drive errors that could lead to drive failure and lost data. The patrol read operation can find and sometimes fix any potential problem with drives before host access. This enhances overall system performance because error recovery during a normal I/O operation might not be necessary.
RAID 6 Uses data striping and parity data across three or more drives (distributed parity) to provide high data throughput and data redundancy, especially for applications that require random access. RAID 6 can survive the failure of two drives. RAID 10 A combination of RAID 0 and RAID 1 that uses data striping across two mirrored drive groups. It provides high data throughput and complete data redundancy.
Redundant configuration A virtual drive that has redundant data on drives in the drive group can be used to rebuild a failed drive. The redundant data can be parity data striped across multiple drives in a drive group, or it can be a complete mirrored copy of the data stored on a second drive. A redundant configuration protects the data in case a drive fails in the configuration. Relative state of charge Predicted remaining battery capacity expressed as a percentage of Full Charge Capacity.
Striping A technique used to write data across all drives in a virtual drive. Each stripe consists of consecutive virtual drive data addresses that are mapped in fixed-size units to each drive in the virtual drive using a sequential pattern. For example, if the virtual drive includes five drives, the stripe writes data to drives one through five without repeating any of the drives. The amount of space consumed by a stripe is the same on each drive. Striping by itself does not provide data redundancy.
