When This Error Hits—and It Will
You're running a backup job on a tape library—say an HP LTO-8 autoloader or an IBM TS3100—and suddenly the job fails. The event log shows ERROR_CLEANER_SLOT_SET (0X000010EB). The short description: A cleaner slot is already reserved. This usually happens when the library's firmware or the SCSI miniport driver tries to allocate a dedicated cleaning slot that's already flagged as occupied. I've seen it most often after a firmware upgrade or when a previous cleaning operation didn't complete properly. The library thinks it's still mid-clean, so it won't let you reserve another slot.
Root Cause: The Slot Is Locked, Not Broken
Your tape library has a set of slots for cleaning cartridges. When the library initiates a cleaning cycle, it reserves one of those slots—marks it as in-use. If that cycle gets interrupted (power loss, unexpected eject, a stuck cartridge), the reservation flag stays set. The library won't clear it on its own. So the next time you or your backup software tries to trigger a clean, it sees the slot as already reserved and throws 0X000010EB. It's not a hardware failure—it's a stale flag in the library's memory. Annoying, but fixable.
How to Fix It—Step by Step
- Check the library's front panel or web interface. Most modern autoloaders have an LCD or a web GUI. Look for a "Cleaning" or "Maintenance" menu. You'll often see a status like "Slot 3 reserved" or "Cleaning in progress." If you can cancel the stuck operation from there, do it.
- If no front panel exists, use the vendor's management tool. For an HP/StoreEver library, use the
hpssaclicommand. For IBM, it'sibmtapecmdor the Tape Library Specialist tool. Run alibrary statuscommand to see which slots are reserved. Then issue aclear cleaning slotorreset elementcommand. Example for HP:hpssacli ctrl slot=3 clear - Reboot the library. I know, it's the IT version of "turn it off and on again." But a cold boot clears many transient flags. Power down the library, wait 30 seconds, power it back up. Then check the slot status—it should be free now.
- Update the firmware. If you're running old firmware (say, pre-2023 on an LTO-7 library), there might be a known bug that doesn't release the reservation after a failed clean. Check the vendor's support site for the latest firmware and apply it. I've fixed a dozen of these with a firmware bump alone.
- Delete and recreate the cleaning slot in your backup software. Software like Veritas NetBackup or Veeam often caches slot assignments. Go into the library configuration, remove the cleaning slot mapping, save, then add it back. This forces the software to re-query the library state.
- As a last resort, manually eject the cleaning cartridge. If the library has a slot for a cleaning tape and it's physically stuck, use the library's force-eject procedure (often involves pressing a button on the slot itself for 5 seconds). Remove the cartridge, wait 10 seconds, reinsert it. The library should re-recognize it as available.
If It Still Fails—Check These
You've done all the steps above, but the error persists. Here's what to look at next:
- The SCSI miniport driver on your Windows server. Open Device Manager, find your tape library under Storage controllers, update the driver. A mismatched or corrupted driver can report a stale reservation. I've seen this with older LSI adapters.
- The library's element addressing. Some libraries have multiple slots, and the reservation might be on a different element than the one you're checking. Use
tapecmd element list(if using IBM) to dump all element statuses. You might find the flag is on slot 5, not slot 3. - A physical problem with the slot itself. If the cleaning cartridge is damaged or non-compliant (e.g., using a non-certified cleaning tape), the library may refuse to clear the reservation. Swap in a known-good cleaning cartridge from a sealed pack.
- Check for a pending self-test. Some libraries (like Quantum i40) run an internal diagnostic after a power cycle that can reset slot states. Wait 10 minutes after a reboot—the reservation might clear automatically.
If none of this works, you're probably looking at a hardware fault in the library's control board. Contact vendor support and have them run a remote diagnostic. But 90% of the time, a firmware update or a simple reboot does the trick. Don't panic—this error is just a sticky flag, not a disaster.