Windows server 2012R2 was upgraded locally to window server 2016 and added to the failover cluster, but there was an issue

2023-08-25T06:01:21.06+00:00

Windows server 2012R2 was upgraded locally to window server 2016 and added to the failover cluster. The disk with the storage link was suddenly disconnected, and after the disconnection, manual reconnection was successful. However, some of the linked disks may experience a repeated state of pending reconnecting ending. After the disconnection, most of the virtual machine link storage failed, resulting in downtime

Windows Server 2016
Windows Server 2016
A Microsoft server operating system that supports enterprise-level management updated to data storage.
2,362 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Limitless Technology 43,916 Reputation points
    2023-08-28T11:18:07.91+00:00

    Hello there,

    How was the upgrade made? Was it a clean install?

    Have you checked the Event Viewer for any trace?

    If you cannot find anything in Event Viewer I would suggest you use tools like Procmon to find the root cause for this behaviour.

    In Windows Server Failover Clustering, it's essential to use disks with resiliency features, such as shared storage, that can handle temporary disconnections without causing cluster failures.

    There is a Hotfix for this issue. Disconnection between storage and node in a Windows Server 2012 R2-based or Windows Server 2012-based cluster environment https://support.microsoft.com/en-au/topic/disconnection-between-storage-and-node-in-a-windows-server-2012-r2-based-or-windows-server-2012-based-cluster-environment-17462246-f445-1bf8-e07e-a7779fea10bd

    Hope this resolves your Query !!

    --If the reply is helpful, please Upvote and Accept it as an answer–

    0 comments No comments