| Previous | Next |
| ERROR_CORRUPT_LOG_CORRUPTED | ERROR_CORRUPT_LOG_DELETED_FULL |
ERROR_CORRUPT_LOG_UNAVAILABLE
the volume corruption log cannot currently be accessed.
ERROR_CORRUPT_LOG_UNAVAILABLE indicates this condition: The log may exist but is unavailable because the volume state, file-system operation, lock, dismount, repair phase, or internal error prevents access. The result is about availability of the tracking mechanism, not a definitive count of corruptions.
Where the result appears
- health queries during mount, dismount, scan, or repair transitions.
- storage agents racing file-system maintenance.
- clustered volumes moving between owners.
- file-system control operations that require the corruption log.
What to collect
- volume lifecycle state and ownership at the time of the request.
- active scan, scrub, repair, snapshot, or dismount operations.
- the original file-system status preceding this Win32 translation.
- whether the same query succeeds after the volume becomes stable.
Handling and recovery
Wait for the current volume transition or maintenance operation to finish, then query again. If unavailability persists in a stable state, collect file-system events and perform a controlled scan instead of assuming the volume is healthy.
Common misinterpretation
“Unavailable” is not the same as “empty.” Absence of readable records does not prove absence of corruption.
References
Looking for a different code? Search another status or error code.