大网数据广告活动
故障转移群集

Troubleshoot Rolling Upgrade Issues

· 52CE 我爱测

Discusses how to troubleshoot rolling upgrade issues.

Summary

This article provides a structured troubleshooting method to resolve common issues that you might encounter during rolling upgrades in Windows Server Failover Clustering (WSFC), Storage Spaces Direct, SQL Server Always On availability groups, and Hyper-V.

Rolling upgrades are essential for maintaining and upgrading systems while experiencing minimal downtime. However, challenges such as compatibility and configuration errors can affect availability, and potentially cause data loss.

Prerequisites

Before you start a rolling upgrade:

  • Verify that the rolling upgrade feature is supported for your workload and operating system (OS) versions.
  • Verify that all cluster nodes are healthy by using the Get-ClusterNode PowerShell command.
  • Make sure that you have up-to-date backups, including:
    • System state
    • Cluster configuration
    • User data

Potential workarounds

Address rolling upgrade failures

  1. Move core resources to another node by using Failover Cluster Manager or the Move-ClusterGroup PowerShell command.
  2. Migrate roles and resources off the node by using Suspend-ClusterNode -Drain.
  3. Check cluster logs for dependencies or errors that might block the operation.

Troubleshooting checklist

  1. Review prerequisites: Make sure that the environment meets all prerequisites that are mentioned in this article.

  2. Validate cluster status: Resolve any validation warnings or errors by running Test-Cluster.

    • Verify the current cluster functional level by using Get-Cluster | Select ClusterFunctionalLevel.
    • Validate network connectivity among all nodes.
  3. Plan and sequence upgrades: Document the sequence of node upgrades (one node at a time).

    • Move cluster roles (such as virtual machines (VMs), availability groups, or file shares) off the node that's being upgraded.
    • Update all nodes to the latest supported updates or hotfixes for the current OS.
  4. Communicate with stakeholders: Inform stakeholders and schedule maintenance windows.

    • Notify monitoring teams in order to avoid unnecessary alerts.
  5. Ensure application awareness: Verify application compatibility for workloads such as SQL Server, Hyper-V, or file services.

    • Inform application owners about planned upgrades.
  6. Conduct pre-upgrade tests: Review logs for Windows, applications, clusters, and storage to identify any pre-existing issues.

Common issues and their respective solutions

1. Rolling upgrade doesn't start or node can't be evicted

Symptoms

You can't pause, drain, or remove a node from the cluster. You receive error messages such as the following example:

Node... cannot be removed from the cluster.

Cause

The node hosts core cluster resources, dependencies are misconfigured or the cluster is unstable.

Solution

  1. Move core resources to another node by using Failover Cluster Manager or Move-ClusterGroup.
  2. move roles and resources by running Suspend-ClusterNode -Drain.
  3. Make sure that the node isn't the last up-to-date or quorum node.
  4. Check cluster logs for blocking dependencies.

2. Can't restore upgraded node to cluster

Symptoms

You receive a version mismatch message or error messages such as the following example:

A node attempted to join a failover cluster but failed due to incompatibility.

Cause

Unsupported OS version mix or nonupdated node.

Solution

  1. Verify the supported OS and cluster version matrix.
  2. Update the node to the latest cumulative update (CU).
  3. Upgrade the OS versions sequentially (for example, 2016 → 2019 → 2022).
  4. Identify versioning errors by using Get-ClusterLog.

3. Resource or service doesn't come online

Symptoms

Resources such as VMs or file shares enter a failed or offline state post-upgrade. Common Event IDs include 1069, 1146, and 1230.

Cause

Misconfiguration during upgrade, missing registry keys or files, or service account failures.

Solution

  1. Check cluster events in Failover Cluster Manager.
  2. Verify resource owner configurations by running Get-ClusterResource | Get-ClusterOwnerNode.
  3. Repair or re-create missing dependencies.
  4. Restart cluster services by running Restart-Service ClusSvc.

4. Quorum or communication loss

Symptoms

Cluster goes offline, nodes enter quarantine, or Event IDs 1135 and 1136 appear.

Cause

Network partition, firewall configuration, or quorum misconfiguration.

Solution

  1. Make sure that all required ports are open.
  2. Check network, DNS, and routing configurations.
  3. Check quorum settings by running Get-ClusterQuorum. Update settings as appropriate.
  4. To identify root causes, run Validate-Cluster.

5. Update failure or known bug

Symptoms

Cluster services stop responding after an update, or resources fail because of a known problematic update.

Cause

Cluster instability occurred after a Microsoft update installation.

Solution

  1. Review Microsoft Knowledge Base (KB) articles for known issues.
  2. Remove problematic updates, if it's necessary.
  3. Apply recommended hotfixes or wait for new updates.
  4. Open a support case if the issue remains unresolved.

6. Cluster validation or functional level errors

Symptoms

Can't update the cluster functional level, or validation fails.

Cause

Mixed OS versions, incomplete upgrades, or outdated drivers.

Solution

  1. Update all nodes, and make sure that they're joined to the cluster.
  2. Update hardware drivers (such as network and storage) and firmware.
  3. Complete the upgrade by using Update-ClusterFunctionalLevel.
  4. Review logs for driver or validation failures.

Advanced troubleshooting and data collection

For persistent or complex issues, collect the following data.

Cluster logs


Get-ClusterLog -TimeSpan 24:00 -Destination

System and application event logs

    
    Get-WinEvent -LogName System -MaxEvents 1000 | Export-Csv <Path>\SystemLogs.csv
    Get-WinEvent -LogName Application -MaxEvents 1000 | Export-Csv <Path>\AppLogs.csv
    

Resource and node status

   
   
    Get-ClusterNode
    Get-ClusterResource
    Get-ClusterGroup
    Test-Cluster
    

Network and driver information

    
    Get-NetAdapter -IncludeHidden | Export-Csv <Path>\NetAdapters.csv
    

Update history


Get-HotFix | Export-Csv \Hotfix.csv

References

Source: Microsoft Learn / IT Pro troubleshooting by Microsoft and contributors. Documentation licensed CC BY 4.0. Code samples are covered by the MIT License. Converted from Markdown, with links normalized and embedded media omitted.

资料来源与适用范围

资料来源
Microsoft Learn / IT Pro troubleshooting
适用范围
See source applicability · Source date 02/12/2026
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY 4.0 (documentation), MIT (code samples)

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。