Download Files
File Format: Dell Update Packages in native Microsoft Windows 64-bit format do not require that Microsoft WOW64 be installed on the Microsoft Windows Server.
File Name: SAS-RAID_Firmware_X37KV_WN64_8.14.0.0.18-14_A08.EXE
File size: 23.83 MB
To ensure the integrity of your download, please verify the checksum value.
MD5: 0d62c2b76850d08c51702e697efdb5d8
SHA1: 4c157419e7aefadd9f460507703569567cd70a59
SHA-256: 5d84533270c3390527ec2a814c69b66fa495f96f4500380f332eb0a7fec4e82f
File Format: The GnuPG signature for Red Hat Linux Update Package can be used to authenticate Dell's identity in the correlated Red Hat Linux Update Package.
File Name: SAS-RAID_Firmware_X37KV_LN64_8.14.0.0.18-14_A08.BIN.sign
File size: 842 Bytes
To ensure the integrity of your download, please verify the checksum value.
MD5: 8f87757b1e4a15f47c8a36f365c42dfa
SHA1: e00cd32f53df56db1f05c5de882f539a4e342285
SHA-256: c2752cbfd237e5896ec4aa199eca40a38f87f2e797baf84bd866d48f595122ab
File Format: This file format contains plain text which can be viewed with a standard text editor.
File Name: SAS_RAID_Firmware_8.14.0.0.18-14_RELNOTES.txt
File size: 25.08 KB
To ensure the integrity of your download, please verify the checksum value.
MD5: 49a762a75b3d149aaf626d043c91db80
SHA1: 43f3fb5c9e42dc2e023a0767db82fe6e06a5272c
SHA-256: 5606c4f33eb304f3ad48ee8c07de7379182e1b0cf030fc07ac4dde5ef8da2552
File Format: Dell Update Packages for Linux can be used as stand-alone applications that ensure that specific validation criteria are met, then apply an update.
Note: Update Packages for Linux are open source. See the Dell Update Packages for Linux Readme for details.
File Name: SAS-RAID_Firmware_X37KV_LN64_8.14.0.0.18-14_A08.BIN
File size: 12.02 MB
To ensure the integrity of your download, please verify the checksum value.
MD5: 716b0286fcad4a0963a19a7acdf56551
SHA1: f76f3c0108d187d65753de2c2771490dd672d6bf
SHA-256: 852290d05ae41f98c75327ba24c1e023c9564d46fa80fa3d991988bc517b21fc
Fixes & Enhancements
Fixes:
====
Fixed an issue where after a firmware update the PERC/HBA controller may not be detected on subsequent system resets.
Fixed controller Fault 2656 seen while reprovisioning a SAS SED drive
Fixed inability to perform VD Blink and Unblink operation from management application
Fixed issue where Enclosure vendor ID and FW revision not listing in HII for external enclosures
Enhancements:
============
Improved CBB Retry logic in FW to prevent firmware assert behaviors
Enhanced efficiency in snapdump generation in HBA controllers
Improved Backplane Topology Error Handling
Important Information
Important Information for Update Packages for Microsoft Windows
################################################################
* Do not run other applications while executing Update Packages.
* Do not run storage controller update packages if the controller is in use by other applications.
* The firmware upgrade may fail if any of the RAID controllers in the system are performing an I/O background task (that is, consistency check, background initialization, rebuild, or reconstruction). Allow the background task to complete before attempting to upgrade the firmware. Patrol Read tasks will not affect a firmware upgrade.
Important Information for Update Packages for Linux
################################################################
* Do not run other applications while executing Update Packages.
* If the following error occurs, "Error while loading shared libraries: libstdc++.so.5: cannot open shared object file: No such file or directory", you must install the compatibility libraries from "www.redhat.com" or from the Red Hat CD. To install the compatibility libraries, use the following command: "RPM -ih compat-libstdc++-33-3.2.3-47.3.i386.rpm"
* When Update Packages stop abruptly due to a power outage or abnormal termination, perform the following steps:
- Remove the lock file.
Type the following command: rm -f /var/lock/.spsetup
- Run the Update Package again to reapply the update.
* Do not run storage controller update packages if the controller is in use by other applications.
The firmware upgrade may fail if any of the RAID controllers in the system are performing an I/O background task (that is, consistency check, background initialization, rebuild, or reconstruction). Allow the background task to complete before attempting to upgrade the firmware. Patrol Read tasks will not affect a firmware upgrade.
* Linux systems running one or more applications that interact with SCSI devices in certain ways are known to cause a kernel panic situation. Therefore, it is recommended that you stop Server Administrator and its Storage Management Service before running storage controller firmware update packages.
To stop the Dell OpenManage(TM) Server Administrator service, run "omconfig system webserver action=stop"
To start the Server Administrator service, run "omconfig system webserver action=start"
To stop the Server Administrator Storage Management Service, run "/etc/init.d/dataeng stop"
To start the Server Administrator Storage Management Service, run "/etc/init.d/dataeng start"
Enablement Inbox OS Drivers:
Enablement inbox drivers have been added to some OSes for initial launch of PERC12 controllers. These drivers are for OS install only and have limited performance and controller management functionality.
Management Applications such as PERCCLI2 and Open Manage will not work with these drivers. Enablement drivers can be identified with version numbers "0.255.xxx.xxx" or "3.xxx.xxx.xxx".
Driver version "8.xxx.xxx.xxx" should be installed as soon as possible or applied during OS install to enable full performance and management functionality of PERC12 controllers
Windows 2022/2025 Inbox OS Driver:
The enablement driver "3.0.71.90" for Windows 2022 has known issues with Multi-CPU (2/4 CPU) and large core count CPU configurations that can cause OS to crash when loading the driver. It is recommended to install the latest "8.xxx.xxx.xxx" driver during OS install or as soon as possible after the install.
If facing issues with crashes during OS installation it is recommended to disable Logical Processors and reduce CPU core count to 16 or less cores per CPU from the HII BIOS/UEFI settings menu. After installing the latest "8.xxx.xxx.xxx" PERC driver these settings can be set back to default.
Additionally, running PERCCLI2 or Open Manage with inbox "3.0.71.90" driver can cause OS to crash. Please install "8.xxx.xxx.xxx" driver before using these management applications In Windows 2022 or later.
Supported Operating Systems
Installation instructions
Performing the Firmware Upgrade
===================================
1. Update the firmware version to this version using preferred method below (Windows DUP, Linux DUP).
2. Reboot for the new FW to take effect
Windows Update Package:
Download
1. From Agile, download the update package and save it to your
local hard drive.
Installation
1. Browse to the location where you downloaded the file and double-click the new file.
2. Read over the release information presented in the dialog window.
3. Download and install any prerequisites identified in the dialog window before proceeding.
4. Click the Install button.
5. Follow the remaining prompts to perform the update.
Linux (RHEL/SLES) Update Package:
Download
1. From Agile, download the update package and save it to your
local hard drive.
Installation
1. Read over the release information presented by executing the
"./SAS-RAID_Firmware_XXXXX_LN_XXXXX.BIN --version" command from the shell.
2. Download and install any prerequisites identified in the above step before proceeding.
3. Run the update by executing "./SAS-RAID_Firmware_XXXXX_LN_XXXXX.BIN" from the shell.
4. Follow the remaining prompts to perform the update.
IDRAC/LC
1. Download the Windows DUP Executable from Agile
2. Upload DUP to IDRAC or LC
3. Submit job and reboot the system
VMware/Ubuntu/PERCcli
1. Download the DUP from Agile to a local system
2. Extract the Payload files from the DUP
Extracted DUP > Common > Payload
3. Download and install the latest PERCcli version to your server if not already installed
4. Copy the DUP payload files to your server
5. Navigate to PERCcli folder
Windows - folder with perccli.exe
Linux - /opt/Megaraid/perccli
VMware - /opt/lsi/perccli
Note that PERCcli requires administrator privileges to run
6. Install the Firmware to your controller with the below command
perccli /c download file= \Path To\.bin
7. Reboot the system