| Previous | Next |
| STATUS_DEVICE_FEATURE_NOT_SUPPORTED | STATUS_INVALID_TOKEN |
STATUS_DEVICE_UNREACHABLE
No usable path reaches the device
The device may still exist in configuration while its active path is down. Examples include a failed fabric route, powered-off downstream bridge, inaccessible virtual back end or storage path that no longer reaches the target. This differs from a protocol rejection because no reliable exchange with the target completed.
Path failover should use class or multipath policy rather than blind request retries. Record which path failed and whether another path reaches the same device identity. A reset of the local adapter will not fix a remote target or disconnected bridge and can disrupt healthy devices sharing that adapter.
What to inspect
- Capture target identity, path or location, parent bus and link state.
- Check alternate paths and whether they identify the same logical device.
- Correlate bridge, adapter, fabric and target events before choosing reset or failover.
References
- Microsoft: Introduction to Plug and Play
- Microsoft: Device objects and device stacks
- Microsoft: Standard device reset interface
- Microsoft Open Specifications: NTSTATUS values
- ReactOS source: storage class PnP and error handling
Looking for a different code? Search another status or error code.