Cluster Shared Volumes root directory 'C:\ClusterStorage' already exists

CaseWhen placing a Hyper-V cluster node in drain mode and then bringing the node back online (re-join), you may come across the following warning message: Cluster Shared Volumes root directory 'C:ClusterStorage' already exists. The directory 'C:ClusterStorage' was renamed to 'C:ClusterStorage.000'. Please verify that applications accessing data in this location have been updated as necessary.At the same time you observe that a temporary new folder C:ClusterStorage.000 has been created as shown below. You observe that the ClusterStorage.000 volumeThe above may occur on more than one Hyper-V hosts and may create outdated copies of more than one subfolders underneath the Cluster Shared Volume (CSV) volumes (cluster disks). For example for VM named VM001, you may have two copies of the "Virtual Machines" folder, one in C:ClusterStorage and one in C:ClusterStorage.000. You observe that the file copies under C:ClusterStorage.000 are outdated and that the synchronized copy exists under C:ClusterStorage.SolutionRoot cause analysisThe most probable cause of the issue is the Windows Failover Cluster (WFC) service. During the WFC service start, the service will try to create/delete or find a CSV$ share in the C:ClusterStorage folder. By design, if the WFC service fails to complete this operation and is unable to place a handle on the CSV volume, a new folder will be created, such as C:ClusterStorage.000, C:ClusterStorage.001, etc. Failure to read the CSV$ share can occur for a number of reasons, with most common reason being that the WFC did not have permissions to access the C:ClusterStorage folder at start time. Other third party applicaitions, such as Antimalware and/or backup agents may place handles on the C:ClusterStorage folder and this could be the reason why the WFC service is not able to access it. Another common reason is that there is temporary network disruption during WFC service startup and therefore the service momentarily cannot access the CSV$ share.Action itemsFirst of all, place the Hyper-V host in question in drain mode and then reboot the host. Afterwards, place the server back to online mode in the WFC cluster and verify operations of the server and all associated VMs. At this point, refresh also the WFC logs to ensure there is no other error/warning. If all operations are running without issues, then it is ok to proceed with below steps. If there are other cluster errors, investigate and resolve these errors first, before moving on with below steps. Take ownership of the C:ClusterStorage.000 folder and all its subfolders recursively. To accomplish this, open a command line prompt and enter following commands.takeown /F "C:ClusterStorage.000" /Ricacls "C:ClusterStorage.000" /grant :F /TTakeown commandicacls commandAfter having taken full control of the C:ClusterStorage.000 folder and all of its subfolders, it is now safe to delete this folder and all subfolders.Hyper-V cluster troubleshootingFor more details on troubleshooting Hyper-V cluster issues, refer to the following article: https://stefanos.cloud/kb/how-to-troubleshoot-hyper-v-cluster-issues/Sourcehttps://social.technet.microsoft.com/Forums/en-US/8724c469-2692-4553-9603-17a1be350ce7/cluster-crash-now-have-clusterstorage000-folder?forum=winserverhyperv
https://stefanos.cloud/kb/cluster-shared-volumes-root-directory-cclusterstorage-already-exists/

Comments

Post a Comment

Popular posts from this blog

Acronis Cyber Protect 15 virtual machine backup not working when using shared mode virtual disks vhds

Image
Case When you apply and run an Acronis Cyber Protect backup against a virtual machine which is part of a guest cluster which makes use of virtual disk shared files of type .vhds (VHD Set), you run across the following error. Activity succeeded with warnings. Activity 'Preparing for backup of virtual machine' succeeded with the following warning 'Windows error: (0xC05CFF0A). The requested operation cannot be performed on the virtual disk as it is currently used in shared mode. Or the error may state something along the lines of: "Failed to open virtual disk file '.vhds'. Unknown format of the virtual disk." The same error as above can occur in virtual machine backup of virtual machines which include a .vdhx shared disk. Solution The above error is by design when you are attempting a virtual machine backup to virtual machine which does not have an Acronis backup agent installed, as per https://kb.acronis.com/content/68573 . According to Acronis, as of July 2
Read more

How to perform hardware health checks in Windows

Image
Case You need to perform an overall hardware health check in a Windows machine, running either a Windows client or a Windows Server operating system. This article provides guidance on the steps to carry out to perform hardware health checks in Windows. Solution Carry out the steps below. - Thoroughly check all Windows event logs (Application, System, Security) for any warnings or errors which may be related to issues you are experiencing with your Windows machine. - Check the device management mmc console by running devmgmt.msc. Ensure that you choose to show all hidden devices from the View menu. If you notice any exclamation marks next to any device, you will need to re-install its driver from the respective manufacturer to ensure that there afterwards no warnings in the device management console. - Check the health of all your disks , either HDD or SSD. Follow instructions in the following KB article for steps to follow to check your disk health: https://stefanos.cloud/kb/how-to-ch
Read more

How to resolve Group Policy error codes 8007071a and 800706ba

Image
Case You are running "Group Policy Update" on an OU inside the Group Policy Management Console in Active Directory but you are receiving RPC errors from your servers or domain-joined workstations, as shown in the example below. After a Group Policy Update, you come across Group Policy error codes 8007071a and 800706ba. This means that the local Windows Firewall is not configured properly to allow Group Policy (GPO) traffic. GPO traffic an be either remote GPO update or remote GP Resultant Set of Policy (RSOP) operations. Solution Option 1 Run gpedit.msc and create a new local group policy object which implements the following policies under Local Computer Policy --> Computer Configuration --> Windows Settings --> Security Settings --> Windows Defender Firewall --> Inbound Rules : The full configuration is shown below. After the above local group policies are configured on each domain server and workstation, you can start applying group policy objects to the dom
Read more