Fix Storage Spaces Direct Storage Pool

Fix Storage Spaces Direct Storage Pool

During the implementation of WSSD POC for one of my customers, I faced issue with S2D storage pool and more precisely with the disks. In fact, after the creation of the S2D Hyper-Converged cluster and so the storage pool, I noticed that the listed capacity was not aligned with expectation and actual hardware configuration.

As you can see below, I quickly identified the issue. Actually, if you want to have more details about your S2D storage pool, we can simply run these PowerShell commands on one of the nodes of the cluster.

In this case, I had an issue with 5 physical disks and more precisely with 4 cache and 1 capacity disk on the same physical host. The hardware failure was very unlikely in this case, I decided to confirm by having a look through the DRAC. And as expected, the hardware was not in cause.

If you are facing this kind of behavior or even a real hardware failure issue, the first thing to do is to retire the disks to the storage pool using these PowerShell commands.

After replacement of physical disks (in this case, it was not needed as hardware was healthy), you can check that the disks are detected with the CanPool parameter set to True, and you add them to the existing S2D storage pool using these Powershell commands.

Note

You can use the following PowerShell command which will turn on the LED of the defaillant disks on a server (to help identify)

Leave a Reply

Your email address will not be published. Required fields are marked *