locked
Storage spaces direct Enable-ClusterStorageSpacesDirect returns with error Failed to start health providers. RRS feed

  • Question

  • 3 identical nodes
    OSdisk raid
    9 disks, Bus Type : SAS

    cluster installed and running.


    PS C:\Users\Administrator> Enable-ClusterStorageSpacesDirect -Verbose
    VERBOSE: 2017/08/14-11:23:09.874 Ensuring that all nodes support S2D
    VERBOSE: 2017/08/14-11:23:09.874 Querying storage information
    VERBOSE: 2017/08/14-11:23:16.998 Sorted disk types present (fast to slow): SSD,HDD. Number of types present: 2
    VERBOSE: 2017/08/14-11:23:16.998 Checking that nodes support the desired cache state
    VERBOSE: 2017/08/14-11:23:17.014 Checking that all disks support the desired cache state
    VERBOSE: 2017/08/14-11:23:19.232 Creating health resource
    VERBOSE: 2017/08/14-11:23:19.498 Starting health providers
    Enable-ClusterStorageSpacesDirect : Failed to start health providers. Run cluster validation, including the S
    torage Spaces Direct tests, to verify the configuration
    At line:1 char:1
    + Enable-ClusterStorageSpacesDirect -Verbose
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : NotSpecified: (MSCluster_StorageSpacesDirect:root/MSCLUSTER/...ageSpacesDirect 
       ) [Enable-ClusterStorageSpacesDirect], CimException
        + FullyQualifiedErrorId : HRESULT 0x800706ef,Enable-ClusterStorageSpacesDirect

    Enable-ClusterStorageSpacesDirect : Failed to run CIM method EnableStorageSpacesDirect on the root/MSCLUSTER/
    MSCluster_StorageSpacesDirect CIM object.  The CIM method returned the following error code: 1775
    At line:1 char:1
    + Enable-ClusterStorageSpacesDirect -Verbose
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : InvalidResult: (MSCluster_StorageSpacesDirect:String) [Enable-ClusterStorageSp 
       acesDirect], CimJobException
        + FullyQualifiedErrorId : CimJob_EnableStorageSpacesDirect_1775,Enable-ClusterStorageSpacesDirect

    Cluster crashes after this.

    Anyone who has any idea.

     

    ENIS


    • Edited by EnisK Monday, August 14, 2017 11:17 AM
    Monday, August 14, 2017 9:35 AM

Answers

  • Hi

    yes the issue is resolved ;)
    It seems that you are not allowed to have any DC on S2D node.


    ENIS

    • Marked as answer by EnisK Wednesday, August 30, 2017 8:53 AM
    Wednesday, August 30, 2017 8:53 AM

All replies

  • Hi ENIS,

    For now, I haven't find more information about such error.

    Could you please checked if all the requirements are met?

    Storage Spaces Direct hardware requirements:

    https://technet.microsoft.com/en-us/windows-server-docs/storage/storage-spaces/storage-spaces-direct-hardware-requirements

    Best Regards,

    Mary


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Tuesday, August 15, 2017 5:10 AM
  • Hi

    We are Fujitsu partner and we got help to choose certified hardware for 3 node S2D solution.
    I have also tripple checked HW requirements before ordering and installing servers.

    We have also involved fujitsu to help us with this strange error but I would appreciate any help that could get me further.

    If you need some more info please let me know.

    Regards
    Enis 


    ENIS

    Tuesday, August 15, 2017 6:22 AM
  • Hi,

    Sorry for late reply. After discussing with Our other engineer, could you please run validation report including S2D and add the screenshot to see if there is any error.

    Best Regards,

    Mary


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Tuesday, August 22, 2017 3:03 AM
  • Hi,

    Any updates?

    Best Regards,

    Mary


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Wednesday, August 30, 2017 7:56 AM
  • Hi

    yes the issue is resolved ;)
    It seems that you are not allowed to have any DC on S2D node.


    ENIS

    • Marked as answer by EnisK Wednesday, August 30, 2017 8:53 AM
    Wednesday, August 30, 2017 8:53 AM