4

I'm trying to run a Windows Server 2019 Storage Spaces Direct (S2D) cluster with 4 SSDs and 8 spindles per cluster node. There were 2 additional SSDs (1 of which is used for OS, the other is unused at this moment). When setting up the S2D cluster it grabbed all available disk as expected. I went to remove one of the SSDs from the pool and everything seemed to work, however when I ran Get-Disk I could not find the disk I removed from the S2D pool. Below are my steps.

  1. Disable auto-pooling

Get-StorageSubSystem Cluster* | Set-StorageHealthSetting -Name "System.Storage.PhysicalDisk.AutoPool.Enabled" -Value False

  1. Retire the disks

Get-PhysicalDisk | ? Model -like "250" | ? DeviceID -ne 0 | Set-PhysicalDisk -Usage Retired

  1. Repair the virtual disks (this is a new cluster so there is only the performance metrics on it)

Get-VirtualDisk | Repair-VirtualDisk -Verbose

  1. Check to make sure the job is complete

Get-StorageJob

  1. Remove the physical disks

Get-StoragePool S2D* | Remove-PhysicalDisk -PhysicalDisks (Get-PhysicalDisk | ? Model -like "250" | ? DeviceID -ne 0)

  1. Verify the disks are removed from the pool

Get-StoragePool S2D* | Get-PhysicalDisk | ? Model -like "250" | ? DeviceID -ne 0

  1. The disks are not in the S2D pool now, so we should be able to run Get-Disk and see them right?

Get-Disk

My results show the OS drive and the S2D volume for the ClusterPerformanceHistory.

OS Drive and ClusterPerformanceHistory Drives

Any help would be appreciated!

BaronSamedi1958
  • 13,676
  • 1
  • 21
  • 53
Stophr
  • 49
  • 1
  • 4

1 Answers1

1

Here’s the single step left to do:

Set-ClusterStorageSpacesDirectDisk -PhysicalDisk $disk -CanBeClaimed:$false
i3laze
  • 11
  • 1