Printable version

Drivers & software

* RECOMMENDED * Online ROM Flash Component for VMware ESXi - Smart Array H240ar, H240nr, H240, H241, H244br, P240nr, P244br, P246br, P440ar, P440, P441, P542D, P741m, P840, P840ar, and P841

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: 5.04(21 Apr 2017)
Operating System(s):
VMware vSphere 6.0 | View all
File name: CP032042.zip (8.7 MB)
This Smart Component provides firmware for the following storage controllers: Smart Array H240ar, H240nr, H240, H241, H244br, P240nr, P244br, P246br, P440ar, P440, P441, P542D, P741m, P840, P840ar, and P841

  • Added support to enable setting the controller boot order in Legacy BIOS Mode.
  • Enhanced debug capabilities when running in HBA-mode and connected to an expander configuration.

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

b76d17c994fd2e963ac9de06592ada723897360bed1e2a802fc3c57fc190c3ca CP032042.zip

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


Installation:

HPE strongly recommends that this firmware update be performed in an offline environment.  If this firmware update is performed online, ensure a graceful shutdown or restart is performed in order to flush all data from the controller cache before the new firmware is activated.  Abruptly rebooting the system while there is data in cache might result in data loss.

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

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

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

     Remote Online:

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

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

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

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

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

             chmod +x CPXXXXXX.vmexe    

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

 


End User License Agreements:
HPE Software License Agreement v1


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

HPE strongly recommends that this firmware update be performed in an offline environment.  If this firmware update is performed online, ensure a graceful shutdown or restart is performed in order to flush all data from the controller cache before the new firmware is activated.  Abruptly rebooting the system while there is data in cache might result in data loss.


Important:

  • HPE strongly recommends that this firmware update be performed in an offline environment.  If this firmware update is performed online, ensure a graceful shutdown or restart is performed in order to flush all data from the controller cache before the new firmware is activated.  Abruptly rebooting the system while there is data in cache might result in data loss.

Notes:

Deliverable Name:
     Online ROM Flash Component for VMware ESXi - Smart Array H240ar, H240nr, H240, H241, H244br, P240nr, P244br, P246br, P440ar, P440, P441, P542D, P741m, P840, P840ar, and P841

Release Version and/or Date:
    5.04

Last Recommended or Critical Version:
    4.52

Previous Version of Firmware:
     4.52

Firmware Dependency:
     None

Enhancements/New Features:    

  • Added support to enable setting the controller boot order in Legacy BIOS Mode.
  • Enhanced debug capabilities when running in HBA-mode and connected to an expander configuration.

Problems Fixed:

  • Kernel core dump using kdump might not complete in Linux when using Smart Array Gen9 firmware version 4.52.
  • Intermittent memory errors might cause the controller to stop responding. (POST Lockup 0x13)
  • System might stop responding if a parity error is found during surface scan of a RAID6 volume. (POST Lockup 0x13)
  • In rare cases, the controller might stop responding while running IO without displaying a lockup code.
  • Non-Maskable Interrupt (NMI) might occur on systems with a Windows OS and HPE Gen9 Smart Array or Smart HBA adapters and performing continuous reboot testing.
  • System IO might stop when using certain 6TiB and 8TiB SAS drives in a dual-path configuration with an HPE Gen9 Smart Array or Smart HBA adapter in HBA-mode, possibly resulting in an OS crash.
  • Physical slot location of SATA drives might not be returned correctly when using Microsoft Storage Spaces Direct (S2D).
  • Multiple direct attach SATA drives within a cluster might show the same World Wide Name (WWN) when using Microsoft Storage Spaces Direct (S2D).
  • Drive LED’s might be illuminated for the wrong drive and/or only illuminate momentarily when connected to an expander configuration with an HPE Gen9 Smart Array or Smart HBA adapter in HBA-mode.
  • Controllers using a 4GB cache module might fail data retention following an unexpected power event. (POST message 1793 - Data in Write-Back Cache has been Lost)
  • System fans might go to 100% if connected drives were spun down.

Known Issues:
     None


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

HPE strongly recommends that this firmware update be performed in an offline environment.  If this firmware update is performed online, ensure a graceful shutdown or restart is performed in order to flush all data from the controller cache before the new firmware is activated.  Abruptly rebooting the system while there is data in cache might result in data loss.


  • Kernel core dump using kdump might not complete in Linux when using Smart Array Gen9 firmware version 4.52.
  • Intermittent memory errors might cause the controller to stop responding. (POST Lockup 0x13)
  • System might stop responding if a parity error is found during surface scan of a RAID6 volume. (POST Lockup 0x13)
  • In rare cases, the controller might stop responding while running IO without displaying a lockup code.
  • Non-Maskable Interrupt (NMI) might occur on systems with a Windows OS and HPE Gen9 Smart Array or Smart HBA adapters and performing continuous reboot testing.
  • System IO might stop when using certain 6TiB and 8TiB SAS drives in a dual-path configuration with an HPE Gen9 Smart Array or Smart HBA adapter in HBA-mode, possibly resulting in an OS crash.
  • Physical slot location of SATA drives might not be returned correctly when using Microsoft Storage Spaces Direct (S2D).
  • Multiple direct attach SATA drives within a cluster might show the same World Wide Name (WWN) when using Microsoft Storage Spaces Direct (S2D).
  • Drive LED’s might be illuminated for the wrong drive and/or only illuminate momentarily when connected to an expander configuration with an HPE Gen9 Smart Array or Smart HBA adapter in HBA-mode.
  • Controllers using a 4GB cache module might fail data retention following an unexpected power event. (POST message 1793 - Data in Write-Back Cache has been Lost)
  • System fans might go to 100% if connected drives were spun down.
  • HPE strongly recommends that this firmware update be performed in an offline environment.  If this firmware update is performed online, ensure a graceful shutdown or restart is performed in order to flush all data from the controller cache before the new firmware is activated.  Abruptly rebooting the system while there is data in cache might result in data loss.
Version:6.88 (2 Apr 2019)
Fixes

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


Fixes the following Issues

  • SATA drive could stop responding  while on HBA mode when non-NCQ commands are executed
  • Controller could stop responding when upgrading due to the DDR Cache Module exceeding its limitations
  • SSD Cache module could become disable while upgrading FW
  • Data from the HPE Smart Drive Backplane could potentially become corrupted if a non-HPE carrier is present

Version:6.60 (26 Jun 2018)
Fixes

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


  • Issue where the QueryAsynchronousEvent could potentially provide incorrect response data
  • Issue where the Cache could potentially get disable after several reboots
Enhancements

  • Added support for larger SmartCache capacity size

Version:6.30 (5 Feb 2018)
Fixes

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


Fixes the following issues:

  • DDR cache could be randomly disabled after several boots
  • The controller could become unresponsive while in HBA mode during the creation of a partition/file system

.


Version:6.06 (25 Sep 2017)
Fixes

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


  • Under the following conditions, the controller might stop responding:
    • During POST following an unexpected power event if there was data in the controller cache.
    • When running I/O to SATA drives. (POST Lockup 0x13)
    • When using a RAID configuration with strip size of 1024KiB. (POST Lockup 0x13)
    • When a WRITE SAME command is sent with a buffer size greater than 512 bytes. (POST Lockup 0x13)
  • In a multi-path environment with nested expanders, the active path to a device might be incorrect following a path failure or restoration.

Version:5.52 (12 Jul 2017)
Fixes

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


  • Controller cache module might be marked as permanently disabled if the Smart Storage Battery is removed or failed while the system is online, even if SSA was previously used to enable write caching without a backup power source.
  • SATA drives might not be presented to the host in a Synergy system with a D3940 Disk Enclosure.
  • A hot-inserted replacement drive might show as a predictive failure if the original drive was identified as a predictive failure.
  • Port/box/bay identifier for physical drives might have an incorrect box number in zoned or multi-path configurations.

Version:5.04(A) (16 May 2017)
Fixes

Upgrade Requirement:
Optional - Users should update to this version if their system is affected by one of the documented fixes or if there is a desire to utilize any of the enhanced functionality provided by this version.


  • Kernel core dump using kdump might not complete in Linux when using Smart Array Gen9 firmware version 4.52.
  • Intermittent memory errors might cause the controller to stop responding. (POST Lockup 0x13)
  • System might stop responding if a parity error is found during surface scan of a RAID6 volume. (POST Lockup 0x13)
  • In rare cases, the controller might stop responding while running IO without displaying a lockup code.
  • Non-Maskable Interrupt (NMI) might occur on systems with a Windows OS and HPE Gen9 Smart Array or Smart HBA adapters and performing continuous reboot testing.
  • System IO might stop when using certain 6TiB and 8TiB SAS drives in a dual-path configuration with an HPE Gen9 Smart Array or Smart HBA adapter in HBA-mode, possibly resulting in an OS crash.
  • Physical slot location of SATA drives might not be returned correctly when using Microsoft Storage Spaces Direct (S2D).
  • Multiple direct attach SATA drives within a cluster might show the same World Wide Name (WWN) when using Microsoft Storage Spaces Direct (S2D).
  • Drive LED’s might be illuminated for the wrong drive and/or only illuminate momentarily when connected to an expander configuration with an HPE Gen9 Smart Array or Smart HBA adapter in HBA-mode.
  • Controllers using a 4GB cache module might fail data retention following an unexpected power event. (POST message 1793 - Data in Write-Back Cache has been Lost)
  • System fans might go to 100% if connected drives were spun down.
Enhancements

  • Added support to enable setting the controller boot order in Legacy BIOS Mode.
  • Enhanced debug capabilities when running in HBA-mode and connected to an expander configuration.
  • Now installs on systems running VMware vSphere 6.5.

          Note: If controller firmware was previously updated to 5.04, it is not necessary to upgrade to version 5.04(A).


Version:5.04 (21 Apr 2017)
Fixes

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

HPE strongly recommends that this firmware update be performed in an offline environment.  If this firmware update is performed online, ensure a graceful shutdown or restart is performed in order to flush all data from the controller cache before the new firmware is activated.  Abruptly rebooting the system while there is data in cache might result in data loss.


  • Kernel core dump using kdump might not complete in Linux when using Smart Array Gen9 firmware version 4.52.
  • Intermittent memory errors might cause the controller to stop responding. (POST Lockup 0x13)
  • System might stop responding if a parity error is found during surface scan of a RAID6 volume. (POST Lockup 0x13)
  • In rare cases, the controller might stop responding while running IO without displaying a lockup code.
  • Non-Maskable Interrupt (NMI) might occur on systems with a Windows OS and HPE Gen9 Smart Array or Smart HBA adapters and performing continuous reboot testing.
  • System IO might stop when using certain 6TiB and 8TiB SAS drives in a dual-path configuration with an HPE Gen9 Smart Array or Smart HBA adapter in HBA-mode, possibly resulting in an OS crash.
  • Physical slot location of SATA drives might not be returned correctly when using Microsoft Storage Spaces Direct (S2D).
  • Multiple direct attach SATA drives within a cluster might show the same World Wide Name (WWN) when using Microsoft Storage Spaces Direct (S2D).
  • Drive LED’s might be illuminated for the wrong drive and/or only illuminate momentarily when connected to an expander configuration with an HPE Gen9 Smart Array or Smart HBA adapter in HBA-mode.
  • Controllers using a 4GB cache module might fail data retention following an unexpected power event. (POST message 1793 - Data in Write-Back Cache has been Lost)
  • System fans might go to 100% if connected drives were spun down.
Enhancements

  • Added support to enable setting the controller boot order in Legacy BIOS Mode.
  • Enhanced debug capabilities when running in HBA-mode and connected to an expander configuration.

Version:4.52 (24 Oct 2016)
Fixes

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


  • SATA SSD’s were incorrectly marked as worn out.
  • Poor performance on the first logical volume with drive write cache enabled.
  • Controller might hang or show as failed in the IML with 20+ SATA SSD’s configured in a RAID6 volume with Smart Path enabled and IO running.
  • System might hang at POST following a reboot.
  • System might lockup at POST following a reboot (POST Lockup 0x13)
  • Duplicate SCSI devices shown in Linux after issuing a bus rescan command.
  • Recovered paths were not restored when using a SmartArray P742m controller connected to an external drive enclosure and a shared storage external enclosure.
  • Smart Array P741m controller missing the embedded SmartCache license key.
  • System might stop responding in response to a rare error (POST Lockup 0x13).
  • Drives might not appear as HPE authentic drives when used in a zoning configuration.
  • Deferred drive firmware flashing might hang at POST with some models of drives.
Enhancements

  • Increased performance of SATA drives by increasing command queue depth.

Version:4.02(B) (21 Apr 2016)
Fixes

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


Problems Fixed in 4.02:

  • Flash-backed write cache might fail on embedded controllers following an unexpected power down event.

  • Detection of all physical drives behind the same expander might fail if a single drive did not spin up.

  • Server power up might take an extended amount of time if failed drives are present behind a controller running in HBA mode.

  • SATA drives might go offline during runtime.

  • Logical volumes might be disabled after flashing enclosure SEP device firmware.

  • Controller might stop responding when running IO with an attached Shared Storage enclosure (POST Lockup 0xAB).

  • Controller might stop responding when running Linux and an abort command is issued by the host.

  • An intermittent aborted IO request with attached SATA drives resulted in a LUN (Logical Unit Number) reset.

  • Incorrectly displayed drive failure message in HPESSA for rebuilding SSD.

  • Incorrectly displayed 0% progress message in HPESSA for sanitizing SSD.

  • Reduced likelihood of POST Lockup 0x13 occurrence due to intermittent memory errors.

Problems Fixed in 4.02 (B):

  • Component might fail to install firmware in a system configured with a shared storage enclosure. The following message would be reported - “Device appears more than once in tree.”

Enhancements

  • Improved controller performance.

  • Servers now power up faster due to improvements in the UEFI controller driver.

Version:3.56 (3 Dec 2015)
Fixes

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


  • Controller might stop responding when drives were reporting errors (POST Lockup 0x13)
  • Controller in HBA mode might stop responding if a command to a SATA drive timed out (POST Lockup 0xAB)
  • Detection of all direct-attached physical drives might fail if a single drive did not spin up
  • A physical drive configured as a spare drive might indicate predictive failure sooner than expected
  • Erroneous Critical message displayed in ADU: “Box Failure Due To Primary Io Module”
  • With SLES11 SP4 installed, the system may fail to boot to the OS after updating to 3.52 SmartArray controller firmware

Version:3.52 (30 Oct 2015)
Fixes

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


  • Controller might stop responding when drives were reporting errors (POST Lockup 0x13)
  • Controller in HBA mode might stop responding if a command to a SATA drive timed out (POST Lockup 0xAB)
  • Detection of all direct-attached physical drives might fail if a single drive did not spin up
  • A physical drive configured as a spare drive might indicate predictive failure sooner than expected
  • Erroneous Critical message displayed in ADU: “Box Failure Due To Primary Io Module”

Version:3 (1 Oct 2015)
Fixes

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


  • Controller might stop responding in the following situations:

    • During reboot or at power-up, if multiple Raw Device Mappings (RDM’s) are configured under VMware

    • During reboot or at power-up, if multiple logical volumes are queued for rebuild, expansion, or transformation

    • When flashing SATA drive firmware on a system running a supported Windows OS, if a drive had previously been removed or failed (POST Lockup 0x13)

  • Drives reported as overheating when not above temperature limits
Enhancements

  • Support booting from controllers in HBA-mode when running with legacy BIOS

  • Improved controller performance following a cold boot of the server


Version:2.52 (15 Jun 2015)
Fixes

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


  • If an HP Smart Array controller is configured with HP SmartCache, upgrade the controller to firmware version 2.52 to avoid a possible lockup (POST lockup 0x13)
  • System fans might run at maximum speed
  • System might be unable to boot from volumes on HP MSA 2040 SAS enclosures
  • Physical drives might be repeated in the UEFI one-time boot menu
  • Installation of a custom Linux ISO might fail to boot with “error: can’t allocate initrd”
  • Controller might stop responding at power up with encryption enabled (POST Lockup 0x13)
  • System might stop responding when sending high numbers of non-NCQ commands to SATA drives behind H-series cards (POST Lockup 0x13)
  • System might stop responding following the hot-removal of a drive from a fault tolerant volume (POST Lockup 0xAB)
  • System might be unable to downgrade controller firmware via UEFI flashing tool
  • If a Smart Array controller with firmware version 2.14 was running in HBA mode and the drives that were connected were previously configured in a LUN, an 1832 POST message was not displayed. Refer to Customer Advisory c04635824 for additional information about this issue.
  • Certain POST messages displayed although the error conditions were not present. The Smart Array Controller firmware has been hardened to reduce the likelihood of these false error messages occurring:
    • POST 1784, which indicated a logical drive failure
    • POST 1795, which indicated a write-back-cache error and disabled cache
Enhancements

  • Improved performance by limiting Surface Scan frequency to once every 14 days
  • Increased performance for tape drives when using variable block sizes
  • Updated type and quantity of information logged to the Active Health System log
  • Added support for the following:
    • Check for drive firmware update needed on hot-plugged devices
    • Non-disruptive online drive firmware updates for supported SATA drives
    • Microsoft Storage Spaces
    • HP MSA 1040 external RAID enclosure
    • Third party external RAID enclosures

Version:2.14 (2 Apr 2015)
Fixes

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


Problems Fixed:

  • Critical issue for all UEFI systems using 2.2 TB or greater volumes configured with GPT partitions. For additional information please refer to the customer advisory # c04602001
  • When rebuilding a logical volume greater than 2TB in size, the controller might cease to function (POST Lockup 0xE0). Controller would report a POST Lockup 0xE0 error and cease to function, when the following conditions were met:

                 1) Encryption enabled and a re-key operation was in progress.
                 2) While IO was in progress, physical drives failed in an Advanced Data Guarding (RAID6 or RAID60) volume, which caused the volume to go into a degraded state.
                 3) Degraded Mode Performance Optimization was enabled via HP Smart Storage Administrator.

  • If a power outage or brownout occurred while running a volume expansion, the controller might cease to function on the following boot (POST Lockup 0x13).
  • HP D2600/D2700 Disk Enclosures might not show the correct box number on the LED display.
  • Controller might become unresponsive if a drive was re-inserted into encrypted LUN while performing IO on it.
  • When running IO with encryption turned on in remote mode and a local key cache enabled, changing the master key might result in encryption being disabled on the next power up.
  • Controller allowed encryption key changes even with locked volumes.
  • A key restore from an Enterprise Secure Key Manager could take a long time for large configurations.
  • Users were unable to install Red Hat Enterprise Linux 6 Update 5 to a logical volume on an HP P2000 MSA Array System if both an HP H241 and H240 Smart Host Bus Adapter were present in the system.
  • When HP D3700 Disk Enclosures were connected to an HP H240 Smart Host Bus Adapter, the maximum number of enclosures displayed in the boot menu was five, although a maximum of eight enclosures were supported.
  • When a volume expansion or encryption re-key operation was performed, and if multiple power losses or brownouts occurred, data might become inaccessible (POST Message 1769).
  • POST messages 1764, 1768, 1784, 1786, 1787, 1789, 1831 have been updated and/or corrected.
Enhancements

Enhancements/New Features:

  • Servers now power up faster due to improvements in the UEFI controller driver.
  • Logical volume transformations are allowed on controllers without data preservation.
  • Drives can now be hot-added in a zoned configuration.

Version:1.34(B) (11 Dec 2014)
Fixes

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


Problems Fixed:

  • Controller may stop responding while running IO (POST Lockup 0xB9). (For additional information please refer to the customer advisory #c04555905)
  • When a server was running and power was removed and then re-applied to an HP D6000, the controller may cease to function (POST Lockup 0xAB).
  • Following a reboot, SATA drives in Bay 1 and Bay 2 of an HP D6000 may fail to be discovered, leading to any configured LUN’s using these bays to go into interim recovery mode.
  • If a power-outage or brownout occurs while running HP SmartCache, the controller may cease to function on the following boot (POST Lockup 0x13).


 

Enhancements

Enhancements/New Features:

  • Added support for HP H241.

Version:1.18 (6 Oct 2014)
Fixes

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


Problems Fixed:

  • Following a server power-cycle reboot, the cache read/write ratio for an HP Smart Array P244br, P440ar, P440, P441, or P840 controller could not be changed using the HP Smart Storage Administrator (HP SSA) GUI Cache Manager feature.
    Note: This issue was not seen when using the HP SSA CLI. 
     

Version:1.14 (9 Sep 2014)
Enhancements

Upgrade Requirement:
Optional - Users should update to this version if their system is affected by one of the documented fixes or if there is a desire to utilize any of the enhanced functionality provided by this version.


Enhancements/New Features:

  • 1.14 is the initial firmware release.

Type: Firmware - Storage Controller
Version: 5.04(21 Apr 2017)
Operating System(s):
VMware vSphere 6.0
VMware vSphere 5.1
VMware vSphere 5.5

Description

This Smart Component provides firmware for the following storage controllers: Smart Array H240ar, H240nr, H240, H241, H244br, P240nr, P244br, P246br, P440ar, P440, P441, P542D, P741m, P840, P840ar, and P841

Enhancements

  • Added support to enable setting the controller boot order in Legacy BIOS Mode.
  • Enhanced debug capabilities when running in HBA-mode and connected to an expander configuration.

Installation Instructions

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

b76d17c994fd2e963ac9de06592ada723897360bed1e2a802fc3c57fc190c3ca CP032042.zip

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


Installation:

HPE strongly recommends that this firmware update be performed in an offline environment.  If this firmware update is performed online, ensure a graceful shutdown or restart is performed in order to flush all data from the controller cache before the new firmware is activated.  Abruptly rebooting the system while there is data in cache might result in data loss.

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

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

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

     Remote Online:

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

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

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

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

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

             chmod +x CPXXXXXX.vmexe    

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

 


Release Notes

End User License Agreements:
HPE Software License Agreement v1


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

HPE strongly recommends that this firmware update be performed in an offline environment.  If this firmware update is performed online, ensure a graceful shutdown or restart is performed in order to flush all data from the controller cache before the new firmware is activated.  Abruptly rebooting the system while there is data in cache might result in data loss.


Important:

  • HPE strongly recommends that this firmware update be performed in an offline environment.  If this firmware update is performed online, ensure a graceful shutdown or restart is performed in order to flush all data from the controller cache before the new firmware is activated.  Abruptly rebooting the system while there is data in cache might result in data loss.

Notes:

Deliverable Name:
     Online ROM Flash Component for VMware ESXi - Smart Array H240ar, H240nr, H240, H241, H244br, P240nr, P244br, P246br, P440ar, P440, P441, P542D, P741m, P840, P840ar, and P841

Release Version and/or Date:
    5.04

Last Recommended or Critical Version:
    4.52

Previous Version of Firmware:
     4.52

Firmware Dependency:
     None

Enhancements/New Features:    

  • Added support to enable setting the controller boot order in Legacy BIOS Mode.
  • Enhanced debug capabilities when running in HBA-mode and connected to an expander configuration.

Problems Fixed:

  • Kernel core dump using kdump might not complete in Linux when using Smart Array Gen9 firmware version 4.52.
  • Intermittent memory errors might cause the controller to stop responding. (POST Lockup 0x13)
  • System might stop responding if a parity error is found during surface scan of a RAID6 volume. (POST Lockup 0x13)
  • In rare cases, the controller might stop responding while running IO without displaying a lockup code.
  • Non-Maskable Interrupt (NMI) might occur on systems with a Windows OS and HPE Gen9 Smart Array or Smart HBA adapters and performing continuous reboot testing.
  • System IO might stop when using certain 6TiB and 8TiB SAS drives in a dual-path configuration with an HPE Gen9 Smart Array or Smart HBA adapter in HBA-mode, possibly resulting in an OS crash.
  • Physical slot location of SATA drives might not be returned correctly when using Microsoft Storage Spaces Direct (S2D).
  • Multiple direct attach SATA drives within a cluster might show the same World Wide Name (WWN) when using Microsoft Storage Spaces Direct (S2D).
  • Drive LED’s might be illuminated for the wrong drive and/or only illuminate momentarily when connected to an expander configuration with an HPE Gen9 Smart Array or Smart HBA adapter in HBA-mode.
  • Controllers using a 4GB cache module might fail data retention following an unexpected power event. (POST message 1793 - Data in Write-Back Cache has been Lost)
  • System fans might go to 100% if connected drives were spun down.

Known Issues:
     None


Fixes

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

HPE strongly recommends that this firmware update be performed in an offline environment.  If this firmware update is performed online, ensure a graceful shutdown or restart is performed in order to flush all data from the controller cache before the new firmware is activated.  Abruptly rebooting the system while there is data in cache might result in data loss.


  • Kernel core dump using kdump might not complete in Linux when using Smart Array Gen9 firmware version 4.52.
  • Intermittent memory errors might cause the controller to stop responding. (POST Lockup 0x13)
  • System might stop responding if a parity error is found during surface scan of a RAID6 volume. (POST Lockup 0x13)
  • In rare cases, the controller might stop responding while running IO without displaying a lockup code.
  • Non-Maskable Interrupt (NMI) might occur on systems with a Windows OS and HPE Gen9 Smart Array or Smart HBA adapters and performing continuous reboot testing.
  • System IO might stop when using certain 6TiB and 8TiB SAS drives in a dual-path configuration with an HPE Gen9 Smart Array or Smart HBA adapter in HBA-mode, possibly resulting in an OS crash.
  • Physical slot location of SATA drives might not be returned correctly when using Microsoft Storage Spaces Direct (S2D).
  • Multiple direct attach SATA drives within a cluster might show the same World Wide Name (WWN) when using Microsoft Storage Spaces Direct (S2D).
  • Drive LED’s might be illuminated for the wrong drive and/or only illuminate momentarily when connected to an expander configuration with an HPE Gen9 Smart Array or Smart HBA adapter in HBA-mode.
  • Controllers using a 4GB cache module might fail data retention following an unexpected power event. (POST message 1793 - Data in Write-Back Cache has been Lost)
  • System fans might go to 100% if connected drives were spun down.

Important

  • HPE strongly recommends that this firmware update be performed in an offline environment.  If this firmware update is performed online, ensure a graceful shutdown or restart is performed in order to flush all data from the controller cache before the new firmware is activated.  Abruptly rebooting the system while there is data in cache might result in data loss.

Revision History

Version:6.88 (2 Apr 2019)
Fixes

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


Fixes the following Issues

  • SATA drive could stop responding  while on HBA mode when non-NCQ commands are executed
  • Controller could stop responding when upgrading due to the DDR Cache Module exceeding its limitations
  • SSD Cache module could become disable while upgrading FW
  • Data from the HPE Smart Drive Backplane could potentially become corrupted if a non-HPE carrier is present

Version:6.60 (26 Jun 2018)
Fixes

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


  • Issue where the QueryAsynchronousEvent could potentially provide incorrect response data
  • Issue where the Cache could potentially get disable after several reboots
Enhancements

  • Added support for larger SmartCache capacity size

Version:6.30 (5 Feb 2018)
Fixes

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


Fixes the following issues:

  • DDR cache could be randomly disabled after several boots
  • The controller could become unresponsive while in HBA mode during the creation of a partition/file system

.


Version:6.06 (25 Sep 2017)
Fixes

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


  • Under the following conditions, the controller might stop responding:
    • During POST following an unexpected power event if there was data in the controller cache.
    • When running I/O to SATA drives. (POST Lockup 0x13)
    • When using a RAID configuration with strip size of 1024KiB. (POST Lockup 0x13)
    • When a WRITE SAME command is sent with a buffer size greater than 512 bytes. (POST Lockup 0x13)
  • In a multi-path environment with nested expanders, the active path to a device might be incorrect following a path failure or restoration.

Version:5.52 (12 Jul 2017)
Fixes

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


  • Controller cache module might be marked as permanently disabled if the Smart Storage Battery is removed or failed while the system is online, even if SSA was previously used to enable write caching without a backup power source.
  • SATA drives might not be presented to the host in a Synergy system with a D3940 Disk Enclosure.
  • A hot-inserted replacement drive might show as a predictive failure if the original drive was identified as a predictive failure.
  • Port/box/bay identifier for physical drives might have an incorrect box number in zoned or multi-path configurations.

Version:5.04(A) (16 May 2017)
Fixes

Upgrade Requirement:
Optional - Users should update to this version if their system is affected by one of the documented fixes or if there is a desire to utilize any of the enhanced functionality provided by this version.


  • Kernel core dump using kdump might not complete in Linux when using Smart Array Gen9 firmware version 4.52.
  • Intermittent memory errors might cause the controller to stop responding. (POST Lockup 0x13)
  • System might stop responding if a parity error is found during surface scan of a RAID6 volume. (POST Lockup 0x13)
  • In rare cases, the controller might stop responding while running IO without displaying a lockup code.
  • Non-Maskable Interrupt (NMI) might occur on systems with a Windows OS and HPE Gen9 Smart Array or Smart HBA adapters and performing continuous reboot testing.
  • System IO might stop when using certain 6TiB and 8TiB SAS drives in a dual-path configuration with an HPE Gen9 Smart Array or Smart HBA adapter in HBA-mode, possibly resulting in an OS crash.
  • Physical slot location of SATA drives might not be returned correctly when using Microsoft Storage Spaces Direct (S2D).
  • Multiple direct attach SATA drives within a cluster might show the same World Wide Name (WWN) when using Microsoft Storage Spaces Direct (S2D).
  • Drive LED’s might be illuminated for the wrong drive and/or only illuminate momentarily when connected to an expander configuration with an HPE Gen9 Smart Array or Smart HBA adapter in HBA-mode.
  • Controllers using a 4GB cache module might fail data retention following an unexpected power event. (POST message 1793 - Data in Write-Back Cache has been Lost)
  • System fans might go to 100% if connected drives were spun down.
Enhancements

  • Added support to enable setting the controller boot order in Legacy BIOS Mode.
  • Enhanced debug capabilities when running in HBA-mode and connected to an expander configuration.
  • Now installs on systems running VMware vSphere 6.5.

          Note: If controller firmware was previously updated to 5.04, it is not necessary to upgrade to version 5.04(A).


Version:5.04 (21 Apr 2017)
Fixes

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

HPE strongly recommends that this firmware update be performed in an offline environment.  If this firmware update is performed online, ensure a graceful shutdown or restart is performed in order to flush all data from the controller cache before the new firmware is activated.  Abruptly rebooting the system while there is data in cache might result in data loss.


  • Kernel core dump using kdump might not complete in Linux when using Smart Array Gen9 firmware version 4.52.
  • Intermittent memory errors might cause the controller to stop responding. (POST Lockup 0x13)
  • System might stop responding if a parity error is found during surface scan of a RAID6 volume. (POST Lockup 0x13)
  • In rare cases, the controller might stop responding while running IO without displaying a lockup code.
  • Non-Maskable Interrupt (NMI) might occur on systems with a Windows OS and HPE Gen9 Smart Array or Smart HBA adapters and performing continuous reboot testing.
  • System IO might stop when using certain 6TiB and 8TiB SAS drives in a dual-path configuration with an HPE Gen9 Smart Array or Smart HBA adapter in HBA-mode, possibly resulting in an OS crash.
  • Physical slot location of SATA drives might not be returned correctly when using Microsoft Storage Spaces Direct (S2D).
  • Multiple direct attach SATA drives within a cluster might show the same World Wide Name (WWN) when using Microsoft Storage Spaces Direct (S2D).
  • Drive LED’s might be illuminated for the wrong drive and/or only illuminate momentarily when connected to an expander configuration with an HPE Gen9 Smart Array or Smart HBA adapter in HBA-mode.
  • Controllers using a 4GB cache module might fail data retention following an unexpected power event. (POST message 1793 - Data in Write-Back Cache has been Lost)
  • System fans might go to 100% if connected drives were spun down.
Enhancements

  • Added support to enable setting the controller boot order in Legacy BIOS Mode.
  • Enhanced debug capabilities when running in HBA-mode and connected to an expander configuration.

Version:4.52 (24 Oct 2016)
Fixes

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


  • SATA SSD’s were incorrectly marked as worn out.
  • Poor performance on the first logical volume with drive write cache enabled.
  • Controller might hang or show as failed in the IML with 20+ SATA SSD’s configured in a RAID6 volume with Smart Path enabled and IO running.
  • System might hang at POST following a reboot.
  • System might lockup at POST following a reboot (POST Lockup 0x13)
  • Duplicate SCSI devices shown in Linux after issuing a bus rescan command.
  • Recovered paths were not restored when using a SmartArray P742m controller connected to an external drive enclosure and a shared storage external enclosure.
  • Smart Array P741m controller missing the embedded SmartCache license key.
  • System might stop responding in response to a rare error (POST Lockup 0x13).
  • Drives might not appear as HPE authentic drives when used in a zoning configuration.
  • Deferred drive firmware flashing might hang at POST with some models of drives.
Enhancements

  • Increased performance of SATA drives by increasing command queue depth.

Version:4.02(B) (21 Apr 2016)
Fixes

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


Problems Fixed in 4.02:

  • Flash-backed write cache might fail on embedded controllers following an unexpected power down event.

  • Detection of all physical drives behind the same expander might fail if a single drive did not spin up.

  • Server power up might take an extended amount of time if failed drives are present behind a controller running in HBA mode.

  • SATA drives might go offline during runtime.

  • Logical volumes might be disabled after flashing enclosure SEP device firmware.

  • Controller might stop responding when running IO with an attached Shared Storage enclosure (POST Lockup 0xAB).

  • Controller might stop responding when running Linux and an abort command is issued by the host.

  • An intermittent aborted IO request with attached SATA drives resulted in a LUN (Logical Unit Number) reset.

  • Incorrectly displayed drive failure message in HPESSA for rebuilding SSD.

  • Incorrectly displayed 0% progress message in HPESSA for sanitizing SSD.

  • Reduced likelihood of POST Lockup 0x13 occurrence due to intermittent memory errors.

Problems Fixed in 4.02 (B):

  • Component might fail to install firmware in a system configured with a shared storage enclosure. The following message would be reported - “Device appears more than once in tree.”

Enhancements

  • Improved controller performance.

  • Servers now power up faster due to improvements in the UEFI controller driver.

Version:3.56 (3 Dec 2015)
Fixes

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


  • Controller might stop responding when drives were reporting errors (POST Lockup 0x13)
  • Controller in HBA mode might stop responding if a command to a SATA drive timed out (POST Lockup 0xAB)
  • Detection of all direct-attached physical drives might fail if a single drive did not spin up
  • A physical drive configured as a spare drive might indicate predictive failure sooner than expected
  • Erroneous Critical message displayed in ADU: “Box Failure Due To Primary Io Module”
  • With SLES11 SP4 installed, the system may fail to boot to the OS after updating to 3.52 SmartArray controller firmware

Version:3.52 (30 Oct 2015)
Fixes

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


  • Controller might stop responding when drives were reporting errors (POST Lockup 0x13)
  • Controller in HBA mode might stop responding if a command to a SATA drive timed out (POST Lockup 0xAB)
  • Detection of all direct-attached physical drives might fail if a single drive did not spin up
  • A physical drive configured as a spare drive might indicate predictive failure sooner than expected
  • Erroneous Critical message displayed in ADU: “Box Failure Due To Primary Io Module”

Version:3 (1 Oct 2015)
Fixes

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


  • Controller might stop responding in the following situations:

    • During reboot or at power-up, if multiple Raw Device Mappings (RDM’s) are configured under VMware

    • During reboot or at power-up, if multiple logical volumes are queued for rebuild, expansion, or transformation

    • When flashing SATA drive firmware on a system running a supported Windows OS, if a drive had previously been removed or failed (POST Lockup 0x13)

  • Drives reported as overheating when not above temperature limits
Enhancements

  • Support booting from controllers in HBA-mode when running with legacy BIOS

  • Improved controller performance following a cold boot of the server


Version:2.52 (15 Jun 2015)
Fixes

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


  • If an HP Smart Array controller is configured with HP SmartCache, upgrade the controller to firmware version 2.52 to avoid a possible lockup (POST lockup 0x13)
  • System fans might run at maximum speed
  • System might be unable to boot from volumes on HP MSA 2040 SAS enclosures
  • Physical drives might be repeated in the UEFI one-time boot menu
  • Installation of a custom Linux ISO might fail to boot with “error: can’t allocate initrd”
  • Controller might stop responding at power up with encryption enabled (POST Lockup 0x13)
  • System might stop responding when sending high numbers of non-NCQ commands to SATA drives behind H-series cards (POST Lockup 0x13)
  • System might stop responding following the hot-removal of a drive from a fault tolerant volume (POST Lockup 0xAB)
  • System might be unable to downgrade controller firmware via UEFI flashing tool
  • If a Smart Array controller with firmware version 2.14 was running in HBA mode and the drives that were connected were previously configured in a LUN, an 1832 POST message was not displayed. Refer to Customer Advisory c04635824 for additional information about this issue.
  • Certain POST messages displayed although the error conditions were not present. The Smart Array Controller firmware has been hardened to reduce the likelihood of these false error messages occurring:
    • POST 1784, which indicated a logical drive failure
    • POST 1795, which indicated a write-back-cache error and disabled cache
Enhancements

  • Improved performance by limiting Surface Scan frequency to once every 14 days
  • Increased performance for tape drives when using variable block sizes
  • Updated type and quantity of information logged to the Active Health System log
  • Added support for the following:
    • Check for drive firmware update needed on hot-plugged devices
    • Non-disruptive online drive firmware updates for supported SATA drives
    • Microsoft Storage Spaces
    • HP MSA 1040 external RAID enclosure
    • Third party external RAID enclosures

Version:2.14 (2 Apr 2015)
Fixes

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


Problems Fixed:

  • Critical issue for all UEFI systems using 2.2 TB or greater volumes configured with GPT partitions. For additional information please refer to the customer advisory # c04602001
  • When rebuilding a logical volume greater than 2TB in size, the controller might cease to function (POST Lockup 0xE0). Controller would report a POST Lockup 0xE0 error and cease to function, when the following conditions were met:

                 1) Encryption enabled and a re-key operation was in progress.
                 2) While IO was in progress, physical drives failed in an Advanced Data Guarding (RAID6 or RAID60) volume, which caused the volume to go into a degraded state.
                 3) Degraded Mode Performance Optimization was enabled via HP Smart Storage Administrator.

  • If a power outage or brownout occurred while running a volume expansion, the controller might cease to function on the following boot (POST Lockup 0x13).
  • HP D2600/D2700 Disk Enclosures might not show the correct box number on the LED display.
  • Controller might become unresponsive if a drive was re-inserted into encrypted LUN while performing IO on it.
  • When running IO with encryption turned on in remote mode and a local key cache enabled, changing the master key might result in encryption being disabled on the next power up.
  • Controller allowed encryption key changes even with locked volumes.
  • A key restore from an Enterprise Secure Key Manager could take a long time for large configurations.
  • Users were unable to install Red Hat Enterprise Linux 6 Update 5 to a logical volume on an HP P2000 MSA Array System if both an HP H241 and H240 Smart Host Bus Adapter were present in the system.
  • When HP D3700 Disk Enclosures were connected to an HP H240 Smart Host Bus Adapter, the maximum number of enclosures displayed in the boot menu was five, although a maximum of eight enclosures were supported.
  • When a volume expansion or encryption re-key operation was performed, and if multiple power losses or brownouts occurred, data might become inaccessible (POST Message 1769).
  • POST messages 1764, 1768, 1784, 1786, 1787, 1789, 1831 have been updated and/or corrected.
Enhancements

Enhancements/New Features:

  • Servers now power up faster due to improvements in the UEFI controller driver.
  • Logical volume transformations are allowed on controllers without data preservation.
  • Drives can now be hot-added in a zoned configuration.

Version:1.34(B) (11 Dec 2014)
Fixes

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


Problems Fixed:

  • Controller may stop responding while running IO (POST Lockup 0xB9). (For additional information please refer to the customer advisory #c04555905)
  • When a server was running and power was removed and then re-applied to an HP D6000, the controller may cease to function (POST Lockup 0xAB).
  • Following a reboot, SATA drives in Bay 1 and Bay 2 of an HP D6000 may fail to be discovered, leading to any configured LUN’s using these bays to go into interim recovery mode.
  • If a power-outage or brownout occurs while running HP SmartCache, the controller may cease to function on the following boot (POST Lockup 0x13).


 

Enhancements

Enhancements/New Features:

  • Added support for HP H241.

Version:1.18 (6 Oct 2014)
Fixes

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


Problems Fixed:

  • Following a server power-cycle reboot, the cache read/write ratio for an HP Smart Array P244br, P440ar, P440, P441, or P840 controller could not be changed using the HP Smart Storage Administrator (HP SSA) GUI Cache Manager feature.
    Note: This issue was not seen when using the HP SSA CLI. 
     

Version:1.14 (9 Sep 2014)
Enhancements

Upgrade Requirement:
Optional - Users should update to this version if their system is affected by one of the documented fixes or if there is a desire to utilize any of the enhanced functionality provided by this version.


Enhancements/New Features:

  • 1.14 is the initial firmware release.

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.