Cómo solucionar problemas de instalación y detección de discos de Storage Spaces Direct (S2D)
A veces, al configurar Storage Spaces Direct, las cosas pueden ponerse un poco raras. Por ejemplo, los discos no se reconocen correctamente o el clúster se niega a habilitarse. O quizás hayas añadido unidades, pero simplemente no aparecen en el pool de almacenamiento, ni siquiera fuera del horario laboral. Es frustrante, y Windows puede complicarlo aún más con sus controladores RAID, peculiaridades del firmware o tipos de unidades no compatibles. Pero con un poco de paciencia y los ajustes adecuados, normalmente puedes conseguir que todo funcione sin problemas. Esta guía te ayudará a resolver algunos problemas comunes: discos que no se muestran, errores al habilitar S2D o discos con tipos de bus no compatibles.¿El objetivo? Tener un clúster funcional con un pool de almacenamiento en buen estado para que finalmente puedas conseguir que Storage Spaces Direct funcione.
Cómo reparar Storage Spaces Direct en Windows Server
Solución 1: Asegúrese de que los discos se detecten correctamente para la agrupación
Si los discos no se muestran como «CanPool» o no están disponibles para S2D, es posible que Windows los esté viendo como RAID o no compatibles. Normalmente, esto se debe al tipo de bus del disco o a que el controlador no reconoce el almacenamiento correctamente. Por qué es útil: Debido a que Windows consulta los discos con Get-PhysicalDisk, y para S2D, los discos deben estar en un modo *compatible* (como SAS, SATA, NVMe).Si se muestran como RAID o tienen un BusType incorrecto, S2D no los usará. Cuándo se aplica: Si sus discos no se muestran en PowerShell con CanPool $True, o recibe errores como «no hay discos con tipos de bus compatibles», entonces esta es su primera parada. Qué esperar: Los discos que anteriormente estaban ocultos o mal clasificados deberían aparecer como disponibles para agrupar. A veces, se necesita un ajuste de firmware o una actualización del controlador.Esto es lo que debe hacer: – Abra PowerShell como administrador y ejecute: powershell Get-PhysicalDisk | Sort-Object BusType Observe la columna BusType. Si indica RAID o algo no compatible (como Desconocido), Windows no está conforme con el modo actual del disco.- Para discos con RAID, es posible que pueda cambiar el tipo de bus a SAS o SATA mediante una modificación del registro (esto varía según el hardware).Es un poco técnico, pero pruebe esto: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\arcsas\Parameters y configúrelo BusTypeen0x0b (which is 11, for SATA).But be warned: making registry changes on RAID controllers can be risky, and sometimes you need to update drivers or firmware instead.- Also, update your controller drivers and firmware. For HPE, Dell, or Lenovo servers, grabbing the latest support packs often fixes detection issues.- Once you’ve got disks showing the correct bus type, rerun: powershell Get-PhysicalDisk | Where-Object { $_. CanPool -eq $true } If disks are now poolable, good — you’re ready to go.
On some setups, Windows might still see disks as RAID, but you can sometimes switch the mode in the server’s BIOS/UEFI or storage controller settings. Because of course, Windows has to make it harder than necessary.
Fix 2: Handling Unsupported Driver or Firmware Issues
If disks aren’t detected properly or are seen as unsupported, updating the controller drivers or firmware can fix a lot of headaches. Why it helps: Because outdated drivers or firmware can present disks as RAID or unsupported types, stopping S2D from working. When it applies: If Get-PhysicalDisk shows disks with “Unknown” BusType or other odd statuses, consider driver/fw updates as the fix. What to expect: Disks should show their true type, and get recognized as suitable for pooling.Here’s what to do: - Visit your hardware manufacturer’s support site and download the latest HBA or RAID controller firmware.- Install the latest driver package for your storage controller.- After firmware updates, reboot and rerun: powershell Get-PhysicalDisk | Sort-Object BusType - Check that the BusType now shows SAS or SATA instead of RAID or Unknown.
Sometimes, you can also change the controller mode from RAID to HBA (passthrough) mode in BIOS/UEFI settings. Or, if your controller supports JBOD mode, switch there. That way, disks will be directly accessible, and S2D can use them properly.
Fix 3: Creating and Managing Storage Pools Properly
Once disks are recognized properly, you can proceed with enabling Storage Spaces Direct.- Run: powershell Enable-ClusterStorageSpacesDirect Sometimes, it takes forever or throws a bus type error. In that case, double-check disk detection first.- If you get an error like “no disks with supported bus types found, ” revisit Fix 1 or 2.- After enabling, go to Failover Cluster Manager, and verify that the pool appears under Storage.- You can rename the pool if needed: powershell Set-StoragePool -FriendlyName "Cluster Pool 1" -NewFriendlyName "S2D" - And create volumes (CSV) from the pool: powershell New-Volume -StoragePoolFriendlyName S2D -FriendlyName CSV001 -FileSystem CSVFS_ReFS -Size 200GB When disks are properly pooled, they won’t show up in Disk Management anymore — that’s okay. S2D handles them.
Fix 4: Replacing a Failed Disk
Sometimes, disks fail or get marked as Retired. Replacing them can be a pain, but PowerShell makes it manageable.- Check current status: powershell Get-StoragePool *S2D* | Get-PhysicalDisk - Find the problematic drive: powershell $Disk = Get-PhysicalDisk | Where-Object { $_. OperationalStatus -ne "OK" } - Mark the disk as Retired: powershell Set-PhysicalDisk -InputObject $Disk -Usage Retired - Remove it from pool: powershell Get-StoragePool *S2D* | Remove-PhysicalDisk -PhysicalDisks $Disk - Use the server’s disk LED (if available) to identify the failed drive, then replace it physically.- Once the new drive is inserted, scan for new disks: powershell $NewDisks = Get-PhysicalDisk | Where-Object { $_. CanPool -eq $true } - Add it back to the pool: powershell Get-StoragePool *S2D* | Add-PhysicalDisk -PhysicalDisks $NewDisks - S2D will automatically rebalance data across the new drive. Just wait for the process to finish.Note: If the new disk isn’t detected immediately, try rescanning disks in Device Manager or reboot.
And yes, disks marked as S2D don’t show up in Disk Management anymore, which can look suspicious. But that’s normal — S2D takes over the raw disks behind the scenes.
Summary
- Check disk bus types and update firmware/drivers if needed.
- Make sure disks are unformatted and in a supported mode.
- Enable Storage Spaces Direct cautiously; watch for errors related to disk detection.
- Replace failed disks carefully, using PowerShell to mark old disks as retired then add new ones.
Wrap-up
Dealing with Storage Spaces Direct isn’t exactly straightforward, especially when hardware quirks get in the way. But once the disks are set correctly and the cluster is happy, you get a pretty resilient, scalable storage solution. Just keep an eye on your bus types, drivers, and firmware — it’s all about the tiny details with S2D. Hopefully, this shaves off a few hours for someone trying to get their cluster to work. Fingers crossed this helps!