| Previous | Next |
| STATUS_LOG_FULL_HANDLER_IN_PROGRESS | STATUS_LOG_CONTAINER_WRITE_FAILED |
STATUS_LOG_CONTAINER_READ_FAILED
STATUS_LOG_CONTAINER_READ_FAILED means the CLFS service encountered an error while reading one of the containers that belongs to the physical log. The code identifies the failed layer as container I/O, but the underlying reason still requires storage and filesystem evidence.
Do not collapse it into STATUS_LOG_METADATA_CORRUPT or STATUS_LOG_SECTOR_INVALID. Those statuses classify validated log structures; this result says that the required container could not be read successfully in the current operation.
What to inspect
- Preserve the base log and all associated containers together, then record the container path, LSN or offset, and underlying I/O status if available.
- Enumerate containers through CLFS to distinguish a missing, inaccessible, or failing member from an unrelated file.
- Investigate storage, path, sharing, and permission evidence before any recovery step that writes to the log.
References
- Microsoft: physical CLFS log and container creation
- Microsoft: ScanLogContainers, GetLogContainerName, AddLogContainer, and RemoveLogContainer
- Microsoft Open Specifications: NTSTATUS values
- Wine: independent NTSTATUS constant definitions
Looking for a different code? Search another status or error code.