This can occur if the storage pool loses its quorum, which means that most drives in the pool have failed or are offline for some reason. When a storage pool is in the Unknown or Unhealthy health state, it means that the storage pool is read-only and can't be modified until the pool is returned to the Warning or OK health states. This condition occurs only with drives hosting pool metadata.Īction: Check the state of your drives and replace any failed drives before there are additional failures. There are failed or missing drives in the storage pool. As a result, your storage pool might have reduced resilience. When the storage pool is in the Warning health state, it means that the pool is accessible, but one or more drives failed or are missing. Pool health state: Healthy Operational state The following sections list the health and operational states. S2D on StorageSpacesDirect1 Read-only Unknown False True Here's an example output showing a storage pool in the Unknown health state with the Read-only operational status: FriendlyName OperationalStatus HealthStatus IsPrimordial IsReadOnly To find out what state a pool is in, use the following PowerShell commands: Get-StoragePool -IsPrimordial $False | Select-Object HealthStatus, OperationalStatus, ReadOnlyReason This isn't a happy cluster.Įvery storage pool has a health status - Healthy, Warning, or Unknown/ Unhealthy, as well as one or more operational states. Here's an example of a variety of (mostly bad) health and operational states on a Storage Spaces Direct cluster that's missing most of its cluster nodes (right-click the column headers to add Operational Status). You can view health and operational states in Server Manager, or with PowerShell. Volumes are created on top of the virtual disks and store your files, but we're not going to talk about volumes here. Pool metadata is written to each drive in the pool. Storage Spaces has three primary objects - physical disks (hard drives, SSDs, etc.) that are added to a storage pool, virtualizing the storage so that you can create virtual disks from free space in the pool, as shown here. It also discusses why a drive can't be added to a pool (the CannotPoolReason). These states can be invaluable when trying to troubleshoot various issues such as why you can't delete a virtual disk because of a read-only configuration. This topic describes the health and operational states of storage pools, virtual disks (which sit underneath volumes in Storage Spaces), and drives in Storage Spaces Direct and Storage Spaces. Applies to: Azure Stack HCI, versions 22H2 and 21H2 Windows Server 2022, Windows Server 2019, Windows Server 2016, Windows Server 2012 R2, Windows Server 2012, Windows 10, Windows 8.1
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |