: When executing updates from within a host operating system, the installer extracts its contents onto a temporary RAM drive. If this driver cache does not clear automatically, iDRAC registers a persistent block.
The error is almost always resolved by clearing the iDRAC job queue and resetting the controller, as detailed in the steps above. By following these best practices, you can ensure smooth firmware updates and minimize server downtime.
Navigate to your Cloud Portal and look at the Deployment History . Look for any task with a status of "Scheduled," "In Progress," or "Cancelling."
Prevention is far better than repeated troubleshooting. The following best practices will significantly reduce the frequency of SUP0108 errors in your environment.
Comprehensive Guide: Resolving iDRAC Error "SUP0108: A deployment or update operation is already in progress" : When executing updates from within a host
The error message itself advises to wait for the operation to conclude. In many cases, a legitimate firmware update is genuinely in progress. As Dell’s official guidance recommends, the first step is simply to wait for the operation to conclude and then retry. However, if the operation does not complete within a reasonable timeframe (10–15 minutes), the underlying operation is likely stuck and requires intervention.
Once the iDRAC returns (can take 2-5 minutes), attempt the update again. 3. Gracefully Reboot the Host Server
The (e.g., R740, R760) or your iDRAC version (e.g., iDRAC9, iDRAC10).
A soft reset restarts the iDRAC management subsystem without impacting production workloads or powering down the host server. This is the most efficient, non-disruptive method to clear ghost lockfiles. : Log into your iDRAC dashboard. Navigate to the Dashboard page or the Maintenance tab. Locate the Quick Links or Diagnostics section. By following these best practices, you can ensure
# Lock is held by another deployment if get_queue_length() < 10: # prevent queue overflow add_to_queue(request_id, str(payload)) return "status": "queued", "message": "A deployment is already in progress. Your request has been queued.", "position": get_queue_length(), "request_id": request_id
: This error often occurs because a RAM drive created for a previous upgrade was not cleared. Shut down the server, unplug the power cables for 10 seconds, and restart to clear the drive. Server Fault Troubleshooting Stuck Jobs Clear the Job Queue
: Large firmware updates (like iDRAC/Lifecycle Controller itself) may exceed standard timeouts, leaving the system in a "Downloading" or "Running" state even after the task has technically completed or failed.
Run the following RACADM command to wipe out all pending and frozen deployment entries: racadm jobqueue delete -i JID_CLEARALL Use code with caution. The following best practices will significantly reduce the
Use a shared Slack or Teams channel to notify the team before hitting "Deploy" on shared staging environments.
: This message can sometimes appear in the iDRAC UI even when no actual update operation is active, simply because the Lifecycle Controller is technically "in use" by another module.
: The iDRAC installer mounts a temporary RAM drive onto the host operating system to unpack and execute firmware binaries. If a past update fails or finishes uncleanly, this RAM drive remains mounted, blocking future update hooks.