# Read storage-pool and virtual-disk health states separately

> What does a Storage Spaces warning mean at the pool versus virtual-disk layer?

- Canonical URL: https://update.dsesecurity.com/updates/dse-20260908-204-read-storage-pool-and-virtual-disk-health-states-separately/
- Publisher: Detection Systems & Engineering (DSE Security)
- Author: DSE Security Editorial Team
- Published: 2026-09-08T18:13:47+00:00
- Modified: 2026-09-08T18:29:33+00:00
- Last reviewed by DSE: 2026-09-08
- Resource type: Guide
- DSE priority: Information
- Topics: Business Continuity, IT
- Reading time: 2 minutes

## What you need to know

What does a Storage Spaces warning mean at the pool versus virtual-disk layer?

## Potentially affected

Administrators investigating health and operational states in Storage Spaces or Storage Spaces Direct.

## DSE recommendation

Create an incident record that traces the affected volume to its virtual disk, pool, and underlying drives.

## Article

## Source facts

Microsoft says a pool warning means the pool remains accessible but has missing or failed drives and may have reduced resilience. An unknown or unhealthy pool is read-only until it returns to an acceptable health state. A virtual-disk warning has a different meaning: some data copies are unavailable, but at least one copy can still be read. [Microsoft Learn](https://learn.microsoft.com/en-us/windows-server/storage/storage-spaces/storage-spaces-states).

## Applicability

Identify whether the reported state belongs to a physical drive, storage pool, virtual disk, or volume. Record health and operational status together. Do not translate the word warning into a single action without identifying the object and its documented meaning.

## DSE recommendation

Create an incident record that traces the affected volume to its virtual disk, pool, and underlying drives. Preserve the initial state and any missing-device identifiers before attempting repair. Ask the storage owner to assess remaining resilience and the workload impact. Avoid deleting or recreating an object to clear an unexplained read-only condition. Establish which documented recovery action fits the actual object state.

## Verification

Requery the same object identifiers after the approved corrective action and compare health, operational status, and application access with the initial record. Confirm restored resilience separately from basic readability. If the layer-level states disagree or a device remains missing, leave the finding open and escalate with the complete object relationship.

## Official references

[Microsoft Learn: Storage Spaces and Storage Spaces Direct health and operational states](https://learn.microsoft.com/en-us/windows-server/storage/storage-spaces/storage-spaces-states). Source reviewed September 8, 2026.

## Primary reference

- Name: Storage Spaces and Storage Spaces Direct health and operational states
- Authority: Microsoft Learn
- URL: https://learn.microsoft.com/en-us/windows-server/storage/storage-spaces/storage-spaces-states
- Source publication date: Not stated by the source

## Citation and use

Preferred citation: “Read storage-pool and virtual-disk health states separately,” DSE Security, https://update.dsesecurity.com/updates/dse-20260908-204-read-storage-pool-and-virtual-disk-health-states-separately/
Publishing principles: https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/
Usage and citation policy: https://update.dsesecurity.com/usage/
Copyright © 2026 Detection Systems & Engineering. All rights reserved.