Summary
In a failover cluster, virtual machines can use Cluster Shared Volumes that are on the same LUN (disk), while still being able to fail over (or move from node to node) independently of one another. Virtual machines can use a Cluster Shared Volume only when communication between the cluster nodes and the volume is functioning correctly, including network connectivity, access, drivers, and other factors.
Event Details
Event ID: | 5123 |
Source: | Microsoft-Windows-FailoverClustering |
Symbolic Name: | DCM_EVENT_ROOT_CREATION_FAILED |
Message: Cluster service failed to create the Cluster Shared Volumes root directory '%2'. The error message was '%1'.Search System Error Codes ( http://go.microsoft.com/fwlink/?LinkId=83027).
|
Causes
This was due to the cluster identity does not have the sufficient privileges.
Resolutions
CSV - Check CSV folder creation and permissions
There was a problem with creating or setting permissions for a folder (directory) needed by Cluster Shared Volumes. These folders have names in this format:
[systemdrive]\ClusterStorage\[volumename]
Where [systemdrive] is the drive letter of the boot disk on a local node, and [volumename] is the name of the volume in Cluster Shared Volumes. An example of a folder name would be C:\ClusterStorage\volume1.
If you do not currently have Event Viewer open, see "Opening Event Viewer and viewing events related to failover clustering." If the event contains an error code that you have not yet looked up, see "Finding more information about error codes that some event messages contain." After reviewing event messages, choose actions that apply to your situation:
Review the System and Application event logs for events indicating a problem with the storage or the disk, or any events related to creating directories or setting permissions.
If the [systemdrive]\[ClusterStorage] folder was created on a local node before Cluster Shared Volumes was enabled, stop the Cluster service on that node, delete the \ClusterStorage folder, and restart the Cluster service.
To perform the following procedures, you must be a member of the local Administrators group on each clustered server, and the account you use must be a domain account, or you must have been delegated the equivalent authority.
Opening Event Viewer and viewing events related to failover clustering
To open Event Viewer and view events related to failover clustering:
If Server Manager is not already open, click Start, click Administrative Tools, and then click Server Manager. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
In the console tree, expand Diagnostics, expand Event Viewer, expand Windows Logs, and then click System.
To filter the events so that only events with a Source of FailoverClustering are shown, in the Actions pane, click Filter Current Log. On the Filter tab, in the Event sources box, select FailoverClustering. Select other options as appropriate, and then click OK.
To sort the displayed events by date and time, in the center pane, click the Date and Time column heading.
Finding more information about the error codes that some event messages contain
To find more information about the error codes that some event messages contain:
View the event, and note the error code.
Look up more information about the error code in one of two ways:
Search System Error Codes ( http://go.microsoft.com/fwlink/?LinkId=83027).
Click Start, point to All Programs, click Accessories, click Command Prompt, and then type:
NET HELPMSG errorcode
Verify
Confirm that the Cluster Shared Volume can come online. If there have been recent problems with writing to the volume, it can be appropriate to monitor event logs and monitor the function of the corresponding clustered virtual machine, to confirm that the problems have been resolved.
To perform the following procedures, you must be a member of the local Administrators group on each clustered server, and the account you use must be a domain account, or you must have been delegated the equivalent authority.
Confirming that a Cluster Shared Volume can come online
To confirm that a Cluster Shared Volume can come online:
To open the failover cluster snap-in, click Start, click Administrative Tools, and then click Failover Cluster Manager. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Yes.
In the Failover Cluster Manager snap-in, if the cluster you want to manage is not displayed, in the console tree, right-click Failover Cluster Manager, click Manage a Cluster, and then select or specify the cluster that you want.
If the console tree is collapsed, expand the tree under the cluster you want to manage, and then click Cluster Shared Volumes.
In the center pane, expand the listing for the volume that you are verifying. View the status of the volume.
If a volume is offline, to bring it online, right-click the volume and then click Bring this resource online.
Using a Windows PowerShell command to check the status of a resource in a failover cluster
To use a Windows PowerShell command to check the status of a resource in a failover cluster:
On a node in the cluster, click Start, point to Administrative Tools, and then click Windows PowerShell Modules. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Yes.
Type:
Get-ClusterSharedVolume
If you run the preceding command without specifying a resource name, status is displayed for all Cluster Shared Volumes in the cluster.
Home
ENU