S2D: disks don’t show up in the disk manager

When you configure S2D cluster with autoconfig=yes or using VMM, S2D creates storage pool with all disks of which parameter CanPool is True. For example, if you have 2 SSDs and 4 HDDs targeted to S2D and other 2 HDDs for system partitions (you plan to use mirrored volumes, for example), they all will be added to S2D pool (except of a system disk, of course, as it’s cannot be pooled).  All physical disks that are part of any pool,including Primordial pool, will not be shown in the disk manager (diskmgmt.msc) if they had been claimed by S2D subsystem. In that case, to make your disk available in the diskmgmt, you need to remove it from pool, rebuild virtual disks (if existed) and unclaim it from S2D. Use the steps below to get your disk back from pool:

#Get all available disks 

Get-PhysicalDisk|ft FriendlyName,SerialNumber,CanPool

#Variable for the disk that you want to remove from $pool

$disk=Get-PhysicalDisk -SerialNumber disk_serial_number
$pool=Get-StoragePool S2D*

#Set disk usage to Retired

$disk|Set-PhysicalDisk -Usage Retired

#Repair Virtual Volumes in the pool

Get-VirtualDisk | ft -AutoSize
Repair-VirtualDisk -FriendlyName "vdisk_name"

#Remove the disk from the pool.
#The disk will be added to the Primordial pool
#...but not be shown in the diskmgmt

Remove-PhysicalDisks $disk -StoragePool $pool

#Tell S2D cluster to not use the removed disk for pool purposes
#....make disk available in the diskmgmt

Set-ClusterS2DDisk -CanBeClaimed 0 -PhysicalDiskIds disk_id

#Optimize pool
Get-StoragePool $pool|Optimize-StoragePool

s2d disk claim

If you removed disk improperly from the pool, you might have the following status for the disk:

{Removing from Pool, Unrecognized Metadata)

Try to reset the physical disk and then disk will be shown in the diskmgmt as well.

Get-PhysicalDisk | ? OperationalStatus -eq "Unrecognized Metadata"|Reset-PhysicalDisk

s2d disk claim_2

P.S. if you add a new server to the S2D, its drives will be automatically added to the pool by default. You can change this behavior by setting AutoPool setting to False.

Get-StorageSubSystem Clu* | Set-StorageHealthSetting -Name “System.Storage.PhysicalDisk.AutoPool.Enabled” -Value False

s2d disk claim_3

FIX: VMM won’t start, error 1067

I’ve recently configured VMM in the restricted environment where you always need to ask IT staff to delegate rights for service and install accounts in order to make SQL Server and VMM Server working. The requirements for DKM container or SPN registration are described at many sites, blogs including official Microsoft docs, but I  faced with a new problem just after VMM installation.

I couldn’t start VMM service. Checked SQL Server services and communication from VMM Server, VMM database properties  and etc…and did not find any unusual or wrong in my configuration. I went then to the VMMLogs and reviewed the report generated after the VMM service start attempt and found interesting strings:

System.AggregateException: One or more errors occurred.—> Microsoft.VirtualManager.DB.CarmineSqlException: The SQL Server service account does not have permission to access Active Directory Domain Services (AD DS).
Ensure that the SQL Server service is running under a domain account or a computer account that has permission to access AD DS.

The following steps helped me to resolve the error:

  • Open Active Directory Users and Computers
  • Expand Builtin container and locate Windows Authorization Access Group
  • Add SQL Service account to the Windows Authorization Access Group
  • Start SCVMMService

or use PowerShell (RSAT-AD-Tools are required):

Add-ADGroupMember sqlsvc -Members “Windows Authorization Access”

Start-Service scvmmservice