Forum Discussion
enabling s2d cluster in virtual test environment issue
- Feb 15, 2019Sorry this was a while ago, and I no longer am using the test environment. I now have two working production clusters. Late response unfortunately.
See this blog which outlines the process for creating a guest cluster with S2D:
https://blogs.msdn.microsoft.com/clustering/2015/05/27/testing-storage-spaces-direct-using-windows-server-2016-virtual-machines/
What hypervisor are you running the VMs on? Hyper-V? VMware? Azure? AWS?
Thanks!
Elden
- Doug SwansonAug 27, 2018Copper Contributor
I am having the same issue.... I have tried it several times.... each time with new VM Builds
- My Lab environment - Server 2019 DC and HyperV
- HP DL360 G7 288 GB Ram
- Storage Controllers P411e for the 4 2.5" 10K 300GB HDD, P411 for the second MSA60, SAS9200-8e for the first MSA60
- Storage Arrays, 2 MSA60
- I am creating 2 VMs and attach physical drives from the MSA60 using the SAS9200-8e controller
- VM1 2-480GB-SSD, 4 3TB-HDD
- VM1 2-480GB-SSD, 4 3TB-HDD
- I used Get-PhysicalDisk to verify all of the disks are up and there are no partitions
- Once Verified I create the cluster
- New-Cluster -Name MyS2DCluster -Node MyS2D1,MyS2D2 -StaticAddress 192.168.10.13
- Verify the Cluster
- Then run Enable-ClusterStorage Spaces Direct -Verbose
- It runs until 27% and hangs on Waiting until SBL disks are surfaced...
Here is the Verbose
PS C:\Windows\system32> Enable-ClusterStorageSpacesDirect -Verbose
VERBOSE: 2018/08/26-16:25:13.619 Ensuring that all nodes support S2D
VERBOSE: 2018/08/26-16:25:13.650 Querying storage information
VERBOSE: 2018/08/26-16:25:15.578 Sorted disk types present (fast to slow): SSD,HDD. Number of types present: 2
VERBOSE: 2018/08/26-16:25:15.578 Checking that nodes support the desired cache state
VERBOSE: 2018/08/26-16:25:15.578 Checking that all disks support the desired cache state
VERBOSE: 2018/08/26-16:25:26.961 Creating health resource
VERBOSE: 2018/08/26-16:25:32.125 Setting cluster property
VERBOSE: 2018/08/26-16:25:32.125 Setting default fault domain awareness on clustered storage subsystem
VERBOSE: 2018/08/26-16:25:32.344 Waiting until physical disks are claimed
VERBOSE: 2018/08/26-16:25:35.360 Number of claimed disks on node 'MyS2D1': 6/6
VERBOSE: 2018/08/26-16:25:38.422 Number of claimed disks on node 'MyS2D2': 6/6
VERBOSE: 2018/08/26-16:25:38.438 Node 'MyS2D1': Waiting until cache reaches desired state (HDD:'ReadWrite' SSD:'WriteO
nly')
VERBOSE: 2018/08/26-16:25:38.453 SBL disks initialized in cache on node 'MyS2D1': 6 (6 on all nodes)
VERBOSE: 2018/08/26-16:25:38.453 Cache reached desired state on MyS2D1
VERBOSE: 2018/08/26-16:25:39.469 Node 'MyS2D2': Waiting until cache reaches desired state (HDD:'ReadWrite' SSD:'WriteO
nly')
VERBOSE: 2018/08/26-16:25:39.485 SBL disks initialized in cache on node 'MyS2D2': 6 (12 on all nodes)
VERBOSE: 2018/08/26-16:25:39.485 Cache reached desired state on MyS2D2
VERBOSE: 2018/08/26-16:25:40.505 Waiting until SBL disks are surfaced
VERBOSE: 2018/08/26-16:25:43.552 Disks surfaced on node 'MyS2D1': 9/12
VERBOSE: 2018/08/26-16:25:43.599 Disks surfaced on node 'MyS2D2': 9/12
- Yusuf AnisDec 23, 2023Copper Contributor
This still haunts me on a virtual build.
OS Win 2022 - Philip ElderSep 06, 2018MVP