Table of Contents

Related Documents

07-Configuring a 9361, 9440, 9460, L460, P5408, or H5408 storage controller

Title	Size	Download
07-Configuring a 9361, 9440, 9460, L460, P5408, or H5408 storage controller	11.51 MB

Configuring an LSI-9440, 9460, 5408, LSI-9361, L460, 9560, or 9540 series storage controller

NOTE:

The BIOS screens might vary by the BIOS version. The screenshots in this chapter are for illustration only.

About LSI-9440, 9460, 5408, LSI-9361, L460, 9560, or 9540 series storage controllers

The storage controllers provide a maximum interface rate of 12 Gbps, and some storage controllers support caching, which greatly increases performance and data security. For more information about storage controller details and the supported cache, access http://www.h3c.com/en/home/qr/default.htm?id=66.

This chapter is applicable to the following storage controllers:

· RAID-LSI-9361-8i(1G)-A1-X

· RAID-LSI-9361-8i(2G)-1-X

· HBA-LSI-9440-8i

· RAID-LSI-9460-8i(2G)

· RAID-LSI-9460-8i(4G)

· RAID-LSI-9460-16i(4G)

· HBA-H5408-Mf-8i

· RAID-P5408-Mf-8i-4GB

· RAID-P5408-Ma-8i-4GB

· RAID-LSI-9560-LP-16i-8GB

· RAID-LSI-9560-LP-8i-4GB

· RAID-P9560-3S-8i-4G

· HBA-LSI-9540-LP-8i

Features

Operating mode

The storage controller supports the following operating modes, as shown in Table 1:

· JBOD mode—In this mode, both JBOD drives and RAID arrays are visible to the operating system. This mode supports simple RAID levels such as RAID 0, RAID 1, and RAID 10.

· RAID mode—This is the default mode. In this mode, both JBOD drives and RAID arrays are visible to the operating system. This mode supports all RAID levels such as RAID 0, RAID 1, RAID 5, RAID 6, RAID 10, RAID 50, and RAID 60.

IMPORTANT:

The LSI storage controller in RAID mode supports configuring JBOD drives (in JBOD or JBOD online state). For more information, see "Switching the drive state." If you use a 9361/9460/9440/9540 controller to configure JBOD drives in RAID mode, you must also enable the JBOD feature. For more information, see "Setting the JBOD state."

Table 1 Supported operating modes

Storage controller model	JBOD mode supported	RAID mode supported
RAID-LSI-9361-8i(1G)-A1-X	Yes	Yes
RAID-LSI-9361-8i(2G)-1-X	Yes	Yes
RAID-LSI-9460-8i(2G)	Yes	Yes
RAID-LSI-9460-8i(4G)	Yes	Yes
RAID-LSI-9460-16i(4G)	Yes	Yes
RAID-P5408-Mf-8i-4GB	Yes	Yes
RAID-P5408-Ma-8i-4GB	Yes	Yes
HBA-H5408-Mf-8i	No	Yes
HBA-LSI-9440-8i	No	Yes
RAID-LSI-9560-LP-8i-4GB	Yes	Yes
RAID-LSI-9560-LP-16i-8GB	Yes	Yes
RAID-P9560-3S-8i-4GB	Yes	Yes
HBA-LSI-9540-LP-8i	No	Yes

RAID levels

The supported RAID levels vary by storage controller model. For more information about the supported RAID levels of each storage controller, contact Technical Support.

Table 2 shows the minimum number of drives required by each RAID level and the maximum number of failed drives supported by each RAID level. For more information about RAID levels, see "Appendix B RAID arrays and fault tolerance."

Table 2 RAID levels and the numbers of drives for each RAID level

RAID level	Min. drives required	Max. failed drives
RAID 0	1	0
RAID 1	2	Number of drives divided by 2
RAID 5	3	1
RAID 6	For the LSI 9560: 4 For the other storage controllers: 3 (4 is recommended.)	2
RAID 00	2	0
RAID 10	4	n, where n is the number of RAID 1 arrays in the RAID 10 array.
RAID 50	6	n, where n is the number of RAID 5 arrays in the RAID 50 array.
RAID 60	For the LSI 9560: 8 For the other storage controllers: 6 (8 is recommended.)	2n, where n is the number of RAID 6 arrays in the RAID 60 array.

NOTE:

Storage controllers described in this chapter support using a maximum of eight member RAID 1/5/6 arrays to form a RAID 10/50/60 array.

Restrictions and guidelines for configuring RAID

· As a best practice, configure RAID with drives that do not contain RAID information.

· To build a RAID successfully and ensure RAID performance, make sure all drives in the RAID are the same type (HDDs or SSDs) and have the same connector type (SAS or SATA).

· For efficient use of storage, use drives that have the same capacity to build a RAID. If the drives have different capacities, the lowest capacity is used across all drives in the RAID.

· If you use one physical drive to create multiple RAIDs, RAID performance might decrease in addition to increased maintenance complexities.

Configuring RAID arrays in UEFI mode

This section describes how to configure RAID arrays through a storage controller in UEFI mode. For more information about how to enter the BIOS and set the boot mode to UEFI, see the BIOS user guide for the server.

RAID array configuration tasks at a glance

To configure a RAID array in UEFI mode, perform the following tasks:

· Accessing the storage controller configuration screen

· Switching the drive state

· Configuring a RAID array

· (Optional.) Configuring hot spare drives

· (Optional.) Deleting a RAID array

· (Optional.) Locating drives

· (Optional.) Initializing a virtual drive

· (Optional.) Initializing a physical drive

· (Optional.) Erasing drives

· (Optional.) Expanding a RAID array

· (Optional.) Migrating the RAID level

· (Optional.) Clearing RAID array information on the drive

· (Optional.) Hiding a virtual drive

· (Optional.) Hiding a RAID array

· (Optional.) Upgrading the storage controller firmware online

Accessing the storage controller configuration screen

1. Access the BIOS. Press Delete, Esc, or F2 as prompted during server POST to open the BIOS setup screen as shown in Figure 1. For some devices, the Front Page screen opens, and you must select Device Management before proceeding to the next step.

For how to navigate screens and modify settings, see the operation instructions at the lower right corner.

Figure 1 BIOS setup screen

2. On the screen as shown in Figure 2, select Advanced > Dynamic Device Configuration (Optional, based on BIOS version) > storage controller model, and press Enter.

In this example, the storage controller model is AVAGO MegaRAID <AVAGO MegaRAID SAS 9361-8i>.

Figure 2 Advanced screen

3. Select Main Menu as shown in Figure 3, and press Enter.

Figure 3 Selecting Main Menu

The storage controller configuration screen as shown in Figure 4 opens. This screen contains five tasks as described in Table 3.

Figure 4 Storage controller configuration screen

Table 3 Storage controller configuration tasks

Option	Description
Configuration Management	Select Configuration Management to perform the following tasks: · Create RAID arrays. · View RAID array properties. · View hot spare drives. · Clear configuration.
Controller Management	Select Controller Management to perform the following tasks: · View and manage controller properties. · Clear, schedule, or run controller events.
Virtual Drive Management	Select Virtual Drive Management to perform the following tasks: · View logical drive properties. · Locate logical drives. · Run consistency check.
Drive Management	Select Drive Management to perform the following tasks: · View physical drive properties. · Locate drives. · Initialize drives. · Rebuild drives.
Hardware Components	Select Hardware Components to perform the following tasks: · View supercapacitor properties. · Manage supercapacitor. · Manage peripheral components.

Switching the drive state

The storage controller supports the following drive states:

· Unconfigured Good—The drive is normal and can be used for RAID array or hot backup configuration.

· Unconfigured Bad—The drive is faulty or has RAID array information remaining on it. If the drive is faulty, replace the drive. If RAID array information remains on the drive, clear the RAID array information.

· Hotspare—The drive is a hot spare drive.

· JBOD/JBOD online—Just a Bunch Of Disks. The drive is a passthrough or passthrough-like drive and does not support RAID configuration. The passthrough drive is in JBOD online state by default for the RAID-LSI-9560-LP-16i-8GB or RAID-LSI-9560-LP-8i-4GB storage controller and in JBOD state for other storage controllers.

To switch from Unconfigured Good state to Unconfigured Bad state:

1. On the storage controller configuration screen as shown in Figure 5, select Drive Management and press Enter.

Figure 5 Storage controller configuration screen

2. On the screen as shown in Figure 6, select the target drive and press Enter.

Figure 6 Drive Management screen

3. On the screen as shown in Figure 7, select Operation and press Enter. On the dialog box that appears, select Make Unconfigured Bad and press Enter.

Figure 7 Operation screen

4. On the screen as shown in Figure 8, select Go and press Enter.

Figure 8 Selecting Go

When the operation is complete, the screen as shown in Figure 9 opens.

Figure 9 Completing drive state switchover

Configuring a RAID array

1. On the storage controller configuration screen as shown in Figure 10, select Configuration Management and press Enter.

Figure 10 Storage controller configuration screen

2. On the screen as shown in Figure 11, select Create Virtual Drive and press Enter.

Figure 11 Selecting Create Virtual Drive

3. On the screen as shown in Figure 12, select Select RAID Level to set the RAID level, and then press Enter.

Figure 12 Setting the RAID level

4. On the screen as shown in Figure 13, select Select Drives From to set the drive capacity source, and then press Enter.

¡ Unconfigured Capacity—The capacity source is the unconfigured drives.

¡ Free Capacity—The capacity source is the remaining drive capacity.

Figure 13 Setting the drive capacity source

5. On the screen as shown in Figure 14, select Select Drives and press Enter.

Figure 14 Selecting Select Drives

6. On the screen as shown in Figure 15, select the target drives. ([Enabled] following a drive means that the drive has been selected.) Then, select Apply Changes and press Enter. A drive in JBOD or Unconfigured Bad status cannot be selected.

Figure 15 Selecting the target drives

7. On the screen as shown in Figure 16, configure the parameters, select Save Configuration, and press Enter. For more information about the parameter description, see Table 4.

Figure 16 Configuring RAID parameters

Table 4 Parameter description

Parameter	Description
Virtual Drive Name	RAID array name, a case-insensitive string of letters, digits, and special characters.
Virtual Drive Size	Capacity for the RAID array.
Virtual Drive Size Unit	Capacity unit for the RAID array.
Stripe Size	Data block size for each drive.
Read Policy	Read cache policy: · Read ahead—Enables read ahead capability. When this capability is enabled, the storage controller can pre-read sequential data or anticipate data to be requested and store the data in the cache · No read ahead—Disables read ahead capability.
Write Policy	Write cache policy: · Write through—Enables the controller to send data transfer completion signal to the host when the physical drives have received all data in a transaction. · Write back—Enables the controller to send data transfer completion signal to the host when the controller cache receives all data in a transaction. If the supercapacitor is faulty or no supercapacitor is present, the Write through policy is used. · Always write back—Uses the Write back policy even if the supercapacitor of the storage controller is absent or faulty. If the server is powered off, the controller cache loses its data because of lack of power.
Access Policy	Read and write policy: · Read/Write · Read Only · Blocked
I/O Policy	I/O policy: · Direct—The definition varies by scenario: ¡ In read scenarios, data is directly read from drives. If Read Ahead is set, read operations preload data to the RAID cache in advance. ¡ In write scenarios, data is first cached in the RAID cache, and then asynchronously written to drives. If the Write Policy field is set to Write through, data is written directly to drives, bypassing the cache. · Cached—Enables the cache module of the RAID controller to process all read and write operations. As a best practice, use this policy only when you configure CacheCade 1.1. The HBA-LSI-9540-LP-8i storage controller does not support configuring an I/O policy in the current software version.
Drive Cache	Drive cache policy: · Enable—Enables the write drive cache policy. With this policy enabled, write performance will improve, but data might get lost upon an unexpected power failure if additional protection mechanism is not in place. · Disable—Disables the write drive cache policy. With this policy enabled, data will not get lost upon an unexpected power failure, but the write performance might be impacted. · Unchanged—Maintains the current drive cache policy.
Disable Background Initialization	Enabling status of background initialization.
Default Initialization	Default initialization mode: · NO. · Fast. · Full.
Emulation Type	Sector size reported to the OS: · Default—Displays 512e (4K) as the sector size as long as one 512e member drive exists, and displays 512n as the sector size if no 512e member drive exists. · Disable—Displays 512n as the sector size if no 512e member drive exists. · Force—Displays 512e (4K) as the sector size even if no 512e member drive exists.
Save Configuration	Select this option to save the configuration.

8. On the screen as shown in Figure 17, select Confirm and press Enter. On the dialog box that opens, select Enabled and press Enter. Then, select Yes and press Enter.

Figure 17 Confirming the configuration

9. On the screen as shown in Figure 18, select OK to return to the storage controller configuration screen.

Figure 18 Completing RAID array configuration

10. Select Virtual Drive Management and press Enter as shown in Figure 19.

Figure 19 Storage controller configuration screen

11. On the screen as shown in Figure 20, you can see the created drives. Select the drive you want to view and press Enter.

Figure 20 Virtual Drive Management screen

12. On the screen as shown in Figure 21, select View Associated Drives and press Enter. You can view the detailed information about the RAID array, including name, level, and drive information.

Figure 21 Selecting View Associated Drives

Configuring hot spare drives

For data security purposes, configure hot spare drives after configuring a RAID array. You can configure global hot spare drives or dedicated hot spare drives.

NOTE:

· A hot spare drive can be used only for RAID levels with redundancy.

· The capacity of a hot spare drive must be equal to or greater than the capacity of the smallest drive in the RAID array.

· Only the drive in Unconfigured Good state can be configured as a hot spare drive.

Configuring a global hot spare drive

1. On the storage controller configuration screen as shown in Figure 22, select Drive Management and press Enter.

Figure 22 Storage controller configuration screen

2. On the screen as shown in Figure 23, select the target drive and press Enter.

Figure 23 Drive Management screen

3. On the screen as shown in Figure 24, select Operation and press Enter. On the dialog box that appears, select Assign Global Hot Spare Drive and press Enter.

Figure 24 Operation screen

4. On the screen as shown in Figure 25, select Go and press Enter.

Figure 25 Selecting Go

5. On the screen as shown in Figure 26, select Confirm and press Enter. On the dialog box that opens, select Enabled and press Enter. Then, select Yes and press Enter.

Figure 26 Confirming the configuration

When the operation is complete, the screen as shown in Figure 27 opens.

Figure 27 Completing global hot spare drive configuration

Configuring a dedicated hot spare drive

1. On the storage controller configuration screen as shown in Figure 28, select Drive Management and press Enter.

Figure 28 Storage controller configuration screen

2. On the screen as shown in Figure 29, select the target drive and press Enter.

Figure 29 Drive Management screen

3. On the screen as shown in Figure 30, select Operation and press Enter. On the dialog box that appears, select Assign Dedicated Hot Spare Drive and press Enter.

Figure 30 Operation screen

4. On the screen as shown in Figure 31, select Go and press Enter.

Figure 31 Selecting Go

5. On the screen as shown in Figure 32, select the drive you want to configure as the hot spare drive. ([Enabled] following the drive means that the drive has been selected.) Then, select OK and press Enter.

Figure 32 Confirming selection

When the operation is complete, the screen as shown in Figure 33 opens.

Figure 33 Completing the operation

Deleting a RAID array

1. On the storage controller configuration screen as shown in Figure 34, select Virtual Drive Management and press Enter.

Figure 34 Storage controller configuration screen

2. On the screen as shown in Figure 35, select the target virtual drive and press Enter.

Figure 35 Virtual Drive Management screen

3. On the screen as shown in Figure 36, select Operation and press Enter. On the dialog box that appears, select Delete Virtual Drive and press Enter.

Figure 36 Operation screen

4. On the screen as shown in Figure 37, select Go and press Enter.

Figure 37 Selecting Go

5. On the screen as shown in Figure 38, select Confirm and press Enter. On the dialog box that opens, select Enabled and press Enter. Then, select Yes and press Enter.

Figure 38 Confirming the deletion

When the operation is complete, the screen as shown in Figure 39 opens.

Figure 39 Completing the operation

Locating drives

This task allows you to locate a physical drive or all drives for a virtual drive.

Locating a physical drive

1. On the storage controller configuration screen as shown in Figure 40, select Drive Management and press Enter.

Figure 40 Storage controller configuration screen

2. On the screen as shown in Figure 41, select the target drive and press Enter.

Figure 41 Selecting the target drive

3. On the screen as shown in Figure 42, select Operation and press Enter. On the dialog box that opens, select Start Locate and press Enter.

Figure 42 Operation screen

4. On the screen as shown in Figure 43, select Go and press Enter.

Figure 43 Selecting Go

When the operation is complete, the screen as shown in Figure 44 opens. The Fault/UID LED on the drive turns steady blue.

Figure 44 Completing locating the physical drive

Locating all drives for a virtual drive

1. On the storage controller configuration screen as shown in Figure 45, select Virtual Drive Management and press Enter.

Figure 45 Storage controller configuration screen

2. On the screen as shown in Figure 46, select the target drive and press Enter.

Figure 46 Selecting the target drive

3. On the screen as shown in Figure 47, select Operation and press Enter. On the dialog box that opens, select Start Locate and press Enter.

Figure 47 Operation screen

4. On the screen as shown in Figure 48, select Go and press Enter.

Figure 48 Selecting Go

When the operation is complete, the screen as shown in Figure 49 opens. The Fault/UID LED on the drive turns steady blue.

Figure 49 Completing locating all drives for a virtual drive

Initializing a virtual drive

This task allows you to initialize a virtual drive to be used by operating systems.

To initialize a virtual drive:

1. On the storage controller configuration screen as shown in Figure 50, select Virtual Drive Management and press Enter.

Figure 50 Storage controller configuration screen

2. On the screen as shown in Figure 51, select the target drive and press Enter.

Figure 51 Virtual Drive Management screen

3. On the screen as shown in Figure 52, select Operation and press Enter. On the dialog box that appears, select Fast Initialization or Slow Initialization and press Enter.

Figure 52 Operation screen

NOTE:

Fast initialization allows immediately writing data. Slow initialization allows writing data after initialization is complete.

4. On the screen as shown in Figure 53, select Go and press Enter.

Figure 53 Selecting Go

5. On the screen as shown in Figure 54, select Confirm and press Enter. On the dialog box that opens, select Enabled and press Enter. Then, select Yes and press Enter.

Figure 54 Confirming the initialization

When the operation is complete, the screen as shown in Figure 55 opens.

Figure 55 Completing the operation

Initializing a physical drive

1. On the storage controller configuration screen as shown in Figure 56, select Drive Management and press Enter.

Figure 56 Storage controller configuration screen

2. On the screen as shown in Figure 57, select the target drive and press Enter.

Figure 57 Drive Management screen

3. On the screen as shown in Figure 58, select Operation and press Enter. On the dialog box that opens, select Initialize Drive and press Enter.

Figure 58 Operation screen

4. On the screen as shown in Figure 59, select Go and press Enter.

Figure 59 Selecting Go

5. On the screen as shown in Figure 60, select Confirm and press Enter. On the dialog box that opens, select Enabled and press Enter. Then, select Yes and press Enter.

Figure 60 Confirming the initialization

When the operation is complete, the screen as shown in Figure 61 opens.

Figure 61 Completing the operation

Erasing drives

CAUTION:

To avoid drive failure, do not perform other operations when erasing a physical drive.

This task allows you to erase data from physical and logical drives.

Erasing a physical drive

1. On the storage controller configuration screen as shown in Figure 62, select Drive Management and press Enter.

Figure 62 Storage controller configuration screen

2. On the screen as shown in Figure 63, select the target drive and press Enter.

Figure 63 Drive Management screen

3. On the screen as shown in Figure 64, select Operation and press Enter.

4. On the dialog box that opens, select Drive Erase and press Enter.

For some controllers, you must select Cryptographic Erase for a SAS drive and select Drive Erase for a SATA drive.

Figure 64 Operation screen

5. On the screen as shown in Figure 65, press Enter and set the Erase Mode (the default Simple mode is recommended).

Figure 65 Setting the Erase Mode

6. On the screen as shown in Figure 66, select Go and press Enter.

Figure 66 Selecting Go

7. On the screen as shown in Figure 67, select Confirm and press Enter. On the dialog box that opens, select Enabled and press Enter. Then, select Yes and press Enter.

Figure 67 Confirming the operation

When the operation is complete, the screen as shown in Figure 68 opens.

Figure 68 Completing the operation

Erasing a logical drive

1. On the storage controller configuration screen as shown in Figure 69, select Virtual Drive Management and press Enter.

Figure 69 Storage controller configuration screen

2. On the screen as shown in Figure 70, select the target drive and press Enter.

Figure 70 Virtual Drive Management screen

3. On the screen as shown in Figure 71, select Operation and press Enter. On the dialog box that appears, select Virtual Drive Erase and press Enter.

Figure 71 Operation screen

4. On the screen as shown in Figure 72, press Enter and set the Erase Mode (the default Simple mode is recommended).

Figure 72 Setting the Erase Mode

5. On the screen as shown in Figure 73, select Go and press Enter.

Figure 73 Selecting Go

6. On the screen as shown in Figure 74, select Confirm and press Enter. On the dialog box that opens, select Enabled and press Enter. Then, select Yes and press Enter.

Figure 74 Confirming the operation

7. When the operation is complete, the screen as shown in Figure 75 opens.

Figure 75 Completing the operation

Expanding a RAID array

This task allows you to expand the RAID array capacity by setting the percentage of available logical drive capacity for availability purposes.

NOTE:

The LSI 9440&9460&9540&9560 controller supports migration and scale-up in UEFI mode or the operating system only when the RAID level is 0, 1, 5, or 6.

To expand a RAID array:

1. On the storage controller configuration screen as shown in Figure 76, select Virtual Drive Management and press Enter.

Figure 76 Storage controller configuration screen

2. On the screen as shown in Figure 77, select the target drive and press Enter.

Figure 77 Virtual Drive Management screen

3. On the screen as shown in Figure 78, select Operation and press Enter. On the dialog box that appears, select Expand Virtual Drive and press Enter.

Figure 78 Operation screen

4. On the screen as shown in Figure 79, select Go and press Enter.

Figure 79 Selecting Go

5. On the screen as shown in Figure 80, modify the value for Enter a Percentage of Available Capacity, select OK, and then press Enter.

Figure 80 Setting the percentage of available capacity

When the operation is complete, the screen as shown in Figure 81 opens.

Figure 81 Completing expanding a RAID array

Migrating the RAID level

This task allows you to change the RAID level without affecting data integrity.

NOTE:

The LSI 9440&9460&9540&9560 controller supports migration and scale-up in UEFI mode or the operating system only when the RAID level is 0, 1, 5, or 6.

To migrate the RAID level:

1. On the storage controller configuration screen as shown in Figure 82, select Virtual Drive Management and press Enter.

Figure 82 Storage controller configuration screen

2. On the screen as shown in Figure 83, select the target drive and press Enter.

Figure 83 Virtual Drive Management screen

3. On the screen as shown in Figure 84, select Operation and press Enter. On the dialog box that appears, select Reconfigure Virtual Drive and press Enter.

Figure 84 Operation screen

4. On the screen as shown in Figure 85, select Go and press Enter.

Figure 85 Selecting Go

5. On the screen as shown in Figure 86, set the RAID level, select Choose the Operation, and then press Enter.

Figure 86 Choose the operation

6. On the screen as shown in Figure 87, select the target drives. ([Enabled] following a drive means that the drive has been selected.) Then, select Apply Changes and press Enter.

Figure 87 Adding drives

7. On the screen as shown in Figure 88, select Confirm and press Enter. On the dialog box that opens, select Enabled and press Enter. Then, select Yes and press Enter.

Figure 88 Confirming the operation

8. On the screen as shown in Figure 89, select Start Operation, and then press Enter.

Figure 89 Start the operation

9. On the screen as shown in Figure 90, select OK, and then press Enter.

Figure 90 Selecting OK

10. On the screen as shown in Figure 91, you can view the migration progress.

Figure 91 Viewing the migration progress

Clearing RAID array information on the drive

This task allows you to clear remaining RAID array information on the drive for reconfiguring RAID array on the drive. The task typically applies to drives in Unconfigured Bad state.

To clear RAID array information on the drive:

1. Switch the drive state from Unconfigured Bad to Unconfigured Good. For more information, see "Switching the drive state."

2. On the storage controller configuration screen as shown in Figure 92, select Configuration Management and press Enter.

Figure 92 Storage controller configuration screen

3. On the screen as shown in Figure 93, select Manage Foreign Configuration and press Enter.

Figure 93 Selecting Manage Foreign Configuration

4. On the screen as shown in Figure 94, select Clear Foreign Configuration and press Enter.

Figure 94 Selecting Clear Foreign Configuration

5. On the screen as shown in Figure 95, select Confirm and press Enter. On the dialog box that opens, select Enabled and press Enter. Then, select Yes and press Enter.

Figure 95 Confirming the operation

When the operation is complete, the screen as shown in Figure 96 opens.

Figure 96 Completing the operation

Hiding a virtual drive

This task allows you to hide a virtual drive to avoid unintentional deletion.

To hide a virtual drive:

1. On the storage controller configuration screen as shown in Figure 97, select Virtual Drive Management and press Enter.

Figure 97 Storage controller configuration screen

2. On the screen as shown in Figure 98, select the target drive and press Enter.

Figure 98 Virtual Drive Management screen

3. On the screen as shown in Figure 99, select Operation and press Enter. On the dialog box that appears, select Hide Virtual Drive and press Enter.

Figure 99 Operation screen

Hiding a RAID array

This task allows you to hide a RAID array to avoid unintentional deletion. If you hide a RAID array, all the virtual drives of the RAID array are hidden.

To hide a RAID array:

1. On the storage controller configuration screen as shown in Figure 100, select Virtual Drive Management and press Enter.

Figure 100 Storage controller configuration screen

2. On the screen as shown in Figure 101, select the target drive and press Enter.

Figure 101 Virtual Drive Management screen

3. On the screen as shown in Figure 102, select Operation and press Enter. On the dialog box that appears, select Hide Drive Group and press Enter.

Figure 102 Operation screen

Upgrading the storage controller firmware online

To use a USB drive for the firmware upgrade, save the firmware file in the root directory or a level-1 folder of the USB drive.

To upgrade the storage controller firmware online:

1. On the Advanced screen as shown in Figure 103, select Update Firmware and press Enter.

Figure 103 Advanced screen

2. On the screen as shown in Figure 104, select the directory of the target firmware and press Enter.

Figure 104 Selecting directory

3. On the screen as shown in Figure 105, select the image file of the target firmware and press Enter.

Figure 105 Selecting image

4. On the screen as shown in Figure 106, select Update and press Enter.

Figure 106 Selecting Update

5. On the screen as shown in Figure 107, select Confirm and press Enter. On the dialog box that opens, select Enabled and press Enter. Then, select Yes and press Enter.

CAUTION:

After confirming the upgrade, the screen is stuck for a short time during which the firmware is being upgraded. Do not perform any other operations during this time.

Figure 107 Confirming the operation

6. On the screen as shown in Figure 108, select OK and press Enter.

Figure 108 Completing the operation

7. Restart the BIOS for the operation to take effect.

Switching the storage controller mode

1. On the Advanced menu, select Main Menu and press Enter.

Figure 109 Selecting Main Menu

2. Select Controller Management and press Enter.

Figure 110 Selecting Controller Management

3. Select Advanced Controller Management and press Enter.

Figure 111 Selecting Advanced Controller Management

4. Select Manage Personality Mode and press Enter.

Figure 112 Selecting Manage Personality Mode

As shown in Figure 113, the storage controller is now is RAID mode. To switch the controller to JBOD mode, select Switch to JBOD Mode and press Enter.

Figure 113 Switching the controller to JBOD mode

5. Select Confirm to enable the specified mode, select Yes and then press Enter.

CAUTION:

When switching the storage controller to JBOD mode, you can also change logical drives managed by the controller to JBOD mode at the same time. Be careful that data might be cleared for logical drives that do not support JBOD mode once you switch the mode. As a best practice, set drive state to Unconfigured Good before you switch the mode of any LSI storage controller. For example, logical drives in RAID 5, RAID 6, RAID 50, or RAID 60 managed by RAID-LSI-9560-LP-8i-4GB storage controller do not support JBOD mode and will be cleared if you switch their mode. For more information, see the screen prompt.

Figure 114 Confirming the mode switching

6. Select OK and press Enter to reboot the operating system for the change to take effect.

Figure 115 Completing the mode switching

Forcing a logical drive to come online

When the number of faulty drives exceeds the tolerance range of the logical drive fault-tolerant method, the management tool interface displays the state of logical drives as Offline. In this case, you can use this feature to force logical drives to come online.

CAUTION:

Using this function may change data in the logical drive. Before forcing a logical drive to come online, perform an evaluation task to determine whether the operation can be performed.

To force a logical drive to come online:

1. On the storage controller screen, select Virtual Drive Management and then press Enter.

Figure 116 Storage controller screen

2. Select the target logical drive, and then press Enter.

Figure 117 Virtual Drive Management screen

3. Select View Associated Drives and then press Enter.

Figure 118 Selecting View Associated Drives

4. Select the target offline member drive, enable the drive, select View Drive Properties, and then press Enter.

Figure 119 Selecting View Drive Properties

5. Select Operation, press Enter, select Place Drive Online, and then press Enter again.

Figure 120 Selecting Place Drive Online

6. Select Go and then press Enter.

Figure 121 Selecting Go

7. Select Confirm, set this field to Enabled, select Yes, and then press Enter.

Figure 122 Confirming the configuration

Figure 123 Operation succeeded

Setting alarm control

Perform this task to enable or disable alarm control.

1. On the storage controller configuration page, select Controller Management and then press Enter.

Figure 124 Storage controller configuration screen

2. On the Controller Management screen, select Advanced Controller Properties and press Enter.

Figure 125 Controller Management screen

3. On the Advanced Controller Properties screen, select Alarm Control and press Enter. Then, select Enabled or Disabled and press Enter.

NOTE:

The buzzer has been removed from the LSI9560/9540 controller. The Alarm Control option is not available for the controller.

Figure 126 Drive management screen

Silencing the buzzer

1. Access the Advanced tab, select the target storage controller (such as AVAGO MegaRAID<AVAGO MegaRAID SAS 9361-8i>) and then press Enter.

Figure 127 Advanced screen

2. Select Silence Alarm and press Enter.

Figure 128 Selecting Silence Alarm

Configuring RAID arrays in legacy mode

This section describes how to configure RAID arrays through a storage controller in legacy mode. For more information about how to enter the BIOS and set the boot mode to legacy, see the BIOS user guide for the server.

Only the LSI-9361 series storage controllers support RAID array configuration in legacy mode. The other storage controllers support displaying managed physical drives and logical drives on the POST screen in legacy mode, but do not support accessing the storage controller configuration screen.

RAID array configuration tasks at a glance

To configure a RAID array in legacy, perform the following tasks:

· Accessing the storage controller configuration screen

· Switching the drive state

· Configuring a RAID array

· (Optional.) Configuring hot spare drives

· (Optional.) Deleting a RAID array

· (Optional.) Locating drives

· (Optional.) Initializing a virtual drive

· (Optional.) Erasing drives

· (Optional.) Expanding a RAID array

· (Optional.) Clearing RAID array information on the drive

· (Optional.) Configuring boot options

Accessing the storage controller configuration screen

1. During server POST, press Ctrl+R as prompted as shown in Figure 129.

Figure 129 Pressing Ctrl+R

2. On the screen as shown in Figure 130, follow the instructions at the bottom of the screen to navigate through screens and modify settings.

Figure 130 LSI RAID management screen

Switching the drive state

The storage controller supports the following drive states:

· Unconfigured Good—The drive is normal and can be used for RAID array or hot backup configuration.

· Unconfigured Bad—The drive is faulty or has RAID array information remaining on it. If the drive is faulty, replace the drive. If the drive has RAID array information remaining on it, clear the information.

· Hotspare—The drive is a hot spare drive.

· JBOD—Just a Bunch Of Drives. The drive is a passthrough drive and does not support RAID configuration.

To switch from Unconfigured Bad state to Unconfigured Good state:

1. On the PD Mgmt screen as shown in Figure 131, select the target drive and press F2.

Figure 131 Selecting the target drive

2. On the screen as shown in Figure 132, select Make unconfigured good and press Enter.

Figure 132 Selecting Make unconfigured good

Configuring a RAID array

1. On the VD Mgmt screen as shown in Figure 133, press F2 and select Create Virtual Drive.

Figure 133 Selecting Create Virtual Drive

2. On the screen as shown in Figure 134, set the RAID level and press Enter.

Figure 134 Setting the RAID level

3. On the screen as shown in Figure 135, select the target drive and press Enter.

Figure 135 Selecting the target drive

4. On the screen as shown in Figure 136, specify the size and name, select Advanced, and then press Enter.

Figure 136 Specifying the RAID array name and size

5. On the screen as shown in Figure 137, configure the parameters, select OK, and then press Enter. For more information about the parameter description, see Table 4.

Figure 137 Configuring advanced RAID array parameters

6. On the screen as shown in Figure 138, select OK, and then press Enter.

Figure 138 Confirming the creation

7. On the screen as shown in Figure 139, select the target RAID array and press Enter. You can view the detailed information about the RAID array, including name, level, and drive information.

Figure 139 Viewing RAID array information

Configuring hot spare drives

For data security purposes, configure hot spare drives after configuring a RAID array. You can configure a global hot spare drive or dedicated hot spare drive.

NOTE:

· A hot spare drive can be used only for RAID levels with redundancy.

· The capacity of the hot spare drive must be equal to or greater than the capacity of the smallest drive in the RAID array.

· Only the drive in Unconfigured Good state can be configured as a hot spare drive.

Configuring a global hot spare drive

1. On the PD Mgmt screen as shown in Figure 140, select the target drive and press F2.

Figure 140 Selecting the target drive

2. On the screen as shown in Figure 141, select Make Global HS and press Enter.

Figure 141 Selecting Make Global HS

3. On the screen as shown in Figure 142, you can view global hot spare drive information by selecting the target drive.

Figure 142 Viewing global hot spare drive information

Configuring a dedicated hot spare drive

NOTE:

This section describes the procedure for configuring a dedicated hot spare drive when creating a RAID array.

1. On the VD Mgmt screen, press F2 and then select Manage Ded.HS.

2. On the screen as shown in Figure 143, select the target drive, select Advanced, and then press Enter.

Figure 143 Selecting the target virtual drive

3. On the screen as shown in Figure 144, select Configure HotSpare, select OK, and then press Enter.

Figure 144 Selecting Configure HotSpare

4. On the screen as shown in Figure 145, select the target drive, select OK, and then press Enter.

Figure 145 Selecting the target drive

Deleting a RAID array

1. On the VD Mgmt screen as shown in Figure 146, select the target drive and press F2.

Figure 146 Selecting the target drive

2. On the screen as shown in Figure 147, select Delete VD and press Enter.

Figure 147 Selecting Delete VD

3. On the screen as shown in Figure 148, select YES and press Enter.

Figure 148 Confirming the operation

Locating drives

This task allows you to locate a physical drive.

To locate drives:

1. On the PD Mgmt screen as shown in Figure 149, select the target drive and press F2.

Figure 149 Selecting the target drive

2. On the screen as shown in Figure 150, select Locate > Start. The Fault/UID LED on the drive turns steady blue. To stop locating drives, select Locate > Stop.

Figure 150 Selecting Locate > Start

Initializing a virtual drive

This task allows you to initialize a virtual drive to be used by operating systems.

To initialize a virtual drive:

1. On the VD Mgmt screen as shown in Figure 151, select the target drive and press F2.

Figure 151 Selecting the target drive

2. On the screen as shown in Figure 152, select Initialization > Start FGI.

Figure 152 Selecting Initialization > Start FGI

NOTE:

· Background Initialization (BGI) first initializes part of the RAID array space for data write operations, and initializes the rest of the RAID array space in the background.

· Full Ground Initialization (FGI) initializes the entire RAID array space. Data write operations can be performed only when the initialization is complete.

3. On the screen as shown in Figure 153, select YES and press Enter.

Figure 153 Confirming the operation

Erasing drives

CAUTION:

To avoid drive failure, do not perform other operations when erasing a physical drive.

This task allows you to erase physical and logical drives.

Erasing a physical drive

1. On the PD Mgmt screen as shown in Figure 154, select the target drive and press F2.

Figure 154 Selecting the target drive

2. On the screen as shown in Figure 155, select the erase mode (the default Simple mode is recommended) and press Enter.

Figure 155 Selecting the erase mode

3. On the screen as shown in Figure 156, select Yes and press Enter.

Figure 156 Confirming the operation

Erasing a logical drive

1. On the VD Mgmt screen as shown in Figure 157, select the target drive and press F2.

Figure 157 Selecting the target drive

2. On the screen as shown in Figure 158, select the erase mode (the default Simple mode is recommended) and press Enter.

Figure 158 Selecting the erase mode

3. On the screen as shown in Figure 159, select YES and press Enter.

Figure 159 Confirming the operation

Expanding a RAID array

This task allows you to expand the RAID array capacity by setting the percentage of available capacity for logical drives.

NOTE:

The LSI 9440&9460&9540&9560 controller supports migration and scale-up in UEFI mode or the operating system only when the RAID level is 0, 1, 5, or 6.

To expand a RAID array:

1. On the VD Mgmt screen as shown in Figure 160, select the target drive and press F2.

Figure 160 Selecting the target drive

2. On the screen as shown in Figure 161, select Expand VD size and press Enter.

Figure 161 Selecting Expand VD size

3. On the screen as shown in Figure 162, modify the value for Enter a percentage of available capacity as needed, select Resize, and then press Enter.

Figure 162 Setting the percentage of available capacity

Clearing RAID array information on the drive

This task allows you to clear remaining RAID array information on the drive for reconfiguring RAID array on the drive.

To clear RAID array information on the drive:

1. Switch the drive state from Unconfigured Bad to Unconfigured Good. For more information, see "Switching the drive state."

2. On the Foreign View screen as shown in Figure 163, select the target storage controller and press F2. Select Foreign Config > Clear and press Enter.

Figure 163 Selecting Foreign Config > Clear

3. On the dialog box that appears as shown in Figure 164, select OK and press Enter.

Figure 164 Confirming the operation

Configuring boot options

1. On the Ctrl Mgmt screen as shown in Figure 165, select the target physical drive or logical drive as the boot device and then press Enter.

Figure 165 Selecting the boot device

2. Select APPLY and then press Enter as shown in Figure 166.

Figure 166 Confirming the operation

Downloading and installing StorCLI

This section introduces the download and installation steps of the OS command line tool. You can use the OS command line tool to manage storage controllers during normal server operation without restarting the server.

Downloading StorCLI

1. Access https://www.h3c.com/cn/BizPortal/DownLoadAccessory/DownLoadAccessoryFilt.aspx.

2. Download the installation package and release notes for the corresponding storage controller firmware as instructed.

3. Decompress the installation package to obtain the StorCLI tool package for different operating systems.

Installing StorCLI

See the release notes to install StorCLI for the corresponding operating system.

Commonly-used commands in StorCLI

This section describes the usage and examples of commonly used commands in StorCLI. You can use the OS command line tool to manage storage controllers during normal server operation without restarting the server.

NOTE:

Commands related to the specified path in this tool do not support spaces and special characters.

Viewing storage controller information

Perform this task to view basic information about an LSI storage controller.

Syntax

storcli64 /ccontroller_id show [logfile=logfilename]

storcli64 /ccontroller_id show all [logfile=logfilename]

Parameters

controller_id: Specifies the ID of a storage controller. If only one storage controller exists, the ID is 0 by default. If multiple storage controllers exist, use the storcli64 /call show command to view the controller ID. To view information about all storage controllers, specify the controller ID as all.

logfilename: Specifies the name of the exported file used to save the filtered information.

Examples

# View basic information about a storage controller.

[root@localhost ~]# storcli64 /c0 show

Generating detailed summary of the adapter, it may take a while to complete.

CLI Version = 007.2408.0000.0000 Nov 15, 2022

Operating system = Linux 4.18.0-193.el8.x86_64

Controller = 0

Status = Success

Description = None

Product Name = MegaRAID 9560-8i 4GB

Serial Number = SK01065334

SAS Address = 500062b2024fe0c0

PCI Address = 00:4b:00:00

System Time = 11/09/2023 14:38:46

Mfg. Date = 03/04/20

Controller Time = 11/09/2023 06:38:47

FW Package Build = 52.24.0-4763

BIOS Version = 7.24.01.0_0x07180100

FW Version = 5.240.02-3768

Driver Name = megaraid_sas

Driver Version = 07.726.02.00

Current Personality = RAID-Mode

Vendor Id = 0x1000

Device Id = 0x10E2

SubVendor Id = 0x1000

SubDevice Id = 0x4010

Host Interface = PCI-E

Device Interface = SAS-12G

Bus Number = 75

Device Number = 0

Function Number = 0

Domain ID = 0

Security Protocol = None

Drive Groups = 1

TOPOLOGY :

========

-----------------------------------------------------------------------------

DG Arr Row EID:Slot DID Type State BT Size PDC PI SED DS3 FSpace TR

-----------------------------------------------------------------------------

0 - - - - RAID1 Optl N 893.750 GB dflt N N none N N

0 0 - - - RAID1 Optl N 893.750 GB dflt N N none N N

0 0 0 249:0 31 DRIVE Onln N 893.750 GB dflt N N none - N

0 0 1 249:1 30 DRIVE Onln N 893.750 GB dflt N N none - N

-----------------------------------------------------------------------------

DG=Disk Group Index|Arr=Array Index|Row=Row Index|EID=Enclosure Device ID

Pdgd=Partially degraded|Offln=Offline|BT=Background Task Active

PDC=PD Cache|PI=Protection Info|SED=Self Encrypting Drive|Frgn=Foreign

DS3=Dimmer Switch 3|dflt=Default|Msng=Missing|FSpace=Free Space Present

TR=Transport Ready

Virtual Drives = 1

VD LIST :

=======

---------------------------------------------------------------

DG/VD TYPE State Access Consist Cache Cac sCC Size Name

---------------------------------------------------------------

0/235 RAID1 Optl RW No RWBD - ON 893.750 GB

---------------------------------------------------------------

VD=Virtual Drive| DG=Drive Group|Rec=Recovery

Cac=CacheCade|OfLn=OffLine|Pdgd=Partially Degraded|Dgrd=Degraded

B=Blocked|Consist=Consistent|R=Read Ahead Always|NR=No Read Ahead|WB=WriteBack

AWB=Always WriteBack|WT=WriteThrough|C=Cached IO|D=Direct IO|sCC=Scheduled

Check Consistency

JBOD Drives = 12

JBOD LIST :

=========

---------------------------------------------------------------------------------------

ID EID:Slt DID State Intf Med Size SeSz Model Vendor Port

---------------------------------------------------------------------------------------

4 249:4 32 Onln SATA HDD 7.277 TB 512B HGST HUS728T8TALE6L4 ATA C0.0 & C0.1

5 249:5 9 Onln SATA HDD 7.277 TB 512B HGST HUS728T8TALE6L4 ATA C0.0 & C0.1

6 249:6 1 Onln SAS HDD 7.277 TB 512B HUS728T8TAL5204 HGST C0.0 & C0.1

7 249:7 33 Onln SATA HDD 7.277 TB 512B HGST HUS728T8TALE6L4 ATA C0.0 & C0.1

8 249:8 16 Onln SATA HDD 7.277 TB 512B HGST HUS728T8TALE6L4 ATA C0.0 & C0.1

9 249:9 22 Onln SATA HDD 7.277 TB 512B HGST HUS728T8TALE6L4 ATA C0.0 & C0.1

10 249:10 17 Onln SATA HDD 7.277 TB 512B HGST HUS728T8TALE6L4 ATA C0.0 & C0.1

11 249:11 11 Onln SATA HDD 7.277 TB 512B HGST HUS728T8TALE6L4 ATA C0.0 & C0.1

12 249:12 20 Onln SATA HDD 7.277 TB 512B HGST HUS728T8TALE6L4 ATA C0.0 & C0.1

13 249:13 13 Onln SATA HDD 7.277 TB 512B HGST HUS728T8TALE6L4 ATA C0.0 & C0.1

14 249:14 12 Onln SATA HDD 7.277 TB 512B HGST HUS728T8TALE6L4 ATA C0.0 & C0.1

15 249:15 21 Onln SATA HDD 7.277 TB 512B HGST HUS728T8TALE6L4 ATA C0.0 & C0.1

---------------------------------------------------------------------------------------

ID=JBOD Target ID|EID=Enclosure Device ID|Slt=Slot No|DID=Device ID|Onln=Online

Offln=Offline|Intf=Interface|Med=Media Type|SeSz=Sector Size

SED=Self Encryptive Drive|PI=Protection Info|Sp=Spun|U=Up|D=Down

Physical Drives = 14

PD LIST :

=======

---------------------------------------------------------------------------------------

EID:Slt DID State DG Size Intf Med SED PI SeSz Model Sp Type

---------------------------------------------------------------------------------------

249:0 31 Onln 0 893.750 GB SATA SSD N N 512B Micron_5300_MTFDDAK960TDS U -

249:1 30 Onln 0 893.750 GB SATA SSD N N 512B Micron_5300_MTFDDAK960TDS U -

249:4 32 Onln - 7.277 TB SATA HDD N N 512B HGST HUS728T8TALE6L4 U JBOD

249:5 9 Onln - 7.277 TB SATA HDD N N 512B HGST HUS728T8TALE6L4 U JBOD

249:6 1 Onln - 7.277 TB SAS HDD N N 512B HUS728T8TAL5204 U JBOD

249:7 33 Onln - 7.277 TB SATA HDD N N 512B HGST HUS728T8TALE6L4 U JBOD

249:8 16 Onln - 7.277 TB SATA HDD N N 512B HGST HUS728T8TALE6L4 U JBOD

249:9 22 Onln - 7.277 TB SATA HDD N N 512B HGST HUS728T8TALE6L4 U JBOD

249:10 17 Onln - 7.277 TB SATA HDD N N 512B HGST HUS728T8TALE6L4 U JBOD

249:11 11 Onln - 7.277 TB SATA HDD N N 512B HGST HUS728T8TALE6L4 U JBOD

249:12 20 Onln - 7.277 TB SATA HDD N N 512B HGST HUS728T8TALE6L4 U JBOD

249:13 13 Onln - 7.277 TB SATA HDD N N 512B HGST HUS728T8TALE6L4 U JBOD

249:14 12 Onln - 7.277 TB SATA HDD N N 512B HGST HUS728T8TALE6L4 U JBOD

249:15 21 Onln - 7.277 TB SATA HDD N N 512B HGST HUS728T8TALE6L4 U JBOD

---------------------------------------------------------------------------------------

EID=Enclosure Device ID|Slt=Slot No|DID=Device ID|DG=DriveGroup

DHS=Dedicated Hot Spare|UGood=Unconfigured Good|GHS=Global Hotspare

UBad=Unconfigured Bad|Sntze=Sanitize|Onln=Online|Offln=Offline|Intf=Interface

Med=Media Type|SED=Self Encryptive Drive|PI=Protection Info

UGUnsp=UGood Unsupported|UGShld=UGood shielded|HSPShld=Hotspare shielded

CFShld=Configured shielded|Cpybck=CopyBack|CBShld=Copyback Shielded

UBUnsp=UBad Unsupported|Rbld=Rebuild

Enclosures = 1

Enclosure LIST :

==============

-----------------------------------------------------------------------------

EID State Slots PD PS Fans TSs Alms SIM Port# ProdID VendorSpecific

-----------------------------------------------------------------------------

249 OK 28 14 0 1 7 0 0 C0.0 & C0.1 x8 Cub exp-2.1.1.0

-----------------------------------------------------------------------------

EID=Enclosure Device ID | PD=Physical drive count | PS=Power Supply count

TSs=Temperature sensor count | Alms=Alarm count | SIM=SIM Count | ProdID=Product ID

Cachevault_Info :

===============

------------------------------------

Model State Temp Mode MfgDate

------------------------------------

CVPM05 Optimal 27C - 2019/09/18

------------------------------------

# View all information about a storage controller and save the information to the specified file.

[root@localhost ~]# storcli64 /c0 show all logfile=logfile.txt

Switching the storage controller mode

Perform this task to switch the storage controller mode.

Syntax

storcli64 /ccontroller_id set personality =mode

Default

A storage controller operates in RAID mode.

Parameters

mode: Specifies the controller mode. Options include:

· raid: Specifies the RAID mode.

· jbod: Specifies the JBOD mode.

Usage guidelines

· Before switching the controller mode to JBOD, make sure the storage controller is using the most recent version. Lower versions may not support the JBOD mode.

· Before using this command, make sure all drives managed by the storage controller are in Unconfigured Good state.

· For the configuration to take effect, you must restart the operating system after executing the command.

Examples

# Switch the storage controller mode to JBOD.

[root@localhost home]# ./storcli64 /c0 set personality=jbod

CLI Version = 007.1017.0000.0000 May 10, 2019

Operating system = Linux 4.18.0-193.el8.x86_64

Controller = 0

Status = Success

Description = None

Controller Properties :

=====================

------------------------------------------------------------------------

Ctrl_Prop Value

------------------------------------------------------------------------

Set Personality JBOD (Reboot the system for the change to take effect.)

------------------------------------------------------------------------

Updating the firmware

Perform this task to upgrade, downgrade, or update the firmware of a storage controller.

Syntax

To upgrade the firmware:

storcli64 /ccontroller_id download file= fw_file

To downgrade or update the firmware:

storcli64 /ccontroller_id download file= fw_file noverchk

Parameters

fw_file: Specifies the firmware file name.

noverchk: Configures the system not to check the firmware image version when downgrading or updating the storage controller firmware.

Usage guidelines

If the firmware file does not exist in the current path, you must add the absolute path to the file name.

Examples

# Upgrade the storage controller firmware.

[root@localhost home]# ./storcli64 /c0 download file=MR_4MB.rom noverchk

Download Completed.

Flashing image to adapter...

CLI Version = 007.1017.0000.0000 May 10, 2019

Operating system = Linux 4.18.0-193.el8.x86_64

Controller = 0

Status = Success

Description = F/W Flash Completed. Please reboot the system for the changes to take effect

# Downgrade or update the firmware.

[root@localhost home]# ./storcli64 /c0 download file=MR_4MB.rom noverchk

Download Completed.

Flashing image to adapter...

CLI Version = 007.1017.0000.0000 May 10, 2019

Operating system = Linux 4.18.0-193.el8.x86_64

Controller = 0

Status = Success

Description = F/W Flash Completed. Please reboot the system for the changes to take effect

Creating and deleting RAID arrays

Perform this task to create and delete RAID arrays.

Syntax

To create a RAID array:

storcli64 /ccontroller_id add vd rraid_level [size=<vd1_size>,..] [name=<vdname1>,..] drives= vd_drives [pdperarray= pdperarraynum] [pdcache=pdcache_policy] [pi] [wt|wb|awb] [nora|ra] [strip=strip_size] [emulationtype=emulationtype] [spares =spares_drives]

To delete a RAID array:

storcli64 /ccontroller_id/vraid_id del

Parameters

raid_level: Specifies the RAID level. Options include 0, 1, 5, 6, 00, 10, 50, and 60.

vd1_size: Specifies the capacity of the RAID array, in gb. If you specify all, it indicates that the array can use all the available capacity.

vdname1: Specify the name of the logical drive.

vd_drives: Specifies member drives. The name of each member drive must be in the enclosure_id:slot_id format, where enclosure_id represents the ID the enclosure in which the drive resides, and slot_id represents the drive slot ID.

pdperarraynum: Specifies the number of drives in the sub-group if the RAID level is 10, 50, or 60.

pdcache_policy: Specifies the cache state for member drives. Options include on, off, and default. Setting this field to default represents retaining the current cache state.

pi: Enables data protection.

wt|wb|awb: Specifies the write cache policy. Write through (wt) notifies the system of transmission completion when data are written into disks. Write back (wb) notifies the system of transmission completion when data are written into the controller cache. Always write back (awb) forces the system to use write back when no supercapacitor is present, which may cause data loss in the event of unexpected power-off.

nora|ra: Specifies the read cache policy. When reading data from RAID, the ra policy enables the system to read the surrounding data and store them in the cache at the same time. When the user accesses these data subsequently, they can can be directly read from the cache, which reduces the disk seeking time and improves read performance.

strip_size: Specifies the strip size. For an MR controller, options include 8, 16, 32, 64, 128, 256, 512, and 1024. For an iMR controller, only 64 is supported. Among all the controllers supported by this document, only the HBA-LSI-9440-8i is an iMR controller.

emulationtype: Options include 0, 1, and 2. By default, the value is 0. 0: Displays the sector size as 512e if member drives include a 512e drive, and 512n if member drives do not include 512e drives. 1: Displays the sector size 512n if member drives do not include 512e drives. 2: Displays the sector size as 512e even if member drives do not include 512e drives.

spares_drives: Specifies hot spare drives. The name of each hot spare drive is in the format of enclosure_id:slot_id.

raid_id: Specifies the ID of the RAID array to be deleted. To obtain the ID, use the ./storcli64 /c0/vall show command. If you specify this field to all, the command deletes all the RAID arrays.

Usage guidelines

When you specify member drives, use a comma (,) to separate two slots and use a hyphen (-) to indicate a slot range.

Examples

# Create RAID 1.

[root@localhost home]# ./storcli64 /c0 add vd r1 size=all drives=2:8,23

CLI Version = 007.1017.0000.0000 May 10, 2019

Operating system = Linux 4.18.0-193.el8.x86_64

Controller = 0

Status = Success

Description = Add VD Succeeded

[root@localhost home]# ./storcli64 /c0/v0 del

CLI Version = 007.1017.0000.0000 May 10, 2019

Operating system = Linux 4.18.0-193.el8.x86_64

Controller = 0

Status = Success

Description = Delete VD succeeded

Locating a physical drive

Perform this task to turn on or turn off the UID LED of a physical drive.

Syntax

storcli64 /ccontroller_id/eenclosure_id/sslot_id action locate

Parameters

enclosure_id: Specifies the enclosure ID. If you specify this field as all, the command turns on the UID LEDs for all drives in all enclosures.

slot_id: Specifies the ID of the physical drive slot. If you specify this field as all, the command turns on the UID LEDs for all drives in the enclosure.

action: Specifies the action to take. Options include:

· start: Turn on the UID LED.

· stop: Turn off the UID LED.

Examples

# Turn on the drive UID LED.

[root@localhost home]# ./storcli64 /c0/e2/s8 start locate

CLI Version = 007.1017.0000.0000 May 10, 2019

Operating system = Linux 4.18.0-193.el8.x86_64

Controller = 0

Status = Success

Description = Start Drive Locate Succeeded.

# Turn off the drive UID LED.

[root@localhost home]# ./storcli64 /c0/e2/s8 stop locate

CLI Version = 007.1017.0000.0000 May 10, 2019

Operating system = Linux 4.18.0-193.el8.x86_64

Controller = 0

Status = Success

Description = Stop Drive Locate Succeeded.

Viewing the JBOD state

Perform this task to view the enabling status of the JBOD function for a storage controller.

Syntax

storcli64 /ccontroller_id jbod

Parameters

Examples

# View the JBOD state.

[root@localhost home]# ./storcli64 /c0 show jbod

CLI Version = 007.1316.0000.0000 Mar 12, 2020

Operating system = Linux 3.10.0-862.el7.x86_64

Controller = 0

Status = Success

Description = None

Controller Properties :

=====================

----------------

Ctrl_Prop Value

----------------

JBOD ON

----------------

Setting the JBOD state

Perform this task to enable or disable the JBOD function for a storage controller in RAID mode.

Syntax

storcli64 /ccontroller_id set jbod=mode

Default

The JBOD function is disabled in RAID mode.

Parameters

mode: Specifies the action to take. Options include:

· on: Enable JBOD.

· off: Disable JBOD.

Usage guidelines

This feature is supported only by the 9361, 9460, 9440, and 9540 controllers.

Examples

# Enable JBOD.

[root@localhost home]# ./storcli64 /c0 set jbod=on

CLI Version = 007.1017.0000.0000 May 10, 2019

Operating system = Linux 4.18.0-193.el8.x86_64

Controller = 0

Status = Success

Description = None

Controller Properties :

=====================

----------------

Ctrl_Prop Value

----------------

JBOD ON

----------------

# Disable JBOD.

[root@localhost home]# ./storcli64 /c0 set jbod=off

CLI Version = 007.1017.0000.0000 May 10, 2019

Operating system = Linux 4.18.0-193.el8.x86_64

Controller = 0

Status = Success

Description = None

Controller Properties :

=====================

----------------

Ctrl_Prop Value

----------------

JBOD OFF

----------------

Switching the drive state

Perform this task to switch the drive state between JBOD and Unconfigured Good.

Syntax

storcli64 /ccontroller_id/eenclosure_id/sslot_id set good [force]

storcli64 /ccontroller_id/eenclosure_id/sslot_id set jbod

Parameters

enclosure_id: Specifies the enclosure ID.

slot_id: Specifies the ID of the physical drive slot.

Usage guidelines

Before switching the drive state from Unconfigured Good to JBOD, make sure the JBOD function is enabled for the storage controller.

Examples

# Switch the drive state to Unconfigured Good.

[root@localhost home]# ./storcli64 /c0/e2/s8 set good force

CLI Version = 007.1017.0000.0000 May 10, 2019

Operating system = Linux 4.18.0-193.el8.x86_64

Controller = 0

Status = Success

Description = Set Drive Good Succeeded.

# Switch the drive state to JBOD.

[root@localhost home]# ./storcli64 /c0/e2/s8 set jbod

CLI Version = 007.1017.0000.0000 May 10, 2019

Operating system = Linux 4.18.0-193.el8.x86_64

Controller = 0

Status = Success

Description = Set Drive JBOD Succeeded.

Viewing drive information

Perform this task to view basic drive information.

Syntax

storcli64 /ccontroller_id/eenclosure_id/sslot_id show [all]

Parameters

enclosure_id: Specifies the enclosure ID.

slot_id: Specifies the ID of the physical drive slot.

Examples

[root@localhost home]# ./storcli64 /c0/e2/s8 show

CLI Version = 007.1017.0000.0000 May 10, 2019

Operating system = Linux 4.18.0-193.el8.x86_64

Controller = 0

Status = Success

Description = Show Drive Information Succeeded.

Drive Information :

=================

-------------------------------------------------------------------------------

EID:Slt DID State DG Size Intf Med SED PI SeSz Model Sp Type

-------------------------------------------------------------------------------

2:8 39 JBOD - 5.458 TB SATA HDD N N 512B ST6000NM0115-1YZ110 U -

-------------------------------------------------------------------------------

EID=Enclosure Device ID|Slt=Slot No.|DID=Device ID|DG=DriveGroup

DHS=Dedicated Hot Spare|UGood=Unconfigured Good|GHS=Global Hotspare

UBad=Unconfigured Bad|Onln=Online|Offln=Offline|Intf=Interface

Med=Media Type|SED=Self Encryptive Drive|PI=Protection Info

UGUnsp=Unsupported|UGShld=UnConfigured shielded|HSPShld=Hotspare shielded

CFShld=Configured shielded|Cpybck=CopyBack|CBShld=Copyback Shielded

UBUnsp=UBad Unsupported

Importing and exporting RAID configuration

Perform this task to save, restore, or import RAID configuration.

Syntax

storcli64 /ccontroller_id get config file=filename

storcli64 /ccontroller_id set config file=filename

Parameters

filename: Specifies the configuration file name.

Usage guidelines

Before performing this task, make sure the server environments are identical for the source and target servers.

For the LSI 9361/9460 in JBOD mode and the LSI 9560 controller in any mode, you must first configure all drives to be in Unconfigured Good state before importing any RAID configuration.

Examples

# Export RAID configuration.

[root@localhost home]# ./storcli64 /c0 get config file=conf.txt

CLI Version = 007.1017.0000.0000 May 10, 2019

Operating system = Linux 4.18.0-193.el8.x86_64

Controller = 0

Status = Success

Description = Config data is saved to the file

# Import RAID configuration.

[root@localhost home]# ./storcli64 /c0 set config file=conf.txt

CLI Version = 007.1017.0000.0000 May 10, 2019

Operating system = Linux 4.18.0-193.el8.x86_64

Controller = 0

Status = Success

Description = Config data is restored to the adapter

Scaling up RAID

Perform this task to scale up a RAID array.

Syntax

storcli64 /ccontroller_id/vraid_id expand size=target_size

Parameters

raid_id: Specifies the ID of the RAID array to be scaled up.

target_size: Specifies the target capacity size.

Usage guidelines

The LSI 9440&9460&9540&9560 controllers support migration and scaling up in UEFI mode or the OS only when the RAID level is 0, 1, 5, or 6.

Examples

# Scale up the RAID capacity to 20Gb.

[root@localhost home]# ./storcli64 /c0/v0 expand size=20gb

CLI Version = 007.1017.0000.0000 May 10, 2019

Operating system = Linux 4.18.0-193.el8.x86_64

Controller = 0

Status = Success

Description = expansion operation succeeded

EXPANSION RESULT :

================

----------------------------------------------------------------------------

VD Size FreSpc ReqSize AbsUsrSz %FreSpc NewSize Status NoArrExp

----------------------------------------------------------------------------

0 10.000 GB 1.808 TB 20.000 GB 37.049 GB 2 47.049 GB - 1.808 TB

----------------------------------------------------------------------------

Size - Current VD size|FreSpc - Freespace available before expansion

%FreSpc - Requested expansion size in % of available free space

AbsUsrSz - User size rounded to nearest %

Migrating the RAID level

Perform this task to change the RAID level without affecting data integrity.

Syntax

storcli64 /ccontroller_id/vraid_id start migrate type=raidx option=operation drives= vd_drives force

Parameters

raid_id: Specifies the ID of the RAID array to be scaled up.

raidx: Specifies the target RAID level.

operation: Specifies whether to add or remove member drives. Options include add and remove.

Usage guidelines

The LSI 9440&9460&9540&9560 controllers support migration and scaling up in UEFI mode or the OS only when the RAID level is 0, 1, 5, or 6.

Examples

[root@localhost home]# ./storcli64 /c0/v0 start migrate type=raid5 option=add drives=2:11

CLI Version = 007.1017.0000.0000 May 10, 2019

Operating system = Linux 4.18.0-193.el8.x86_64

Controller = 0

Status = Success

Description = Start Reconstruction Operation Success

[root@localhost home]# ./storcli64 /c0/v0 start migrate type=raid0 option=remove drives=2:9

CLI Version = 007.1017.0000.0000 May 10, 2019

Operating system = Linux 4.18.0-193.el8.x86_64

Controller = 0

Status = Success

Description = Start Reconstruction Operation Success

Managing external configuration

Perform this task to import or delete external configuration.

Syntax

storcli64 /ccontroller_id/fall operation

Parameters

operation: Specifies the action to take. Options include:

· import: Import external configuration.

· del: Delete external configuration.

Usage guidelines

If multiple storage controllers exist, use the storcli64 /call show command to obtain a controller ID.

Examples

# Import external configuration.

[root@localhost home]# ./storcli64 /c0/fall import

CLI Version = 007.1017.0000.0000 May 10, 2019

Operating system = Linux 4.18.0-193.el8.x86_64

Controller = 0

Status = Success

Description = Successfully imported foreign configuration

# Delete external configuration.

[root@localhost home]# ./storcli64 /c0/fall del

CLI Version = 007.1017.0000.0000 May 10, 2019

Operating system = Linux 4.18.0-193.el8.x86_64

Controller = 0

Status = Success

Description = Successfully deleted foreign configuration

Configuring hot spare drives

Perform this task to add hot spare drives for a redundant RAID array.

Syntax

storcli64 /ccontroller_id/eenclosure_id/sslot_id add hotsparedrive

storcli64 /ccontroller_id/eenclosure_id/sslot_id add hotsparedrive dgs=drive_group

storcli64 /ccontroller_id/eenclosure_id/sslot_id delete hotsparedrive

Default

If you do not specify the dgs keyword for an add operation, the command adds a global hot spare.

Parameters

enclosure_id: Specifies the enclosure ID.

slot_id: Specifies the ID of the physical drive slot.

drive_group: Specify the drive group ID.

Usage guidelines

· If multiple storage controllers exist, use the storcli64 /call show command to obtain a controller ID.

· Hot spare disks must use consistent interface protocols as the member drives of the RAID array, and must have higher or the same capacity as the member drives.

Examples

# Add a global hot spare.

[root@localhost home]# ./storcli64 /c0/e2/s11 add hotsparedrive

CLI Version = 007.1017.0000.0000 May 10, 2019

Operating system = Linux 4.18.0-193.el8.x86_64

Controller = 0

Status = Success

Description = Add Hot Spare Succeeded.

# Add a dedicated hot spare.

[root@localhost home]# ./storcli64 /c0/e2/s8 add hotsparedrive dgs=0

CLI Version = 007.1017.0000.0000 May 10, 2019

Operating system = Linux 4.18.0-193.el8.x86_64

Controller = 0

Status = Success

Description = Add Hot Spare Succeeded.

# Delete a hot spare.

[root@localhost home]# ./storcli64 /c0/e2/s8 delete hotsparedrive

CLI Version = 007.1017.0000.0000 May 10, 2019

Operating system = Linux 4.18.0-193.el8.x86_64

Controller = 0

Status = Success

Description = Delete Hot Spare Succeeded.

Collecting logs

Perform this task to export storage controller logs. A SnapDump file is a log file that can be automatically generated in scenarios with abnormal RAID controllers. You can obtain the SnapDump log for the current RAID controller.

Syntax

storcli /ccontroller_id show all logfile=logfilename

storcli /ccontroller_id show snapdump

storcli /ccontroller_id get snapdump

storcli /ccontroller_id get snapdump id=all

storcli /ccontroller_id get snapdump id=snapdump_id file= logfilename

storcli /ccontroller_id show alilog logfile=logfilename

storcli /ccontroller_id show events logfile=logfilename

storcli /ccontroller_id show termlog logfile=logfilename

Parameters

logfilename: Specifies the log file name.

snapdump_id: Specifies the SnapDump log ID.

logfilename: Specifies the name of the .zip file into which SnapDump data will be written.

Restrictions and guidelines

· Generating SnapDump data is a resource-intensive operation, which might lead to I/O timeouts. Therefore, leave a minimum of a 10-minute interval between two consecutive get SnapDump requests.

· The LSI9440-8i (any firmware version) and the LSI9540-8i (firmware version earlier than 52.26.0-5014) support only one SnapDump. Each execution of the storcli /ccontroller_id get snapdump command overwrites existing SnapDump data on the controller. If an issue occurs, first execute storcli /ccontroller_id show snapdump to check if SnapDump has been auto-generated.

¡ If SnapDump has been generated, use the storcli /ccontroller_id get snapdump id=all or storcli /ccontroller_id get snapdump id=snapdump_id file= logfilename command to download SnapDump data.

¡ If SnapDump has not been generated, use the storcli /ccontroller_id get snapdump command to trigger the controller to generate new SnapDump data.

· Switching the storage controller mode and updating the firmware will discard all SnapDump data on the DDR and flash.

Table 5 Support for SnapDump

Storage controller	Support for SnapDump	Remarks
LSI9361-8i	No	N/A
LSI9440-8i	Yes	· SnapDump data is saved on the flash. · Only one SnapDump is supported.
LSI9460-8i	Yes	· SnapDump data is saved on the DDR. · If a supercapacitor is in place, the SnapDump data can be retained for up to four reboots. · If no supercapacitor is in place, the SnapDump data will be lost after a reboot.
LSI9460-16i	Yes	· SnapDump data is saved in the cache. · If a supercapacitor is in place, the SnapDump data can be retained for up to four reboots. · If no supercapacitor is in place, the SnapDump data will be lost after a reboot.
LSI9540-8i	Yes	· SnapDump data is saved on the flash. · In a version earlier than 52.26.0-5014, only one SnapDump is supported.
LSI9560-8i	Yes	SnapDump data is saved on the flash.
LSI9560-16i	Yes	SnapDump data is saved on the flash.

Examples

# Display all information of a controller, and save the .txt file that records the information in the specified location.

[root@localhost home]# storcli64 /c0 show all logfile=/log/showall.txt

# Display the current SnapDump properties of the controller and the SnapDump data on the controller.

[root@localhost home]# storcli64 /c0 show snapdump

CLI Version = 007.2612.0000.0000 June 13, 2023

Operating system = Linux 5.14.0-70.22.1.el9_0.x86_64

Controller = 0

Status = Success

Description = None

SnapDump Properties :

===================

-----------------------------------------

Ctrl_Prop Value

-----------------------------------------

Snapdump ON

Snapdump Save Count N/A

Snapdump Delay OCR 15

Snapdump properties Read-Write

Snapdump Preboot Trace Buffer ON

Snapdump Current Count 1

-----------------------------------------

SnapDump Details :

================

----------------------------------------------

ID Snapdump Size Snapdump time OnDemand

----------------------------------------------

0 2492649 09-15-2023 11:43:26 Yes

----------------------------------------------

# Execute the command without specifying any ID to trigger the controller to generate new SnapDump data and download existing SnapDump data from the controller.

[root@localhost home]# storcli64 /c0 get snapdump

CLI Version = 007.2612.0000.0000 June 13, 2023

Operating system = Linux 5.14.0-70.22.1.el9_0.x86_64

Controller = 0

Status = Success

Description = Download Support Log

Snapdump :

========

---------------------------------------

Ctrl Status Ctrl_Prop ErrCd ErrMsg

---------------------------------------

0 Success Get Snapdump 0 -

---------------------------------------

# Download all existing SnapDump data from the controller. The system names the file in the snapdump_c#(controller_id)_id#(snapdump_id)_yy_mm_dd_hh_mm_ss.zip format.

[root@localhost home]# /opt/MegaRAID/storcli/storcli64 /c0 get snapdump id=all

CLI Version = 007.2612.0000.0000 June 13, 2023

Operating system = Linux 3.10.0-1160.el7.x86_64

Controller = 0

Status = Success

Description = None

Snapdump :

========

---------------------------------------

Ctrl Status Ctrl_Prop ErrCd ErrMsg

---------------------------------------

0 Success Get Snapdump 0 -

---------------------------------------

# Specify the SnapDump ID and export SnapDump data to the specified file. If the file already exists, it will be truncated and new information will be added.

[root@localhost home]# storcli64 /c0 get snapdump id=0 file=snapdump.zip

CLI Version = 007.2612.0000.0000 June 13, 2023

Operating system = Linux 5.14.0-70.22.1.el9_0.x86_64

Controller = 0

Status = Success

Description = None

Snapdump :

========

---------------------------------------

Ctrl Status Ctrl_Prop ErrCd ErrMsg

---------------------------------------

0 Success Get Snapdump 0 -

---------------------------------------

# Output the alilog logs to a .txt file and save the file in the specified location.

[root@localhost home]# ./storcli64 /c0 show alilog logfile=/log/alilog.txt

# Output the events logs to a .txt file and save the file in the specified location.

[root@localhost home]# storcli64 /c0 show events logfile=/log/events.txt

# Output the termlog logs to a .txt file and save the file in the specified location.

[root@localhost home]# storcli64 /c0 show termlog logfile=/log/termlog.txt

Managing logs

Perform this task to filter or clear storage controller logs.

Syntax

storcli64 /ccontroller_id show termlog

storcli64 /ccontroller_id show events

storcli64 /ccontroller_id show snapdump

storcli64 /ccontroller_id delete termlog

storcli64 /ccontroller_id delete events

storcli64 /ccontroller_id delete snapdump force

storcli64 /ccontroller_id set snapdump state=on|off

Parameters

controller_id: Specifies the ID of a storage controller. If only one storage controller exists, the ID is 0 by default. If multiple storage controllers exist, use the storcli64 command to view the controller ID.

Examples

# Display TTY logs.

[root@localhost home]# ./storcli64 /c0 show termlog

Firmware Term Log Information on controller 0:

03/13/22 9:12:37: C0:TTY History buffer cleared

CLI Version = 007.1017.0000.0000 May 10, 2019

Operating system = Linux 4.18.0-193.el8.x86_64

Controller = 0

Status = Success

Description = None

# Display event logs.

[root@localhost home]# ./storcli64 /c0 show events

seqNum: 0x00079e17

Time: Sun Mar 13 09:13:18 2022

Code: 0x0000001e

Class: 0

Locale: 0x20

Event Description: Event log cleared

Event Data:

===========

None

CLI Version = 007.1017.0000.0000 May 10, 2019

Operating system = Linux 4.18.0-193.el8.x86_64

Controller = 0

Status = Success

Description = None

Events = GETEVENTS

Controller Properties :

=====================

------------------------------------

Ctrl Status Method Value

------------------------------------

0 Success handleSuboption Events

------------------------------------

# Display the current SnapDump properties of the controller and the SnapDump data on the controller.

[root@localhost 0920]# storcli64 /c0 show snapdump

CLI Version = 007.2612.0000.0000 June 13, 2023

Operating system = Linux 5.14.0-70.22.1.el9_0.x86_64

Controller = 0

Status = Success

Description = None

SnapDump Properties :

===================

-----------------------------------------

Ctrl_Prop Value

-----------------------------------------

Snapdump ON

Snapdump Save Count N/A

Snapdump Delay OCR 15

Snapdump properties Read-Write

Snapdump Preboot Trace Buffer ON

Snapdump Current Count 2

-----------------------------------------

SnapDump Details :

================

----------------------------------------------

ID Snapdump Size Snapdump time OnDemand

----------------------------------------------

0 1643485 09-19-2023 07:03:58 Yes

1 2499469 09-20-2023 06:48:47 Yes

----------------------------------------------

# Clear all records in the TTY logs.

[root@localhost home]# ./storcli64 /c0 delete termlog

CLI Version = 007.1017.0000.0000 May 10, 2019

Operating system = Linux 4.18.0-193.el8.x86_64

Controller = 0

Status = Success

Description = None

Controller Properties :

=====================

----------------------------

Ctrl Method Result

----------------------------

0 Delete Termlog deleted

----------------------------

# Clear all records in the event logs.

[root@localhost home]# ./storcli64 /c0 delete events

CLI Version = 007.1017.0000.0000 May 10, 2019

Operating system = Linux 4.18.0-193.el8.x86_64

Controller = 0

Status = Success

Description = None

Controller Properties :

=====================

---------------------------------

Ctrl Status Method Value

---------------------------------

0 Success DeleteEvents Events

---------------------------------

# Clear all SnapDump data.

[root@localhost 0920]# storcli64 /c0 delete snapdump force

CLI Version = 007.2612.0000.0000 June 13, 2023

Operating system = Linux 5.14.0-70.22.1.el9_0.x86_64

Controller = 0

Status = Success

Description = Snapdump delete

# Disable the SnapDump function.

[root@localhost ~]# storcli64 /c0 set snapdump state=off

CLI Version = 007.2612.0000.0000 June 13, 2023

Operating system = Linux 5.14.0-70.22.1.el9_0.x86_64

Controller = 0

Status = Success

Description = None

Controller Properties :

=====================

-------------------

Ctrl_Prop Value

-------------------

Set Snapdump off

-------------------

# Enable the SnapDump function.

[root@localhost ~]# storcli64 /c0 set snapdump state=on

CLI Version = 007.2612.0000.0000 June 13, 2023

Operating system = Linux 5.14.0-70.22.1.el9_0.x86_64

Controller = 0

Status = Success

Description = None

Controller Properties :

=====================

-------------------

Ctrl_Prop Value

-------------------

Set Snapdump on

-------------------

Configuring RAID cache settings

Perform this task to configure RAID cache settings.

Syntax

storcli64 /ccontroller_id/vraid_id set wrcache={wt|wb|awb}

storcli64 /ccontroller_id/vraid_id set rdcache={ra|nora}

Parameters

raid_id: Specifies the target RAID ID.

{wt|wb|awb}: Specifies the write cache policy. Write through (wt) notifies the system of transmission completion when data are written into disks. Write back (wb) notifies the system of transmission completion when data are written into the controller cache. Always write back (awb) forces the system to use write back when no supercapacitor is present, which may cause data loss in the event of unexpected power-off.

{ra|nora}: Specifies the read cache policy. When reading data from RAID, the ra policy enables the system to read the surrounding data and store them in the cache at the same time. When the user accesses these data subsequently, they can can be directly read from the cache, which reduces the disk seeking time and improves read performance.

Usage guidelines

If multiple storage controllers exist, use the storcli64 /call show command to obtain a controller ID.

Examples

[root@localhost home]# ./storcli64 /c0/v0 set wrcache=awb

CLI Version = 007.1017.0000.0000 May 10, 2019

Operating system = Linux 4.18.0-193.el8.x86_64

Controller = 0

Status = Success

Description = None

Detailed Status :

===============

---------------------------------------

VD Property Value Status ErrCd ErrMsg

---------------------------------------

0 wrCache AWB Success 0 -

---------------------------------------

[root@localhost home]# ./storcli64 /c0/v0 set rdcache=nora

CLI Version = 007.1017.0000.0000 May 10, 2019

Operating system = Linux 4.18.0-193.el8.x86_64

Controller = 0

Status = Success

Description = None

Detailed Status :

===============

---------------------------------------

VD Property Value Status ErrCd ErrMsg

---------------------------------------

0 rdCache NoRA Success 0 -

---------------------------------------

Setting the RAID access policy

Perform this task to configure the read and write permissions for RAID.

Syntax

storcli64 /ccontroller_id/vraid_id set accesspolicy={rw|ro|blocked}

Parameters

raid_id: Specifies the target RAID ID.

{rw|ro|blocked}: Specifies the access policy. rw represents read and write, ro represents read-only, and blocked represents no access.

Usage guidelines

If multiple storage controllers exist, use the storcli64 /call show command to obtain a controller ID.

Examples

# Set the RAID access policy to read-only.

[root@localhost home]# ./storcli64 /c0/v0 set accesspolicy=rw

CLI Version = 007.1017.0000.0000 May 10, 2019

Operating system = Linux 4.18.0-193.el8.x86_64

Controller = 0

Status = Success

Description = None

Detailed Status :

===============

----------------------------------------

VD Property Value Status ErrCd ErrMsg

----------------------------------------

0 AccPolicy RW Success 0 -

----------------------------------------

Setting the read/write cache state for member drives

Perform this task to set the read and write cache state for member drives.

Syntax

storcli64 /ccontroller_id/vraid_id set pdcache= pdcache_policy

Parameters

raid_id: Specifies the target RAID ID.

pdcache_policy: Specifies the cache policy. Options include on, off, and default. Setting this field to default represents retaining the current cache state.

Usage guidelines

If multiple storage controllers exist, use the storcli64 /call show command to obtain a controller ID.

Examples

# Disable the read/write cache.

[root@localhost home]# ./storcli64 /c0/v0 set pdcache=off

CLI Version = 007.1017.0000.0000 May 10, 2019

Operating system = Linux 4.18.0-193.el8.x86_64

Controller = 0

Status = Success

Description = None

Detailed Status :

===============

---------------------------------------

VD Property Value Status ErrCd ErrMsg

---------------------------------------

0 PdCac Off Success 0 -

Viewing the cache state of member drives

Perform this task to view the cache state of member drives.

Syntax

storcli64 /ccontroller_id /eenclosure_id/sslot_id show all

Parameters

enclosure_id: Specifies the enclosure ID.

slot_id: Specifies the ID of the physical drive slot.

Usage guidelines

· If multiple storage controllers exist, use the storcli64 /call show command to obtain a controller ID.

· If you use this command to view the cache state of member drives for the LSI-9361 storage controller, the command output displays Write Cache = N/A.

Examples

# View the cache state of member drives.

[root@localhost ~]# storcli64 /c1 /e252/s10 show all

CLI Version = 007.1705.0000.0000 Mar 31, 2021

Operating system = Linux 4.18.0-193.el8.x86_64

Controller = 1

Status = Success

Description = Show Drive Information Succeeded.

Drive /c1/e252/s10 :

==================

---------------------------------------------------------------------------------

EID:Slt DID State DG Size Intf Med SED PI SeSz Model Sp Type

---------------------------------------------------------------------------------

252:10 20 Onln 0 893.750 GB SATA SSD N N 512B INTEL SSDSC2KB960G8 U -

---------------------------------------------------------------------------------

EID=Enclosure Device ID|Slt=Slot No|DID=Device ID|DG=DriveGroup

DHS=Dedicated Hot Spare|UGood=Unconfigured Good|GHS=Global Hotspare

UBad=Unconfigured Bad|Sntze=Sanitize|Onln=Online|Offln=Offline|Intf=Interface

Med=Media Type|SED=Self Encryptive Drive|PI=Protection Info

UGUnsp=UGood Unsupported|UGShld=UGood shielded|HSPShld=Hotspare shielded

CFShld=Configured shielded|Cpybck=CopyBack|CBShld=Copyback Shielded

UBUnsp=UBad Unsupported|Rbld=Rebuild

Drive /c1/e252/s10 - Detailed Information :

=========================================

Drive /c1/e252/s10 State :

========================

Shield Counter = 0

Media Error Count = 0

Other Error Count = 0

Drive Temperature = 36C (96.80 F)

Predictive Failure Count = 0

S.M.A.R.T alert flagged by drive = No

Drive /c1/e252/s10 Device attributes :

====================================

SN = PHYF832001H8960CGN

Manufacturer Id = ATA

Model Number = INTEL SSDSC2KB960G8

NAND Vendor = NA

WWN = 55CD2E414FA85A2E

Firmware Revision = XCV10120

Raw size = 894.252 GB [0x6fc81ab0 Sectors]

Coerced size = 893.750 GB [0x6fb80000 Sectors]

Non Coerced size = 893.752 GB [0x6fb81ab0 Sectors]

Device Speed = 6.0Gb/s

Link Speed = 6.0Gb/s

NCQ setting = Enabled

Write Cache = Enabled

Logical Sector Size = 512B

Physical Sector Size = 4 KB

Connector Name = C1.0 x1

Drive /c1/e252/s10 Policies/Settings :

====================================

Drive position = DriveGroup:0, Span:0, Row:0

Enclosure position = 1

Connected Port Number = 11(path0)

Sequence Number = 10

Commissioned Spare = No

Emergency Spare = No

Last Predictive Failure Event Sequence Number = 0

Successful diagnostics completion on = N/A

FDE Type = None

SED Capable = No

SED Enabled = No

Secured = No

Cryptographic Erase Capable = Yes

Sanitize Support = CryptoErase, OverWrite, BlockErase

Locked = No

Needs EKM Attention = No

PI Eligible = No

Certified = No

Wide Port Capable = No

Unmap capable = Yes

Unmap capable for LDs = No

Multipath = No

Port Information :

================

-----------------------------------------

Port Status Linkspeed SAS address

-----------------------------------------

0 Active 6.0Gb/s 0x300062b20c75204a

-----------------------------------------

Inquiry Data =

40 00 ff 3f 37 c8 10 00 00 00 00 00 3f 00 00 00

00 00 00 00 48 50 46 59 33 38 30 32 31 30 38 48

36 39 43 30 4e 47 20 20 00 00 00 00 00 00 43 58

31 56 31 30 30 32 4e 49 45 54 20 4c 53 53 53 44

32 43 42 4b 36 39 47 30 20 38 20 20 20 20 20 20

20 20 20 20 20 20 20 20 20 20 20 20 20 20 01 80

00 40 00 2f 00 40 00 00 00 00 06 00 ff 3f 10 00

3f 00 10 fc fb 00 01 fd ff ff ff 0f 00 00 07 00

Erasing data on a physical drive

Perform this task to start or stop erasing data on a physical drive or view the erasure process.

Syntax

storcli64 /ccontroller_id/eenclosure_id/sslot_id start erase mode

storcli64 /ccontroller_id/eenclosure_id/sslot_id show erase

storcli64 /ccontroller_id/eenclosure_id/sslot_id stop erase

Parameters

enclosure_id: Specifies the enclosure ID.

slot_id: Specifies the ID of the physical drive slot.

mode: Specify the action to take. Options include simple, normal, and thorough, which represents one-time, three-time, and nine-time erasure operations, respectively.

Usage guidelines

If multiple storage controllers exist, use the storcli64 /call show command to obtain a controller ID.

Examples

# Perform one-time erasure for data on a physical drive.

[root@localhost home]# ./storcli64 /c0/e2/s11 start erase simple

CLI Version = 007.1017.0000.0000 May 10, 2019

Operating system = Linux 4.18.0-193.el8.x86_64

Controller = 0

Status = Success

Description = Start Drive Erase Succeeded.

# View the erasure process.

[root@localhost home]# ./storcli64 /c0/e2/s11 show erase

CLI Version = 007.1017.0000.0000 May 10, 2019

Operating system = Linux 4.18.0-193.el8.x86_64

Controller = 0

Status = Success

Description = Show Drive Erse Status Succeeded.

------------------------------------------------------

Drive-ID Progress% Status Estimated Time Left

------------------------------------------------------

/c0/e2/s11 0 In progress 0 Seconds

------------------------------------------------------

# Stop erasing the physical drive.

[root@localhost home]# ./storcli64 /c0/e2/s11 stop erase

CLI Version = 007.1017.0000.0000 May 10, 2019

Operating system = Linux 4.18.0-193.el8.x86_64

Controller = 0

Status = Success

Description = Stop Drive Erase Succeeded.

Viewing supercapacitor information

Perform this task to view supercapacitor information.

Syntax

storcli64 /ccontroller_id/cv show all

Parameters

Examples

[root@localhost ~]# storcli64 /c0/cv show all

CLI Version = 007.1705.0000.0000 Mar 31, 2021

Operating system = Linux 4.18.0-193.el8.x86_64

Controller = 0

Status = Success

Description = None

Cachevault_Info :

===============

--------------------

Property Value

--------------------

Type CVPM05

Temperature 25 C

State Optimal

--------------------

Firmware_Status :

===============

---------------------------------------

Property Value

---------------------------------------

NVCache State OK

Replacement required No

No space to cache offload No

Module microcode update required No

---------------------------------------

GasGaugeStatus :

==============

------------------------------

Property Value

------------------------------

Pack Energy 319 J

Capacitance 100 %

Remaining Reserve Space 0

------------------------------

Design_Info :

===========

------------------------------------

Property Value

------------------------------------

Date of Manufacture 18/09/2019

Serial Number 21428

Manufacture Name LSI

Design Capacity 374 J

Device Name CVPM05

tmmFru N/A

CacheVault Flash Size 8.187 GB

scapBatversionNo 0x00

scapSerialNo 0x53b4

scap Date of Manufacture 18/09/2019

scapPcbAssmNo 50046-01

scapPCBversionNo B

scapBatPackAssmNo 49571-222

Module Version 07251-01

------------------------------------

Properties :

==========

---------------------------------------------------------------------

Property Value

---------------------------------------------------------------------

Auto Learn Period 27d (2412000 seconds)

Next Learn time 2022/07/18 21:59:20 (711496760 seconds)

Learn Delay Interval 0 hour(s)

Auto-Learn Mode Transparent

Last Successful Learn Time Completed, MON, June 20, 2022 at 23:59:20

---------------------------------------------------------------------

Manually making a physical drive come online or go offline

Perform this task to manually make a physical drive come online or go offline.

Syntax

storcli64 /ccontroller_id/eenclosure_id/sslot_id set mode

Parameters

enclosure_id: Specifies the enclosure ID.

slot_id: Specifies the ID of the physical drive slot.

mode: Specifies the action to take. Options include offline and online.

Examples

# Manually make a physical drive go offline.

[root@localhost home]# ./storcli64 /c0/e2/s23 set offline

CLI Version = 007.1017.0000.0000 May 10, 2019

Operating system = Linux 4.18.0-193.el8.x86_64

Controller = 0

Status = Success

Description = Set Drive Offline Succeeded.

# Manually make a physical drive come online.

[root@localhost home]# ./storcli64 /c0/e2/s23 set online

CLI Version = 007.1017.0000.0000 May 10, 2019

Operating system = Linux 4.18.0-193.el8.x86_64

Controller = 0

Status = Success

Description = Set Drive Online Succeeded.

Configuring Patrol Read parameters

Perform this task to view and configure Patrol Read parameters.

Syntax

storcli64 /ccontroller_id set patrolread starttime=start_time maxconcurrentpd=number

storcli64 /ccontroller_id set patrolread delay=delay_time

storcli64 /ccontroller_id show patrolread

Parameters

start_time: Specifies the start time.

number: Specifies the number of drives to be checked concurrently.

delay_time: Specifies the check cycle.

Usage guidelines

· Patrol read takes effect only on member drives of RAID arrays.

· The start time must be a sharp hour.

Examples

# Configure Patrol Read parameters.

[root@localhost home]# ./storcli64 /c0 set pr starttime=2022/03/19 15 maxconcurrentpd=32

CLI Version = 007.1017.0000.0000 May 10, 2019

Operating system = Linux 4.18.0-193.el8.x86_64

Controller = 0

Status = Success

Description = None

Controller Properties :

=====================

---------------------------------------

Ctrl_Prop Value

---------------------------------------

PR Starttime 2022/03/19 15:00:00

PR MaxConcurrentPd 32

---------------------------------------

# View Patrol Read parameters.

[root@localhost home]# ./storcli64 /c0 show pr

CLI Version = 007.1017.0000.0000 May 10, 2019

Operating system = Linux 4.18.0-193.el8.x86_64

Controller = 0

Status = Success

Description = None

Controller Properties :

=====================

---------------------------------------------

Ctrl_Prop Value

---------------------------------------------

PR Mode Auto

PR Execution Delay 168 hours

PR iterations completed 1

PR Next Start time 03/19/2022, 15:00:00

PR on SSD Disabled

PR Current State Stopped

PR Excluded VDs None

PR MaxConcurrentPd 32

---------------------------------------------

Configuring consistency check parameters

Perform this task to view and configure consistency check parameters.

Syntax

storcli64 /ccontroller_id[/vraid_id] show cc

storcli64 /ccontroller_id/vraid_id start cc force

storcli64 /ccontroller_id/vraid_id op cc

storcli64 /ccontroller_id set cc=conc delay=delay_time starttime=start_time

Parameters

raid_id: Specifies the target RAID ID.

op: Specifies the action to take. Options include pause, resume, and stop.

delay_time: Specifies the consistency check cycle.

start_time: Specifies the start time.

Usage guidelines

If you do not specify the /vraid_id option when executing the storcli64 show cc command, the command displays the consistency check parameters. If you specify the /vraid_id option, the command displays the specific check progress.

Examples

# View the consistency check parameters.

[root@localhost home]# ./storcli64 /c0 show cc

CLI Version = 007.1017.0000.0000 May 10, 2019

Operating system = Linux 4.18.0-193.el8.x86_64

Controller = 0

Status = Success

Description = None

Controller Properties :

=====================

-----------------------------------------------

Ctrl_Prop Value

-----------------------------------------------

CC Operation Mode Concurrent

CC Execution Delay 2

CC Next Starttime 03/19/2022, 15:00:00

CC Current State Stopped

CC Number of iterations 1

CC Number of VD completed 0

CC Excluded VDs None

-----------------------------------------------

# View the consistency check progress.

[root@localhost home]# ./storcli64 /c0/v0 show cc

CLI Version = 007.1017.0000.0000 May 10, 2019

Operating system = Linux 4.18.0-193.el8.x86_64

Controller = 0

Status = Success

Description = None

VD Operation Status :

===================

-----------------------------------------------------------

VD Operation Progress% Status Estimated Time Left

-----------------------------------------------------------

0 CC - Not in progress -

-----------------------------------------------------------

# Enable consistency check.

[root@localhost home]# ./storcli64 /c0/v0 start cc force

CLI Version = 007.1017.0000.0000 May 10, 2019

Operating system = Linux 4.18.0-193.el8.x86_64

Controller = 0

Status = Success

Description = Start CC Operation Success

# Stop consistency check.

[root@localhost home]# ./storcli64 /c0/v0 stop cc

CLI Version = 007.1017.0000.0000 May 10, 2019

Operating system = Linux 4.18.0-193.el8.x86_64

Controller = 0

Status = Success

Description = Stop CC Operation Success

# Configure consistency check parameters.

[root@localhost home]# ./storcli64 /c0 set cc=conc delay=2 starttime=2022/03/19 15

CLI Version = 007.1017.0000.0000 May 10, 2019

Operating system = Linux 4.18.0-193.el8.x86_64

Controller = 0

Status = Success

Description = None

Controller Properties :

=====================

---------------------------------

Ctrl_Prop Value

---------------------------------

CC Mode CONC

CC delay 2

CC Starttime 2022/03/19 15:00:00

---------------------------------

Performing RAID rebuild or copyback

Perform this task to start or stop a RAID rebuild or copyback task or view the task status.

Syntax

storcli64 /ccontroller_id/eenclosure_id/sslot_id op func

Parameters

enclosure_id: Specifies the enclosure ID.

slot_id: Specifies the ID of the physical drive slot.

op: Specifies the action to take. Options include show, pause, resume, and stop.

func: Specifies a function, such as copyback and rebuild.

Examples

# View the copyback progress.

[root@localhost home]# ./storcli64 /c0/e2/s23 show copyback

CLI Version = 007.1017.0000.0000 May 10, 2019

Operating system = Linux 4.18.0-193.el8.x86_64

Controller = 0

Status = Success

Description = Show Drive Copyback Status Succeeded.

---------------------------------------------------------

Drive-ID Progress% Status Estimated Time Left

---------------------------------------------------------

/c0/e2/s23 - Not in progress -

---------------------------------------------------------

# View the rebuild progress.

[root@localhost home]# ./storcli64 /c0/e2/s23 show rebuild

CLI Version = 007.1017.0000.0000 May 10, 2019

Operating system = Linux 4.18.0-193.el8.x86_64

Controller = 0

Status = Success

Description = Show Drive Rebuild Status Succeeded.

---------------------------------------------------------

Drive-ID Progress% Status Estimated Time Left

---------------------------------------------------------

/c0/e2/s23 - Not in progress -

---------------------------------------------------------

Managing task resources

Perform this task to set the Patrol Read rate, consistency check rate, bgi backstage initialization rate, rebuild rate, and reconstruction rate.

Syntax

storcli64 /ccontroller_id set func=rate_value

Default

The rate for each task is 30%.

Parameters

func: Specifies the function. Options include prrate, ccrate, bgirate, rebuildrate, and reconrate.

rate_value: Specifies the rate value, in the range of 0 to 100.

Usage guidelines

If multiple storage controllers exist, use the storcli64 /call show command to obtain a controller ID.

Examples

# Set the reconstruction rate.

[root@localhost home]# ./storcli64 /c0 set reconrate=40

CLI Version = 007.1017.0000.0000 May 10, 2019

Operating system = Linux 4.18.0-193.el8.x86_64

Controller = 0

Status = Success

Description = None

Controller Properties :

=====================

----------------

Ctrl_Prop Value

----------------

ReconRate 40%

----------------

Filtering and clearing PreservedCache data

Perform this task to filter and clear PreservedCache data.

Syntax

storcli64 /ccontroller_id show preservedcache

storcli64 /ccontroller_id/vraid_id delete preservedcache force

Parameters

raid_id: Specifies the target RAID ID.

Examples

# Filter PreservedCache data.

[root@localhost home]# ./storcli64 /c0 show preservedcache

CLI Version = 007.1017.0000.0000 May 10, 2019

Operating system = Linux 4.18.0-193.el8.x86_64

Controller = 0

Status = Success

Description = No Virtual Drive has Preserved Cache Data.

# Clear PreservedCache data.

[root@localhost home]# ./storcli64 /c0/v0 delete preservedcache force

CLI Version = 007.1017.0000.0000 May 10, 2019

Operating system = Linux 4.18.0-193.el8.x86_64

Controller = 0

Status = Success

Description = No Virtual Drive has Preserved Cache Data.

Upgrading the drive firmware

Perform this task to upgrade the drive firmware.

Syntax

storcli64 /ccontroller_id/eenclosure_id/sslot_id download src=fw_file

Parameters

enclosure_id: Specifies the enclosure ID.

slot_id: Specifies the ID of the physical drive slot.

fw_file: Specifies the firmware file.

Examples

# Upgrade the drive firmware.

[root@localhost home]# ./storcli64 /c0/e2/s8 download src=fw.bin

Starting microcode update .....please wait...

Flashing PD image ..... please wait...

CLI Version = 007.1017.0000.0000 May 10, 2019

Operating system = Linux 4.18.0-193.el8.x86_64

Controller = 0

Status = Success

Description = Firmware Download succeeded.

Drive Firmware Download :

========================

--------------------------------------------------------------------------------

Drive Status ErrCd ErrMsg

--------------------------------------------------------------------------------

/c0/e2/s8 Success 0

---------------------------------------------------------------------------------

Setting alarm control

Perform this task to set alarm control.

Syntax

storcli64 /ccontroller_id show alarm

storcli64 /ccontroller_id set alarm={on|off|silence}

Parameters

on: Enable alarm control. With this feature enabled, the buzzer sounds an alarm when a critical error occurs.

off: Disable alarm control. With this feature disabled, the buzzer is silenced for any activity and will not sound an alarm for any error, including critical errors.

silence: Silence the buzzer. Any ongoing alarms will be stopped. If a critical error still exists and alarm control is enabled, it will be activated again after a restart. If alarm control is disabled, this option will also be disabled.

Examples

# View alarm control status.

[root@localhost storcli]# ./storcli64 /c0 show alarm

CLI Version = 007.2408.0000.0000 Nov 15, 2022

Operating system = Linux 4.18.0-425.3.1.el8.x86_64

Controller = 0

Status = Success

Description = None

Controller Properties :

=====================

----------------

Ctrl_Prop Value

----------------

Alarm OFF

----------------

# Disable alarm control.

[root@localhost storcli]# ./storcli64 /c0 set alarm=off

CLI Version = 007.2408.0000.0000 Nov 15, 2022

Operating system = Linux 4.18.0-425.3.1.el8.x86_64

Controller = 0

Status = Success

Description = None

Controller Properties :

=====================

----------------

Ctrl_Prop Value

----------------

Alarm OFF

----------------

# Enable alarm control.

[root@localhost storcli]# ./storcli64 /c0 set alarm=on

CLI Version = 007.2408.0000.0000 Nov 15, 2022

Operating system = Linux 4.18.0-425.3.1.el8.x86_64

Controller = 0

Status = Success

Description = None

Controller Properties :

=====================

----------------

Ctrl_Prop Value

----------------

Alarm ON

----------------

# Silence the buzzer.

[root@localhost storcli]# ./storcli64 /c0 set alarm=silence

CLI Version = 007.2408.0000.0000 Nov 15, 2022

Operating system = Linux 4.18.0-425.3.1.el8.x86_64

Controller = 0

Status = Success

Description = None

Controller Properties :

=====================

------------------

Ctrl_Prop Value

------------------

Alarm SILENCE

------------------

Set Firmware Device order

Perform this task to view Firmware Device order status or enable or disable Firmware Device order.

Syntax

storcli64 /ccontroller_id show deviceorderbyfirmware

storcli64 /ccontroller_id set deviceorderbyfirmware=mode

Parameters

mode: Specifies the state of Firmware Device order.Options include:

· on: Enable Firmware Device order.

· off: Disable Firmware Device order.

Usage guidelines

Only the 9460/9440/9540/9560 controllers support this command.

Enabling this feature is only applicable to Linux. For other operating systems such as Windows or VMware, this feature is not supported. If you enable it accidentally in an unsupported system, system hang may occur during the boot process.

With this feature enabled, the reporting order of devices on the storage card during server reboot will change. The devices will be reported in the order of the boot disk, logical disk, and pass-through disk. However, note that all storage controllers will introduce random reporting order for logical disks. In the case of JBOD mode of 9460 controller and all modes of 9560 controller, there may be random reporting order for pass-through disk devices.

This configuration takes effect after you restart the server.

This feature is supported in LSI 9440/9460 51.15.0-3630 and higher versions.

This feature is supported in LSI 9560 52.15.0-3720 and higher versions.

This feature is supported in LSI 9540 52.20.0-4341 and higher versions.

Examples

# View the Firmware Device order state of a storage controller.

[root@localhost ~]# storcli64 /c0 show deviceorderbyfirmware

CLI Version = 007.2203.0000.0000 May 11, 2022

Operating system = Linux 4.18.0-240.el8.x86_64

Controller = 0

Status = Success

Description = None

Controller Properties :

=====================

-------------------------------------

Ctrl_Prop Value

-------------------------------------

Firmware based device ordering OFF

-------------------------------------

# Enable Firmware Device order for a storage controller.

[root@localhost ~]# storcli64 /c0 set deviceorderbyfirmware=on

CLI Version = 007.2203.0000.0000 May 11, 2022

Operating system = Linux 4.18.0-240.el8.x86_64

Controller = 0

Status = Success

Description = Please reboot the system for the changes to take effect

Controller Properties :

=====================

-------------------------------------

Ctrl_Prop Value

-------------------------------------

Firmware based device ordering ON

-------------------------------------

# Disable Firmware Device order for a storage controller.

[root@localhost ~]# storcli64 /c0 set deviceorderbyfirmware=off

CLI Version = 007.2203.0000.0000 May 11, 2022

Operating system = Linux 4.18.0-240.el8.x86_64

Controller = 0

Status = Success

Description = Please reboot the system for the changes to take effect

Controller Properties :

=====================

-------------------------------------

Ctrl_Prop Value

-------------------------------------

Firmware based device ordering OFF

-------------------------------------

Setting direct pd mapping

Perform this task to view the state of direct pd mapping or enable or disable direct pd mapping for an LSI storage controller.

Syntax

storcli64 /ccontroller_id show directpdmapping

storcli64 /ccontroller_id set directpdmapping=mode

Parameters

mode: Specifies the state of direct pd mapping.Options include:

· on: Enable direct pd mapping.

· off: Disable direct pd mapping.

Usage guidelines

Only the 9460/9440/9540/9560 controllers support this command.

This feature cannot be enabled when the storage controller is connected to the Expander backplane. Enabling it accidentally may cause the storage controller to enter Failed state.

With this feature enabled, during the server reboot phase, the pass-through disk devices under the storage controller will be reported based on their slot numbers.

This configuration takes effect after you restart the server.

This feature is supported in LSI 9440/9460 51.15.0-3630 and higher versions.

This feature is supported in LSI 9560 52.15.0-3720 and higher versions.

This feature is supported in LSI 9540 52.20.0-4341 and higher versions.

Examples

# View the state of direct pd mapping for a storage controller.

[root@localhost ~]# storcli64 /c0 show directpdmapping

CLI Version = 007.2203.0000.0000 May 11, 2022

Operating system = Linux 4.18.0-240.el8.x86_64

Controller = 0

Status = Success

Description = None

Controller Properties :

=====================

----------------------

Ctrl_Prop Value

----------------------

Directpdmapping OFF

----------------------

# Enable direct pd mapping for a storage controller.

[root@localhost ~]# storcli64 /c0 set directpdmapping=on

CLI Version = 007.2203.0000.0000 May 11, 2022

Operating system = Linux 4.18.0-240.el8.x86_64

Controller = 0

Status = Success

Description = None

Controller Properties :

=====================

------------------------------------------------

Ctrl_Prop Value

------------------------------------------------

Directpdmapping ON (Requires reboot for effect)

------------------------------------------------

# Disable direct pd mapping for a storage controller.

[root@localhost ~]# storcli64 /c0 set directpdmapping=off

CLI Version = 007.2203.0000.0000 May 11, 2022

Operating system = Linux 4.18.0-240.el8.x86_64

Controller = 0

Status = Success

Description = None

Controller Properties :

=====================

-------------------------------------------------

Ctrl_Prop Value

-------------------------------------------------

Directpdmapping OFF (Requires reboot for effect)

-------------------------------------------------

Checking the PSoC information

Perform this task to view the PSoC firmware of a storage controller.

Syntax

storcli64 /ccontroller_id/ show all | grep -i psoc

Parameters

Usage guidelines

For the LSI 9560 controller, you can view the PSoC information or update the PSoC firmware only when either of the following conditions is met:

· The controller firmware version is 52.20.0-4341 or later and the StorCLI version is 7.2007.0000.0000 or later.

· The controller firmware version is 52.22.0-4544 or later and the StorCLI version is 7.2307.0000.0000 or later.

Examples

# Display PSoC information, including the PSoC FW Version, PSoC Part Number, and PSoC support status.

[root@localhost ~]# storcli64 /c0 show all | grep -i psoc

PSOC FW Version = 0x001B

PSOC Hardware Version = 0x0003

PSOC Part Number = 15987-270-4GB

Support PSOC Update = Yes

Support PSOC Part Information = Yes

Upgradable PSOC = Present

Updating the PSoC firmware

Perform this task to update the PSoC firmware of a storage controller.

Syntax

storcli64 /ccontroller_id download file= fw_file

storcli64 /ccontroller_id download file= fw_file noverchk

Parameters

fw_file: Specifies the PSoC firmware file.

noverchk: Configures the system not to check the firmware image version when downgrading or updating the storage controller firmware.

Usage guidelines

When you use this command, follow these restrictions and guidelines:

· If the PSoC firmware file of the storage controller is not in the current path, you must add the absolute path of the file in front of the file name.

· Commands used to specify paths in the StorCLI tool do not support spaces and special characters.

· After updating the PSoC firmware, you must perform an AC power cycle of the server for the update to take effect.

· For the LSI 9560 controller, you can view the PSoC information or update the PSoC firmware only when either of the following conditions is met:

¡ The controller firmware version is 52.20.0-4341 or later and the StorCLI version is 7.2007.0000.0000 or later.

¡ The controller firmware version is 52.22.0-4544 or later and the StorCLI version is 7.2307.0000.0000 or later.

Examples

# Upgrade the PSoC firmware of a storage controller.

[root@localhost ~]# storcli64 /c0 download file=pblp_catalog.signed.rom

Download Completed.

Flashing image to adapter...

CLI Version = 007.2408.0000.0000 Nov 15, 2022

Operating system = Linux 4.18.0-193.el8.x86_64

Controller = 0

Status = Success

Description = F/W Flash Completed. Please shutdown the system for the changes to take effect

# Downgrade or update the PSoC firmware of a storage controller.

[root@localhost ~]# storcli64 /c0 download file=pblp_catalog.signed.rom noverchk

Download Completed.

Flashing image to adapter...

CLI Version = 007.2408.0000.0000 Nov 15, 2022

Operating system = Linux 4.18.0-193.el8.x86_64

Controller = 0

Status = Success

Description = F/W Flash Completed. Please shutdown the system for the changes to take effect

Configuring emergency hot spare drives

Perform this task to configure the emergency hot spare feature. With this feature configured, if a drive in any redundant RAID array fails and no specific hot spare drive is assigned, an idle drive of the same type managed by the same storage controller replaces the drive in fail or prefail state. Then, the drive starts data rebuilding to avoid data loss.

Syntax

storcli64 /ccontroller_id set eghs eug={on|off}

storcli64 /ccontroller_id set eghs smarter={on|off}

storcli64 /ccontroller_id set eghs state={on|off}

Parameters

eug: Specifies drives in Unconfigured Good state as emergency hot spare drives.

smarter: Specifies drives in SMART Error state as emergency hot spare drives.

state: Specifies drives in Unconfigured Good and hot spare state as emergency hot spare drives.

Usage guidelines

If multiple storage controllers exist, use the storcli64 /call show command to obtain the controller ID.

The hot spare drive must use the same interface protocol as the member drives of the RAID array, and has a capacity equal to or larger than any member drives.

Examples

# Configure drives in Unconfigured Good state as emergency hot spare drives.

[root@localhost ~]# storcli /c0 set eghs eug=on

CLI Version = 007.2807.0000.0000 Dec 22, 2023

Operating system = Linux 5.14.0-70.22.1.el9_0.x86_64

Controller = 0

Status = Success

Description = None

Controller Properties :

=====================

------------------

Ctrl_Prop Value

------------------

EmergencyUG ON

------------------

# Configure drives in SMART Error state as emergency hot spare drives.

[root@localhost ~]# storcli /c0 set eghs smarter=on

CLI Version = 007.2807.0000.0000 Dec 22, 2023

Operating system = Linux 5.14.0-70.22.1.el9_0.x86_64

Controller = 0

Status = Success

Description = None

Controller Properties :

=====================

-----------------------

Ctrl_Prop Value

-----------------------

EmergencySmarter ON

-----------------------

# Configure drives in Unconfigured Good and hot spare state as emergency hot spare drives.

[root@localhost ~]# storcli /c0 set eghs state=on

CLI Version = 007.2807.0000.0000 Dec 22, 2023

Operating system = Linux 5.14.0-70.22.1.el9_0.x86_64

Controller = 0

Status = Success

Description = None

Controller Properties :

=====================

-------------------

Ctrl_Prop Value

-------------------

EmergencyGHS ON

-------------------

Support for fault alarming

Fault alarming includes alarming for faults that have occurred and predictive faults. Support for fault alarming depends on the storage controller model and connection mode. For more information, see Table 6 and Table 7.

Table 6 Support for fault alarming

Storage controller series	RAID-mode directly-connected drives	RAID-mode connected drive expander modules	JBOD-mode directly-connected drives	JBOD-mode connected drive expander modules
LSI-9361	Yes	Yes	Yes	Yes
LSI-9440	Yes	Yes	N/A	N/A
LSI-9460	Yes	Yes	Yes	Yes
LSI-9540	Yes	Yes	N/A	N/A
LSI-9560	Yes	Yes	Yes	Yes

Table 7 Support for Predictive Failure Analysis (PFA)

Storage controller series	RAID-mode directly-connected drives	RAID-mode connected drive expander modules	JBOD-mode directly-connected drives	JBOD-mode connected drive expander modules
LSI-9361	Support identifying the FPA state only for Unconfigured Good drives, members of logical drives, and hot spare drives (LED not flashing amber at 0.5 Hz)	Support identifying the FPA state only for Unconfigured Good drives, members of logical drives, and hot spare drives (LED flashing amber at 0.5 Hz)	No	No
LSI-9440			N/A	N/A
LSI-9460			Support identifying the FPA state for all drives (LED not flashing amber at 0.5)	Support identifying the FPA state for all drives (LED flashing amber at 0.5 Hz only supported on UG, logical drives, and hot spare drives)
LSI-9540			N/A	N/A
LSI-9560	Support identifying the FPA state for all drives (LED not flashing amber at 0.5 Hz)	Support identifying the FPA state for all drives (LED flashing amber at 0.5 Hz)	Support identifying the FPA state for all drives (LED not flashing amber at 0.5 Hz)	Support identifying the FPA state for all drives (LED flashing amber at 0.5 Hz)

Troubleshooting

For detailed information about collecting storage controller fault information, diagnosing and locating faults, and troubleshooting servers, see H3C Servers Troubleshooting Guide.

Compatibility

For information about storage controller and server compatibility, access http://www.h3c.com/en/home/qr/default.htm?id=66.

Downloading and installing drivers

Access the H3C official website to download the storage controller drivers. For more information about installing drivers, see the release notes for the driver program.

H3C G3&G5 Servers Storage Controller User Guide-6W109

Configuring an LSI-9440, 9460, 5408, LSI-9361, L460, 9560, or 9540 series storage controller

Operating mode

RAID levels

Restrictions and guidelines for configuring RAID

Configuring RAID arrays in UEFI mode

RAID array configuration tasks at a glance

Configuring hot spare drives

Configuring a global hot spare drive

Configuring a dedicated hot spare drive

Deleting a RAID array

Locating a physical drive

Locating all drives for a virtual drive

Erasing a physical drive

Erasing a logical drive

Expanding a RAID array

Upgrading the storage controller firmware online

Switching the storage controller mode

Forcing a logical drive to come online

Setting alarm control

Silencing the buzzer

RAID array configuration tasks at a glance

Configuring hot spare drives

Configuring a global hot spare drive

Configuring a dedicated hot spare drive

Erasing a physical drive

Erasing a logical drive

Expanding a RAID array

Switching the drive state

Viewing drive information

Scaling up RAID

Viewing supercapacitor information

Manually making a physical drive come online or go offline

Performing RAID rebuild or copyback

Upgrading the drive firmware

Configuring emergency hot spare drives

Troubleshooting

Downloading and installing drivers

Intelligent Terminal Products

Product Support Services

Technical Service Solutions

Resource Center

Policy

Online Help

Become a Partner

Partner Policy & Program

Global Learning

Partner Sales Resources

Service Business

News & Events

Contact Us