Storage Pool only shows one of two physical drives as integrated

Hello Chris,

Thank you for your question and for reaching out with your question today.

It appears that you have a Storage Spaces configuration on your Windows Server 2019 PC with two pools, but one of the virtual disks is showing a warning status. Here are the steps you can take to troubleshoot and potentially reinstate the virtual disk:

**Note**: Before proceeding with any troubleshooting steps, make sure you have a backup of your important data to avoid any potential data loss.

1. **Check Physical Disk Health**: Since one of the drives is showing a warning status, it's essential to verify the health of the physical disks involved. You can use PowerShell to get detailed information about the physical disks:

   Open PowerShell with administrator privileges and run the following command:

   ```powershell
   Get-PhysicalDisk | Select-Object DeviceID, MediaType, OperationalStatus, HealthStatus, Size

Ensure that all the physical disks are in a healthy state and have the correct operational status.

2. Check Virtual Disk Status: Run the following command to check the status of virtual disks:

      Get-VirtualDisk | Select-Object FriendlyName, OperationalStatus, HealthStatus, Size
   

   Make sure the virtual disk in question is listed, and check its operational status and health status.
3. Repairing the Virtual Disk: If the virtual disk shows a warning status and it's not visible within the server, you can try repairing it using the Repair-VirtualDisk cmdlet. First, identify the FriendlyName of the virtual disk you want to repair from the output of the previous command. To repair the virtual disk, run the following command:

      Repair-VirtualDisk -FriendlyName "YourVirtualDiskFriendlyName"
   

   This command will attempt to repair the virtual disk and bring it back to a healthy state.
4. Check Storage Spaces Status: Ensure that the Storage Spaces service is running correctly on your Windows Server PC. You can check its status by running the following command:

      Get-Service -Name "SpacesSvc"
   

   If it's not running, you can start the service using the following command:

      Start-Service -Name "SpacesSvc"
   

5. Check Event Logs: Check the Event Viewer for any relevant error messages or warnings related to Storage Spaces. Look for events with the source "Storage Spaces Driver" or "Virtual Disk Service."
6. Update Drivers and Firmware: Make sure your system's drivers and firmware, especially for the storage controller, are up-to-date. Outdated drivers or firmware can sometimes cause issues with Storage Spaces.

If the above steps don't resolve the issue, you may need to seek assistance from a storage expert or Microsoft Support for more in-depth troubleshooting. Remember to proceed with caution and always have a backup of your data before attempting any significant changes to storage configurations.

I used AI provided by ChatGPT to formulate part of this response. I have verified that the information is accurate before sharing it with you.

If the reply was helpful, please don’t forget to upvote or accept as answer.

Best regards.

Thanks for the response.

I had already performed the repair on the virtual disk which appeared to go well, but when it completed and a reboot performed, the virtual drive was still not viewable. Both drives when opened using a disk caddy attached to my laptop still have all data.

The only difference between the two drives when installed on the server is that one is shown as SATA and the other as ATA. The SATA drive shows Chassis as "Integrated: Adaptor 2: Port 2" whereas the ATA drive shows Chassis as entirely blank.

What will be the effect of deleting the Virtual Disk? Or should I just remove the drive described as ATA and then reinstall it?

By the way when I attempt the Get-Service command, I get the following response:

I have now replaced the two 500Gb drives with a pair of 2Tb drives, and copied the 500Gb drive data to the new Virtual Disk. All is currently well.

Thanks to all for the responses. Although these did not help exactly, I was able to discover from further searches a definitive solution. This is the article I found: https://techcommunity.microsoft.com/t5/windows-server-for-it-pro/refs-volume-appears-raw-version-doesn-t-match-expected-value/m-p/3058652/page/4