Windows Storage Pools Stuck in Read-Only State: Suspected Bad SATA Card
Windows Storage Pools, introduced in Windows 8 and enhanced in Windows 10 and 11, allow users to group physical disks into storage pools and then create virtual disks called storage spaces from the available capacity. These storage spaces can be configured with various resiliency options, such as mirroring or parity, to protect data from drive failures.
The Problem: Storage Pool Stuck in Read-Only State
In this scenario, we have an 8-drive storage pool using Storage Spaces in Windows 11 with one parity configuration. The storage pool has been running smoothly for months, but suddenly, it becomes read-only, and the system reports a suspected bad SATA card.
Understanding the Read-Only State
When a storage pool is in a read-only state, it means that new writes are not allowed, but existing data can still be read. This state is usually triggered by a problem that might cause data loss if writing is allowed to continue. The suspected bad SATA card in this scenario could be the cause of the issue, as it might be intermittently failing, causing data inconsistencies.
Investigating the Problem
To diagnose the issue, you can use the Windows Event Viewer to look for events related to the storage pool and the SATA controller. Event IDs 129 and 130 in the Microsoft-Windows-StorageSpaces-Driver event log can provide useful information about the health of the storage pool and potential issues with the drives or the controller.
# To open Event Viewer, press Win + X and select "Event Viewer"
# In Event Viewer, navigate to Windows Logs > Microsoft-Windows-StorageSpaces-Driver
# Look for events with IDs 129 and 130 for more information about the issue
Resolving the Read-Only State
To resolve the read-only state, you can try the following steps:
- Replace the suspected bad SATA card and ensure it is compatible with your system.
- Remove and re-add the affected drives to the storage pool, if possible.
- Create a new storage pool with the remaining good drives and migrate the data from the affected storage pool.
- As a last resort, you can reset the storage pool to factory defaults, which will erase all data. This option should only be used if all other methods have failed and the data is no longer needed.
Preventing Future Issues
To prevent similar issues in the future, ensure that all hardware components are compatible and functioning properly. Regularly monitor the health of your storage pool and drives using tools like the Windows Event Viewer and the built-in Windows Disk Management utility.
- Windows Storage Pools can become read-only due to hardware or software issues.
- In this scenario, a suspected bad SATA card caused a storage pool to become read-only.
- To resolve the issue, replace the SATA card, remove and re-add affected drives, create a new storage pool, or reset the storage pool to factory defaults.
- Regularly monitor storage pool health to prevent future issues.