Investigate detached Storage Spaces Direct volumes beyond physical-disk health

Source facts

Microsoft documents a Storage Spaces Direct condition in which Get-VirtualDisk reports Detached while Get-PhysicalDisk reports the underlying disks as Healthy. It separately describes virtual disks failing to come online with insufficient redundancy information after unexpected node restarts. The troubleshooting guidance calls for checking drive support, hardware condition, firmware, updates, and the Storage Spaces Direct section of cluster validation. Microsoft documentation.

Applicability

Use this review when virtual-disk availability and physical-disk health appear inconsistent. Identify the affected virtual disk, pool, nodes, and recent restart or power events. Select the source section matching the observed symptom and software version.

DSE recommendation

Preserve both virtual-disk and physical-disk observations before attempting repair. Build a timeline of the preceding node events and gather the corresponding validation and hardware information. Assign the investigation to the storage owner and involve the vendor when hardware support or health is uncertain. Keep an unrelated healthy physical-disk result from closing a virtual-disk availability incident.

Verification

After an approved corrective action, inspect the virtual disk’s operational state and verify the intended workload access. Compare the result with the original symptom and retained event timeline. Record redundancy and hardware findings separately. Escalate unresolved disagreement between layers instead of repeatedly changing storage settings without an identified cause.

Official references

Microsoft Learn: Storage Spaces Direct troubleshooting. Source reviewed September 8, 2026.