| Previous | Next |
| STATUS_RM_ALREADY_STARTED | STATUS_VIDEO_DRIVER_DEBUG_REPORT_REQUEST |
STATUS_LOG_NO_RESTART
STATUS_LOG_NO_RESTART is about a CLFS restart area, not about whether the physical log file or its containers exist. A restart area is application-owned recovery information written through WriteLogRestartArea; CLFS can return the last successfully written one to a client that needs to resume its own state machine.
A newly created stream can legitimately have no restart area. The same result can also appear when a caller assumes that every stream carries recovery state, or when the expected checkpoint was never made durable. It should not be treated as proof that the entire log is corrupt.
What to inspect
- Identify the stream and the recovery path that called
ReadLogRestartArea, including whether a restart area is required by that client design. - Compare the last successful
WriteLogRestartAreaand flush activity with the failure; a normal record append is not automatically a replacement checkpoint. - Use
ValidateLogand complete log evidence only when a missing checkpoint is unexpected; do not manufacture a restart area from unrelated records.
References
- Microsoft: WriteLogRestartArea, ReadLogRestartArea, and ValidateLog
- Microsoft: CLFS stable-storage and recovery model
- Microsoft Open Specifications: NTSTATUS values
- Wine: independent NTSTATUS constant definitions
Looking for a different code? Search another status or error code.