Getting events 1101 and 1108 when creating csv volumes

Robert Lien 0 Reputation points
2026-11-17T19:27:00.4033333+00:00

Hello,

I have a 4 node s2d cluster running server 2019. It has been unstable with production VMs. I have now cleared the cluster, and am troubleshooting, why im getting events 1101 and 1108 when creating csv volumes or putting a node into maintenance?

Anyone experience any of this?

I have latest controller drivers and firmware, fully windows update.

Thank you

Windows for business | Windows Server | Storage high availability | Clustering and high availability
0 comments No comments

2 answers

Sort by: Newest
  1. Hirwa Sano Chretien 160 Reputation points Independent Advisor
    2026-11-17T21:25:45.7133333+00:00

    Hello,

    Since you have already cleared the cluster, I would focus on identifying what happens during CSV creation and node maintenance before making further changes to the storage configuration.

    Even with updated firmware, drivers, and Windows updates, S2D instability can still be caused by network configuration differences, unsupported storage controllers, disk health issues, or leftover storage metadata.

    1. Capture the event details

    Open Event Viewer (eventvwr.msc) and locate Events 1101 and 1108 immediately after reproducing the issue.

    Check the Event Source, complete General message, timestamp, and Details tab, including the XML data.

    You can also capture the events using PowerShell:

    $Start = Get-Date
    
    # Reproduce the CSV creation or maintenance operation here.
    
    Get-WinEvent -FilterHashtable @{
        LogName = 'System'
        StartTime = $Start
    } | Where-Object { $_.Id -in 1101,1108 } |
    Select-Object TimeCreated, ProviderName, Id, LevelDisplayName, Message |
    Format-List
    

    The event source and complete messages are essential because event IDs alone do not identify the failing component.

    2. Check storage health and disk availability

    Run:

    Get-PhysicalDisk | Format-Table FriendlyName, OperationalStatus, HealthStatus, CanPool, Usage
    
    Get-VirtualDisk | Format-Table FriendlyName, OperationalStatus, HealthStatus
    
    Get-StoragePool -IsPrimordial $false | Format-Table FriendlyName, OperationalStatus, HealthStatus
    
    Get-StorageJob
    

    Check for unhealthy or degraded disks, incomplete storage jobs, and disks that cannot be pooled. If CanPool is False, investigate the reason before attempting to clean or reset any disk.

    3. Verify network and RDMA configuration

    S2D depends heavily on reliable communication between nodes. Check that the network adapter configuration is consistent across all four nodes, particularly RDMA settings and, if using RoCE, DCB, PFC and ETS configuration.

    Run:

    Get-NetAdapterRdma
    
    Get-SmbMultichannelConnection
    
    Get-NetAdapter | Format-Table Name, Status, LinkSpeed
    

    These commands report information from the local node, so run them on all four nodes and compare the results. Look for unexpected differences, unavailable RDMA interfaces, or missing SMB Multichannel connections.

    4. Verify storage controller compatibility

    Confirm that the storage controllers are configured in a supported HBA or pass-through mode rather than traditional hardware RAID mode.

    Also verify that the exact server, controller, drive models and firmware combinations are supported for Storage Spaces Direct. Having the latest firmware does not necessarily mean the hardware configuration is supported.

    5. Run cluster validation

    Since the cluster has already been cleared, run cluster validation on the current configuration and review any storage or network-related warnings before proceeding with additional configuration changes.

    Test-Cluster -Include "Storage Spaces Direct","Inventory","Network","System Configuration"
    

    Review the storage and network results carefully, particularly any warnings or failures relating to disk eligibility, connectivity, and configuration consistency.

    6. Collect cluster logs

    Immediately after reproducing the issue, collect the cluster logs:

    Get-ClusterLog -UseLocalTime -TimeSpan 30 -Destination C:\ClusterLogs
    

    This collects the last 30 minutes of cluster activity. Review the logs from all four nodes and correlate the entries with the timestamps of Events 1101 and 1108.

    Microsoft documentation for further guidance:

    Troubleshoot Storage Spaces Direct

    Storage Spaces Direct hardware requirements

    Troubleshoot storage issues in Hyper-V and Windows Server failover clusters

    If the physical disks and virtual disks report healthy states but the events continue, the event provider and complete messages, together with the cluster logs and validation report, will be important for identifying the underlying failure.

    If this answer helps resolve your issue, please consider accepting it as the answer. This will also help other community members facing the same problem find the solution more easily.

    Was this answer helpful?

    0 comments No comments

  2. AI answer

    2026-11-17T19:28:08.36+00:00

    Event IDs 1101 and 1108 are not sufficient by themselves to diagnose the failure; capture their ProviderName, full message, timestamp, and correlated cluster/storage state while reproducing CSV creation or node maintenance.

    Capture the failing operation

    Run the following from elevated PowerShell immediately before reproducing the problem:

    $Start = Get-Date
    
    # Reproduce CSV creation or the node maintenance operation here.
    
    Get-WinEvent -FilterHashtable @{StartTime=$Start} |
      Where-Object Id -in 1101,1108 |
      Select-Object TimeCreated, ProviderName, Id, LevelDisplayName, Message |
      Format-List
    
    Get-ClusterLog -UseLocalTime -TimeSpan 30 -Destination C:\ClusterLogs
    Get-ClusterSharedVolume | Format-List *
    Get-VirtualDisk | Format-Table FriendlyName,HealthStatus,OperationalStatus
    Get-PhysicalDisk | Format-Table FriendlyName,HealthStatus,OperationalStatus
    Get-StorageJob
    

    The provider and complete message are essential because event numbers are provider-specific. Preserve the cluster logs from all four nodes, plus the FailoverClustering event channels. Microsoft’s storage troubleshooting guidance recommends collecting these items together so the events can be correlated with the affected CSV and virtual disk.^1^

    In the cluster log, start at the event timestamp and search for:

    • The CSV or cluster disk name.
    • IsAlive, Online, Offline, Move, or Group move.
    • RHS, timeout, NetFT, or SMB.
    • A virtual disk changing to Detached, No Redundancy, InService, or Regenerating.

    Microsoft recommends working backward from the first resource failure rather than treating later failover events as the initiating fault.^2^

    Distinguish normal maintenance events from a failure

    If the provider is Microsoft-Windows-FailoverClustering and the messages only report that a CSV entered and then exited maintenance, that can be expected around a maintenance operation. Suspend-ClusterResource deliberately enables maintenance for a disk or CSV; for a CSV, dependent resources are taken offline and client access is interrupted.^3^

    Do not classify the events as harmless if any of the following also occurs:

    • CSV remains offline or pending offline.
    • The operation hangs or times out.
    • A virtual disk becomes unhealthy or detached.
    • Storage jobs remain suspended.
    • A node is evicted or the RHS process terminates.
    • CSV access or VM I/O fails.

    Also distinguish CSV resource maintenance from S2D physical-disk maintenance. A physical disk in In maintenance mode has reads and writes halted; transitional states should normally progress through Starting maintenance mode or Stopping maintenance mode and return to Healthy/OK.^4^

    If the problem occurs during node drain

    The documented planned-drain failure pattern involves CSVs becoming unresponsive or pending offline, prolonged I/O pauses, RHS termination, and sometimes node eviction. Contributing conditions include the draining node owning quorum, file locks, NetFT packet loss, network congestion, and inconsistent adapter settings that prevent SMB Multichannel connectivity.^5^

    If your captured logs match that pattern:

    1. Move quorum ownership and critical cluster roles away from the node before draining it.
    2. Compare network-adapter configuration across all four nodes.
    3. Check the cluster log for NetFT packet loss and SMB Multichannel failures.
    4. Check for file locks against the affected CSV.
    5. Run cluster validation and review the Storage Spaces Direct and network sections.

    Since controller drivers, firmware, and Windows updates are already current, those checks do not need to be repeated. Cluster validation remains useful because it tests the active configuration and verifies that cache devices and S2D storage are reported without errors.^6^

    Do not apply recovery overrides unless the state matches

    Commands involving DiskRecoveryAction, DiskRunChkDsk, removing a disk from CSV, or forcing it online are recovery procedures—not general troubleshooting steps. Use them only if Get-VirtualDisk specifically reports No Redundancy or Detached, following the matching Microsoft procedure.^6^

    If every reproduction causes an actual CSV or node-maintenance failure while the virtual disks remain Healthy/OK, submit the cluster logs, exported FailoverClustering logs, validation report, and exact 1101/1108 provider messages to Microsoft Support. Those details are required to distinguish an S2D resource failure from a network, SMB, filter-driver, or cluster-orchestration issue.


    References

    1. Troubleshoot storage issues in Hyper-V and Windows Server failover clusters
    2. Unexpected cluster failover troubleshooting guidance
    3. Suspend-ClusterResource (FailoverClusters) | Microsoft Learn
    4. Troubleshoot Storage Spaces and Storage Spaces Direct health and operational states
    5. Shared Volumes Don't Respond During Planned Cluster Node Drain - Windows Server | Microsoft Learn
    6. Troubleshoot Storage Spaces Direct
    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.