The problem stems from the inner workings of Dell's and iDRAC management engines. Common root causes include:
or by holding the "i" button on the front of the server for 16 seconds. Best Practices to Avoid SUP0108 Avoid Heavy CPU Load
One user in Dell’s community forums encountered this issue immediately after uploading firmware via Redfish, before even triggering the SimpleUpdate action, forcing them to reboot the iDRAC to escape the locked state. The problem stems from the inner workings of
: In most cases, the system is simply processing a previous request. Wait for the operation to conclude and then retry.
Wait at least 15 to 20 minutes between consecutive component updates. : In most cases, the system is simply
Before taking drastic action, wait for the update to complete. The Dell documentation indicates that the best first step is to allow the current operation to conclude. Sometimes, this can take up to an hour or more if a substantial firmware update is pending. 2. Reset iDRAC from the Web Interface
: The firmware installer creates a temporary RAM drive on the host OS to extract files. If a previous update failed or didn't clean up properly, this drive remains and blocks new updates. Before taking drastic action, wait for the update
Or with the new sf CLI:
Reattach the power cables and wait 2 minutes for iDRAC to initialize before hitting the power button to boot up the host system. Best Practices to Prevent SUP0108 During Upgrades
SUP0108 Error Message: “A deployment or update operation is already in progress. Please wait for the current operation to finish before starting a new one.” Severity: Medium (Operational Blocker) Component: Azure Arc Agent (Guest Configuration / Extensions)