Printable version

Drivers & software

* RECOMMENDED * Supplemental Update / Online ROM Flash Component for Linux (x64) - 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): Red Hat Enterprise Linux 6 Server (x86-64)
Red Hat Enterprise Linux 7 Server
SUSE Linux Enterprise Server 11 (AMD64/EM64T)
SUSE Linux Enterprise Server 12
SUSE Linux Enterprise Server 15
Multi-part download
File name: firmware-smartarray-f7c07bdbbd-1.60-1.1.x86_64.compsig (2.2 KB)
File name: firmware-smartarray-f7c07bdbbd-1.60-1.1.x86_64.rpm (8.0 MB)
This x64 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:

334908e93f86d750b66f3788ebe97d0b0d05b206820468c772d701ac3ca392f2 rpm/RPMS/x86_64/firmware-smartarray-f7c07bdbbd-1.60-1.1.x86_64.compsig
335f2f9355b13a32085abc66f11b5d96e67653f1971c90275a854c6b6e8c5f02 rpm/RPMS/x86_64/firmware-smartarray-f7c07bdbbd-1.60-1.1.x86_64.rpm

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


Installation:

To update firmware from Linux operating system on target server:

Updating firmware with rpm installed:

  • Install the firmware rpm using the command:  rpm -ivh <rpm_filename>.  This extracts the contents of the rpm to the '/usr/lib/x86_64-linux-gnu' location
  • The CP034557.scexe script is located in the 'scexe-compat' folder. The actual name of the 'firmware-smartarray-f7c07bdbbd-*' folder is based on the version of the rpm installed in the first step above
  • To install firmware, you can execute ONE of the following commands:
    • ./ CP034557.scexe in the '/usr/lib/x86_64-linux-gnu/scexe-compat' location (OR)
    • ./setup in the '/usr/lib/x86_64-linux-gnu/firmware-smartarray-f7c07bdbbd-*' location
  • The results of the firmware upgrade are saved to the Component.log file, located in the /var/cpq/ directory
  • To uninstall the rpm, run the command: rpm -e <rpm_package_name>, which is the rpm filename without the '.rpm' extension

Updating firmware without installing the rpm:

  • Extract the contents of the rpm using the command: rpm2cpio <rpm_filename>.rpm | cpio -id.  This extracts the contents of the rpm to 'usr' folder in the current directory
  • Navigate to the 'usr/lib/x86_64-linux-gnu/firmware-smartarray-f7c07bdbbd-*' location and run ./setup to update the firmware. The actual name of the 'firmware-smartarray-f7c07bdbbd-*' folder is based on the version of the rpm installed in the step above
  • The results of the firmware upgrade are saved to the Component.log file, located in the /var/cpq/ directory

Additional Information:

Installing the firmware rpm package (rpm -ivh) does not update the firmware.  It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.

 

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

Offline:

  • Place the Service Pack for ProLiant on a USB key using the USB Key Utility for Windows.
  • Place the desired firmware to be updated in the directory, /SPP20xxxxx/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.

Online:

  • Login as root. (You must be root in order to apply the ROM update.)
  • Place the desired firmware to be updated in the directory, /SPP20xxxxx/packages
  • Run launch_sum.sh script which is found in the root of the ISO
  • Follow the instructions on the screen

 


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:
     Supplemental Update / Online ROM Flash Component for Linux (x64) - 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

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

Version:1.04(B) (25 Sep 2017)
Enhancements

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

  • Customers who already have firmware version 1.04 installed do not need to update to 1.04 (B).

 

Version 1.04 (B)

  • Added support for new models of HPE ProLiant servers:
    • DL120 Gen10

Version 1.04

  • Initial firmware release for HPE P/E-Class SR Gen10 controllers.
     

Version:1.04 (12 Jul 2017)
Fixes

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


  • Initial firmware release for HPE P/E-Class SR Gen10 controllers.
Enhancements

  • Initial firmware release for HPE P/E-Class SR Gen10 controllers.

Type: Firmware - Storage Controller
Version: 1.60(19 Jul 2018)
Operating System(s):
Red Hat Enterprise Linux 6 Server (x86-64)
Red Hat Enterprise Linux 7 Server
SUSE Linux Enterprise Server 11 (AMD64/EM64T)
SUSE Linux Enterprise Server 12
SUSE Linux Enterprise Server 15

Description

This x64 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:

334908e93f86d750b66f3788ebe97d0b0d05b206820468c772d701ac3ca392f2 rpm/RPMS/x86_64/firmware-smartarray-f7c07bdbbd-1.60-1.1.x86_64.compsig
335f2f9355b13a32085abc66f11b5d96e67653f1971c90275a854c6b6e8c5f02 rpm/RPMS/x86_64/firmware-smartarray-f7c07bdbbd-1.60-1.1.x86_64.rpm

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


Installation:

To update firmware from Linux operating system on target server:

Updating firmware with rpm installed:

  • Install the firmware rpm using the command:  rpm -ivh <rpm_filename>.  This extracts the contents of the rpm to the '/usr/lib/x86_64-linux-gnu' location
  • The CP034557.scexe script is located in the 'scexe-compat' folder. The actual name of the 'firmware-smartarray-f7c07bdbbd-*' folder is based on the version of the rpm installed in the first step above
  • To install firmware, you can execute ONE of the following commands:
    • ./ CP034557.scexe in the '/usr/lib/x86_64-linux-gnu/scexe-compat' location (OR)
    • ./setup in the '/usr/lib/x86_64-linux-gnu/firmware-smartarray-f7c07bdbbd-*' location
  • The results of the firmware upgrade are saved to the Component.log file, located in the /var/cpq/ directory
  • To uninstall the rpm, run the command: rpm -e <rpm_package_name>, which is the rpm filename without the '.rpm' extension

Updating firmware without installing the rpm:

  • Extract the contents of the rpm using the command: rpm2cpio <rpm_filename>.rpm | cpio -id.  This extracts the contents of the rpm to 'usr' folder in the current directory
  • Navigate to the 'usr/lib/x86_64-linux-gnu/firmware-smartarray-f7c07bdbbd-*' location and run ./setup to update the firmware. The actual name of the 'firmware-smartarray-f7c07bdbbd-*' folder is based on the version of the rpm installed in the step above
  • The results of the firmware upgrade are saved to the Component.log file, located in the /var/cpq/ directory

Additional Information:

Installing the firmware rpm package (rpm -ivh) does not update the firmware.  It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps.

 

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

Offline:

  • Place the Service Pack for ProLiant on a USB key using the USB Key Utility for Windows.
  • Place the desired firmware to be updated in the directory, /SPP20xxxxx/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.

Online:

  • Login as root. (You must be root in order to apply the ROM update.)
  • Place the desired firmware to be updated in the directory, /SPP20xxxxx/packages
  • Run launch_sum.sh script which is found in the root of the ISO
  • Follow the instructions on the screen

 


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:
     Supplemental Update / Online ROM Flash Component for Linux (x64) - 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

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

Version:1.04(B) (25 Sep 2017)
Enhancements

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

  • Customers who already have firmware version 1.04 installed do not need to update to 1.04 (B).

 

Version 1.04 (B)

  • Added support for new models of HPE ProLiant servers:
    • DL120 Gen10

Version 1.04

  • Initial firmware release for HPE P/E-Class SR Gen10 controllers.
     

Version:1.04 (12 Jul 2017)
Fixes

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


  • Initial firmware release for HPE P/E-Class SR Gen10 controllers.
Enhancements

  • Initial firmware release for HPE P/E-Class SR Gen10 controllers.