locked
S2D - Unable to create disks/see all pool capacity RRS feed

  • Question

  • Hi Everyone,

    I have a setup as follows:

    3 servers each with 2x 1TB SSD and 2x 4TB HDD
    All of the storage is seen correctly by the OS and is added into the storage spaces direct primordial pool without issue.

    When I go to create an actual storage pool through PS or GUI it creates just fine, but here is where we see the first oddity.  The pool automatically assigns all SSDs as journal disks and shows all but 1GB as used on each drive.  HDDs show normally with only about 1 GB used. When I go to create a virtual disk from the pool the GUI only shows 18GB available for a 2-way mirror. Even more odd is if I recreate the pool that number changes.  Attempting to create the disk from PS results in this lovely error:

    Extended information:
    The storage pool does not have sufficient eligible resources for the creation of the specified virtual disk.
    
    Recommended Actions:
    - Choose a combination of FaultDomainAwareness and NumberOfDataCopies (or PhysicalDiskRedundancy) supported by the
    storage pool.
    - Choose a value for NumberOfColumns that is less than or equal to the number of physical disks in the storage fault
    domain selected for the virtual disk.
    
    PS C:\> Get-StoragePool -FriendlyName S2D | Get-PhysicalDisk | ft Usage,Size,MediaType,AllocatedSize
    
    Usage                Size MediaType AllocatedSize
    -----                ---- --------- -------------
    Journal     1024081264640 SSD        990526832640
    Journal     1024081264640 SSD        990526832640
    Auto-Select 4000762036224 HDD          1342177280
    Auto-Select 4000762036224 HDD          1342177280
    Journal     1024081264640 SSD        990526832640
    Auto-Select 4000762036224 HDD          1342177280
    Auto-Select 4000762036224 HDD          1342177280
    Auto-Select 4000762036224 HDD          1342177280
    Auto-Select 4000762036224 HDD          1342177280
    Journal     1024081264640 SSD        990526832640
    Journal     1024081264640 SSD        990526832640
    Journal     1024081264640 SSD        990526832640


    To me I would like to create a tiered mirror space with a 3-column mirror of SSD as fast tier and a 3 column mirror of HDD as the capacity tier.  I am still unclear why i would want journal disks at all if I have enough SSD capacity as part of the virtual disks.

    Can anyone help with what might be missing here?  Happy to post any outputs you may need to help...

    Friday, July 1, 2016 9:24 PM

All replies

  • Hi Thildemar,

    As I could not find any official document about the issue, I would suggest you upgrade the OS to the latest TP5 version.

    Anyway, as Server 2016 is a preview version, some features may not work properly.

    Best Regards,

    Leo


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

    Monday, July 4, 2016 6:40 AM
  • Thanks for the reply Leo.

    All servers are running TP5 with the latest updates.  S2D seems to be something that is working for others in this build and I assume this is a pretty straight forward use case.

    Perhaps one of the storage team or another expert might chime in with ideas?

    Thanks!

    Adam

    Tuesday, July 5, 2016 1:49 PM