| Previous | Next |
| STATUS_JOB_NO_CONTAINER | STATUS_REPARSE_POINT_ENCOUNTERED |
STATUS_DEVICE_UNRESPONSIVE
No response is different from busy, absent, or unsupported
STATUS_DEVICE_UNRESPONSIVE describes a communication failure with a target that is expected to answer. T10 includes conditions such as 05h/00h LOGICAL UNIT DOES NOT RESPOND TO SELECTION and several communication-failure states. The precise bus or protocol reason must come from the lower completion data.
Compare this status carefully with neighboring cases. A busy device answers but cannot accept the request; an absent device is not represented by a usable current target; an unresponsive device is addressed but fails to produce the expected response. That distinction determines whether to inspect queue ownership, enumeration, or transport timeouts and link recovery.
Capture the first timeout and path state before resetting the device or controller. Repeated resets can restore service, but they can also erase firmware logs and make every later request fail for the secondary reason “reset in progress.” On multipath storage, test alternate valid paths only after preserving the failing path’s evidence.
What to inspect
- Request timeout, transport completion, controller status, and full sense data if any response was returned.
- Path state and link or fabric events at the time of the first missed response.
- Reset history and whether responsiveness returns temporarily or the same path fails immediately again.
References
- INCITS T10: SCSI ASC/ASCQ assignments
- Microsoft: Interpreting storage sense data
- Microsoft: Multipath I/O troubleshooting guidance
- Microsoft: Windows storage driver architecture
- Microsoft Open Specifications: NTSTATUS values
Looking for a different code? Search another status or error code.