Printable version

Drivers & software

** CRITICAL ** Online ROM Flash Component for Windows (x64) - HPE Smart Array P408i-p, P408e-p, P408i-a, P408i-c, E208i-p, E208e-p, E208i-c, E208i-a, P408i-sb, 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: 3.00(11 Aug 2020)
Operating System(s): Microsoft Windows Server 2012 R2
Microsoft Windows Server 2016
Microsoft Windows Server 2019
Multi-part download
File name: cp044558.compsig (2.2 KB)
File name: cp044558.exe (5.8 MB)
File name: cp044558.md5 (48 Bytes)
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, P408i-sb, P204i-c, P204i-b, P816i-a and P416ie-m SR Gen10

 The following enhancements are part of the Smart Array controller firmware
   v3.00:

     * After a firmware upgrade and reboot, the background parity
       initialization process starts for logical drives with incomplete or
       failed background parity initialization status.

     * Previously, background surface scans for data consistency could wait
       up to 14 days between runs. Surface scan now restarts immediately when
       a consistency check fails. When no surface scan issues are found,
       surface scan maintains the 14 day waiting period.

Prerequisites:

     * Back up your data before initiating a firmware update.


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

4ee40a855995889f0d02681786ab857448ee4e3046aed63aca7c8adb10f97a1e cp044558.md5
b7c14318af59e92af18e01b9209ee934c7eb9326622158f4b8d71765c3210a4e cp044558.exe
5dea6b5d99104d46ea74daeb28ec9010b03a78fc0f9e329b93161759842e2e17 cp044558.compsig

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


Installation:

 The HPE Smart Array SR Gen10 Controller firmware is available at the
   following website: https://www.hpe.com/support/hpesc.

   When you use a downloaded component to update the firmware, see the
   installation instructions provided with the downloaded component.

   IMPORTANT:

   After installation, a server restart is required to activate the firmware.
   Avoid power interruptions during the firmware installation and activation
   processes.

   Depending on your logical drive configuration and status, the firmware
   might initiate the background parity initialization process for one or
   more logical drives. The process starts when you reboot to activate the
   firmware, and it completes one drive at a time.

   If background parity initialization is initiated, the following message is
   displayed during POST:

   1729-Slot 1 Drive Array - Performance may increase after optimization Scan completes.
   Action: No Action Needed.

   You can monitor the status by using the HPE SSA GUI or the HPE SSA CLI.


End User License Agreements:
HPE Software License Agreement v1
Hewlett-Packard End User License Agreement


Upgrade Requirement:
Critical - HPE requires users update to this version immediately.


Notes:

Related information

   The latest documentation for HPE Smart Array SR Gen10 controllers is
   available at:

   https://www.hpe.com/info/SmartArrayGen10-docs


Upgrade Requirement:
Critical - HPE requires users update to this version immediately.


  The following issues have been fixed in Smart Array controller firmware
   v3.00:

     * Background surface scan might not repair media errors on 12G SAS
       drives in RAID 1, 5, 10, and 50 logical drives.

     * In some I/O workloads, the file system or application might read
       incorrect data from encrypted RAID 0 (with two or more physical
       drives) or RAID 10/10ADM (with four or more physical drives) logical
       drives.

     * A controller might hang when a Test Unit Ready command fails during
       SSD logical drive Rapid Parity Initialization.

     * During a rebuild and extreme simultaneous host I/O writes, the rebuild
       operation might use old data, resulting in subsequent host reads that
       might return old data.

     * A host might read incorrect data after background parity
       initialization finishes on a logical drive on a single array with
       multiple logical drives.

     * A controller lockup issue might occur during the repair of an
       unrecoverable read error (URE) on a RAID 5 volume.

     * A controller lockup issue might occur during SmartCache error
       handling.

     * A controller lockup issue might occur during controller boot when
       SmartCache is enabled.

     * A file system or application might read incorrect data when a
       coalesced host request encounters a fatal error.

     * A failed drive installed during controller boot is not identified as a
       failed drive.

     * The failed drive status LED is not illuminated when a good drive is
       replaced with a failed drive in a backplane.

     * In configurations with backplanes, a failed drive installed as a
       replacement for a previously configured RAID volume is not identified
       as a failed drive.

     * A rebuild of a logical drive created from SSD drives fails to start
       within 1,200 seconds.

     * A performance drop during 16k to 256k sequential reads with low queue
       depth occurs on a logical drive with cache enabled.

     * A controller lockup issue might occur during a simultaneous host write
       and background cache flush operation.

     * Incorrect connector information is displayed for SATA drives after
       certain physical events in a dual I/O module enclosure configuration.

     * A failed drive that is physically present in a drive bay is not
       reported correctly.

     * Devices might drop out of a configuration after multiple create or
       delete drive zone group commands are issued.

     * The drive status LED does not flash during sanitize operations if
       drives are attached to an expander.

     * Cache disable status is not updated correctly when backup power source
       charging times out.

     * The clear configuration command might not clear the configuration if
       SmartCache is enabled and the system was previously shut down
       ungracefully.

     * The clear configuration command fails if a SmartCache volume has
       multiple UREs within a SmartCache page block size.

     * A controller lockup issue might occur when toggling a path to an
       enclosure in a dual domain configuration.

     * The controller runs in survival mode if a temperature sensor is not
       detected.

     * The clear configuration command might report failures when it
       encounters an installed drive with failed status.

     * A performance drop occurs during sequential workloads.

     * A controller failure might occur when running concurrent I/O to
       unassigned drives and drives in a RAID logical drive.

     * After a reboot, a bad drive might prevent controller discovery or
       operating system startup.

     * A host request is incorrectly returned as Failed when a failed drive
       in a degraded volume is replaced.

     * Modifying the spare configuration under an active spare rebuild causes
       the rebuild process to stop.

     * Incorrect device location reporting occurs when direct-attach drives
       are not attached to a backplane and an enclosure management schema is
       not defined.

     * RAID volume configuration settings are not applied when a disk drive
       transitions from unassigned to RAID usage during runtime.

     * A RAID volume with a failed drive reappears after a clear
       configuration operation completes and the system is rebooted.

     * A controller might hang during a SmartCache flush task that encounters
       multiple unrecoverable media errors (UREs).

     * A response of all zeros is sent for ATA PASSTHROUGH commands, such as
       SMART READ DATA, through Out of Band (OOB) host transport.

Version:3.21 (16 Dec 2020)
Fixes

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


  • A controller lockup issue occurs when clearing the configuration of an encryption-enabled controller.
  • When unconfigured drives are directly attached, the PHY ID is always 0 in the ADU report or lsscsi output.
  • A file system or application might read incorrect data when there is pending read or write operation and an array transformation is in progress on the logical drives.
  • A rekey operation on a SmartCache volume pauses when the controller firmware is upgraded and the server is warm rebooted.
  • A SMART READ DATA command sent with an out-of-band method returns a response of all zeros.
  • The Maximum Connection Number calculation for an indirectly attached wide-port end-target is incorrect.
  • In some servers, the CPU takes a long time to send a completion message for a PCIe task. This time period exceeds the timeout limit and results in a completion timeout, which triggers a fatal error.
  • A firmware exception might occur during task management abort handling for a non-NCQ SATA command.
  • A missing SMP request might cause a firmware timeout.
  • A topology rescan might report complete status prematurely.
  • I2C read failures occur when multiple write commands are sent to the SEEPROM without allowing sufficient time between commands.
  • A controller lockup issue might occur when the PHYs fluctuate between link up/link down status.
  • The encryption self-test reports a false failure on a hardware block that is not used by the controller.
  • A SATA firmware lockup issue might occur when a Report Zones command receives a link error during a device reset.
  • Open frames cause an I/O timeout that results in an Open Reject Bad Destination response and a host I/O timeout. This situation causes a server node to be evicted from a cluster.
  • Removing a redundant fan module in an attached JBOD causes Failed JBOD status.
  • The controller might not respond for up to 15 minutes when a drive reports a hardware failure.
  • Specifying an incorrect serial number in the API when attempting to HALON flash a drive does not result in the expected error.
  • A SmartCache write bypass might result in a cache line getting stuck on a pending queue if the write to the primary logical drive is retried.
  • A controller might not respond if it is repeatedly forced between SIS (Inbox) and PQI I/O submission modes at the same time as an I/O timeout.
  • An issue in the write coalescing logic might cause a partially coalesced opportunity to be abandoned under high queue depth workloads.
  • The OS driver reports a lockup code that does not match the code provided by the firmware.
  • SATA drives are unnecessarily reset during a power-on self-test.
  • The bay number of a non-hot-plug drive is reported as 255/0xFF when the device inventory requery API is initiated.
  • A controller might not respond when a clear configuration action is initiated at the same time that a degraded volume is undergoing Rapid Parity Initialization.
  • I/O coalescing is not enabled when DDR cache is not present or enabled.
  • A drive incorrectly reports failed status if it is spun down and then used to create a volume with Rapid Parity Initialization.
  • SmartCache metadata is lost after a new volume is created while running I/O traff ic.
  • An abnormal volume state is observed with multiple SmartCache volumes configured using 512e drives.
  • A controller might not respond during volume transformation if the backup power source goes off line, is spuriously hot-removed, or indicates a cabling error.
  • A LUN reset issue occurs during heavy write I/O workloads on cache enabled volumes.
  • An incorrect spare SSD physical drive state is reported during a rebuild.
  • An I/O latency issue occurs during periodic disk write metadata operations.
  • A drive failure code might be incorrectly updated with a generic drive failure code.
  • When an expanding SmartCache volume is migrated to another controller after an ungraceful shutdown, the volume is not configured correctly.
  • A controller might not respond when an expanding volume is migrated from a controller that supports DDR cache to a controller that does not support DDR cache.
  • In a split mirror configuration, the cache ratio is reset to the default values after a backup cable error.
  • A controller might not respond after a cold boot during volume rekeying.
  • A controller lockup issue might occur in an HBA SAS drive dual path configuration.
  • A device reset command initiated by a host utility has a timeout issue in minimum power mode.
  • If you use the identify all LED command frequently, the command might not aff ect all drive LEDs.
  • A controller does not respond when you run the Internal Test Unit Ready command during drive hot removal or addition.
  • Marking an Unrecoverable Read Error (URE) on a drive might return success status even though the drive did not plant the URE successfully.
  • A controller lock up issue might occur when resuming a rebuild operation after a reboot.
  • A surface scan inconsistency check event is not logged for RAID 1 volumes.
  • A controller lock up issue might occur when activating a spare drive for an encrypted volume during I/Os.
  • A drive that failed due to read capacity is presented to the host.
  • A periodic background drive temperature check might skip every other minute.
  • A controller lockup issue might occur during expansion after multiple subsequent attempts to abort the expansion process.
  • A backup/restore error occurs during controller migration.
  • Encryption host management commands are processed for a SmartCache volume, even though these commands do not apply to SmartCache volumes.
  • A host might read incorrect data after an array expansion operation.
  • High severity events logged when a controller is in the critical event buff er overflow condition are not prioritized.
  • Redundant surface scan pass complete events might be posted for the same surface scan iteration if the controller is rebooted during the scan.
  • During an expander firmware upgrade (reduced functionality mode), the last management device index remains open for processing I/Os, and an I/O timeout might occur.
  • A performance drop is observed on certain queue depths for the 4 kB sequential write workload on RAID logical volumes with SmartPath and DDR caching disabled.
  • A command timeout issue occurs during expander firmware upgrade with Non-DisruptiveSoft Reset.
Enhancements

  • Enhanced the performance of sequential READ I/Os greater than 256KiB for cached logical drives.
  • Added support for user-configurable expander scan duration parameters.
  • Improved background consistency check to scan logical drives more eff iciently.
  • Added support for Port Discovery Protocol host tool option to support SGPIO or UBM backplanes.
  • Improved handling of reserved SMBUS addresses.

Version:3.00 (11 Aug 2020)
Fixes

Upgrade Requirement:
Critical - HPE requires users update to this version immediately.


  The following issues have been fixed in Smart Array controller firmware
   v3.00:

     * Background surface scan might not repair media errors on 12G SAS
       drives in RAID 1, 5, 10, and 50 logical drives.

     * In some I/O workloads, the file system or application might read
       incorrect data from encrypted RAID 0 (with two or more physical
       drives) or RAID 10/10ADM (with four or more physical drives) logical
       drives.

     * A controller might hang when a Test Unit Ready command fails during
       SSD logical drive Rapid Parity Initialization.

     * During a rebuild and extreme simultaneous host I/O writes, the rebuild
       operation might use old data, resulting in subsequent host reads that
       might return old data.

     * A host might read incorrect data after background parity
       initialization finishes on a logical drive on a single array with
       multiple logical drives.

     * A controller lockup issue might occur during the repair of an
       unrecoverable read error (URE) on a RAID 5 volume.

     * A controller lockup issue might occur during SmartCache error
       handling.

     * A controller lockup issue might occur during controller boot when
       SmartCache is enabled.

     * A file system or application might read incorrect data when a
       coalesced host request encounters a fatal error.

     * A failed drive installed during controller boot is not identified as a
       failed drive.

     * The failed drive status LED is not illuminated when a good drive is
       replaced with a failed drive in a backplane.

     * In configurations with backplanes, a failed drive installed as a
       replacement for a previously configured RAID volume is not identified
       as a failed drive.

     * A rebuild of a logical drive created from SSD drives fails to start
       within 1,200 seconds.

     * A performance drop during 16k to 256k sequential reads with low queue
       depth occurs on a logical drive with cache enabled.

     * A controller lockup issue might occur during a simultaneous host write
       and background cache flush operation.

     * Incorrect connector information is displayed for SATA drives after
       certain physical events in a dual I/O module enclosure configuration.

     * A failed drive that is physically present in a drive bay is not
       reported correctly.

     * Devices might drop out of a configuration after multiple create or
       delete drive zone group commands are issued.

     * The drive status LED does not flash during sanitize operations if
       drives are attached to an expander.

     * Cache disable status is not updated correctly when backup power source
       charging times out.

     * The clear configuration command might not clear the configuration if
       SmartCache is enabled and the system was previously shut down
       ungracefully.

     * The clear configuration command fails if a SmartCache volume has
       multiple UREs within a SmartCache page block size.

     * A controller lockup issue might occur when toggling a path to an
       enclosure in a dual domain configuration.

     * The controller runs in survival mode if a temperature sensor is not
       detected.

     * The clear configuration command might report failures when it
       encounters an installed drive with failed status.

     * A performance drop occurs during sequential workloads.

     * A controller failure might occur when running concurrent I/O to
       unassigned drives and drives in a RAID logical drive.

     * After a reboot, a bad drive might prevent controller discovery or
       operating system startup.

     * A host request is incorrectly returned as Failed when a failed drive
       in a degraded volume is replaced.

     * Modifying the spare configuration under an active spare rebuild causes
       the rebuild process to stop.

     * Incorrect device location reporting occurs when direct-attach drives
       are not attached to a backplane and an enclosure management schema is
       not defined.

     * RAID volume configuration settings are not applied when a disk drive
       transitions from unassigned to RAID usage during runtime.

     * A RAID volume with a failed drive reappears after a clear
       configuration operation completes and the system is rebooted.

     * A controller might hang during a SmartCache flush task that encounters
       multiple unrecoverable media errors (UREs).

     * A response of all zeros is sent for ATA PASSTHROUGH commands, such as
       SMART READ DATA, through Out of Band (OOB) host transport.

Enhancements

 The following enhancements are part of the Smart Array controller firmware
   v3.00:

     * After a firmware upgrade and reboot, the background parity
       initialization process starts for logical drives with incomplete or
       failed background parity initialization status.

     * Previously, background surface scans for data consistency could wait
       up to 14 days between runs. Surface scan now restarts immediately when
       a consistency check fails. When no surface scan issues are found,
       surface scan maintains the 14 day waiting period.


Version:2.65 (13 Mar 2020)
Fixes

Upgrade Requirement:
Critical - HPE requires users update to this version immediately.


REMOVED -  Firmware version 2.65 is NO LONGER AVAILABLE for download. Review HPE Customer Bulletin a00097210en_us for additional information that includes replacement firmware version.

  • Prevents a potential data inconsistency from occurring after experiencing an Unrecoverable Read Error (URE) on a drive configured in RAID 1/10/ADM Fault Tolerant Mode.
  • Prevents a potential data inconsistency from occurring during initial configuration and operation of a volume configured in RAID 5/6/50/60 Fault Tolerant Mode.

o   For additional information regarding Compute and Storage platforms, reference Customer Bulletin a00097210en_us.

  • HPE does NOT recommend independently updating to Firmware Versions Newer than 1.99 for HPE Smart Array SR Gen10 Controllers on HPE SimpliVity Gen10 systems.
    For additional information regarding SimpliVity platforms, reference Customer Bulletin a00097566en_us

 

IMPORTANT: RAID 0 and drives in HBA Mode are not affected.


Version:2.62 (20 Dec 2019)
Fixes

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


REMOVED -  Firmware version 2.62 is NO LONGER AVAILABLE for download. Review HPE Customer Bulletin a00097210en_us for additional information that includes replacement firmware version.

 

Fixes the following unexpected behaviors:

  • Controller could stop responding with a 0x1A91 message during active path failure when scanning expander indexes.
  • Controller could stop responding during I/O processing and Smart Cache flush process if there is an invalid transient message return by the physical drives.
  • When predictive spare rebuild is triggered on Smart Cache, the rebuilding process could fail to start.
  • Data could become inaccessible when a SATA drive overruns a data transfer
  • Controller memory could become unstable when the response to an Identify Device command (IDD) is received from a drive
  • Communication between the host system and a RAID5/6 volume could potentially fail after an I/O timeout on one of the drives in the array.
  • System could stop responding with a 0x1E30 message when an ATA locked drive is discovered
  • If a command is execute during a drive sanitize operation the controller could stop responding.
Enhancements

  • Add UBM1 Support
  • Support for backup power source charge timeout values from UEFI
  • UBM2 backplane support
  • Drive hotplug support for UBM backplanes

Version:2.02 (10 Sep 2019)
Fixes

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


REMOVED -  Firmware version 2.02 is NO LONGER AVAILABLE for download. Review HPE Customer Bulletin a00097210en_us for additional information that includes replacement firmware version.

 

Fixes the following unexpected behaviors:

  • Controller could stop responding with a 0x1A91 message during active path failure when scanning expander indexes.
  • Controller could stop responding during I/O processing and Smart Cache flush process if there is an invalid transient message return by the physical drives.
  • When predictive spare rebuild is triggered on Smart Cache, the rebuilding process could fail to start.
  • Data could become inaccessible when a SATA drive overruns a data transfer
  • Controller memory could become unstable when the response to an Identify Device command (IDD) is received from a drive
  • Communication between the host system and a RAID5/6 volume could potentially fail after an I/O timeout on one of the drives in the array.
  • System could stop responding with a 0x1E30 message when an ATA locked drive is discovered
  • If a command is execute during a drive sanitize operation the controller could stop responding.

Version:1.99 (18 Jun 2019)
Fixes

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


REMOVED -  Firmware version 1.99 is NO LONGER AVAILABLE for download. Review HPE Customer Bulletin a00097210en_us for additional information that includes replacement firmware version..

 

Fixes the following unexpected behaviors:

  • Controller could stop responding with a 0x1A91 message during active path failure when scanning expander indexes.
  • Controller could stop responding during I/O processing and Smart Cache flush process if there is an invalid transient message return by the physical drives.
  • When predictive spare rebuild is triggered on Smart Cache, the rebuilding process could fail to start.
  • Data could become inaccessible when a SATA drive overruns a data transfer
  • Controller memory could become unstable when the response to an Identify Device command (IDD) is received from a drive
  • Communication between the host system and a RAID5/6 volume could potentially fail after an I/O timeout on one of the drives in the array.
  • System could stop responding with a 0x1E30 message when an ATA locked drive is discovered
  • If a command is execute during a drive sanitize operation the controller could stop responding.

Version:1.98 (2 Apr 2019)
Fixes

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


REMOVED -  Firmware version 1.98 is NO LONGER AVAILABLE for download. Review HPE Customer Bulletin a00097210en_us for additional information that includes replacement firmware version..

 

Fixes the following unexpected behaviors:

  • Controller could stop responding with a 0x1A91 message during active path failure when scanning expander indexes.
  • Controller could stop responding during I/O processing and Smart Cache flush process if there is an invalid transient message return by the physical drives.
  • When predictive spare rebuild is triggered on Smart Cache, the rebuilding process could fail to start.
  • Data could become inaccessible when a SATA drive overruns a data transfer
  • Controller memory could become unstable when the response to an Identify Device command (IDD) is received from a drive
  • Communication between the host system and a RAID5/6 volume could potentially fail after an I/O timeout on one of the drives in the array.
  • System could stop responding with a 0x1E30 message when an ATA locked drive is discovered
  • If a command is execute during a drive sanitize operation the controller could stop responding.

Version:1.65(B) (27 Nov 2018)
Enhancements

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

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


Added support for Microsoft Windows Server 2019 OS.


Version:1.65 (27 Sep 2018)
Fixes

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


  • System might stop responding at POST and fail to load an OS. This issue is more likely to occur if System BIOS version is 1.40 or later. However, systems running older BIOS versions could experience this issue also.

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: 3.00(11 Aug 2020)
Operating System(s):
Microsoft Windows Server 2012 R2
Microsoft Windows Server 2016
Microsoft Windows Server 2019

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, P408i-sb, P204i-c, P204i-b, P816i-a and P416ie-m SR Gen10

Enhancements

 The following enhancements are part of the Smart Array controller firmware
   v3.00:

     * After a firmware upgrade and reboot, the background parity
       initialization process starts for logical drives with incomplete or
       failed background parity initialization status.

     * Previously, background surface scans for data consistency could wait
       up to 14 days between runs. Surface scan now restarts immediately when
       a consistency check fails. When no surface scan issues are found,
       surface scan maintains the 14 day waiting period.

Installation Instructions

Prerequisites:

     * Back up your data before initiating a firmware update.


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

4ee40a855995889f0d02681786ab857448ee4e3046aed63aca7c8adb10f97a1e cp044558.md5
b7c14318af59e92af18e01b9209ee934c7eb9326622158f4b8d71765c3210a4e cp044558.exe
5dea6b5d99104d46ea74daeb28ec9010b03a78fc0f9e329b93161759842e2e17 cp044558.compsig

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


Installation:

 The HPE Smart Array SR Gen10 Controller firmware is available at the
   following website: https://www.hpe.com/support/hpesc.

   When you use a downloaded component to update the firmware, see the
   installation instructions provided with the downloaded component.

   IMPORTANT:

   After installation, a server restart is required to activate the firmware.
   Avoid power interruptions during the firmware installation and activation
   processes.

   Depending on your logical drive configuration and status, the firmware
   might initiate the background parity initialization process for one or
   more logical drives. The process starts when you reboot to activate the
   firmware, and it completes one drive at a time.

   If background parity initialization is initiated, the following message is
   displayed during POST:

   1729-Slot 1 Drive Array - Performance may increase after optimization Scan completes.
   Action: No Action Needed.

   You can monitor the status by using the HPE SSA GUI or the HPE SSA CLI.


Release Notes

End User License Agreements:
HPE Software License Agreement v1
Hewlett-Packard End User License Agreement


Upgrade Requirement:
Critical - HPE requires users update to this version immediately.


Notes:

Related information

   The latest documentation for HPE Smart Array SR Gen10 controllers is
   available at:

   https://www.hpe.com/info/SmartArrayGen10-docs


Fixes

Upgrade Requirement:
Critical - HPE requires users update to this version immediately.


  The following issues have been fixed in Smart Array controller firmware
   v3.00:

     * Background surface scan might not repair media errors on 12G SAS
       drives in RAID 1, 5, 10, and 50 logical drives.

     * In some I/O workloads, the file system or application might read
       incorrect data from encrypted RAID 0 (with two or more physical
       drives) or RAID 10/10ADM (with four or more physical drives) logical
       drives.

     * A controller might hang when a Test Unit Ready command fails during
       SSD logical drive Rapid Parity Initialization.

     * During a rebuild and extreme simultaneous host I/O writes, the rebuild
       operation might use old data, resulting in subsequent host reads that
       might return old data.

     * A host might read incorrect data after background parity
       initialization finishes on a logical drive on a single array with
       multiple logical drives.

     * A controller lockup issue might occur during the repair of an
       unrecoverable read error (URE) on a RAID 5 volume.

     * A controller lockup issue might occur during SmartCache error
       handling.

     * A controller lockup issue might occur during controller boot when
       SmartCache is enabled.

     * A file system or application might read incorrect data when a
       coalesced host request encounters a fatal error.

     * A failed drive installed during controller boot is not identified as a
       failed drive.

     * The failed drive status LED is not illuminated when a good drive is
       replaced with a failed drive in a backplane.

     * In configurations with backplanes, a failed drive installed as a
       replacement for a previously configured RAID volume is not identified
       as a failed drive.

     * A rebuild of a logical drive created from SSD drives fails to start
       within 1,200 seconds.

     * A performance drop during 16k to 256k sequential reads with low queue
       depth occurs on a logical drive with cache enabled.

     * A controller lockup issue might occur during a simultaneous host write
       and background cache flush operation.

     * Incorrect connector information is displayed for SATA drives after
       certain physical events in a dual I/O module enclosure configuration.

     * A failed drive that is physically present in a drive bay is not
       reported correctly.

     * Devices might drop out of a configuration after multiple create or
       delete drive zone group commands are issued.

     * The drive status LED does not flash during sanitize operations if
       drives are attached to an expander.

     * Cache disable status is not updated correctly when backup power source
       charging times out.

     * The clear configuration command might not clear the configuration if
       SmartCache is enabled and the system was previously shut down
       ungracefully.

     * The clear configuration command fails if a SmartCache volume has
       multiple UREs within a SmartCache page block size.

     * A controller lockup issue might occur when toggling a path to an
       enclosure in a dual domain configuration.

     * The controller runs in survival mode if a temperature sensor is not
       detected.

     * The clear configuration command might report failures when it
       encounters an installed drive with failed status.

     * A performance drop occurs during sequential workloads.

     * A controller failure might occur when running concurrent I/O to
       unassigned drives and drives in a RAID logical drive.

     * After a reboot, a bad drive might prevent controller discovery or
       operating system startup.

     * A host request is incorrectly returned as Failed when a failed drive
       in a degraded volume is replaced.

     * Modifying the spare configuration under an active spare rebuild causes
       the rebuild process to stop.

     * Incorrect device location reporting occurs when direct-attach drives
       are not attached to a backplane and an enclosure management schema is
       not defined.

     * RAID volume configuration settings are not applied when a disk drive
       transitions from unassigned to RAID usage during runtime.

     * A RAID volume with a failed drive reappears after a clear
       configuration operation completes and the system is rebooted.

     * A controller might hang during a SmartCache flush task that encounters
       multiple unrecoverable media errors (UREs).

     * A response of all zeros is sent for ATA PASSTHROUGH commands, such as
       SMART READ DATA, through Out of Band (OOB) host transport.

Revision History

Version:3.21 (16 Dec 2020)
Fixes

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


  • A controller lockup issue occurs when clearing the configuration of an encryption-enabled controller.
  • When unconfigured drives are directly attached, the PHY ID is always 0 in the ADU report or lsscsi output.
  • A file system or application might read incorrect data when there is pending read or write operation and an array transformation is in progress on the logical drives.
  • A rekey operation on a SmartCache volume pauses when the controller firmware is upgraded and the server is warm rebooted.
  • A SMART READ DATA command sent with an out-of-band method returns a response of all zeros.
  • The Maximum Connection Number calculation for an indirectly attached wide-port end-target is incorrect.
  • In some servers, the CPU takes a long time to send a completion message for a PCIe task. This time period exceeds the timeout limit and results in a completion timeout, which triggers a fatal error.
  • A firmware exception might occur during task management abort handling for a non-NCQ SATA command.
  • A missing SMP request might cause a firmware timeout.
  • A topology rescan might report complete status prematurely.
  • I2C read failures occur when multiple write commands are sent to the SEEPROM without allowing sufficient time between commands.
  • A controller lockup issue might occur when the PHYs fluctuate between link up/link down status.
  • The encryption self-test reports a false failure on a hardware block that is not used by the controller.
  • A SATA firmware lockup issue might occur when a Report Zones command receives a link error during a device reset.
  • Open frames cause an I/O timeout that results in an Open Reject Bad Destination response and a host I/O timeout. This situation causes a server node to be evicted from a cluster.
  • Removing a redundant fan module in an attached JBOD causes Failed JBOD status.
  • The controller might not respond for up to 15 minutes when a drive reports a hardware failure.
  • Specifying an incorrect serial number in the API when attempting to HALON flash a drive does not result in the expected error.
  • A SmartCache write bypass might result in a cache line getting stuck on a pending queue if the write to the primary logical drive is retried.
  • A controller might not respond if it is repeatedly forced between SIS (Inbox) and PQI I/O submission modes at the same time as an I/O timeout.
  • An issue in the write coalescing logic might cause a partially coalesced opportunity to be abandoned under high queue depth workloads.
  • The OS driver reports a lockup code that does not match the code provided by the firmware.
  • SATA drives are unnecessarily reset during a power-on self-test.
  • The bay number of a non-hot-plug drive is reported as 255/0xFF when the device inventory requery API is initiated.
  • A controller might not respond when a clear configuration action is initiated at the same time that a degraded volume is undergoing Rapid Parity Initialization.
  • I/O coalescing is not enabled when DDR cache is not present or enabled.
  • A drive incorrectly reports failed status if it is spun down and then used to create a volume with Rapid Parity Initialization.
  • SmartCache metadata is lost after a new volume is created while running I/O traff ic.
  • An abnormal volume state is observed with multiple SmartCache volumes configured using 512e drives.
  • A controller might not respond during volume transformation if the backup power source goes off line, is spuriously hot-removed, or indicates a cabling error.
  • A LUN reset issue occurs during heavy write I/O workloads on cache enabled volumes.
  • An incorrect spare SSD physical drive state is reported during a rebuild.
  • An I/O latency issue occurs during periodic disk write metadata operations.
  • A drive failure code might be incorrectly updated with a generic drive failure code.
  • When an expanding SmartCache volume is migrated to another controller after an ungraceful shutdown, the volume is not configured correctly.
  • A controller might not respond when an expanding volume is migrated from a controller that supports DDR cache to a controller that does not support DDR cache.
  • In a split mirror configuration, the cache ratio is reset to the default values after a backup cable error.
  • A controller might not respond after a cold boot during volume rekeying.
  • A controller lockup issue might occur in an HBA SAS drive dual path configuration.
  • A device reset command initiated by a host utility has a timeout issue in minimum power mode.
  • If you use the identify all LED command frequently, the command might not aff ect all drive LEDs.
  • A controller does not respond when you run the Internal Test Unit Ready command during drive hot removal or addition.
  • Marking an Unrecoverable Read Error (URE) on a drive might return success status even though the drive did not plant the URE successfully.
  • A controller lock up issue might occur when resuming a rebuild operation after a reboot.
  • A surface scan inconsistency check event is not logged for RAID 1 volumes.
  • A controller lock up issue might occur when activating a spare drive for an encrypted volume during I/Os.
  • A drive that failed due to read capacity is presented to the host.
  • A periodic background drive temperature check might skip every other minute.
  • A controller lockup issue might occur during expansion after multiple subsequent attempts to abort the expansion process.
  • A backup/restore error occurs during controller migration.
  • Encryption host management commands are processed for a SmartCache volume, even though these commands do not apply to SmartCache volumes.
  • A host might read incorrect data after an array expansion operation.
  • High severity events logged when a controller is in the critical event buff er overflow condition are not prioritized.
  • Redundant surface scan pass complete events might be posted for the same surface scan iteration if the controller is rebooted during the scan.
  • During an expander firmware upgrade (reduced functionality mode), the last management device index remains open for processing I/Os, and an I/O timeout might occur.
  • A performance drop is observed on certain queue depths for the 4 kB sequential write workload on RAID logical volumes with SmartPath and DDR caching disabled.
  • A command timeout issue occurs during expander firmware upgrade with Non-DisruptiveSoft Reset.
Enhancements

  • Enhanced the performance of sequential READ I/Os greater than 256KiB for cached logical drives.
  • Added support for user-configurable expander scan duration parameters.
  • Improved background consistency check to scan logical drives more eff iciently.
  • Added support for Port Discovery Protocol host tool option to support SGPIO or UBM backplanes.
  • Improved handling of reserved SMBUS addresses.

Version:3.00 (11 Aug 2020)
Fixes

Upgrade Requirement:
Critical - HPE requires users update to this version immediately.


  The following issues have been fixed in Smart Array controller firmware
   v3.00:

     * Background surface scan might not repair media errors on 12G SAS
       drives in RAID 1, 5, 10, and 50 logical drives.

     * In some I/O workloads, the file system or application might read
       incorrect data from encrypted RAID 0 (with two or more physical
       drives) or RAID 10/10ADM (with four or more physical drives) logical
       drives.

     * A controller might hang when a Test Unit Ready command fails during
       SSD logical drive Rapid Parity Initialization.

     * During a rebuild and extreme simultaneous host I/O writes, the rebuild
       operation might use old data, resulting in subsequent host reads that
       might return old data.

     * A host might read incorrect data after background parity
       initialization finishes on a logical drive on a single array with
       multiple logical drives.

     * A controller lockup issue might occur during the repair of an
       unrecoverable read error (URE) on a RAID 5 volume.

     * A controller lockup issue might occur during SmartCache error
       handling.

     * A controller lockup issue might occur during controller boot when
       SmartCache is enabled.

     * A file system or application might read incorrect data when a
       coalesced host request encounters a fatal error.

     * A failed drive installed during controller boot is not identified as a
       failed drive.

     * The failed drive status LED is not illuminated when a good drive is
       replaced with a failed drive in a backplane.

     * In configurations with backplanes, a failed drive installed as a
       replacement for a previously configured RAID volume is not identified
       as a failed drive.

     * A rebuild of a logical drive created from SSD drives fails to start
       within 1,200 seconds.

     * A performance drop during 16k to 256k sequential reads with low queue
       depth occurs on a logical drive with cache enabled.

     * A controller lockup issue might occur during a simultaneous host write
       and background cache flush operation.

     * Incorrect connector information is displayed for SATA drives after
       certain physical events in a dual I/O module enclosure configuration.

     * A failed drive that is physically present in a drive bay is not
       reported correctly.

     * Devices might drop out of a configuration after multiple create or
       delete drive zone group commands are issued.

     * The drive status LED does not flash during sanitize operations if
       drives are attached to an expander.

     * Cache disable status is not updated correctly when backup power source
       charging times out.

     * The clear configuration command might not clear the configuration if
       SmartCache is enabled and the system was previously shut down
       ungracefully.

     * The clear configuration command fails if a SmartCache volume has
       multiple UREs within a SmartCache page block size.

     * A controller lockup issue might occur when toggling a path to an
       enclosure in a dual domain configuration.

     * The controller runs in survival mode if a temperature sensor is not
       detected.

     * The clear configuration command might report failures when it
       encounters an installed drive with failed status.

     * A performance drop occurs during sequential workloads.

     * A controller failure might occur when running concurrent I/O to
       unassigned drives and drives in a RAID logical drive.

     * After a reboot, a bad drive might prevent controller discovery or
       operating system startup.

     * A host request is incorrectly returned as Failed when a failed drive
       in a degraded volume is replaced.

     * Modifying the spare configuration under an active spare rebuild causes
       the rebuild process to stop.

     * Incorrect device location reporting occurs when direct-attach drives
       are not attached to a backplane and an enclosure management schema is
       not defined.

     * RAID volume configuration settings are not applied when a disk drive
       transitions from unassigned to RAID usage during runtime.

     * A RAID volume with a failed drive reappears after a clear
       configuration operation completes and the system is rebooted.

     * A controller might hang during a SmartCache flush task that encounters
       multiple unrecoverable media errors (UREs).

     * A response of all zeros is sent for ATA PASSTHROUGH commands, such as
       SMART READ DATA, through Out of Band (OOB) host transport.

Enhancements

 The following enhancements are part of the Smart Array controller firmware
   v3.00:

     * After a firmware upgrade and reboot, the background parity
       initialization process starts for logical drives with incomplete or
       failed background parity initialization status.

     * Previously, background surface scans for data consistency could wait
       up to 14 days between runs. Surface scan now restarts immediately when
       a consistency check fails. When no surface scan issues are found,
       surface scan maintains the 14 day waiting period.


Version:2.65 (13 Mar 2020)
Fixes

Upgrade Requirement:
Critical - HPE requires users update to this version immediately.


REMOVED -  Firmware version 2.65 is NO LONGER AVAILABLE for download. Review HPE Customer Bulletin a00097210en_us for additional information that includes replacement firmware version.

  • Prevents a potential data inconsistency from occurring after experiencing an Unrecoverable Read Error (URE) on a drive configured in RAID 1/10/ADM Fault Tolerant Mode.
  • Prevents a potential data inconsistency from occurring during initial configuration and operation of a volume configured in RAID 5/6/50/60 Fault Tolerant Mode.

o   For additional information regarding Compute and Storage platforms, reference Customer Bulletin a00097210en_us.

  • HPE does NOT recommend independently updating to Firmware Versions Newer than 1.99 for HPE Smart Array SR Gen10 Controllers on HPE SimpliVity Gen10 systems.
    For additional information regarding SimpliVity platforms, reference Customer Bulletin a00097566en_us

 

IMPORTANT: RAID 0 and drives in HBA Mode are not affected.


Version:2.62 (20 Dec 2019)
Fixes

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


REMOVED -  Firmware version 2.62 is NO LONGER AVAILABLE for download. Review HPE Customer Bulletin a00097210en_us for additional information that includes replacement firmware version.

 

Fixes the following unexpected behaviors:

  • Controller could stop responding with a 0x1A91 message during active path failure when scanning expander indexes.
  • Controller could stop responding during I/O processing and Smart Cache flush process if there is an invalid transient message return by the physical drives.
  • When predictive spare rebuild is triggered on Smart Cache, the rebuilding process could fail to start.
  • Data could become inaccessible when a SATA drive overruns a data transfer
  • Controller memory could become unstable when the response to an Identify Device command (IDD) is received from a drive
  • Communication between the host system and a RAID5/6 volume could potentially fail after an I/O timeout on one of the drives in the array.
  • System could stop responding with a 0x1E30 message when an ATA locked drive is discovered
  • If a command is execute during a drive sanitize operation the controller could stop responding.
Enhancements

  • Add UBM1 Support
  • Support for backup power source charge timeout values from UEFI
  • UBM2 backplane support
  • Drive hotplug support for UBM backplanes

Version:2.02 (10 Sep 2019)
Fixes

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


REMOVED -  Firmware version 2.02 is NO LONGER AVAILABLE for download. Review HPE Customer Bulletin a00097210en_us for additional information that includes replacement firmware version.

 

Fixes the following unexpected behaviors:

  • Controller could stop responding with a 0x1A91 message during active path failure when scanning expander indexes.
  • Controller could stop responding during I/O processing and Smart Cache flush process if there is an invalid transient message return by the physical drives.
  • When predictive spare rebuild is triggered on Smart Cache, the rebuilding process could fail to start.
  • Data could become inaccessible when a SATA drive overruns a data transfer
  • Controller memory could become unstable when the response to an Identify Device command (IDD) is received from a drive
  • Communication between the host system and a RAID5/6 volume could potentially fail after an I/O timeout on one of the drives in the array.
  • System could stop responding with a 0x1E30 message when an ATA locked drive is discovered
  • If a command is execute during a drive sanitize operation the controller could stop responding.

Version:1.99 (18 Jun 2019)
Fixes

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


REMOVED -  Firmware version 1.99 is NO LONGER AVAILABLE for download. Review HPE Customer Bulletin a00097210en_us for additional information that includes replacement firmware version..

 

Fixes the following unexpected behaviors:

  • Controller could stop responding with a 0x1A91 message during active path failure when scanning expander indexes.
  • Controller could stop responding during I/O processing and Smart Cache flush process if there is an invalid transient message return by the physical drives.
  • When predictive spare rebuild is triggered on Smart Cache, the rebuilding process could fail to start.
  • Data could become inaccessible when a SATA drive overruns a data transfer
  • Controller memory could become unstable when the response to an Identify Device command (IDD) is received from a drive
  • Communication between the host system and a RAID5/6 volume could potentially fail after an I/O timeout on one of the drives in the array.
  • System could stop responding with a 0x1E30 message when an ATA locked drive is discovered
  • If a command is execute during a drive sanitize operation the controller could stop responding.

Version:1.98 (2 Apr 2019)
Fixes

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


REMOVED -  Firmware version 1.98 is NO LONGER AVAILABLE for download. Review HPE Customer Bulletin a00097210en_us for additional information that includes replacement firmware version..

 

Fixes the following unexpected behaviors:

  • Controller could stop responding with a 0x1A91 message during active path failure when scanning expander indexes.
  • Controller could stop responding during I/O processing and Smart Cache flush process if there is an invalid transient message return by the physical drives.
  • When predictive spare rebuild is triggered on Smart Cache, the rebuilding process could fail to start.
  • Data could become inaccessible when a SATA drive overruns a data transfer
  • Controller memory could become unstable when the response to an Identify Device command (IDD) is received from a drive
  • Communication between the host system and a RAID5/6 volume could potentially fail after an I/O timeout on one of the drives in the array.
  • System could stop responding with a 0x1E30 message when an ATA locked drive is discovered
  • If a command is execute during a drive sanitize operation the controller could stop responding.

Version:1.65(B) (27 Nov 2018)
Enhancements

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

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


Added support for Microsoft Windows Server 2019 OS.


Version:1.65 (27 Sep 2018)
Fixes

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


  • System might stop responding at POST and fail to load an OS. This issue is more likely to occur if System BIOS version is 1.40 or later. However, systems running older BIOS versions could experience this issue also.

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.

Legal Disclaimer: Products sold prior to the November 1, 2015 separation of Hewlett-Packard Company into Hewlett Packard Enterprise Company and HP Inc. may have older product names and model numbers that differ from current models.