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_61YM8_WN64_8.14.0.0.18-14_A11.EXE
File size: 23.83 MB
To ensure the integrity of your download, please verify the checksum value.
MD5: cedc71fd914766e0a8b4ca3dae07148e
SHA1: fac13e5faa55ddd5fdc2aecd29a48c47f8f8851d
SHA-256: 7a4d9155945563afbd8ca2a4dc111f1b4d9f23ef0d029a0333d492c3ae2cd4d7
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_61YM8_LN64_8.14.0.0.18-14_A11.BIN.sign
File size: 842 Bytes
To ensure the integrity of your download, please verify the checksum value.
MD5: 1211e49b56a9971ff1f6b502b6ca8614
SHA1: 1a17590de7b35e8668c4958ad133b430d13abfd6
SHA-256: 607a7a73bf98ac4daa4cc430a74ef44b59e9adc46326704aa6af30b6826595b9
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: 24.52 KB
To ensure the integrity of your download, please verify the checksum value.
MD5: b8b7e8983f202a815ee93a40cf8da516
SHA1: 9cec63cc43ffbb2b7694e3a88cfe394cc397a261
SHA-256: 95b7924ecaded21394bed95bf2eedd08faff212a2d790ae8ff7fb1846a21522a
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.<br /><b>Note:</b> Update Packages for Linux are open source. See the Dell Update Packages for Linux Readme for details.
File Name: SAS-RAID_Firmware_61YM8_LN64_8.14.0.0.18-14_A11.BIN
File size: 12.02 MB
To ensure the integrity of your download, please verify the checksum value.
MD5: 57044d8909762a29f568f5ec567c112b
SHA1: f04118d2c8d551c2b2468892dc33485987384924
SHA-256: 9811bff876132fedba0760fb46acc2430bf3890fb1887f4053264042fc5f0ae4
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 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 set
Supported Operating Systems
Installation instructions
Performing the Firmware Upgrade
===================================
Update the firmware version to this version using preferred method below (Windows DUP, Linux DUP).
Windows Update Package:
Download
1. From http://www.dell.com/support/home, 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 Update Package:
Download
1. From http://www.dell.com/support/home, download the update package and save it to your
local hard drive.
Installation
1. Read over the release information presented by executing the
"./SAS-NON-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-NON-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 http://www.dell.com/support/home
2. Upload DUP to IDRAC or LC
3. Submit job and reboot the system
PERCcli2
Note that PERCcli requires administrator privileges to run
1. Download the DUP from http://www.dell.com/support/home to a local system
2. Extract the Payload files from the DUP
Extracted DUP > Common > Payload
3. Download and install the latest PERCCLI2 version to your server if not already installed
4. Copy the DUP payload files to your server
5. Navigate to PERCCLI2 folder
Windows - folder with perccli2.exe
Linux - /opt/Megaraid/perccli2
ESXi 7.0 U3
VMware - /opt/lsi/perccli2
ESXi 8.0 U2
VMware - /opt/perccli2/bin
6. Install the Firmware to your controller with the below command
perccli /c download file= \Path To\.rom
ESXi 8.0 U2
esxcli perccli2 controller download firmware -i c -z 0 -f \Path To\.rom -a online (0 - controller index no.)
Note: Online activation doesnt require reboot of the server