none
Enable-ClusterS2D on TP5 fails with virtual disks "Unsupported Media Type"

    General discussion

  • It seems the Enable-ClusterS2D command in TP5 fails when using hyperv virtual disks with unsupported media type errors (see below).  This make sense as I understand that command now performs more operations for us related to the storage pool, but this particular error should probably get fixed as hyper-v test deployment is valid.  I am unaware of any way to set the media type on a disk prior to it being added to a storage pool, so the only workaround I found was to use the -SkipEligibilityChecks flag when using  Enable-ClusterS2D.  Once created things seem to be working normally.


    PS C:\Windows\system32> Enable-ClusterStorageSpacesDirect
    WARNING: Disk number 1 ({1886c28a-bef0-715a-185c-9dcf443a5ba7}, friendly name 'Msft Virtual Disk') on node S2DNode2 has
     unsupported media type
    WARNING: Disk number 2 ({73ec1f7c-d894-ab6b-31a8-358b42b37bc5}, friendly name 'Msft Virtual Disk') on node S2DNode2 has
     unsupported media type
    WARNING: Disk number 1 ({1886c28a-bef0-715a-185c-9dcf443a5ba7}, friendly name 'Msft Virtual Disk') on node S2DNode1 has
     unsupported media type
    WARNING: Disk number 2 ({73ec1f7c-d894-ab6b-31a8-358b42b37bc5}, friendly name 'Msft Virtual Disk') on node S2DNode1 has
     unsupported media type
    WARNING: Disk number 1 ({1886c28a-bef0-715a-185c-9dcf443a5ba7}, friendly name 'Msft Virtual Disk') on node S2DNode3 has
     unsupported media type
    WARNING: Disk number 2 ({73ec1f7c-d894-ab6b-31a8-358b42b37bc5}, friendly name 'Msft Virtual Disk') on node S2DNode3 has
     unsupported media type
    Enable-ClusterStorageSpacesDirect : Disk eligibility failed
    At line:1 char:1
    + Enable-ClusterStorageSpacesDirect
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : InvalidOperation: (MSCluster_StorageSpacesDirect:root/MSCLUSTER/...ageSpacesDirect) [Ena
       ble-ClusterStorageSpacesDirect], CimException
        + FullyQualifiedErrorId : HRESULT 0x80070032,Enable-ClusterStorageSpacesDirect
    
    PS C:\Windows\system32>


    • Edited by Thildemar Thursday, April 28, 2016 7:14 PM
    Thursday, April 28, 2016 7:14 PM

All replies

  • This is expected/known behavior in TP5 when using virtual machines. We use a combination of the bus type and media type to determine devices to use for caching and the automatic configuration of storage pool and storage tiers. This works in TP5 for physical machines. We are working to make automatic configuration also work for virtual machines in our next milestone.

    You can work around this by turning off automatic configuration and skip eligibility checks when enabling S2D, and then manually create the storage pool and storage tiers afterwards. 

    Below is an example of the steps to do this: 

    #Create cluster and enable S2D
    New-Cluster -Name CJ-CLU -Node node1,node2,node3 -NoStorage
    Enable-ClusterS2D -CacheMode Disabled -AutoConfig:0 -SkipEligibilityChecks

    #Create storage pool and set media type to HDD
    New-StoragePool -StorageSubSystemFriendlyName *Cluster* -FriendlyName S2D -ProvisioningTypeDefault Fixed -PhysicalDisk (Get-PhysicalDisk | ? CanPool -eq $true)

    Get-StorageSubsystem *cluster* | Get-PhysicalDisk | Where MediaType -eq "UnSpecified" | Set-PhysicalDisk -MediaType HDD

    #Create storage tiers
    $pool = Get-StoragePool S2D
    New-StorageTier -StoragePoolUniqueID ($pool).UniqueID -FriendlyName Performance -MediaType HDD -ResiliencySettingName Mirror
    New-StorageTier -StoragePoolUniqueID ($pool).UniqueID -FriendlyName Capacity -MediaType HDD -ResiliencySettingName Parity

    #Create a volume
    New-Volume -StoragePool $pool -FriendlyName Mirror -FileSystem CSVFS_REFS -StorageTiersFriendlyNames Performance, Capacity -StorageTierSizes 2GB, 10GB

    Cheers

    ClausJor [MSFT]

     
    • Edited by clausjor Thursday, April 28, 2016 8:22 PM
    Thursday, April 28, 2016 8:18 PM
  • Thanks Claus,

    This is what I assumed. I just wanted to make sure anyone else hitting that error knew what was going on and your team had a plan for release.

    -Adam

    Thursday, April 28, 2016 8:25 PM
  • We just got the blog on how to deploy Spaces Direct in a VM updated with these steps as well:

    https://blogs.msdn.microsoft.com/clustering/2015/05/27/testing-storage-spaces-direct-using-windows-server-2016-virtual-machines/

    Thanks!
    Elden

    Friday, April 29, 2016 10:35 PM
  • Claus-

    How do we enable the caching in our virtual machine testing? In the example above all the disks are MediaType HDD. Do we just do what we previously did in CTP4, Set-PhysicalDisk -MediaType SSD and then Set-PhysicalDisk -Usage Journal? Or do we need to set a CacheMode on the S2DCluster?

    -Scott

    Thursday, May 5, 2016 7:11 PM
  • It is not currently possible to configure S2D with caching devices in a virtual deployment.

    Clausjor [MSFT]

    Friday, May 6, 2016 8:12 PM

  • #Create storage tiers
    $pool = Get-StoragePool S2D
    New-StorageTier -StoragePoolUniqueID ($pool).UniqueID -FriendlyName Performance -MediaType HDD -ResiliencySettingName Mirror
    New-StorageTier -StoragePoolUniqueID ($pool).UniqueID -FriendlyName Capacity -MediaType HDD -ResiliencySettingName Parity

     
    Hi Claus, thanks for clearing this up. Just a simple Question: Why do you refer the Performance tier as Mirror and Capacity as Parity. Is Mirror faster than Parity?
    Friday, May 20, 2016 9:41 AM
  • Hi Claus, thanks for clearing this up. Just a simple Question: Why do you refer the Performance tier as Mirror and Capacity as Parity. Is Mirror faster than Parity?

    Yes, the performance tier is mirror (which is faster)... and the capacity tier is parity (which gives better size efficiency)

    Thanks!
    Elden

    Monday, May 23, 2016 4:03 PM