storage spaces direct - virtual disk repair error

Evgeniy Bit 1 Reputation point
2021-02-19T07:03:57.977+00:00

Hello! We have s2d cluster with 4 nodes. After reboot one node - some off virtual disks was degraded operational and health status.

69989-image.png

When we try start repair virtual disk manual - received error
69849-image.png
And see suspend storage-jobs
69945-image.png

But all PhysicalDisks in storage pool is ok
69879-image.png
I think that this error is due to the fact that the free space on the storage pool is less than 20%, since restarting the node 2 weeks ago, when the free space on the storage pool was more than 20%, there was no such error
69858-image.png

Please tell me how you can solve the problem without adding physical disks or removing virtual disks

Windows for business | Windows Server | Storage high availability | Other
0 comments No comments
{count} votes

3 answers

Sort by: Most helpful
  1. Xiaowei He 9,936 Reputation points
    2021-02-22T08:12:07.657+00:00

    Hi,

    restarting the node 2 weeks ago, when the free space on the storage pool was more than 20%

    Just curious about why restart node 2 makes the free space on the storage pool more than 20%? Do you mean restarting freed up some space?

    As far as I'm concerned, firstly, we need to check if the error is due to the 20% free space, please check when the issue occurs, does the S2D meet the Fault tolerance:

    https://learn.microsoft.com/en-us/windows-server/storage/storage-spaces/storage-spaces-fault-tolerance

    If the issue is really due to that we need to have 20% free space while the S2D is running out of space, I'm afraid to say if we don't have more slots, we are unable to add space to the space pool.

    Thanks for your time!
    Best Regards,
    Anne

    -----------------------------

    If the Answer is helpful, please click "Accept Answer" and upvote it.

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments No comments

  2. Evgeniy Bit 1 Reputation point
    2021-02-24T14:42:30.267+00:00

    Just curious about why restart node 2 makes the free space on the storage pool more than 20%? Do you mean restarting freed up some space?

    No, I mean that 2 weeks ago there was more than 20% free space in the storage pool, and when I rebooted node, I did not have such problems. In any case, the
    version about 20% free space was wrong. New information:
    At last week i delete one of virtual disk and after run command Get-StoragePool S2D | Optimize-StoragePool, virtual disks with warning health status was repairs.

    But wow we have more 35% free space in storage pool but i have a same problems after rebooted another node.

    71623-image.png

    71632-image.png

    71633-image.png

    71613-image.png

    All nodes up
    71614-image.png
    All disks ok and healthy
    71662-image.png

    We don't understand what's going on, please help us

    All nodes have the same disks configuration
    2 nvme and 22 hdd

    0 comments No comments

  3. Evgeniy Bit 1 Reputation point
    2021-02-24T15:47:38.54+00:00

    Also i find errors 300, 301 on node which own storage pool :
    300
    Physical disk {e22ac6a7-03b8-01d5-c914-9d87c548c9f6} failed to read the configuration or returned corrupt data for virtual disk {975e1eda-ee6d-49c2-8ed3-d10244b4cbc1}. As a result the in-memory configuration may not be the most recent copy of configuration. Return Code: {Operation Failed}
    The requested operation was unsuccessful.

    301
    All pool disks failed to read the configuration or returned corrupt data for virtual disk {975e1eda-ee6d-49c2-8ed3-d10244b4cbc1}. As a result the virtual disk will not attach. Return Code: {Operation Failed}
    The requested operation was unsuccessful.

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.