Kioxia PM6 program for BA08 FW for model number(s) KPM6XMUG400G, KPM6XMUG800G, KPM6XRUG15T3, KPM6XRUG7T68, KPM6XRUG3T84, KPM6XRUG1T92, KPM6XRUG960G, KPM6XVUG6T40,KPM6XVUG3T20, KPM6XVUG1T60, KPM6XVUG800G, KPM6XVUG12T8,KPM6XMUG1T60, KPM6XMUG3T20
已安装 此文件是作为最近更新的一部分自动安装的。如果您遇到任何问题，您可以手动下载并重新安装。此页面的内容可能已自动翻译。要提供反馈，请填写页面底部的表单。
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
推荐
以管理员身份登录 Windows 以使用自动扫描。如果您已以管理员身份登录并看到此消息，请重新启动。 您的系统由 IT 管理员管理，并且功能可能受限。
查找更多更新。使用 SupportAssist 查找适用于您的设备的所有最新驱动程序更新。
补丁和增强功能
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
了解详情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
版本
BA08, A00
发布日期
11 5月 2021
下载类型
固件
类别
SAS驱动器
重要性
推荐Dell Technologies 建议在下一个计划的更新周期期间应用此更新。更新包含用于维护整体系统运行状况的更改。它可确保系统软件保持最新状态并与其他系统模块（固件、BIOS、驱动程序和软件）兼容，并且可能包括其他新功能。
可用格式 查看重要信息
文件格式： MS Windows（64位）的更新包。
文件名： SAS-Drive_Firmware_5D5VX_WN64_BA08_A00.EXE
文件大小： 10.51 MB
这是一个大文件。根据您的连接速度，可能需要一些时间来下载。
格式说明:
如戴尔更新包为原生微软64位格式，则不需要在微软Windows服务器上安装WOW64。
为确保下载的完整性，请验证校验和值。
MD5：
efb2f66514bac391a3eb02446e01137a
SHA1：
c1c636a83e13fe54fecc0bbf93dd5df58b975802
SHA-256：
1ec7f1d09ca648a7f11c4eb7d3c17ed93decf4eb9566e45c432191d4c4f2b984
文件格式： 包含加密签名的GnuPG文件
文件名： SAS-Drive_Firmware_5D5VX_LN_BA08_A00.BIN.sign
文件大小： 226 Bytes
这是一个大文件。根据您的连接速度，可能需要一些时间来下载。
格式说明:
Red Hat Linux更新包的GnuPG签名可用于验证戴尔在相关Red Hat Linux更新包中的身份。
为确保下载的完整性，请验证校验和值。
MD5：
0f14b6883b3a720e003f1af9a48101e7
SHA1：
2101b5c2dded573b43da9799d5faa4bed15eaaed
SHA-256：
f52e4a71ff24d231185a16457fbd4bb49d6b7ab9db6525703d8e265245f8c8e5
文件格式： 面向MS Windows（32位）的更新包
文件名： SAS-Drive_Firmware_5D5VX_WN32_BA08_A00.EXE
文件大小： 9.31 MB
这是一个大文件。根据您的连接速度，可能需要一些时间来下载。
格式说明:
Microsoft Windows 32位格式中的戴尔更新包(DUP)设计为可以在Microsoft Windows 64位操作系统上运行。Microsoft Windows 64位格式中的戴尔更新包(DUP)仅可在Microsoft Windows 64位操作系统上运行。选择设备驱动程序更新时，请务必选择适合您的操作系统的更新。
为确保下载的完整性，请验证校验和值。
MD5：
dab743859709fd33dfafe2a854267561
SHA1：
3e2817612cbbe871b4323e2ecbc469ff4a42d64f
SHA-256：
388c56153ef7ecc49afe6293a8d8fc1be28a64e3f1d76369cda776d346392090
文件格式： Red Hat Linux的更新包
文件名： SAS-Drive_Firmware_5D5VX_LN_BA08_A00.BIN
文件大小： 6.23 MB
这是一个大文件。根据您的连接速度，可能需要一些时间来下载。
格式说明:
适用于Linux 的戴 尔更新包是在 满足特定的标准系统环境下使用的独立应用程序。，然后应用更新。
注意：Linux的更新包是开源的。查看适用于Linux 的戴 尔更新包自述以了解 详情，了解详情。
注意：Linux的更新包是开源的。查看适用于Linux 的戴 尔更新包自述以了解 详情，了解详情。
为确保下载的完整性，请验证校验和值。
MD5：
17188c51e10d703a4c0afc13439961ae
SHA1：
66ee822bc9ed03a5bf5e0f712e16b9b0e51a8a2c
SHA-256：
fcbe1ea384ea0274ea945bb76fa8e2c814b68f846fafa84134730f0a686b9f51
开始下载软件，即表示您接受戴尔软件许可协议 ( 英文版 ) 条款。
重要信息
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.
受支持的操作系统
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® Enterprise 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
Microsoft Windows Server 2008 R2
Windows Storage Server 2012
Windows Server 2016
Windows Server 2003 x64
适用于
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
安装说明
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_