{
    "api_version": "1",
    "kind": "dse_post",
    "self": "https://update.dsesecurity.com/api/v1/posts/dse-20260908-204-read-storage-pool-and-virtual-disk-health-states-separately/",
    "item": {
        "id": "https://update.dsesecurity.com/updates/dse-20260908-204-read-storage-pool-and-virtual-disk-health-states-separately/",
        "slug": "dse-20260908-204-read-storage-pool-and-virtual-disk-health-states-separately",
        "url": "https://update.dsesecurity.com/updates/dse-20260908-204-read-storage-pool-and-virtual-disk-health-states-separately/",
        "alternate_urls": {
            "markdown": "https://update.dsesecurity.com/updates/dse-20260908-204-read-storage-pool-and-virtual-disk-health-states-separately.md",
            "json": "https://update.dsesecurity.com/api/v1/posts/dse-20260908-204-read-storage-pool-and-virtual-disk-health-states-separately/"
        },
        "title": "Read storage-pool and virtual-disk health states separately",
        "summary": "What does a Storage Spaces warning mean at the pool versus virtual-disk layer?",
        "format": {
            "slug": "guide",
            "name": "Guide"
        },
        "priority": {
            "slug": "info",
            "name": "Information"
        },
        "featured": false,
        "image": {
            "theme": "continuity-recovery",
            "label": "Continuity & recovery",
            "alt": "Paired infrastructure paths converging on a stable recovered service.",
            "card_url": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-card.webp?v=1.8.20",
            "hero_url": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-hero.webp?v=1.8.20",
            "social_url": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-social-v2.jpg?v=1.8.20",
            "width": 2400,
            "height": 1350
        },
        "topics": [
            {
                "slug": "business-continuity",
                "name": "Business Continuity",
                "url": "https://update.dsesecurity.com/topic/business-continuity/"
            },
            {
                "slug": "it",
                "name": "IT",
                "url": "https://update.dsesecurity.com/topic/it/"
            }
        ],
        "author": {
            "name": "DSE Security Editorial Team",
            "url": "https://update.dsesecurity.com/#editorial-team",
            "type": "Organization"
        },
        "publisher": {
            "name": "Detection Systems & Engineering",
            "url": "https://dsesecurity.com/"
        },
        "published_at": "2026-09-08T18:13:47+00:00",
        "modified_at": "2026-09-08T18:29:33+00:00",
        "reviewed_on": "2026-09-08",
        "reading_minutes": 2,
        "word_count": 234,
        "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.",
        "primary_source": {
            "name": "Storage Spaces and Storage Spaces Direct health and operational states",
            "url": "https://learn.microsoft.com/en-us/windows-server/storage/storage-spaces/storage-spaces-states",
            "published_on": null,
            "authority": "Microsoft Learn"
        },
        "publishing_principles": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/",
        "usage_info": "https://update.dsesecurity.com/usage/",
        "copyright_notice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.",
        "content_html": "<h2>Source facts</h2>\n<p>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. <a href=\"https://learn.microsoft.com/en-us/windows-server/storage/storage-spaces/storage-spaces-states\" target=\"_blank\" rel=\"noopener noreferrer\">Microsoft Learn</a>.</p>\n<h2>Applicability</h2>\n<p>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.</p>\n<h2>DSE recommendation</h2>\n<p>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.</p>\n<h2>Verification</h2>\n<p>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.</p>\n<h2>Official references</h2>\n<p><a href=\"https://learn.microsoft.com/en-us/windows-server/storage/storage-spaces/storage-spaces-states\" target=\"_blank\" rel=\"noopener noreferrer\">Microsoft Learn: Storage Spaces and Storage Spaces Direct health and operational states</a>. Source reviewed September 8, 2026.</p>",
        "content_text": "Source facts\nMicrosoft 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.\nApplicability\nIdentify 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.\nDSE recommendation\nCreate 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.\nVerification\nRequery 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.\nOfficial references\nMicrosoft Learn: Storage Spaces and Storage Spaces Direct health and operational states. Source reviewed September 8, 2026.",
        "content_markdown": "## Source facts\n\nMicrosoft 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).\n\n## Applicability\n\nIdentify 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.\n\n## DSE recommendation\n\nCreate 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.\n\n## Verification\n\nRequery 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.\n\n## Official references\n\n[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."
    },
    "json_ld": {
        "@context": "https://schema.org",
        "@graph": [
            {
                "@type": "Organization",
                "@id": "https://dsesecurity.com/#organization",
                "name": "Detection Systems & Engineering",
                "alternateName": "DSE Security",
                "url": "https://dsesecurity.com/",
                "logo": {
                    "@type": "ImageObject",
                    "url": "https://update.dsesecurity.com/assets/dse-logo-20260812.png?v=1.8.20"
                }
            },
            {
                "@type": "Organization",
                "@id": "https://update.dsesecurity.com/#editorial-team",
                "name": "DSE Security Editorial Team",
                "url": "https://update.dsesecurity.com/",
                "parentOrganization": {
                    "@id": "https://dsesecurity.com/#organization"
                }
            },
            {
                "@type": "WebSite",
                "@id": "https://update.dsesecurity.com/#website",
                "name": "DSE Updates",
                "alternateName": "DSE Security Knowledge Hub",
                "url": "https://update.dsesecurity.com/",
                "inLanguage": "en-US",
                "publisher": {
                    "@id": "https://dsesecurity.com/#organization"
                },
                "potentialAction": {
                    "@type": "SearchAction",
                    "target": {
                        "@type": "EntryPoint",
                        "urlTemplate": "https://update.dsesecurity.com/?q={search_term_string}"
                    },
                    "query-input": "required name=search_term_string"
                }
            },
            {
                "@type": "WebPage",
                "@id": "https://update.dsesecurity.com/updates/dse-20260908-204-read-storage-pool-and-virtual-disk-health-states-separately/",
                "url": "https://update.dsesecurity.com/updates/dse-20260908-204-read-storage-pool-and-virtual-disk-health-states-separately/",
                "isPartOf": {
                    "@id": "https://update.dsesecurity.com/#website"
                },
                "lastReviewed": "2026-09-08"
            },
            {
                "@type": "BreadcrumbList",
                "@id": "https://update.dsesecurity.com/updates/dse-20260908-204-read-storage-pool-and-virtual-disk-health-states-separately/#breadcrumbs",
                "itemListElement": [
                    {
                        "@type": "ListItem",
                        "position": 1,
                        "name": "DSE Updates",
                        "item": "https://update.dsesecurity.com/"
                    },
                    {
                        "@type": "ListItem",
                        "position": 2,
                        "name": "Read storage-pool and virtual-disk health states separately",
                        "item": "https://update.dsesecurity.com/updates/dse-20260908-204-read-storage-pool-and-virtual-disk-health-states-separately/"
                    }
                ]
            },
            {
                "@type": [
                    "Article",
                    "TechArticle"
                ],
                "@id": "https://update.dsesecurity.com/updates/dse-20260908-204-read-storage-pool-and-virtual-disk-health-states-separately/#article",
                "identifier": "https://update.dsesecurity.com/updates/dse-20260908-204-read-storage-pool-and-virtual-disk-health-states-separately/",
                "url": "https://update.dsesecurity.com/updates/dse-20260908-204-read-storage-pool-and-virtual-disk-health-states-separately/",
                "headline": "Read storage-pool and virtual-disk health states separately",
                "description": "What does a Storage Spaces warning mean at the pool versus virtual-disk layer?",
                "abstract": "What does a Storage Spaces warning mean at the pool versus virtual-disk layer?",
                "articleBody": "Source facts\nMicrosoft 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.\nApplicability\nIdentify 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.\nDSE recommendation\nCreate 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.\nVerification\nRequery 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.\nOfficial references\nMicrosoft Learn: Storage Spaces and Storage Spaces Direct health and operational states. Source reviewed September 8, 2026.",
                "datePublished": "2026-09-08T18:13:47+00:00",
                "dateModified": "2026-09-08T18:29:33+00:00",
                "mainEntityOfPage": {
                    "@id": "https://update.dsesecurity.com/updates/dse-20260908-204-read-storage-pool-and-virtual-disk-health-states-separately/"
                },
                "inLanguage": "en-US",
                "isAccessibleForFree": true,
                "author": {
                    "@type": "Organization",
                    "name": "DSE Security Editorial Team",
                    "url": "https://update.dsesecurity.com/#editorial-team"
                },
                "publisher": {
                    "@id": "https://dsesecurity.com/#organization"
                },
                "image": {
                    "@type": "ImageObject",
                    "@id": "https://update.dsesecurity.com/updates/dse-20260908-204-read-storage-pool-and-virtual-disk-health-states-separately/#primaryimage",
                    "url": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-social-v2.jpg?v=1.8.20",
                    "contentUrl": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-social-v2.jpg?v=1.8.20",
                    "width": 1200,
                    "height": 630,
                    "caption": "Read storage-pool and virtual-disk health states separately"
                },
                "articleSection": [
                    "Business Continuity",
                    "IT"
                ],
                "keywords": [
                    "Business Continuity",
                    "IT",
                    "Guide",
                    "Information priority"
                ],
                "genre": "Guide",
                "about": [
                    {
                        "@type": "Thing",
                        "name": "Business Continuity",
                        "url": "https://update.dsesecurity.com/topic/business-continuity/"
                    },
                    {
                        "@type": "Thing",
                        "name": "IT",
                        "url": "https://update.dsesecurity.com/topic/it/"
                    }
                ],
                "wordCount": 234,
                "timeRequired": "PT2M",
                "publishingPrinciples": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/",
                "usageInfo": "https://update.dsesecurity.com/usage/",
                "copyrightHolder": {
                    "@id": "https://dsesecurity.com/#organization"
                },
                "copyrightNotice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.",
                "citation": {
                    "@type": "CreativeWork",
                    "name": "Storage Spaces and Storage Spaces Direct health and operational states",
                    "url": "https://learn.microsoft.com/en-us/windows-server/storage/storage-spaces/storage-spaces-states"
                }
            }
        ]
    }
}