Fix STATUS_SETMARK_DETECTED (0X80000021) Tape Error

You're running a backup job on a Windows Server 2016 machine, using a tape drive like an HP LTO-6 or a Dell PowerVault. The job gets about 15 minutes in, and then the backup software throws STATUS_SETMARK_DETECTED with the code 0X80000021. The tape stops, the software logs the error, and you're stuck with an incomplete backup.

This error almost always shows up when the backup software tries to write data past a point on the tape where a set mark was placed. A set mark is like a bookmark that tape drives use to separate different backup sets. If the software loses track of where it is—for example, after a power failure or a jam—it might try to write right on top of a set mark. The drive sees that as a conflict and returns 0X80000021 to the operating system.

In plain English: the tape drive is telling Windows, "I found a marker on the tape that shouldn't be here." It's not a hardware failure, not a driver bug. It's a positioning problem. The tape is still good, the drive is still good. You just need to reset the tape position and make sure your backup software knows where it's supposed to write.

What You'll Need

You'll need the tape management software that came with your drive (like HP Library & Tape Tools or Dell OpenManage) or the software you use for backups (like Veeam or Windows Server Backup). Also, make sure you have the tape's barcode or label handy so you can identify the right cartridge.

Step 1: Stop the Backup Job and Unload the Tape

1. Open your backup software's console.
2. Look for the currently running job and cancel it. Wait a few seconds for it to fully stop.
3. In most backup software, you'll see an option to "Eject" or "Unload" the tape. Click that. If you're using a standalone tape drive, you can press the eject button on the front of the drive. If the tape is in a library, use the library management interface to move the tape to an I/O slot.
4. Wait until the tape is completely out of the drive. You'll see the cartridge partially sticking out. After ejecting, the drive's light might blink for a few seconds—that's normal.

After this step, you should have the tape in your hand or in a slot. If the tape doesn't eject, you might need to power cycle the drive. Turn off the server or the tape library, wait 10 seconds, turn it back on. Then try ejecting again.

Step 2: Rewind the Tape to the Beginning

Most backup software has a "Rewind" or "Move to Beginning" option. You can also do it from the tape drive's front panel if it has one. If you're using a library, use the library's management software.

1. Insert the tape back into the drive if you ejected it. Make sure it clicks into place.
2. Open your tape management tool. For Windows, you can use tapeutil from a command prompt (running as administrator) if you're comfortable with command line. Type tapeutil /rewind and press Enter. If that command fails, try tapeutil /rtn which means "rewind and unload"—that rewinds and ejects the tape.
3. Alternatively, in your backup software, look for a media tab, select the tape, and choose "Rewind" or "Position to Start."
4. After rewinding, the tape should make a whirring sound as it spins back to the beginning. When it stops, you're ready.

After rewinding, the drive should show a ready state. If you get any error during rewind, check the drive's health with the vendor's diagnostics tool. But it's rare—the rewind usually works fine.

Step 3: Clear the Set Mark from the Tape's Memory

Sometimes the set mark is stored in the tape's internal memory, not just on the media. You can clear it with a format operation. Be aware: formatting a tape erases all data on it. Only do this if you don't need the data on that tape.

1. In your backup software, locate the tape in the media pool.
2. Right-click the tape and choose "Format" or "Erase." Confirm the action.
3. Wait for the format to complete. It can take a few minutes for a full tape. You'll see a progress bar in the software.
4. Once done, the tape is clean and ready for new data.

If you don't want to format the tape because it has important data, skip this step. But then you'll need to make sure your backup software is set to append to the tape rather than overwrite. Appending past the last set mark is usually safe, but overwriting isn't.

Step 4: Adjust Backup Software Settings

The root cause is often that the backup software is set to "Overwrite" a tape that already has a set mark. Change it to "Append" or "Write to a new tape" if you're okay with that. Here's how to do it in most software:

1. Open the backup job or policy that failed.
2. Look for media options, usually under "Storage" or "Destination."
3. Find the drop-down that says "Overwrite" or "Append." Change it to "Append" if you want to keep existing data, or "Write to a new tape" if you're using a fresh tape.
4. Save the job and try running it again.

If your software has a setting called "Ignore set marks" or something similar, enable it. Some advanced backup tools have that option under the tape driver settings. That's the real fix if you can't format the tape.

Step 5: Update the Tape Driver and Firmware

Older tape drivers on Windows 10 or Server 2016/2019 might misreport set marks. Check the manufacturer's website for the latest driver. For example, HP has the "HP Tape Driver" on their support page, and LTO drives need a firmware update from the vendor.

1. Go to the drive manufacturer's support site.
2. Search for your model, like "HP LTO-6 SAS."
3. Download the latest tape driver and firmware. Read the release notes—if they mention "set mark" or "positioning," that's your fix.
4. Install the driver first, then update the firmware using the vendor's tool (e.g., HP Tape Tools). Firmware updates usually take a few minutes and may require a reboot.

After the update, restart the server to make sure the new driver loads.

If It Still Fails

If you've done all this and the error persists, the tape cartridge might be physically damaged. Try a different tape. If a different tape works, the original tape is bad—recycle it. If the error happens with multiple tapes, the drive might have a firmware bug that the vendor hasn't fixed. Contact support and mention the error code. They might have a specific workaround.

Also, check the system event log. Look for entries from the tape driver with a source like "Tape" or "TapeDrv." The event details may include more info about which operation triggered the error.

And one more thing: if you're using Windows Server Backup, there's a known issue where it fails on tapes with existing set marks. The workaround is to use a different backup tool, like Veeam or Backup Exec, which handles set marks better. It's an opinion, but I've seen it fix this exact error in production.