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_R3KN0_WN64_8.8.0.0.18-26_A02_01.EXE
File size: 25.59 MB
To ensure the integrity of your download, please verify the checksum value.
MD5: 865af78d3e678a32f46a30fea14288e1
SHA1: d2c92883ba40424d8ac3fa8880692550327d7567
SHA-256: 0df146d1d1dad04a8fdbdfb185010acf15ffc0389352dfd983a323ba9885ecac
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_R3KN0_LN64_8.8.0.0.18-26_A02_01.BIN.sign
File size: 842 Bytes
To ensure the integrity of your download, please verify the checksum value.
MD5: 08d52b11f3f077b2cc85805f8ad29f73
SHA1: 2fc9c88f09030740eff3b4e6140b5f22bc2f6ddf
SHA-256: 4a15f113416341ebb75fdb20db377d59650f6a8151125e7a22bbaa84b25d8591
File Format: This file format contains plain text which can be viewed with a standard text editor.
File Name: SAS_RAID_Firmware_8_8_0_0_18_26_Release_Notes.txt
File size: 17.4 KB
To ensure the integrity of your download, please verify the checksum value.
MD5: 7792d376d3b7522388bc353b2f8eddfa
SHA1: 22b3ba27b21acb8a7b621ba9965c35675eb6a892
SHA-256: 0ec0386be9d17e0faa32ecfd6f41ba9d69e65a976da1415a66c8a0d158b36bb3
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_R3KN0_LN64_8.8.0.0.18-26_A02_01.BIN
File size: 13.06 MB
To ensure the integrity of your download, please verify the checksum value.
MD5: d345ce6ec0b140e34ccf38f183c31862
SHA1: 651e3666507adee877a15f3e9435f2442ef2870e
SHA-256: d126e01ff4ce9dbc26cbc9007abad67281179229f6c0609b188841651d5c129e
Fixes & Enhancements
Fixes
=========
Fixed an issue that could cause controller to fault during sleep/shutdown/reboot operations
Fixed an issue that caused NVMe drive to be reported as HDD instead of SSD in windows
Fixed invalid slot number being reported for backplane events
Fixed some issues that could cause fault during cache preservation operations
Fixed an issue that cause backplane slot information not to get set correctly on drive removal
Fixed an issue that caused redudant path restored event to get generated incorrectly during SED drive unlock
Fixed an issue that caused NVMe drives to disappear after a controller overtemp condition occurs
Fixed an issue that caused NVMe drives to disappear on certain configs when removing drives in slots 0 & 1 or 4 & 5
Fixed an issue that could cause a controller fault deadlock during config creation
Fixed an issue that could cause a controller fault during RAID 6 rebuild operations
Fixed an issue that could cause the controller to fault during offline/staged firmware update
Fixed an issue that caused stale drive data to be shown in HII if drive changed to BAD/Failed state
Fixed an issue that could cause battery failure or removal to not get reported properly
Fixed an issue that caused NVMe negotiated link speed to be reported as 32.0 GT/s instead of 16.0GT/s
Fixed an issue that could cause slow drive discovery on an enclosure during path failover scenarios
Fixed an issue that caused UBM backplane discovery error event to get generated incorrectly
Fixed an issue that could cause controller to fault during reset when removing and inserting drives
Enhancements
=============
Enabled full SED drive ownership;
Added support for SED drive PSID erase
Changed controller connector names reported in HII and PERCcli to match cable information
Optimized controller discovery over sideband after a controller reset
Added support for reporting first device in Linux OSes
Added support for SATA drives that do not support SEQUENTIAL QUEUED log requests
Added support for Read Ahead Cache on HDD Virtual Disks
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