Printable version

Drivers & software

* RECOMMENDED * Online ROM Flash Component for VMware ESXi - HPE Smart Array P408i-p, P408e-p, P408i-a, P408i-c, E208i-p, E208e-p, E208i-c, E208i-a, P408e-m, P204i-c, P204i-b, P816i-a and P416ie-m SR Gen10

By downloading, you agree to the terms and conditions of the Hewlett Packard Enterprise Software License Agreement.
Note:  Some software requires a valid warranty, current Hewlett Packard Enterprise support contract, or a license fee.

Type: Firmware - Storage Controller
Version: 1.60(19 Jul 2018)
Operating System(s): VMware vSphere 6.0
VMware vSphere 6.5
Multi-part download
File name: CP034555.compsig (2.2 KB)
File name: CP034555.zip (14 MB)
This Smart Component provides firmware for the following storage controllers: HPE Smart Array P408i-p, P408e-p, P408i-a, P408e-m, P408i-c, E208i-p, E208e-p, E208i-c, E208i-a, P204i-c, P204i-b, P816i-a and P416ie-m SR Gen10

  • Increased SmartCache maximum logical volume size.
  • Added support for SmartCache in UEFI configuration tools.
  • Added the ability to control drive write cache settings.
  • Added the ability to select the drive erase pattern.

To ensure the integrity of your download, HPE recommends verifying your results with the following SHA-256 Checksum values:

58510ec87ca326382c2416560680a73af330bf068c11fd5f6c86223f4fcd8f96 CP034555.compsig
cc2515637386fd6547b3120f5dab8f09bfd63372cd292b847ec70617f0d34f66 CP034555.zip

Reboot Requirement:
Reboot is required after installation for updates to take effect and hardware stability to be maintained.


Installation:

 

To use Smart Update Manager from the Service Pack for ProLiant:

     Offline (
The SPP Offline mode boots a special Linux OS environment, thus the Linux Smart Components are used, not the VMware Smart Components):

  • Place the Service Pack for ProLiant on a USB key using the USB Key Utility for Windows.
  • Place the desired Linux firmware component to be updated in the directory, /packages on the USB key.
  • Boot from the newly created Service Pack for ProLiant USB key.
  • Follow Smart Update Manager steps to complete firmware update.

     Remote Online:

  • Download the appropriate SPP.
  • Add the component to the SPP.
  • Mount the SPP on a remote server running Windows or Linux that has a network connection to the ESXi host to be updated.
  • Run SUM.
  • Add the ESXi host to be updated as a remote target/node.
  • Enter IP or DNS address of the ESXi host to be updated Enter the ESXi host credentials (root or administrator username and password).
  • For SUM 6.0 and newer, select both the Additional Package with the added component and the SPP Baseline on the node Inventory page.
  • Follow Smart Update Manager Steps and complete the firmware update.

Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
 
To use HP Insight Control for vCenter:

  • Log in to the vSphere Client.
  • Select a server or cluster in the inventory tree.
  • Click the HP Insight Management tab.
  • Follow Insight Control for vCenter steps to update firmware using a Smart Component

To update firmware from VMware ESXi operating system on target server:

  • Enable Tech Support Mode on the ESXi host.
  • Login as root. (You must be root in order to apply the update.)
  • Place the Smart Component zip file in a temporary directory.
  • Unzip the file CPXXXXXX.zip
  • Ensure that CPXXXXXX.vmexe is executable by using the command:

             chmod +x CPXXXXXX.vmexe    

  • From the same directory, execute the Smart Component. For example: ./CPXXXXXX.vmexe
  • Follow the directions given by the Smart Component.
  • Logout
  • Disable Tech Support Mode on the ESXi host.

 


End User License Agreements:
HPE Software License Agreement v1


Upgrade Requirement:
Recommended - HPE recommends users update to this version at their earliest convenience.


Notes:

Deliverable Name:
     Online ROM Flash Component for VMware ESXi - HPE Smart Array P408i-p, P408e-p, P408i-a, P408i-c, E208i-p, E208e-p, E208i-c, E208i-a, P408e-m, P204i-c, P204i-b, P816i-a and P416ie-m SR Gen10

Release Version and/or Date:
    1.60

Last Recommended or Critical Version:
    1.34

Previous Version of Firmware:
     None

Firmware Dependency:
     None

Enhancements/New Features:

  • Increased SmartCache maximum logical volume size.
  • Added support for SmartCache in UEFI configuration tools.
  • Added the ability to control drive write cache settings.
  • Added the ability to select the drive erase pattern.

Problems Fixed:     

  • Connectivity to HPE D6020 disk enclosures might be lost if connected to multiple servers.
  • In rare cases, data could become unavailable on a RAID 6 (ADG) volume during a rebuild or parity consistency check.
  • Inability to configure unassigned drives if a failed RAID volume was present.
  • After multiple reboots, unassigned drives might be erroneously assigned as spares for configured RAID volumes.
  • System might continuously reboot after splitting a mirrored volume.
  • Volume transformation might fail or not resume after a system reboot.
  • Maximum command queue depth for SATA drives was limited.
  • Controller might stop responding:
    • During power up device discovery. (POST Lockup 0x1ABD or 0x20227)
    • If multiple completions are received for an IO command. (POST Lockup 0x1BE0)
    • If a drive enclosure is power cycled while IO is running. (POST Lockup 0x1C50 or 0x27006)
    • If a drive enclosure is power cycled while a drive is sanitizing. (POST Lockup 0x1E30)
    • When attempting to modify the controller cache settings while IO is running. (POST Lockup 0x1E30)
    • If a drive failed. (POST Lockup 0x27006)
    • When adding or removing drives from a RAID 5 or RAID 50 volume during a rebuild. (POST Lockup 0xFFFFF001)
    • During POST prior to loading an operating system.
    • When Unrecoverable Read Errors (URE’s) are found on drives.
    • When deleting volumes while a rebuild is occurring and URE’s and found.
    • Following completion of Rapid Parity Initialization (RPI) of a new RAID volume.
    • During a volume transformation.
  • A drive undergoing RPI might be presented to the operating system.
  • Controller slot ID might be shown incorrectly in management tools.
  • Incorrect drive bay numbers might be shown in a dual domain configuration.
  • Drive sanitize might report incorrect status information.
  • Status of the Smart Storage Battery might be reported incorrectly.
  • Incorrect POST message 1831 indicating loss of SmartCache data.
  • Incorrect text in POST message 1786.
  • Various scenarios where drive LEDs might not be displayed correctly.
  • The RESTful management interface might fail when attempting to:
    • Change drive write cache configuration.
    • Configure a new RAID volume.

Known Issues:
     None


Upgrade Requirement:
Recommended - HPE recommends users update to this version at their earliest convenience.


  • Connectivity to HPE D6020 disk enclosures might be lost if connected to multiple servers.
  • In rare cases, data could become unavailable on a RAID 6 (ADG) volume during a rebuild or parity consistency check.
  • Inability to configure unassigned drives if a failed RAID volume was present.
  • After multiple reboots, unassigned drives might be erroneously assigned as spares for configured RAID volumes.
  • System might continuously reboot after splitting a mirrored volume.
  • Volume transformation might fail or not resume after a system reboot.
  • Maximum command queue depth for SATA drives was limited.
  • Controller might stop responding:
    • During power up device discovery. (POST Lockup 0x1ABD or 0x20227)
    • If multiple completions are received for an IO command. (POST Lockup 0x1BE0)
    • If a drive enclosure is power cycled while IO is running. (POST Lockup 0x1C50 or 0x27006)
    • If a drive enclosure is power cycled while a drive is sanitizing. (POST Lockup 0x1E30)
    • When attempting to modify the controller cache settings while IO is running. (POST Lockup 0x1E30)
    • If a drive failed. (POST Lockup 0x27006)
    • When adding or removing drives from a RAID 5 or RAID 50 volume during a rebuild. (POST Lockup 0xFFFFF001)
    • During POST prior to loading an operating system.
    • When Unrecoverable Read Errors (URE’s) are found on drives.
    • When deleting volumes while a rebuild is occurring and URE’s and found.
    • Following completion of Rapid Parity Initialization (RPI) of a new RAID volume.
    • During a volume transformation.
  • A drive undergoing RPI might be presented to the operating system.
  • Controller slot ID might be shown incorrectly in management tools.
  • Incorrect drive bay numbers might be shown in a dual domain configuration.
  • Drive sanitize might report incorrect status information.
  • Status of the Smart Storage Battery might be reported incorrectly.
  • Incorrect POST message 1831 indicating loss of SmartCache data.
  • Incorrect text in POST message 1786.
  • Various scenarios where drive LEDs might not be displayed correctly.
  • The RESTful management interface might fail when attempting to:
    • Change drive write cache configuration.
    • Configure a new RAID volume.
Version:1.60 (19 Jul 2018)
Fixes

Upgrade Requirement:
Recommended - HPE recommends users update to this version at their earliest convenience.


  • Connectivity to HPE D6020 disk enclosures might be lost if connected to multiple servers.
  • In rare cases, data could become unavailable on a RAID 6 (ADG) volume during a rebuild or parity consistency check.
  • Inability to configure unassigned drives if a failed RAID volume was present.
  • After multiple reboots, unassigned drives might be erroneously assigned as spares for configured RAID volumes.
  • System might continuously reboot after splitting a mirrored volume.
  • Volume transformation might fail or not resume after a system reboot.
  • Maximum command queue depth for SATA drives was limited.
  • Controller might stop responding:
    • During power up device discovery. (POST Lockup 0x1ABD or 0x20227)
    • If multiple completions are received for an IO command. (POST Lockup 0x1BE0)
    • If a drive enclosure is power cycled while IO is running. (POST Lockup 0x1C50 or 0x27006)
    • If a drive enclosure is power cycled while a drive is sanitizing. (POST Lockup 0x1E30)
    • When attempting to modify the controller cache settings while IO is running. (POST Lockup 0x1E30)
    • If a drive failed. (POST Lockup 0x27006)
    • When adding or removing drives from a RAID 5 or RAID 50 volume during a rebuild. (POST Lockup 0xFFFFF001)
    • During POST prior to loading an operating system.
    • When Unrecoverable Read Errors (URE’s) are found on drives.
    • When deleting volumes while a rebuild is occurring and URE’s and found.
    • Following completion of Rapid Parity Initialization (RPI) of a new RAID volume.
    • During a volume transformation.
  • A drive undergoing RPI might be presented to the operating system.
  • Controller slot ID might be shown incorrectly in management tools.
  • Incorrect drive bay numbers might be shown in a dual domain configuration.
  • Drive sanitize might report incorrect status information.
  • Status of the Smart Storage Battery might be reported incorrectly.
  • Incorrect POST message 1831 indicating loss of SmartCache data.
  • Incorrect text in POST message 1786.
  • Various scenarios where drive LEDs might not be displayed correctly.
  • The RESTful management interface might fail when attempting to:
    • Change drive write cache configuration.
    • Configure a new RAID volume.
Enhancements

  • Increased SmartCache maximum logical volume size.
  • Added support for SmartCache in UEFI configuration tools.
  • Added the ability to control drive write cache settings.
  • Added the ability to select the drive erase pattern.

Version:1.34(B) (26 Jun 2018)
Enhancements

Upgrade Requirement:
Recommended - HPE recommends users update to this version at their earliest convenience.

Note: If version 1.34 was previously installed, then it is not necessary to upgrade to version 1.34 (B).


  • Added support for the HPE Smart Array P408e-m Controller.

Version:1.34 (22 Dec 2017)
Fixes

Upgrade Requirement:
Recommended - HPE recommends users update to this version at their earliest convenience.


  • Controller might stop responding while handling a drive error.  (POST Lockup 0x27006)
  • Controller might stop responding after a drive hot-removal or hot-insertion.  (POST Lockup codes 0x1EA or 0x15010)
  • Controller might stop responding during a volume expansion or rekey.  (POST Lockup code 0x1E30)
  • Controller might stop responding while performing heavy writes to a RAID 0 or RAID 1 logical drive that has a flash backed write cache enabled.  (POST Lockup 0x1BC0)
  • Various scenarios where drive LEDs might not be displayed correctly.
  • Drives might not be detected after a cold boot.
  • A hot-inserted drive might be immediately reported as failed.
  • A failed or charging HPE Smart Storage Battery might be reported as “missing” in SSA and iLO.
  • The RESTful management interface might be unable to detect physical drives or make configuration changes to the controller.
  • Option to enable “No Battery Write Cache” in SSA is not available if an HPE Smart Storage Battery is not installed.
  • Customer specified read/write controller cache ratio is not honored if “No Battery Write Cache” is enabled.
  • Controller cache might be displayed as temporarily disabled following an unexpected shutdown and subsequent reboot.
  • Unable to modify the controller cache read/write ratio following an unexpected shutdown and subsequent reboot.
  • The controller cache might become disabled when running VMware ESXi 6.0 if the controller and guest OS are configured to use PCI pass-through.
  • If multiple logical volumes are present on the same array, and one of the volumes is rebuilding, the others might be incorrectly marked as failed.
  • A drive at index 0 might incorrectly display as rebuilding if a logical volume on the controller is currently rebuilding.
  • System might hang during power-up or appear unresponsive during runtime if a logical volume composed of SSD’s is created or rebuilding.
  • Negotiated link rate for drives might not be correct.
  • Storage enclosure information for direct attached drives might not be returned correctly in Windows.
  • The HPE SmartCache feature was not available by default on the P816i-a SR Gen10 controller.
Enhancements

  • Support for ATA Sanitize Freeze/Antifreeze Lock.
  • Ability to select boot controller in Legacy BIOS mode with multiple controllers installed.
  • Updated Hard Drive Carrier LED behavior for the HPE ProLiant XL450 Gen10 Server.
  • Ability to set rebuild priorities via the RESTful management interface.
  • Supported settings – High, MediumHigh, Medium, Low

Type: Firmware - Storage Controller
Version: 1.60(19 Jul 2018)
Operating System(s):
VMware vSphere 6.0
VMware vSphere 6.5

Description

This Smart Component provides firmware for the following storage controllers: HPE Smart Array P408i-p, P408e-p, P408i-a, P408e-m, P408i-c, E208i-p, E208e-p, E208i-c, E208i-a, P204i-c, P204i-b, P816i-a and P416ie-m SR Gen10

Enhancements

  • Increased SmartCache maximum logical volume size.
  • Added support for SmartCache in UEFI configuration tools.
  • Added the ability to control drive write cache settings.
  • Added the ability to select the drive erase pattern.

Installation Instructions

To ensure the integrity of your download, HPE recommends verifying your results with the following SHA-256 Checksum values:

58510ec87ca326382c2416560680a73af330bf068c11fd5f6c86223f4fcd8f96 CP034555.compsig
cc2515637386fd6547b3120f5dab8f09bfd63372cd292b847ec70617f0d34f66 CP034555.zip

Reboot Requirement:
Reboot is required after installation for updates to take effect and hardware stability to be maintained.


Installation:

 

To use Smart Update Manager from the Service Pack for ProLiant:

     Offline (
The SPP Offline mode boots a special Linux OS environment, thus the Linux Smart Components are used, not the VMware Smart Components):

  • Place the Service Pack for ProLiant on a USB key using the USB Key Utility for Windows.
  • Place the desired Linux firmware component to be updated in the directory, /packages on the USB key.
  • Boot from the newly created Service Pack for ProLiant USB key.
  • Follow Smart Update Manager steps to complete firmware update.

     Remote Online:

  • Download the appropriate SPP.
  • Add the component to the SPP.
  • Mount the SPP on a remote server running Windows or Linux that has a network connection to the ESXi host to be updated.
  • Run SUM.
  • Add the ESXi host to be updated as a remote target/node.
  • Enter IP or DNS address of the ESXi host to be updated Enter the ESXi host credentials (root or administrator username and password).
  • For SUM 6.0 and newer, select both the Additional Package with the added component and the SPP Baseline on the node Inventory page.
  • Follow Smart Update Manager Steps and complete the firmware update.

Refer to the SPP documentation for detailed instructions at: http://www.hpe.com/info/spp/documentation
 
To use HP Insight Control for vCenter:

  • Log in to the vSphere Client.
  • Select a server or cluster in the inventory tree.
  • Click the HP Insight Management tab.
  • Follow Insight Control for vCenter steps to update firmware using a Smart Component

To update firmware from VMware ESXi operating system on target server:

  • Enable Tech Support Mode on the ESXi host.
  • Login as root. (You must be root in order to apply the update.)
  • Place the Smart Component zip file in a temporary directory.
  • Unzip the file CPXXXXXX.zip
  • Ensure that CPXXXXXX.vmexe is executable by using the command:

             chmod +x CPXXXXXX.vmexe    

  • From the same directory, execute the Smart Component. For example: ./CPXXXXXX.vmexe
  • Follow the directions given by the Smart Component.
  • Logout
  • Disable Tech Support Mode on the ESXi host.

 


Release Notes

End User License Agreements:
HPE Software License Agreement v1


Upgrade Requirement:
Recommended - HPE recommends users update to this version at their earliest convenience.


Notes:

Deliverable Name:
     Online ROM Flash Component for VMware ESXi - HPE Smart Array P408i-p, P408e-p, P408i-a, P408i-c, E208i-p, E208e-p, E208i-c, E208i-a, P408e-m, P204i-c, P204i-b, P816i-a and P416ie-m SR Gen10

Release Version and/or Date:
    1.60

Last Recommended or Critical Version:
    1.34

Previous Version of Firmware:
     None

Firmware Dependency:
     None

Enhancements/New Features:

  • Increased SmartCache maximum logical volume size.
  • Added support for SmartCache in UEFI configuration tools.
  • Added the ability to control drive write cache settings.
  • Added the ability to select the drive erase pattern.

Problems Fixed:     

  • Connectivity to HPE D6020 disk enclosures might be lost if connected to multiple servers.
  • In rare cases, data could become unavailable on a RAID 6 (ADG) volume during a rebuild or parity consistency check.
  • Inability to configure unassigned drives if a failed RAID volume was present.
  • After multiple reboots, unassigned drives might be erroneously assigned as spares for configured RAID volumes.
  • System might continuously reboot after splitting a mirrored volume.
  • Volume transformation might fail or not resume after a system reboot.
  • Maximum command queue depth for SATA drives was limited.
  • Controller might stop responding:
    • During power up device discovery. (POST Lockup 0x1ABD or 0x20227)
    • If multiple completions are received for an IO command. (POST Lockup 0x1BE0)
    • If a drive enclosure is power cycled while IO is running. (POST Lockup 0x1C50 or 0x27006)
    • If a drive enclosure is power cycled while a drive is sanitizing. (POST Lockup 0x1E30)
    • When attempting to modify the controller cache settings while IO is running. (POST Lockup 0x1E30)
    • If a drive failed. (POST Lockup 0x27006)
    • When adding or removing drives from a RAID 5 or RAID 50 volume during a rebuild. (POST Lockup 0xFFFFF001)
    • During POST prior to loading an operating system.
    • When Unrecoverable Read Errors (URE’s) are found on drives.
    • When deleting volumes while a rebuild is occurring and URE’s and found.
    • Following completion of Rapid Parity Initialization (RPI) of a new RAID volume.
    • During a volume transformation.
  • A drive undergoing RPI might be presented to the operating system.
  • Controller slot ID might be shown incorrectly in management tools.
  • Incorrect drive bay numbers might be shown in a dual domain configuration.
  • Drive sanitize might report incorrect status information.
  • Status of the Smart Storage Battery might be reported incorrectly.
  • Incorrect POST message 1831 indicating loss of SmartCache data.
  • Incorrect text in POST message 1786.
  • Various scenarios where drive LEDs might not be displayed correctly.
  • The RESTful management interface might fail when attempting to:
    • Change drive write cache configuration.
    • Configure a new RAID volume.

Known Issues:
     None


Fixes

Upgrade Requirement:
Recommended - HPE recommends users update to this version at their earliest convenience.


  • Connectivity to HPE D6020 disk enclosures might be lost if connected to multiple servers.
  • In rare cases, data could become unavailable on a RAID 6 (ADG) volume during a rebuild or parity consistency check.
  • Inability to configure unassigned drives if a failed RAID volume was present.
  • After multiple reboots, unassigned drives might be erroneously assigned as spares for configured RAID volumes.
  • System might continuously reboot after splitting a mirrored volume.
  • Volume transformation might fail or not resume after a system reboot.
  • Maximum command queue depth for SATA drives was limited.
  • Controller might stop responding:
    • During power up device discovery. (POST Lockup 0x1ABD or 0x20227)
    • If multiple completions are received for an IO command. (POST Lockup 0x1BE0)
    • If a drive enclosure is power cycled while IO is running. (POST Lockup 0x1C50 or 0x27006)
    • If a drive enclosure is power cycled while a drive is sanitizing. (POST Lockup 0x1E30)
    • When attempting to modify the controller cache settings while IO is running. (POST Lockup 0x1E30)
    • If a drive failed. (POST Lockup 0x27006)
    • When adding or removing drives from a RAID 5 or RAID 50 volume during a rebuild. (POST Lockup 0xFFFFF001)
    • During POST prior to loading an operating system.
    • When Unrecoverable Read Errors (URE’s) are found on drives.
    • When deleting volumes while a rebuild is occurring and URE’s and found.
    • Following completion of Rapid Parity Initialization (RPI) of a new RAID volume.
    • During a volume transformation.
  • A drive undergoing RPI might be presented to the operating system.
  • Controller slot ID might be shown incorrectly in management tools.
  • Incorrect drive bay numbers might be shown in a dual domain configuration.
  • Drive sanitize might report incorrect status information.
  • Status of the Smart Storage Battery might be reported incorrectly.
  • Incorrect POST message 1831 indicating loss of SmartCache data.
  • Incorrect text in POST message 1786.
  • Various scenarios where drive LEDs might not be displayed correctly.
  • The RESTful management interface might fail when attempting to:
    • Change drive write cache configuration.
    • Configure a new RAID volume.

Revision History

Version:1.60 (19 Jul 2018)
Fixes

Upgrade Requirement:
Recommended - HPE recommends users update to this version at their earliest convenience.


  • Connectivity to HPE D6020 disk enclosures might be lost if connected to multiple servers.
  • In rare cases, data could become unavailable on a RAID 6 (ADG) volume during a rebuild or parity consistency check.
  • Inability to configure unassigned drives if a failed RAID volume was present.
  • After multiple reboots, unassigned drives might be erroneously assigned as spares for configured RAID volumes.
  • System might continuously reboot after splitting a mirrored volume.
  • Volume transformation might fail or not resume after a system reboot.
  • Maximum command queue depth for SATA drives was limited.
  • Controller might stop responding:
    • During power up device discovery. (POST Lockup 0x1ABD or 0x20227)
    • If multiple completions are received for an IO command. (POST Lockup 0x1BE0)
    • If a drive enclosure is power cycled while IO is running. (POST Lockup 0x1C50 or 0x27006)
    • If a drive enclosure is power cycled while a drive is sanitizing. (POST Lockup 0x1E30)
    • When attempting to modify the controller cache settings while IO is running. (POST Lockup 0x1E30)
    • If a drive failed. (POST Lockup 0x27006)
    • When adding or removing drives from a RAID 5 or RAID 50 volume during a rebuild. (POST Lockup 0xFFFFF001)
    • During POST prior to loading an operating system.
    • When Unrecoverable Read Errors (URE’s) are found on drives.
    • When deleting volumes while a rebuild is occurring and URE’s and found.
    • Following completion of Rapid Parity Initialization (RPI) of a new RAID volume.
    • During a volume transformation.
  • A drive undergoing RPI might be presented to the operating system.
  • Controller slot ID might be shown incorrectly in management tools.
  • Incorrect drive bay numbers might be shown in a dual domain configuration.
  • Drive sanitize might report incorrect status information.
  • Status of the Smart Storage Battery might be reported incorrectly.
  • Incorrect POST message 1831 indicating loss of SmartCache data.
  • Incorrect text in POST message 1786.
  • Various scenarios where drive LEDs might not be displayed correctly.
  • The RESTful management interface might fail when attempting to:
    • Change drive write cache configuration.
    • Configure a new RAID volume.
Enhancements

  • Increased SmartCache maximum logical volume size.
  • Added support for SmartCache in UEFI configuration tools.
  • Added the ability to control drive write cache settings.
  • Added the ability to select the drive erase pattern.

Version:1.34(B) (26 Jun 2018)
Enhancements

Upgrade Requirement:
Recommended - HPE recommends users update to this version at their earliest convenience.

Note: If version 1.34 was previously installed, then it is not necessary to upgrade to version 1.34 (B).


  • Added support for the HPE Smart Array P408e-m Controller.

Version:1.34 (22 Dec 2017)
Fixes

Upgrade Requirement:
Recommended - HPE recommends users update to this version at their earliest convenience.


  • Controller might stop responding while handling a drive error.  (POST Lockup 0x27006)
  • Controller might stop responding after a drive hot-removal or hot-insertion.  (POST Lockup codes 0x1EA or 0x15010)
  • Controller might stop responding during a volume expansion or rekey.  (POST Lockup code 0x1E30)
  • Controller might stop responding while performing heavy writes to a RAID 0 or RAID 1 logical drive that has a flash backed write cache enabled.  (POST Lockup 0x1BC0)
  • Various scenarios where drive LEDs might not be displayed correctly.
  • Drives might not be detected after a cold boot.
  • A hot-inserted drive might be immediately reported as failed.
  • A failed or charging HPE Smart Storage Battery might be reported as “missing” in SSA and iLO.
  • The RESTful management interface might be unable to detect physical drives or make configuration changes to the controller.
  • Option to enable “No Battery Write Cache” in SSA is not available if an HPE Smart Storage Battery is not installed.
  • Customer specified read/write controller cache ratio is not honored if “No Battery Write Cache” is enabled.
  • Controller cache might be displayed as temporarily disabled following an unexpected shutdown and subsequent reboot.
  • Unable to modify the controller cache read/write ratio following an unexpected shutdown and subsequent reboot.
  • The controller cache might become disabled when running VMware ESXi 6.0 if the controller and guest OS are configured to use PCI pass-through.
  • If multiple logical volumes are present on the same array, and one of the volumes is rebuilding, the others might be incorrectly marked as failed.
  • A drive at index 0 might incorrectly display as rebuilding if a logical volume on the controller is currently rebuilding.
  • System might hang during power-up or appear unresponsive during runtime if a logical volume composed of SSD’s is created or rebuilding.
  • Negotiated link rate for drives might not be correct.
  • Storage enclosure information for direct attached drives might not be returned correctly in Windows.
  • The HPE SmartCache feature was not available by default on the P816i-a SR Gen10 controller.
Enhancements

  • Support for ATA Sanitize Freeze/Antifreeze Lock.
  • Ability to select boot controller in Legacy BIOS mode with multiple controllers installed.
  • Updated Hard Drive Carrier LED behavior for the HPE ProLiant XL450 Gen10 Server.
  • Ability to set rebuild priorities via the RESTful management interface.
  • Supported settings – High, MediumHigh, Medium, Low