| Previous | Next |
| ERROR_SETMARK_DETECTED | ERROR_PARTITION_FAILURE |
ERROR_NO_DATA_DETECTED
no more data is on the tape.
ERROR_NO_DATA_DETECTED means that the tape drive found no additional recorded data at the current or subsequent position. In this case, the decisive context is restore and verification scans, together with media barcode/serial, partition, file and block position, and backup-set identity.
Where the result appears
- restore and verification scans.
- catalog reconstruction from tape.
- reading beyond the last recorded block.
- blank or partially written media.
Typical causes
- the operation reached the end of recorded data.
- the loaded cartridge is blank or not the expected volume.
- the tape was erased, truncated, or incompletely written.
- positioning selected an unused partition or area.
Evidence to collect
- media barcode/serial, partition, file and block position, and backup-set identity.
- whether filemarks or setmarks were encountered first.
- write history, erase operations, and job completion records.
- drive sense information and tape health indicators.
For this condition, begin the investigation with media barcode/serial, partition, file and block position, and backup-set identity. Correlate it with whether filemarks or setmarks were encountered first and check whether the operation reached the end of recorded data. Capture the original this result immediately after the failing call so later cleanup does not replace the thread-local error value.
Handling and recovery
Verify media identity and expected dataset length before concluding that data was lost. In a spanning restore, request the next cataloged volume. For a write job, distinguish normal blank space from an unexpectedly incomplete backup and retain job logs.
Any retry policy for this Win32 error should be tied to evidence that the loaded cartridge is blank or not the expected volume has changed. Before another attempt, verify write history, erase operations, and job completion records. If positioning selected an unused partition or area still applies, stop the retry sequence and preserve the first diagnostic event.
Common misinterpretation
This result does not necessarily indicate a read error. The drive may be functioning correctly and reporting that no recorded blocks remain.
Guidance for developers
When surfacing this result through another layer, retain its Win32 domain, numeric value, and the operation described by catalog reconstruction from tape. A useful telemetry record also includes drive sense information and tape health indicators. For the-related handling, decisions must use the numeric value and documented API contract rather than localized wording.
A focused test should reproduce the condition in which the tape was erased, truncated, or incompletely written, assert this result, and confirm that the program releases resources associated with reading beyond the last recorded block. The recovery test should also verify that media barcode/serial, partition, file and block position, and backup-set identity is refreshed before the operation resumes.
References
Looking for a different code? Search another status or error code.