Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Wednesday, August 17, 2016 10:58 PM
Hi Everyone,
I have touched on this (or a very similar) issue in a couple of past posts, but want to get an up-to-date post with all of the info in hopes one of the storage team will chime in. (See previous posts : Here and Here)
I have a 3 node cluster setup and validated for Storage Spaces Direct. Each node has two 1TB SSDs and two 4TB HDDs (total 6 of each) all of which are cleaned of partitions and data (running on Dell HBA330s). All nodes have the required networking in places, are joined in a cluster and are running Server 2016 TP5 with the latest updates. Running cluster validation for Storage Spaces direct comes back with only the warning about 3 node cluster vs 4 (I only want mirrors, so 3 should work).
The problem is no matter what I do I cannot seem to get a proper virtual disk to create. I am trying to create a tiered disk with the SSD space as a hot tier and HDD space as a cold tier, each in a mirror. If I try this from Powershell I get "The storage pool does not have sufficient eligible resources for the creation of the specified virtual disk". From the GUI in failover cluster manager I can get to the Size screen, but the free space readings are always under a few GB and change each time I run the GUI.
Here is what I get on a fresh manual setup via PS:
PS C:\> Enable-ClusterStorageSpacesDirect -Autoconfig $false
Confirm
Are you sure you want to perform this action?
Performing operation 'Enable Cluster Storage Spaces Direct' on Target 'IGA-S2D'.
[Y] Yes [A] Yes to All [N] No [L] No to All [S] Suspend [?] Help (default is "Y"): y
PS C:\> Get-StorageSubSystem
FriendlyName HealthStatus OperationalStatus
Windows Storage on IGA-S2D1 Healthy OK
Clustered Windows Storage on IGA-S2D Healthy OK
PS C:\> New-StoragePool -StorageSubSystemFriendlyName "Clustered Windows Storage on IGA-S2D" -FriendlyName S2D -Provisio
ningTypeDefault Fixed -PhysicalDisk (Get-PhysicalDisk | ? CanPool -eq $true)
FriendlyName OperationalStatus HealthStatus IsPrimordial IsReadOnly
S2D OK Healthy False False
PS C:\> $pool = Get-StoragePool S2D
PS C:\> $pool | Get-PhysicalDisk | FT FriendlyName,OperationalStatus,HealthStatus,Usage,Size
FriendlyName OperationalStatus HealthStatus Usage Size
ATA Samsung SSD 850 OK Healthy Auto-Select 1024081264640
ATA Samsung SSD 850 OK Healthy Auto-Select 1024081264640
ATA WDC WD4002FYYZ-0 OK Healthy Auto-Select 4000762036224
ATA WDC WD4002FYYZ-0 OK Healthy Auto-Select 4000762036224
ATA Samsung SSD 850 OK Healthy Auto-Select 1024081264640
ATA WDC WD4002FYYZ-0 OK Healthy Auto-Select 4000762036224
ATA WDC WD4002FYYZ-0 OK Healthy Auto-Select 4000762036224
ATA WDC WD4002FYYZ-0 OK Healthy Auto-Select 4000762036224
ATA WDC WD4002FYYZ-0 OK Healthy Auto-Select 4000762036224
ATA Samsung SSD 850 OK Healthy Auto-Select 1024081264640
ATA Samsung SSD 850 OK Healthy Auto-Select 1024081264640
ATA Samsung SSD 850 OK Healthy Auto-Select 1024081264640
PS C:\> New-StorageTier -StoragePoolUniqueID ($pool).UniqueID -FriendlyName SSD -MediaType SSD -ResiliencySettingName Mirror
ObjectId : {1}\\IGA-S2D\root/Microsoft/Windows/Storage/Providers_v2\SPACES_StorageTier.ObjectId="{6116563
c-31ed-4aa3-a54c-90034eddd5d3}:ST:{72ceedad-fa7c-4e66-9b0a-4c83782c8891}{fd5eeb52-486c-4dd9-8f
5c-7b0dfb52dcc8}"
PassThroughClass :
PassThroughIds :
PassThroughNamespace :
PassThroughServer :
UniqueId : {fd5eeb52-486c-4dd9-8f5c-7b0dfb52dcc8}
Description :
FriendlyName : SSD
Interleave : 262144
MediaType : SSD
NumberOfColumns : Auto
NumberOfGroups : 1
PhysicalDiskRedundancy : 1
ResiliencySettingName : Mirror
Size : 0
PSComputerName :
PS C:\> New-StorageTier -StoragePoolUniqueID ($pool).UniqueID -FriendlyName HDD -MediaType HDD -ResiliencySettingName Mirror
ObjectId : {1}\\IGA-S2D\root/Microsoft/Windows/Storage/Providers_v2\SPACES_StorageTier.ObjectId="{6116563
c-31ed-4aa3-a54c-90034eddd5d3}:ST:{72ceedad-fa7c-4e66-9b0a-4c83782c8891}{a9a4faab-0498-4b98-84
d4-950a35778d3c}"
PassThroughClass :
PassThroughIds :
PassThroughNamespace :
PassThroughServer :
UniqueId : {a9a4faab-0498-4b98-84d4-950a35778d3c}
Description :
FriendlyName : HDD
Interleave : 262144
MediaType : HDD
NumberOfColumns : Auto
NumberOfGroups : 1
PhysicalDiskRedundancy : 1
ResiliencySettingName : Mirror
Size : 0
PSComputerName :
PS C:\> New-Volume -StoragePool $pool -FriendlyName Mirror -FileSystem CSVFS_REFS -StorageTierFriendlyNames SSD,HDD -Sto
rageTierSizes 10GB, 100GB
Invoke-CimMethod : Not Supported
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.
Activity ID: {5daef213-f30c-4064-9531-a19be278f73c}
At C:\windows\system32\windowspowershell\v1.0\Modules\Storage\StorageScripts.psm1:1047 char:27
+ ... $output = Invoke-CimMethod -CimSession $session -InputObject $pool ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidOperation: (StorageWMI:) [Invoke-CimMethod], CimException
+ FullyQualifiedErrorId : StorageWMI 1,Microsoft.Management.Infrastructure.CimCmdlets.InvokeCimMethodCommand
As you can see there should be more than enough disk space for the requested disk. It does not matter what sizes I use the same thing occurs.
If I allow the Enable-ClusterStorageSpacesDirect to auto configure it created a storage pool with my disks. The only difference is it attempts to assign all of the SSDs as Journal disks, which would be a waste. I still cant create any meaningful virtual disk with the auto-created pool, even if I change the SSDs back to auto from journal (tried both ways).
I have also tried all of this from the Failover cluster manager GUI and the Server Manager GUI. Both report odd free space numbers and even if I request a disk inside of those (1GB tiered disk) it will still fail.
I am happy to try any combination of commands anyone things may work or to post more PS/screenshots if they would help.
Could really use @clausjor or team to take a look and see if there is a bug that needs fixed prior to RC or if I am doing something wrong...
All replies (7)
Thursday, August 18, 2016 5:11 PM ✅Answered
Finding a few mote things:
- Sizing displays correctly with disks in manual mode, but then tiers and enclosure awareness will not work.
- Disk creates correctly with expected sizing if I use only half the disks (One SSD and One HDD in each of the three nodes) - This using auto mode and with desired tiers/mirror
These two make me think there is some bug with a 3-Node cluster with each node having two disks. Considering this has a nice even number of disks for mirror (6), I don't see why this should be an issue.
Hoping this will be fixed for release, but would love some acknowledgement or confirmation.
Thursday, August 18, 2016 4:37 AM
Hi Thildemar,
Thanks for your post.
Thanks for keep testing server 2016. I'm sorry again have to say that as Server 2016 is a preview version, some features may not work properly. I still couldn't found the official documents to explain this problem. And since the lad limited, couldn't test for you.
As time cost long, you still have this issue, and you could also submit your idea in the windows server feedback. If it's really a bug, that would be the feedback. And it would also be helpful for those users in similar scenario to discuss it.
https://windowsserver.uservoice.com/forums/295047-general-feedback
Appreciate your support and understanding.
Best Regards,
Mary
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 Subscriber Support, contact [email protected].
Thursday, August 18, 2016 1:58 PM
Mary - I just added a feedback item for this, though that section seems more related to feature requests than actual bug tracking. Afraid it will go unnoticed for some time.
I did find another odd behavior. Running Get-StorageTierSupportedSize gives a different value for min/max size each time it is run:
PS C:\> while(1 -le 10){get-date; Get-StorageTierSupportedSize SSD -ResiliencySettingName Mirror | FT -AutoSize
Thursday, August 18, 2016 7:52:35 AM
SupportedSizes TierSizeMin TierSizeMax TierSizeDivisor
{} 0 0 0
Thursday, August 18, 2016 7:52:35 AM
SupportedSizes TierSizeMin TierSizeMax TierSizeDivisor
{} 805306368 805306368 805306368
Thursday, August 18, 2016 7:52:36 AM
SupportedSizes TierSizeMin TierSizeMax TierSizeDivisor
{} 805306368 5637144576 805306368
Thursday, August 18, 2016 7:52:37 AM
SupportedSizes TierSizeMin TierSizeMax TierSizeDivisor
{} 805306368 7247757312 805306368
Thursday, August 18, 2016 7:52:39 AM
SupportedSizes TierSizeMin TierSizeMax TierSizeDivisor
{} 536870912 98784247808 536870912
Thursday, August 18, 2016 7:52:41 AM
SupportedSizes TierSizeMin TierSizeMax TierSizeDivisor
{} 805306368 4831838208 805306368
Thursday, August 18, 2016 7:52:42 AM
SupportedSizes TierSizeMin TierSizeMax TierSizeDivisor
{} 805306368 5637144576 805306368
Thursday, August 18, 2016 7:52:44 AM
SupportedSizes TierSizeMin TierSizeMax TierSizeDivisor
{} 805306368 805306368 805306368
Thursday, August 18, 2016 7:52:45 AM
SupportedSizes TierSizeMin TierSizeMax TierSizeDivisor
{} 805306368 13690208256 805306368
Thursday, August 18, 2016 7:52:47 AM
SupportedSizes TierSizeMin TierSizeMax TierSizeDivisor
{} 805306368 805306368 805306368
Thursday, August 18, 2016 7:52:48 AM
SupportedSizes TierSizeMin TierSizeMax TierSizeDivisor
{} 805306368 8858370048 805306368
Thursday, August 18, 2016 7:52:50 AM
SupportedSizes TierSizeMin TierSizeMax TierSizeDivisor
{} 805306368 8858370048 805306368
This is looking more and more like a bug to me...
Friday, August 19, 2016 1:19 AM
Hi Thildemar，
Thanks for sharing your findings. I'm sorry that couldn't give more helpful idea for your issue.
You could submit your idea in the windows server feedback. If it's really a bug, that would be the feedback.
And anyway, you test and findings must be very helpful for other users are in similar scenario.
Appreciate your support and understanding.
Best Regards,
Mary
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 Subscriber Support, contact [email protected].
Thursday, December 8, 2016 6:10 PM
Hello All,
I am new to this and having trouble with Storage Spaces Direct on Windows Server 2016.
Attempting to follow: https://argonsys.com/learn-microsoft-cloud/articles/storage-spaces-direct-configuration/
Failover Cluster Manager tells me I have 734gb free space on my S2D Storage Pool and healthy status.
PS C:\Windows\system32> Get-StorageTierSupportedSize
cmdlet Get-StorageTierSupportedSize at command pipeline position 1
Supply values for the following parameters:
FriendlyName[0]: Capacity
FriendlyName[1]:
SupportedSizes TierSizeMin TierSizeMax TierSizeDivisor
{} 1342177280 391915765760 1342177280
PS C:\Windows\system32> New-Volume -StoragePoolFriendlyName S2D* -FriendlyName MultiResilient -FileSystem CSVFS_REFS -StorageTierFriendlyName Capacity -StorageTierSizes 391gb
New-Volume : Not Supported
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.
Activity ID: {2e2df68e-ee0e-419d-b91e-a724f5296574}
At line:1 char:1
- New-Volume -StoragePoolFriendlyName S2D* -FriendlyName MultiResilient ...
-
+ CategoryInfo : InvalidOperation: (:) [New-Volume], CimException
+ FullyQualifiedErrorId : StorageWMI 1,Microsoft.Management.Infrastructure.CimCmdlets.InvokeCimMethodCommand,New-Volume
Any help is appreciated here. Thank you!
Thursday, December 8, 2016 6:21 PM
Just issued a 300gb -storagetiersize command and it worked. I have a 315gb Volume1 on each server now.
I haven't understood how I'm limited to 300gb when my pool is over 700gb. Please help.
Tuesday, February 7, 2017 8:25 AM
It is happens, because automatically all SSD drives become Journal Drives.
Just before apply commandlet New-Volume with SSD drives, try to convert them to Auto mode. It can be done in this manner:
Get-PhysicalDisk | FT FriendlyName, Mediatype, BusType -autosize
Find the Friendly name of your SSD drives, then push them to Auto mode:
Get-PhysicalDisk -FriendlyName "SSDDriveFriendlyName" | Set-PhysicalDisk -Usage "AutoSelect"
After that, creation of Performance Tier with SSD drives will goes without errors.