Install the cumulative update 2019 KB5027222 on one node in a Windows S2D cluster Reboot to join the cluster causes a storage failure

Question

Install the 2019 cumulative update 5027222 for one node in a Windows S2D cluster Rebooting to join the cluster results in a storage failure and all VMs go into a paused state, but Cluster Shared Volumes can be accessed?
It returned to normal after 10 minutes.

What could possibly cause this to happen?

Answer 1

Hello,

Thank you for your question and for reaching out with your question today.

There could be several factors that contribute to the storage failure and VMs going into a paused state after installing the 2019 cumulative update 5027222 and rebooting to join the cluster in a Windows S2D (Storage Spaces Direct) cluster. Here are a few possible causes to consider:

1. Storage Spaces Direct configuration: It's possible that the cumulative update affected the configuration or integrity of the Storage Spaces Direct infrastructure in some way. This can result in issues with accessing the underlying storage for VMs.
2. Hardware or driver compatibility: The update may have exposed compatibility issues with specific hardware components or drivers in the cluster. It's essential to ensure that all hardware components, including storage controllers and network adapters, are compatible with the Windows Server version and cumulative update being installed.
3. Time required for recovery: After joining a cluster and rebooting, it can take some time for the cluster services and storage infrastructure to fully stabilize. During this recovery period, the VMs may be paused until the cluster resources are back online and functioning correctly.
4. Configuration or settings conflicts: There might be conflicts between the updated cumulative update and the existing configuration or settings of the S2D cluster. It's crucial to review and validate the configuration settings, including networking, storage, and cluster settings, to ensure they are properly aligned with the updated software.

To troubleshoot and resolve the issue, consider the following steps:

1. Review event logs: Check the event logs on the affected node, cluster, and VMs for any relevant error messages or warnings that can provide insights into the root cause of the storage failure.
2. Validate hardware and drivers: Ensure that all hardware components and drivers are compatible with the Windows Server version and cumulative update installed. Check for any updated drivers or firmware from the hardware vendor and apply them as needed.
3. Verify cluster configuration: Double-check the configuration settings of the S2D cluster, including networking, storage, and cluster settings, to ensure they are correctly configured and aligned with the cumulative update.
4. Monitor the recovery process: When the cluster experiences issues during the recovery period after joining and rebooting, monitor the cluster and VMs closely. If the issue persists for an extended period or if the VMs do not recover, further investigation may be necessary.

Remember to perform proper testing and have backups in place before applying updates or making configuration changes to a production cluster. This helps mitigate risks and ensures a recovery path in case of unexpected issues.

I used AI provided by ChatGPT to formulate part of this response. I have verified that the information is accurate before sharing it with you.

If the reply was helpful, please don’t forget to upvote or accept as answer.