A corrupted WSUS database often causes ghost operations. Run the cleanup of ConfigMgr.
: For older systems, avoid skipping too many versions at once; perform updates in smaller "steps". Avoid High CPU Loads
: During explicit updates (such as an iDRAC9 firmware upgrade), the installer places a temporary RAM drive onto the host operating system to extract components. If this environment isn't cleared, subsequent updates are blocked.
: The most standard solution is to wait for the current operation to finish. Some updates, particularly for iDRAC 9, can take anywhere from 20 minutes to 4 hours to fully conclude. Clear the Job Queue A corrupted WSUS database often causes ghost operations
A clogged job queue is the primary reason the system thinks a deployment is "already in progress". You can clear out stalled or scheduled operations via the RACADM CLI: Establish an SSH connection to your iDRAC IP address. Check for active jobs by running: racadm jobqueue view Use code with caution. If stuck tasks appear, clear the entire database using: racadm jobqueue delete -i JID_CLEARALL Use code with caution. 3. Perform a System "Cold Boot" (Fleaflicker Power Cycle)
: Many instances of this bug are resolved in newer firmware versions (e.g., iDRAC9 firmware 7.20.10.50).
If the LCC is in a "recovery mode," it may need to be re-enabled: Enter during boot. Go to iDRAC Settings -> Lifecycle Controller . Avoid High CPU Loads : During explicit updates
If you have the permissions, manually cancel the stuck deployment. Once the status moves to "Failed" or "Cancelled," the SUP0108 block should lift.
The Azure Arc agent processes extension deployments sequentially. If an automated process (like Azure Policy remediation) attempts to install an extension while a manual deployment is running, the agent correctly rejects the second request.
The Dell iDRAC SUP0108 error indicates a "deployment or update operation is already in progress," often triggered by a hung process, stuck RAM drive, or a false positive during firmware updates. Resolution typically involves resetting the iDRAC, clearing the job queue, or performing a cold boot to clear stuck, temporary data. For detailed troubleshooting, see the official Dell Knowledge Base . iDRAC10 Version 1.20.25.00 Release Notes Some updates, particularly for iDRAC 9, can take
The most common cause is a stuck job in the queue. Clearing this allows the Lifecycle Controller to accept new instructions. Log in to the iDRAC web console. Navigate to Maintenance > Job Queue . Click Select All (or check the box for all jobs). Click Delete or Delete All . Wait a few minutes and try your deployment/update again.
: Certain versions of iDRAC9 and iDRAC10 throw this error when attempting to mount drivers even when absolutely no background tasks are running. Step-by-Step Fixes for Error SUP0108 1. Reset the iDRAC (Warm Reboot)
This error typically occurs when the system detects a "lockfile" or active process that hasn't cleared, even if no operation appears active in the UI. Stuck RAM Drive