This release contains firmware version CSD8 for STX drives. Vendor model numbers ST4000NM015A.<br/>Drive need to be at firmware version CSD7 for this update to complete. Customers with drives that are on firmware version CSD3 need to update to firmware version CSD7 first.
This release contains firmware version CSD8 for STX drives. Vendor model numbers ST4000NM015A. Drive need to be at firmware version CSD7 for this update to complete. Customers with drives that are on firmware version CSD3 need to update to firmware version CSD7 first.
Fixes: -Fix an issue where inaccurate write timing can cause unrecoverable read error -Fix the issue where drive stops responding to COMINIT after hard reset -Fix the issue where SANITIZE does not resume after host reset -Fix the issue where the SAS speed negotiation can fail at lower interface speed -Fix the issue where unexpected Reservation Conflict status is reported after firmware download -Fix issues where assert can result -Fix issues where hang condition can result -Fix issues where command timeout can result -Fix an issue where IOEDC error can result
Enhancements: -Improve reliability features -Improve event logging/sense data reporting accuracy -Improve throughput performance for specific workloads -Improve throughput performance during certain system vibrations -Improve recovery paths for various error situations
This update will not run if any of the following conditions exist 1. Any Virtual Disk that is not optimal. 2. A RAID container that is performing a Background Initialization or Consistency Check. 3. A Rebuild, Resync, or copyback function is taking place. 4. A RAID set that is Partially Degraded or in a Degraded state. 5. Drives are on firmware version CSD3
This update will run on drives remaining in a RAID set that is in a Offline state.
There is an architectural constraint with Dell DUP HDD firmware update utility, related to system memory utilization, which is typically encountered on systems with minimal system memory, memory-intensive configurations, multiple RAID controllers, or memory-intensive applications. This issue is typically reported as - The operation was not successful because the device buffer write has failed. And will result in an aborted attempt to update firmware on the identified HDD. Error codes associated with this failure mode include 8009 and 8017. Once an error is detected, the update session is aborted. There is no data integrity or data availability risk associated with this issue. Subsequent attempts to update the HDD firmware may succeed, particularly if system resources are freed up.
1. Click the "Download Now" link to download the file. 2. When the File Download window appears, click "Save" to save the file to your 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. 5. Click the Install button. 6. Follow the remaining prompts to perform the update.
Dell Update Package instructions for Linux DUP (RHEL/SLES/Ubuntu):
1. Click the "Download Now" link to download the file. 2. When the File Download window appears, click "Save" to save the file to your hard drive. Installation 1. Browse to the location where you downloaded the file and run the update by executing "./ SAS_Firmware__LN__A00.BIN " from the shell. 2. Read over the release information presented in the dialog window. 3. Download and install any prerequisites identified in the dialog window before proceeding. 5. Click the Install button. 6. Follow the remaining prompts to perform the update.
GnuPG Signature of Dell Update Package Instructions:
Download the latest GnuPG Signature of Dell Update Package from support.dell.com.
1. Browse to the location where you downloaded the file. 2. Read over the release information presented in the dialog window. Installation 1. Import the Dell public key. (You only need to do this once on your system.) 2. Verify the Dell Update Package by using its signature file, SAS_Firmware__LN__A00.BIN.sign.