When problems are identified in the storage architecture, Storage Spaces generates errors, and then logs these errors to the Event Log. You can access these events by using the Event Log tool, or by accessing the recorded errors by using Server Manager or Windows PowerShell cmdlets. The following table identifies common Event IDs associated with problematic storage.
Event ID Message Cause
100 Physical drive %1 failed to read the configuration or returned corrupt data for storage pool %2. As a result, the in-memory configuration might not be the most recent copy of the configuration.
Return Code: %3.
A physical drive can fail to read the configuration or return corrupt data for a storage pool for the following reasons:
The physical drive might fail requests with device I/O errors.
The physical drive might contain corrupted storage pool configuration data.
The physical drive might contain insufficient memory resources.
MCT USE ONL Y. STUDENT USE PROHIBITED
Installation, Storage, and Compute with Windows Server 2016 4-23
Event ID Message Cause
102 Majority of the physical drives of storage pool %1 failed a configuration update, which caused the pool to go into a failed state. Return Code: %2.
• A write failure might occur when writing a storage pool configuration to physical drives for the following reasons:
• Physical drives might fail requests with device I/O errors.
• An insufficient number of physical drives are online and updated with their latest configurations.
• The physical drive might contain insufficient memory resources.
103 The capacity consumption of the storage pool %1 has exceeded the threshold limit set on the pool. Return Code: %2.
The capacity consumption of the storage pool has exceeded the threshold limit set on the pool.
104 The capacity consumption of the storage pool %1 is now below the threshold limit set on the pool. Return Code: %2.
The capacity consumption of the storage pool returns to a level that is below the threshold limit set on the pool.
200 Windows was unable to read the drive header for physical drive %1. If you know the drive is still usable, then resetting the drive health by using the command line or GUI might clear this failure condition and enable you to reassign the drive to its storage pool. Return Code: %2.
Windows was unable to read the drive header for a physical drive.
201 Physical drive %1 has invalid meta-data.
Resetting the health status by using the command line or GUI might bring the physical drive to the primordial pool.
Return Code: %2.
The metadata on a physical drive has become corrupt.
202 Physical drive %1 has invalid meta-data.
Resetting the health status by using the command line or GUI might resolve the issue. Return Code: %2.
The metadata on a physical drive has become corrupt.
203 An I/O failure has occurred on Physical
drive %1. Return Code: %2. An I/O failure has occurred on a physical drive.
300 Physical drive %1 failed to read the configuration or returned corrupt data for storage space %2. As a result, the in-memory configuration might not be the most recent copy of the configuration.
Return Code: %3.
• A physical drive can fail to read the configuration or return corrupt data for the following reasons:
• The physical drive might fail requests with device I/O errors.
• The physical drive might contain corrupted storage space configuration data.
• The physical drive might contain insufficient memory resources.
MCT USE ONL Y. STUDENT USE PROHIBITED
4-24 Implementing Storage Spaces and Data Deduplication
Event ID Message Cause
301 All pool drives failed to read the
configuration or returned corrupt data for storage space %1. As a result, the storage space will not attach. Return Code: %2.
• You can experience all physical drives failing to read their configuration or returning corrupt data for storage spaces for the following reasons:
• Physical drives might fail requests with device I/O errors.
• Physical drives might contain
corrupted storage pool configuration data.
• The physical drive might contain insufficient memory resources.
302 Majority of the pool drives hosting space meta-data for storage space %1 failed a space meta-data update, which caused the storage pool to go in failed state. Return Code: %2.
• The majority of the pool drives hosting space metadata for a storage space can fail a metadata update for the following reasons:
• Physical drives might fail requests with device I/O errors.
• Insufficient number of physical drives have online storage space metadata.
• The physical drive might contain insufficient memory resources.
303 Drives hosting data for storage space have failed or are missing. As a result, no copy of data is available. Return Code: %2.
This event can occur if a drive in the storage pool fails or is removed.
304 One or more drives hosting data for storage space %1 have failed or are missing. As a result, at least one copy of data is not available. However, at least one copy of data is still available. Return Code:
%2.
One or more drives hosting data for a storage space have failed or are missing.
As a result, at least one copy of data is not available. However, at least one copy of data is still available.
306 The attempt to map or allocate more storage for the storage space %1 has failed. This is because there was a write failure involved in the updating the storage space metadata. Return Code: %2.
The attempt to map or allocate more storage for the storage space has failed.
More physical drives are needed.
307 The attempt to unmap or trim the storage
space %1 has failed. Return Code: %2. The attempt to unmap or trim the listed storage space has failed.
308 The driver initiated a repair attempt for
storage space %1. Return Code: %2. The driver initiated a repair attempt for storage space. This is a normal condition.
No further action is required.
MCT USE ONL Y. STUDENT USE PROHIBITED
Installation, Storage, and Compute with Windows Server 2016 4-25