S2D Storage Jobs Failing

Error codes for common storage job failures

From time to time, a Storage Spaces Direct (S2D) storage job, whether this is a Virtual Disk Repair, Physical Disk Removal or Storage Pool Rebalance/Optimization, will suspend or fail for some reason. When this happens, we need to understand why this is the case, and resolve if possible. Follow the steps below to sort it out.

  1. Ascertain the current storage pool owner either through Failover Cluster Manager, or the below Powershell
1
Get-ClusterGroup | ? Name -like ((get-storagepool s2d*).uniqueid).trim('{}') 
  1. Open event viewer on the storage pool owner and navigate to StorageManagement log.
  2. Review 20XX events and compare them to the error codes below.

Storage Spaces Direct S2D Failed Jobs Error Logs Virtual Disk

Event Log Example

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
Log Name:      Microsoft-Windows-StorageManagement/Operational
Source:        Microsoft-Windows-StorageManagement-WSP-Spaces
Event ID:      2005
Task Category: None
Level:         Error
Description:
An error occurred during storage job execution.

Job Name:	Repair
Error Code:	4

Error Code Translations

Standard CIM Return Codes

Error ValueDescription
0Success
1Not Supported
2Unspecified Error
3Timeout
4Failed
5Invalid Parameter
6In Use / Disk is in use
7This command is not supported on x86 running in x64 environment
8Object Not Found

Extended CIM Return Codes

Error ValueDescription
4096Method Parameters Checked - Job Started
4097Size not supported
4098Timeout not supported
4099The device is busy

Storage Management API Return Codes

Common Errors 40000 - 40999

Error ValueDescription
40000Not enough available capacity
40001Access denied
40002There are not enough resources to complete the operation.
40003Cache out of date
40004An unexpected I/O error has occurred
40005You must specify a size by using either the Size or the UseMaximumSize parameter. You can specify only one of these parameters at a time.
40006The object or object type requested does not exist in cache.
40007The request failed due to a fatal device hardware error.
40018The specified object is managed by the Microsoft Failover Clustering component. The disk must be in cluster maintenance mode and the cluster resource status must be online to perform this operation.

Disk Errors 41000 - 41999

Error ValueDescription
41000The disk has not been initialized.
41001The disk has already been initialized.
41002The disk is read only.
41003The disk is offline.
41004The disk’s partition limit has been reached.
41005The specified partition alignment is not valid. It must be a multiple of the disk’s sector size.
41006A parameter is not valid for this type of partition.
41007Cannot clear with OEM partitions present. To clear OEM partitions, use the RemoveOEM flag.
41008Cannot clear with data partitions present. To clear data partitions, use the RemoveData flag.
41009Operation not supported on a critical disk.
41010The specified partition type is not valid.
41011Only the first 2 TB are usable on MBR disks.
41012The specified offset is not valid.
41013Cannot convert the style of a disk with data or other known partitions on it.
41014The disk is not large enough to support a GPT partition style.

Partition Errors 42000 - 42999

Error ValueDescription
42000The partition was deleted, although its access paths were not.
42001The extended partition still contains other partitions.
42002The requested access path is already in use.
42004Cannot assign access paths to hidden partitions.
42005Cannot remove a volume GUID path.
42006Cannot remove the drive letter of a boot or paging file partition.
42007The access path is not valid.
42008Cannot shrink a partition containing a volume with errors.
42009Cannot resize a partition containing an unknown file system.
42010The operation is not allowed on a system or critical partition.
42011This operation is only supported on data partitions.
42012Cannot assign multiple drive letters to a partition.
42013Cannot assign drive letter to this type of partition.

Volume Errors 43000 - 43999

Error ValueDescription
43000The specified cluster size is invalid
43001The specified file system is not supported
43002The volume cannot be quick formatted
43003The number of clusters exceeds 32 bits
43004The specified UDF version is not supported
43005The cluster size must be a multiple of the disk’s physical sector size
43006Cannot perform the requested operation when the drive is read only
43007The repair failed
43008The scan failed
43009A snapshot error occured while scanning this drive. You can try again, but if this problem persists, run an offline scan and fix.
43010A scan is already running on this drive. Chkdsk can not run more than one scan on a drive at a time.
43011A snapshot error occured while scanning this drive. You can try again, but if this problem persists, run an offline scan and fix.
43012A snapshot error occured while scanning this drive. Run an offline scan and fix.
43013Cannot open drive for direct access
43014Cannot determine the file system of the drive
43015This setting may not be changed due to the group policy setting
43016This setting may not be changed due to the global registry setting

Storage Provider Errors 46000 - 46999

Error ValueDescription
46000The storage provider cannot connect to the storage provider.
46001The storage provider cannot connect to the storage subsystem.
46002The storage provider does not support a required profile.
46003The storage provider does not support a required association.
46004Cannot register/unregister the storage subsystem on local host.
46005The storage subsystem is not registered.
46006This subsystem is already registered.
46007This subsystem is already registered with another user’s credentials. Use the -Force flag to remove the existing registration and add a new one anyway.
46008Failover clustering could not be enabled for this storage object.

Storage Subsystem Errors 47000 - 47999

Error ValueDescription
47000No storage pools were found that can support this virtual disk configuration.
47001This subsystem does not support creation of virtual disks with the specified provisioning type.

Partition Errors 48000 - 48999

Error ValueDescription
48000This operation is not supported on primordial storage pools.
48001The storage pool is reserved for special usage only.
48002The specified resiliency setting is not supported by this storage pool.
48004There are not enough physical disks in the storage pool to create the specified virtual disk configuration.
48005The specified storage pool could not be found.
48006The storage pool could not complete the operation because its health or operational status does not permit it.
48007The storage pool could not complete the operation because its configuration is read-only.
48008The storage pool contains virtual disks.
48009The number of thin provisioning alert thresholds specified exceeds the limit for this storage pool.
48010You must specify the size info (either the Size or UseMaximumSize parameter) or the tier info (the StorageTiers and StorageTierSizes parameters), but not both size info and tier info.
48011No auto-allocation drives found in storage pool.

Resiliency Settings Errors 49000 - 49999

Error ValueDescription
49000No resiliency setting with that name exists.
49001The value for NoSinglePointOfFailure is not supported.
49002The value for PhysicalDiskRedundancy is outside of the supported range of values.
49003The value for NumberOfDataCopies is outside of the supported range of values.
49004The value for ParityLayout is outside of the supported range of values.
49005The value for Interleave is outside of the supported range of values.
49006The value for NumberOfColumns is outside of the supported range of values.

Virtual Disk Errors 50000 - 50999

Error ValueDescription
50000The specified virtual disk could not be found.
50001Could not repair the virtual disk because too many physical disks failed. Not enough information exists on the remaining physical disks to reconstruct the lost data.
50002The virtual disk could not complete the operation because another computer controls its configuration.
50003The virtual disk could not complete the operation because its health or operational status does not permit it.
50004The virtual disk could not complete the operation because its Manual Attach status does not permit it.
50005The value for WriteCacheSize is outside of the supported range of values.

Physical Disk Errors 51000 - 51999

Error ValueDescription
51000One of the physical disks specified is not supported by this operation.
51001Not enough physical disks were specified to successfully complete the operation.
51002One of the physical disks specified is already in use.
51003One of the physical disks specified uses a sector size that is not supported by this storage pool.
51004One of the physical disks specified could not be removed because it is still in use.
51005One or more physical disks are not connected to the nodes on which the pool is being created.

Masking Set Errors 52000 - 52999

Error ValueDescription
52000The device number specified is not valid.
52001The HostType requested is not supported.
52002DeviceAccess must be specified for each virtual disk.

Initiator ID Errors 53000 - 53999

Error ValueDescription
53000The initiator address specified is not valid
53001Only one initiator address is acceptable for this operation.

Target Port Errors 54000 - 54999

Error ValueDescription
54000The target port address specified is not valid.

TechNet Article - Storage Management API Common Return Codes