Loading...
Loading...
A BAT0020 event may be reported indicating that the SDPM battery is not ready, even though the battery has not failed. System Event Log (SEL) Lifecycle (LC) Log iDRAC > Maintenance > Lifecycle log > Search for BAT TSR > Hardware > Logs > Lifecycle Log > Search for BAT Only PowerFlex FG (Fine‑Granularity) and EC (Erasure Coding) storage pools use acceleration devices, which rely on the SDPM memory and its battery. If you are using a PowerFlex MG (Medium‑Granularity) storage pool and see the BAT0020 error, your data is safe—the SDPM subsystem is not involved. For MG storage pools, the steps in the Resolution section still apply, but the issue is not critical. To determine PowerFlex data layout using PowerFlex manager: To determine PowerFlex data layout via SCLI: # scli --query_storage_pool --storage_pool_name <PoolName> --protection_domain_name <ProtectionDomainName> | egrep "Data layout" Example Outputs: Data layout: Erasure Coding Data layout: Medium Granularity Data layout: Fine Granularity
SDPM BAT0020 error does not necessarily indicate a battery failure. PowerFlex 16G versions with iDRAC prior to 7.30.10.50 can generate false or transient BAT0020 alerts. False Positive Alerts: Transient BAT0020 events may be reported even when the battery is healthy. These false-positive events do not indicate a battery failure. Temporary communication issues may trigger a BAT0020 alert. True Hardware Alerts: This can occur when the battery has been discharged due to loss of power or the system being shut down. The battery may also trigger this error if it is no longer able to charge to an acceptable level due to wear over time.
CAUTION: Do not replace the battery as a first step. If the issue is caused by a false-positive alert, replacing the battery will not resolve the problem and the alert will reoccur. Step 1: Verify whether the alert is a false positive Check the health status of the SDPM devices: For PowerFlex core versions 4.5.7 and later: Review the SDPM state directly from the PowerFlex alerts in the user interface. For PowerFlex core versions prior to 4.5.7: Run the following command from the node OS CLI: ndctl list -D -H Note: The ndctl package is only installed on nodes participating in FG storage pools. A healthy SDPM device may show: { "dev":"nmem0", "health": { "health_state":"ok" } } Examples of unhealthy states include: { "dev":"nmem0", "health": { "health_state":"non-critical" } } or { "dev":"nmem0", "enabled":false } Step 2: Determine next steps False-Positive Alert: If all SDPM devices report "health_state":"ok" and are in an enabled state, the alert is a false positive. Proceed to the Firmware Update (Resolution) section below. True Hardware Failure: If any SDPM device reports a degraded/non-healthy state or is disabled , treat this as a valid hardware issue. Follow standard hardware troubleshooting and replacement procedures for the battery or persistent memory module. Firmware Update (Resolution) The false-positive BAT0020 condition is addressed in iDRAC 7.30.10.50 firmware or newer. When updating to iDRAC 7.30.10.50 or newer , Dell also recommends updating to BIOS 2.10.1 or later , and CPLD 1.2.7 or later . The fix is integrated into the following RCM\IC validated releases (and all subsequent releases) that contain these minimum versions: RCM 3.8.4.2 - Gen 1 RCM 3.9.1.2 - Gen 2 RCM 3.8.5.0 - Gen 1 RCM 3.9.2.0 - Gen 2 IC 51.384.02 - Gen 1 IC 51.391.02 - Gen 2 IC 52.385.00 - Gen 1 IC 52.392.00 - Gen 2 See PowerFlex: Release Matrix for associated PowerFlex Manager and Core release versions. Upgrade Options # OPTION DESCRIPTION WHEN TO USE 1 Recommended – Upgrade to a supported RCM or IC release that contains the fix. Deploy the full RCM/IC bundle that includes iDRAC 7.30.10.50+, BIOS 2.10.1+, and CPLD 1.2.7+. PowerFlex: Systems with ProSupport are Eligible for Upgrades by Dell RPS Team . When you can schedule a coordinated firmware‑bundle upgrade (minimum service impact). 2 Alternative – Single Component Upgrade (SCU). Upgrade iDRAC to 7.30.10.50 or later and BIOS to 2.10.1 or later using the SCU workflow. SCU handles the firmware flash, then reboots the node in maintenance mode. PowerFlex: How to Perform Single Component Upgrade (SCU) Note: CPLD 1.2.7 or newer cannot be upgraded via SCU until PFMP 5.2 is released. When you need a quicker, component‑level update and can accept a later CPLD upgrade separately. CPLD Upgrade (If required) If the system is running PFMP 5.1.x or earlier, the CPLD must be upgraded manually to version 1.2.7 or later. Follow the PowerFlex: How to Update the CPLD Firmware Manually Using iDRAC procedure. When PFMP 5.2 (or newer) is available, the CPLD can be upgraded through SCU. Important Caution When using SCU, only iDRAC and BIOS are updated automatically. After SCU completes, you must perform the CPLD upgrade (manual step) and reboot the affected node before the system returns to normal operation. Firmware files (minimum‑fix versions) COMPONENT MINIMUM VERSION FILE NAME (DOWNLOADABLE .EXE) iDRAC 7.30.10.50 iDRAC_7.30.10.50_A00.exe BIOS 2.10.1 BIOS_G93PH_WN64_2.10.1.EXE CPLD (R760/660) 1.2.7 CPLD_Firmware_XJG0V_WN64_1.2.7_A00.EXE Download the appropriate files from the Dell Technologies Support site, ensuring you select the exact model and firmware revision for your hardware. Note: Newer version can be found on the " All Driver Versions " tab. Next steps after upgrade Verify that the iDRAC, BIOS, and CPLD firmware versions meet or exceed the minimums listed above. Re‑run ndctl list -D -H (or check the PowerFlex UI) to confirm the SDPM health state returns to "health_state":"ok" . Monitor the system for a clean boot and confirm that the BAT0020 alert no longer appears. If the alert persists after the firmware upgrades, treat it as a true hardware issue and follow the battery‑ or persistent‑memory‑replacement procedures. Impacted Versions Versions lower than: iDRAC 7.30.10.50 BIOS 2.10.1 CPLD 1.2.7 Fixed In Versions (and newer) iDRAC 7.30.10.50 BIOS 2.10.1 CPLD 1.2.7 Minimum RCM / IC's that contain fixed versions above: RCM 3.8.4.2 RCM 3.9.1.2 IC 51.391.01 IC 51.391.02 Workaround t o clear transient events if unable to complete resolution steps immediately. 1- Reset SEL Logs iDRAC UI > Maintenance > System Event Log > Clear 2- Soft reset iDRAC (No Service Impact or downtime needed) Node will not reboot only management module will reboot iDRAC UI > Dashboard > More Actions > Reboot iDRAC
Click on a version to see all relevant bugs