Environment:
Windows 2016 FCI cluster with S2D running SQL Server cluster on 2 VMs in Azure.
New vhd disk has been added to a single VM in the cluster with intention to use it as local. Because 'AutoPool' is enabled, it grabbed the disk and marked its Usage property as 'Auto-Select'.
Question: how do I change that single disk to Manual-Select so that I could create local volume from it?
Running: Set-PhysicalDisk -UniqueId mydiskId -Usage ManualSelect
errors out with non-descriptive message.
Here's the output of physical disks with the one I'd like to remove highlighted in yellow, storage pools and storage settings:
S2D
Just came across this link https://docs.microsoft.com/en-us/powershell/module/storage/set-physicaldisk?view=winserver2012r2-ps that states "When using the Storage Spaces subsystem, Set-PhysicalDisk only works on physical disks that have been added to a storage pool"
This is not my case as the disk I'd like to remove is not part of any pool.
Is there any other command to remove my disk from auto pooling without actually disabling AutoPool setting, as per @CosmosDarvin answer in Is there any way to prevent Storage Spaces Direct from automatically adding disks? ?
Also, what are the repercussions if I set AutoPool to false? This is live cluster. BTW, I'm not planning on adding more vhd disks to pools frequently (maybe once a year) so disabling AutoPooling would be ok with me but I'd like to understand if there are any other effect this change may cause.
Best Answer
You can easily do what you want, check this link out:
https://docs.microsoft.com/en-us/powershell/module/storage/get-storagesubsystem
Get-StorageSubSystem Cluster* | Set-StorageHealthSetting -Name "System.Storage.PhysicalDisk.AutoPool.Enabled" -Value False
As a side effect: I'd check AlwaysOn Availability Groups (AGs) for SQL Server, rather than messing with FCI + super-slow S2D in Azure.