| Previous | Next |
| STATUS_BIZRULES_NOT_ENABLED | STATUS_IMAGE_AT_DIFFERENT_BASE |
STATUS_FT_READ_FROM_COPY
A specific redundant copy produced valid data
STATUS_FT_READ_FROM_COPY reports success for a read directed at a specified copy of redundant data. In a fault-tolerant volume, copies exist so data can remain available after a disk or member failure. A successful read from one copy is therefore useful evidence about that copy, but it does not establish that every redundant member is healthy or synchronized.
This status is particularly informative when paired with STATUS_NOT_READ_FROM_COPY for another copy. Together, the results can show that one member is readable while a specific alternative is not. Preserve copy identity and request order so later recovery code can distinguish the known-readable source from the member that failed.
Do not infer which physical disk is “primary” solely from the NTSTATUS name. Map the copy identifier through the volume-management layer and inspect the actual mirror or fault-tolerant set. Before repair or resynchronization, verify which copy contains the expected current data.
What to inspect
- The logical copy identifier and its physical or virtual volume member mapping.
- Results of reads from the other redundant copies for the same data range.
- Synchronization, rebuild, or member-transition events that can explain why copies differ in availability.
References
- Microsoft Open Specifications: VDS glossary
- Microsoft Open Specifications: Disk Management Remote Protocol glossary
- Microsoft: Basic and Dynamic Disks
- Microsoft Open Specifications: NTSTATUS values
Looking for a different code? Search another status or error code.