03-17-2017 01:22 PM
03-17-2017 01:22 PM
I am trying to setup a s2d cluster within a virtual hyper-v hyper-converged setup with two vms, but when attempting to enable-clusters2d it gets hung up at 27% with "Waiting until SBL disks are surfaced"
06-21-2017 04:28 PM
Dell? Firmware. Make sure your firmware is up to date.
What is the East-West fabric (between nodes)?
06-21-2017 04:33 PM
06-29-2017 10:07 AM
My solution to this when I worked on it was to disable-cluster2d, then I re-created the vhdx files, and enable-cluster2d again.
07-01-2017 08:32 AM
See this blog which outlines the process for creating a guest cluster with S2D:
What hypervisor are you running the VMs on? Hyper-V? VMware? Azure? AWS?
08-26-2018 05:14 PM
I am having the same issue.... I have tried it several times.... each time with new VM Builds
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
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
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
09-06-2018 11:38 AM
@Doug Swanson Did you get this resolved?
How are the VHDX files being exposed to the S2D VM Nodes?
09-06-2018 01:46 PM
When you recreated the VHDX files,
1. Did you create them all individually? Or, did you create one and copy it to all the others? Or some combination?
2. Are these fixed or dynamically expanding VHDX disks?
3. Are you using Windows Server 2016 or 2019? In Windows Server 2019, there is an additional .MHT file for enabling S2D that may give you some hints as to the issue.
4. Did all the S2D tests in Validation pass?
02-15-2019 01:58 PMSolution