Kioxia PM6 program for BA08 FW for model number(s) KPM6XMUG400G, KPM6XMUG800G, KPM6XRUG15T3, KPM6XRUG7T68, KPM6XRUG3T84, KPM6XRUG1T92, KPM6XRUG960G, KPM6XVUG6T40,KPM6XVUG3T20, KPM6XVUG1T60, KPM6XVUG800G, KPM6XVUG12T8,KPM6XMUG1T60, KPM6XMUG3T20
Installed This file was automatically installed as part of a recent update. If you are experiencing any issues, you can manually download and reinstall.This release contains firmware version BA08 for Kioxia drives. Vendor model numbers KPM6XMUG400G, KPM6XMUG800G, KPM6XRUG15T3, KPM6XRUG7T68, KPM6XRUG3T84, KPM6XRUG1T92, KPM6XRUG960G, KPM6XVUG6T40,KPM6XVUG3T20, KPM6XVUG1T60, KPM6XVUG800G, KPM6XVUG12T8,KPM6XMUG1T60, KPM6XMUG3T20
Recommended
Check compatibility
Enter your Dell Service Tag or model
Want to look up your product? Enter a product identifier. Show me how
This driver is not compatible
This driver is not applicable for the selected product. Choose another product to re-enter your product details for this driver or visit the Product Support page to view all drivers for a different product.
Sign in to Windows as an admin to use automatic scan. If your're already signed in as an admin and seeing this message, please reboot. Your system is managed by your IT admin and features might be limited.
Find more updates. Use SupportAssist to find all the latest driver updates for your device.
Fixes & Enhancements
Fixes:
Regression including performacne of BA08 FW for PM6. Issue: 6.4TB or bigger capacity may detect LBA mismatch condition internally and stop the drive operation. Drive goes to the failure mode and does not recover by the drive power cycle.
Cause: 6.4TB or bigger capacity model uses 512Gb Flash Memory. When reading data from the Flash Memory, the FW mistakenly drops the one bit of the physical address, causing the LBA mismatch condition internally. The user-data stored in the Flash memory are protected by the LBA seeded CRC and the drive correctly detected the LBA mismatch then stop the drive operation.
Fix: Fix FW to handle the physical address correctly regardless of 512Gb or 256Gb Flash Memory. Issue: When the Die Retirement (Chip Kill) is needed and a random write operation hits the flash memory, which is being retired, the drive may fall into a failure mode and report SNS=04/44/E0.
Cause: When the Die Retirement (Chip Kill) is necessary and a write access is happened to that Die, the BE (Backend) CPU goes into recovery mode and reports the status to FE (Front End) CPU. When this report is sent to FE CPU, FE CPU instructs BE CPU to do Shutdown (=STOP UNIT). However, this shutdown request was issued without waiting for the Die Retirement to complete, causing SNS=04/44/E0. All user-data are unreadable in this situation.
Fix: FE CPU waits for BE CPU operation to complete before issuing shutdown. Fix the MU 1.6TB and MU2 1.92TB power consumption over spec issue.
Enhancements:
Regression including performacne of BA08 FW for PM6. Issue: 6.4TB or bigger capacity may detect LBA mismatch condition internally and stop the drive operation. Drive goes to the failure mode and does not recover by the drive power cycle.
Cause: 6.4TB or bigger capacity model uses 512Gb Flash Memory. When reading data from the Flash Memory, the FW mistakenly drops the one bit of the physical address, causing the LBA mismatch condition internally. The user-data stored in the Flash memory are protected by the LBA seeded CRC and the drive correctly detected the LBA mismatch then stop the drive operation.
Fix: Fix FW to handle the physical address correctly regardless of 512Gb or 256Gb Flash Memory. Issue: When the Die Retirement (Chip Kill) is needed and a random write operation hits the flash memory, which is being retired, the drive may fall into a failure mode and report SNS=04/44/E0.
Cause: When the Die Retirement (Chip Kill) is necessary and a write access is happened to that Die, the BE (Backend) CPU goes into recovery mode and reports the status to FE (Front End) CPU. When this report is sent to FE CPU, FE CPU instructs BE CPU to do Shutdown (=STOP UNIT). However, this shutdown request was issued without waiting for the Die Retirement to complete
Read MoreRegression including performacne of BA08 FW for PM6. Issue: 6.4TB or bigger capacity may detect LBA mismatch condition internally and stop the drive operation. Drive goes to the failure mode and does not recover by the drive power cycle.
Cause: 6.4TB or bigger capacity model uses 512Gb Flash Memory. When reading data from the Flash Memory, the FW mistakenly drops the one bit of the physical address, causing the LBA mismatch condition internally. The user-data stored in the Flash memory are protected by the LBA seeded CRC and the drive correctly detected the LBA mismatch then stop the drive operation.
Fix: Fix FW to handle the physical address correctly regardless of 512Gb or 256Gb Flash Memory. Issue: When the Die Retirement (Chip Kill) is needed and a random write operation hits the flash memory, which is being retired, the drive may fall into a failure mode and report SNS=04/44/E0.
Cause: When the Die Retirement (Chip Kill) is necessary and a write access is happened to that Die, the BE (Backend) CPU goes into recovery mode and reports the status to FE (Front End) CPU. When this report is sent to FE CPU, FE CPU instructs BE CPU to do Shutdown (=STOP UNIT). However, this shutdown request was issued without waiting for the Die Retirement to complete, causing SNS=04/44/E0. All user-data are unreadable in this situation.
Fix: FE CPU waits for BE CPU operation to complete before issuing shutdown. Fix the MU 1.6TB and MU2 1.92TB power consumption over spec issue.
Enhancements:
Regression including performacne of BA08 FW for PM6. Issue: 6.4TB or bigger capacity may detect LBA mismatch condition internally and stop the drive operation. Drive goes to the failure mode and does not recover by the drive power cycle.
Cause: 6.4TB or bigger capacity model uses 512Gb Flash Memory. When reading data from the Flash Memory, the FW mistakenly drops the one bit of the physical address, causing the LBA mismatch condition internally. The user-data stored in the Flash memory are protected by the LBA seeded CRC and the drive correctly detected the LBA mismatch then stop the drive operation.
Fix: Fix FW to handle the physical address correctly regardless of 512Gb or 256Gb Flash Memory. Issue: When the Die Retirement (Chip Kill) is needed and a random write operation hits the flash memory, which is being retired, the drive may fall into a failure mode and report SNS=04/44/E0.
Cause: When the Die Retirement (Chip Kill) is necessary and a write access is happened to that Die, the BE (Backend) CPU goes into recovery mode and reports the status to FE (Front End) CPU. When this report is sent to FE CPU, FE CPU instructs BE CPU to do Shutdown (=STOP UNIT). However, this shutdown request was issued without waiting for the Die Retirement to complete
Version
BA08, A00
Release date
11 May 2021
Download Type
Firmware
Category
SAS Drive
Importance
RecommendedDell Technologies recommends applying this update during your next scheduled update cycle. The update contains changes to maintain overall system health. It ensures that the system software remains current and compatible with other system modules (firmware, BIOS, drivers, and software) and may include other new features.
Available formats View Important Information
File Format: Update Package for MS Windows 64-Bit.
File Name: SAS-Drive_Firmware_5D5VX_WN64_BA08_A00.EXE
File Size: 10.51 MB
This is a large file. Depending on your connection speed, it may take some time to download.
Format Description:
Dell Update Packages in native Microsoft Windows 64-bit format do not require that Microsoft WOW64 be installed on the Microsoft Windows Server.
To ensure the integrity of your download, please verify the checksum value.
MD5:
efb2f66514bac391a3eb02446e01137a
SHA1:
c1c636a83e13fe54fecc0bbf93dd5df58b975802
SHA-256:
1ec7f1d09ca648a7f11c4eb7d3c17ed93decf4eb9566e45c432191d4c4f2b984
File Format: A GnuPG file which contains a cryptographic signature
File Name: SAS-Drive_Firmware_5D5VX_LN_BA08_A00.BIN.sign
File Size: 226 Bytes
This is a large file. Depending on your connection speed, it may take some time to download.
Format Description:
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.
To ensure the integrity of your download, please verify the checksum value.
MD5:
0f14b6883b3a720e003f1af9a48101e7
SHA1:
2101b5c2dded573b43da9799d5faa4bed15eaaed
SHA-256:
f52e4a71ff24d231185a16457fbd4bb49d6b7ab9db6525703d8e265245f8c8e5
File Format: Update Package for MS Windows 32-Bit
File Name: SAS-Drive_Firmware_5D5VX_WN32_BA08_A00.EXE
File Size: 9.31 MB
This is a large file. Depending on your connection speed, it may take some time to download.
Format Description:
Dell Update Packages (DUP) in Microsoft Windows 32bit format have been designed to run on Microsoft Windows 64bit Operating Systems. Dell Update Packages (DUP) in Microsoft Windows 64bit format will only run on Microsoft Windows 64bit Operating Systems. When selecting a device driver update be sure to select the one that is appropriate for your operating system.
To ensure the integrity of your download, please verify the checksum value.
MD5:
dab743859709fd33dfafe2a854267561
SHA1:
3e2817612cbbe871b4323e2ecbc469ff4a42d64f
SHA-256:
388c56153ef7ecc49afe6293a8d8fc1be28a64e3f1d76369cda776d346392090
File Format: Update Package for Red Hat Linux
File Name: SAS-Drive_Firmware_5D5VX_LN_BA08_A00.BIN
File Size: 6.23 MB
This is a large file. Depending on your connection speed, it may take some time to download.
Format Description:
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.
Note: Update Packages for Linux are open source. See the Dell Update Packages for Linux Readme for details.
To ensure the integrity of your download, please verify the checksum value.
MD5:
17188c51e10d703a4c0afc13439961ae
SHA1:
66ee822bc9ed03a5bf5e0f712e16b9b0e51a8a2c
SHA-256:
fcbe1ea384ea0274ea945bb76fa8e2c814b68f846fafa84134730f0a686b9f51
By downloading, you accept the terms of the Dell Software License Agreement.
Important Information
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.
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. 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.
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.
Supported Operating Systems
Novell SuSE Linux ES 11
Windows Server 2008 x64
Suse Linux ES 10
Linux
Windows Server 2012
Red Hat® Enterprise Linux 6
Red Hat® Enterprise Linux 7
Red Hat® Ent Linux 5
Red Hat® Enterprise Linux 8
Windows Storage Server 2012 R2
Novell SuSE Linux ES 10
SuSE Linux Desktop 11
SUSE Linux ES 12
SuSE Linux ES 15
Windows Server 2012 R2
Windows Server 2008 x86
Windows Server 2003
Windows Server 2019 LTSC
Windows Server 2022 LTSC
Windows Server 2008 R2
Windows Storage Server 2012
Windows Server 2016
Windows Server 2003 x64
Applies to
PM6 10WPD SSDR,1.6T,2E,IS12,2.5,X,P60,EC
Model Number: KPM6XMUG1T60
Regulatory Model Number: KPM6XMUG1T60
Vendor PN: SDFUN85DAB
PM6 10WPD SSDR,3.2T,2E,IS12,2.5,X,P60,EC
Model Number: KPM6XMUG3T20
Regulatory Model Number: KPM6XMUG3T20
Vendor PN: SDFUN84DAB
PM6 10WPD SSDR,400G,2E,IS12,2.5,X,P60,EC
Model Number: KPM6XMUG400G
Regulatory Model Number: KPM6XMUG400G
Vendor PN: SDFUN87DAB
PM6 10WPD SSDR,800G,2E,IS12,2.5,X,P60,EC
Model Number: KPM6XMUG800G
Regulatory Model Number: KPM6XMUG800G
Vendor PN: SDFUN86DAB
PM6 1WPD SSDR,1.9T,2E,IS12,2.5,X,P6,EC
Model Number: KPM6XRUG1T92
Regulatory Model Number: KPM6XRUG1T92
Vendor PN: SDFUS85DAB
PM6 1WPD SSDR,15.T,2E,IS12,2.5,X,P6,EC
Model Number: KPM6XRUG15T3
Regulatory Model Number: KPM6XRUG15T3
Vendor PN: SDFUS81DAB
PM6 1WPD SSDR,3.8T,2E,IS12,2.5,X,P6,EC
Model Number: KPM6XRUG3T84
Regulatory Model Number: KPM6XRUG3T84
Vendor PN: SDFUS84DAB
PM6 1WPD SSDR,7.6T,2E,IS12,2.5,X,P6,EC
Model Number: KPM6XRUG7T68
Regulatory Model Number: KPM6XRUG7T68
Vendor PN: SDFUS83DAB
PM6 1WPD SSDR,960G,2E,IS12,2.5,X,P6,EC
Model Number: KPM6XRUG960G
Regulatory Model Number: KPM6XRUG960G
Vendor PN: SDFUS86DAB
PM6 3WPD SSDR,1.6T,2E,IS12,2.5,X,P63,EC
Model Number: KPM6XVUG1T60
Regulatory Model Number: KPM6XVUG1T60
Vendor PN: SDFUQ85DAB
PM6 3WPD SSDR,12.T,2E,IS12,2.5,X,P63,EC
Model Number: KPM6XVUG12T8
Regulatory Model Number: KPM6XVUG12T8
Vendor PN: SDFUQ81DAB
PM6 3WPD SSDR,3.2T,2E,IS12,2.5,X,P63,EC
Model Number: KPM6XVUG3T20
Regulatory Model Number: KPM6XVUG3T20
Vendor PN: SDFUQ84DAB
PM6 3WPD SSDR,6.4T,2E,IS12,2.5,X,P63,EC
Model Number: KPM6XVUG6T40
Regulatory Model Number: KPM6XVUG6T40
Vendor PN: SDFUQ83DAB
PM6 3WPD SSDR,800G,2E,IS12,2.5,X,P63,EC
Model Number: KPM6XVUG800G
Regulatory Model Number: KPM6XVUG800G
Vendor PN: SDFUQ86DAB
Installation instructions
Dell Update Package instructions for Windows Dup:
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-Drive_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-Drive_Firmware__LN__A00.BIN.Sign.
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-Drive_Firmware_
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-Drive_Firmware_
Drivers help and tutorials
For more downloads go to the Drivers and downloads. For help on using the information on this page, please visit Driver Help and Tutorials.