Loading...
Loading...
iDRAC's FW update job failure: iDRAC's Lifecycle log: RED097: Unable to complete the firmware update operation because the specified firmware image is for a component that is not in the target system inventory or the component is disabled for performing the update. Impact FW update failure leads to entire SO upgrade failure.
Due to a PowerEdge issue, the incorrect FW file is chosen from the RCM or IC package for the update flow. There are two different NVMe drive firmware packages with level 2.5.0: Incorrect FW: Express-Flash-PCIe-SSD_Firmware_ 5CM3G _WN64_2.5.0_A0 6 _01.EXE Correct FW: Express-Flash-PCIe-SSD_Firmware_ 5V3P7 _WN64_2.5.0_A0 5 _01.EXE Note: Several lab tests found a manual upgrade to be ineffective and usually tends to fail. A drain flea power procedure was found to be the best solution. See Resolution section for details.
To address the issue and rerun the upgrade successfully, the server must drain flea power: Ensure that all the PowerFlex components residing on the server are ready for a prolonged reboot (for example SDS or SDR put into Protected Maintenance Mode (PMM), Primary or Secondary MDM role-replaced with a TieBreaker MDM or a Standby MDM, and so forth) Log in to the iDRAC web interface Go to Configuration > BIOS Settings > click Miscellaneous Settings to expend the options. To overcome the issue and rerun the upgrade successfully, the server must drain flea power: Ensure that all the PowerFlex components residing on the server are ready for a prolonged reboot (for example SDS or SDR put into Protected Maintenance Mode (PMM), Primary or Secondary MDM role-replaced with a TieBreaker MDM or a Standby MDM, and so forth) Log in to the iDRAC web interface Go to Configuration > BIOS Settings > click Miscellaneous Settings to expend the options: In Miscellaneous Settings , select Power Cycle Request > Full Power Cycle from the dropdown, and click Apply And Reboot : The process simulates a physical AC power disconnect, causing the iDRAC connection to temporarily drop: The job appears in the iDRAC's Job Queue with a status of "pending reboot" The process can be monitored in the virtual console, where it shows as running within the Lifecycle Controller. The server reboots, and the iDRAC connection is lost temporarily. Once the server restarts, log back in to the iDRAC to confirm the process is complete. Impacted versions RCM 3.7.1.0 - 3.8.2.0 IC 40.370.00 - 46.382.00 Fixed versions RCM 3.8.3.0 IC 48.383.00
Click on a version to see all relevant bugs
Dell Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.