| Previous | Next |
| STATUS_HV_PENDING_PAGE_REQUESTS | STATUS_SPACES_PAUSE |
STATUS_SPACES_REPAIRED
Repair completion is not the root-cause report for STATUS_SPACES_REPAIRED
This informational status says that a Storage Spaces repair task reached its successful completion point. It does not identify why repair became necessary, whether a failed member was replaced, or whether every object in the storage pool is healthy now. Repair work can restore resiliency after a degraded member or allocation, but it does not turn unreliable hardware into healthy hardware.
What to verify before closing the incident
- Check the
HealthStatusandOperationalStatusof the pool, the affected virtual disk, and its physical disks. - Check
Get-StorageJobfor any remaining regeneration or repair work instead of assuming that one completed job represents the whole pool. - Record the original disk, enclosure, controller, or connectivity condition that triggered repair; replace or isolate an unhealthy member rather than repeatedly rebuilding onto it.
References
Native status interpretation
STATUS_SPACES_REPAIRED is 0x00E70000, an NTSTATUS success value. AllStat describes it as “The repair was successful.”. The first useful question is which native API, IRP, protocol operation, or subsystem in the kernel, native API, or subsystem that returned the status produced that status.
Debugging sequence
- Preserve this result before RtlNtStatusToDosError, HRESULT conversion, exception translation, or provider-specific remapping removes information.
- compare the exact spaces / repaired operation on a working system and record differences in object lifetime, access token, device state, negotiated protocol, and policy.
- For kernel I/O, keep the device stack, IRP major/minor function, request parameters, completion routine, and the first component that completed the request with this result.
Recovery considerations
A retry is appropriate only after the owner of this result has changed the state described by “The repair was successful.”, or when its contract explicitly marks the status as transient. If the value reports corruption, invalid format, access policy, or a lifecycle mismatch, preserve evidence and correct that cause before repeating the request.
Native status interpretation
This result is 0x00E70000, an NTSTATUS success value. AllStat describes it as “The repair was successful.”.
Looking for a different code? Search another status or error code.