S2D virtual disk’s Operational status and Health status after a node is restarted

Hi guys, 

Every time any of four nodes of the Windows Server 2016 Failover Cluster is restarted (even when put on pause and then gracefully restarted) an S2D virtual disk goes into Degraded, Incomplete status. 

When a node is back online after restart it’s Operation Status is In Service but Health status still Warning.

So every time this happens I need to run Repair-VirtualDisk -FriendlyName MirrorVolume1 to fix it which not only takes a lot of time to complete but also affects performance of all virtual machines which virtual disks are stored on that virtual disk.

My question is - should it be like that? I mean surely when a node is restarted there should be some impact on a virtual disk. But when a node is back online after restart should a virtual disk’s health be back to normal?


Read full post . . . .

Go Que Newsroom