You do not see the cluster disk in explorer or diskmgmt on Failover in a Windows 2008 or Windows 2008 R2 Cluster

Applies to: Windows Server 2008 DatacenterWindows Server 2008 EnterpriseWindows Server 2008 R2 Datacenter


You failover the file share resource from Node A to Node B and the file share disk (example N:) doesn’t show up in the explorer or disk management console. We see following events as the drive letter got swapped during failover and the file share resource won't come online even if the dependencies of the files share i.e. disk and IP were online.

Log Name:      System
Source:        Microsoft-Windows-FailoverClustering
Event ID:      1588
Task Category: File Server Resource
Level:         Error
User:          SYSTEM
Cluster file server resource 'AdminData' cannot be brought online. The resource failed to create file share 'NAMEOF FILESHARE RESOURCE$' associated with network name 'NAMEOF FILESHARE RESOURCE'. The error code was '3'. Verify that the folders exist and are accessible. Additionally, confirm the state of the Server service on this cluster node using Server Manager and look for other related events on this cluster node. It may be necessary to restart the network name resource 'NAMEOF FILESHARE RESOURCE' in this clustered service or application.

We also see:

Log Name:      System
Source:        Microsoft-Windows-Kernel-Tm
Event ID:      1
Task Category: None
Level:         Information
Keywords:      None
User:          SYSTEM
The Transaction (UOW=%1, Description='%3') was unable to be committed, and instead rolled back; this was due to an error message returned by CLFS while attempting to write a Prepare or Commit record for the Transaction.  The CLFS error returned was: %4.

Log Name:      System
Source:        Microsoft-Windows-UserPnp
Event ID:      20010
Task Category: (7010)
Level:         Information
User:          SYSTEM
One or more of the Plug and Play service's subsystems has changed state. 
PlugPlay install subsystem enabled: 'true' 
PlugPlay caching subsystem enabled: 'true' 


This happens if you have a network drive mapped on the Node B with the same drive letter (i.e. N:) which was assigned to the cluster disk on the Active node.

This happens if you have the Mapped network drive assigned with the same drive letter which was held by cluster disk resource on the active node or on the node before failover. If there is the local hard disk with same drive letter then this issue doesn’t happen as the part manager assign the same drive letter by swapping it.


You will be able to see the disk with drive letter N: on Node B in explorer and disk management once you disconnect the mapped network drive. Even if you don’t disconnect the network drive the drive letter would be still accessible with share and also viewable with same drive letter N: under failover cluster MMC.

More Information

Failover Cluster Step-by-Step Guide: Configuring a Two-Node File Server Failover Cluster