


Verify that this problem is caused by Symantec Endpoint Protection (SEP) 11.0 Release Update 5 (RU5). To resolve this problem, follow these steps: For example, this problem is known to occur after you install or migrate to Symantec Endpoint Protection 11.0 Release Update 5 (RU5) on the cluster nodes. This problem is known to occur when antivirus software that is not cluster-aware is installed, upgraded, or reconfigured. Error: 183.Ġ0000db0.00000868:: INFO Physical Disk : VolumeIsNtfs: Volume \?\GLOBALROOT\Device\Harddisk15\Partition1\ has FS type NTFS Cause Error 3Ġ0000db0.00000868:: WARN Physical Disk : OnlineThread: Failed to set volguid ?\Volume. Similarly, on a Windows Server cluster node you may see following entries are logged in the Cluster log:Ġ0000db0.00000868:: WARN Physical Disk : OnlineThread: Failed to get volume guid for device \?\GLOBALROOT\Device\Harddisk15\Partition1. ChkDsk may write information to the Application Event Log with Event ID 26180.ĭescription: Cluster disk resource 'Disk Q:' could not be mounted. If available, ChkDsk output will be in the file "C:\WINDOWS\Cluster\ChkDsk_Disk2_SigB05E593B.log". When this problem occurs, the following entries are logged in the Cluster log for the physical disk resource that entered the failed state:ĭiskspCheckPath: GetFileAttrs(Q:) returned status of 87.Ġ00020cc.000014d0:: WARN Physical Disk :ĭiskspCheckDriveLetter: Checking drive name (Q:) returns 87Īdditionally, the following events are logged in the System Event log:ĭescription: Cluster disk resource "Disk Q:" is corrupt. If you restart the cluster node that has the physical disk resource that did not come online, the problem is temporarily resolved. On a cluster node that is running Windows Server, a physical disk resource may enter the Failed state when you try to move a group that contains the physical disk resource. This article helps solve an issue where a physical disk resource doesn't come online on a cluster node.Īpplies to: Windows Server 2012 R2 Original KB number: 981475 Symptoms
