Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Thursday, October 18, 2018 9:46 PM
Hello,
hyper-v 2016 cluster volume folder appear in yellow Folder instead of cluster icon , in addition this folder empty , and if i try to live migrate any VM has storage on this folder from another host to this host it will fail .
i think is a permeation issue , the node cant brows all the volume with the right permissions...
Osama Yotman Systems Consultant
All replies (16)
Thursday, December 13, 2018 10:51 AM ✅Answered | 1 vote
Dears,
this issue were solved by install and Enable MPIO windows feature ( Multi-path input output )
Osama Yotman Systems Consultant
Thursday, October 18, 2018 10:42 PM
Hi,
There seems to be an issue here, as you have two "ClusterStorage" folders, I believe the "ClusterStorage.000" folder is created when a cluster node fails to access the CSV.
By default the cluster accesses the default path "C:\ClusterStorage", if there are any permission problems and the cluster can't access "C:\ClusterStorage\ then it will create a new folder "C:\ClusterStorage.000" which it can access.
How does your cluster environment look like, servers, storage?
You may also perform a cluster validation to check for any errors/warnings.
Best regards,
Leon
Blog: https://thesystemcenterblog.com LinkedIn:
Friday, October 19, 2018 12:10 AM
Hello,
thanks for your reply,
I m rolling out to 2016 , im in a Mixed environment Hyper-v Fail over cluster ( 2012/2016) , but this issue only with 2016 host server , the live migration fails if the VM within a voulme appear like folder to 2016 host.
in another hand , there is volumes look good and i had no issue in LM.
VMs within Volume1 has no issue with migration , but Volume2 cant migrate them, and the vhd folder gives me access denied on the folder level..
but its work pefectly on 2012 R2 ,
Osama Yotman Systems Consultant
Friday, October 19, 2018 10:26 AM
What is your result if you type the following command in a Command Prompt (Admin)
Dir C:\ClusterStorage
Blog: https://thesystemcenterblog.com LinkedIn:
Friday, October 19, 2018 11:16 AM
all the volumes are there
Osama Yotman Systems Consultant
Friday, October 19, 2018 11:24 AM
Sorry, I misstyped,
Dir "c:\ClusterStorage"
With the quotation marks.
Blog: https://thesystemcenterblog.com LinkedIn:
Friday, October 19, 2018 11:27 AM
same result
Osama Yotman Systems Consultant
Friday, October 19, 2018 11:28 AM
Do it in a Command Prompt
Blog: https://thesystemcenterblog.com LinkedIn:
Friday, October 19, 2018 11:34 AM
I have 9 nodes the each one have different corrupted folders
Osama Yotman Systems Consultant
Friday, October 19, 2018 11:43 AM
Yeah you can clearly see that Volume 2 is not a "JUNCTION" (a mountpoint), it is a "DIR" so it seems that the cluster is failing to create a mountpoint for some reason.
This could be due to lack of write/access permissions for the nodes, also check if you have any antivirus or backup software which could be causing "access violation".
Blog: https://thesystemcenterblog.com LinkedIn:
Friday, October 19, 2018 11:49 AM
Thanks for your clarification,
is there any standard for the permissions , and where i can set them if they are corrupted ??
the weird is the Same Server before format was working perfectly i just reformatted it to server 2016 all the policy remain same.
can i reset the permission to the best practice
Osama Yotman Systems Consultant
Friday, October 19, 2018 12:04 PM
Can you run the command below in a Command Prompt on the cluster node that is failing and list the result here:
Mountvol /L
Blog: https://thesystemcenterblog.com LinkedIn:
Saturday, October 20, 2018 10:35 AM
Possible values for VolumeName along with current mount points are:
\?\Volume{1c6ec430-0000-0000-0000-100000000000}\
** *** NO MOUNT POINTS *****
\?\Volume{1c6ec430-0000-0000-0000-501f00000000}\
C:\
\?\Volume{33ecaddc-e737-4551-a9f5-88cc8ad33c74}\
** *** NO MOUNT POINTS *****
\?\Volume{93a20086-e128-4641-8e34-e854833e8a21}\
** C:\ClusterStorage\Volume5\**
** C:\ClusterStorage.000\Volume5\**
\?\Volume{e634b315-486c-4c8f-b0ae-3d1e038f27da}\
C:\ClusterStorage\Volume8\
\?\Volume{9d2e91b7-7587-415e-b6bd-95a14cf7de21}\
C:\ClusterStorage\Volume12\
\?\Volume{9b239a70-bf2e-40b7-96c9-898dbf4fcd41}\
C:\ClusterStorage\Volume9\
\?\Volume{2e2e1ca7-94b6-46dd-b78a-d9c9bc664534}\
C:\ClusterStorage\Volume2\
\?\Volume{47565de4-2de5-4a9a-a1f9-c95aad5eb95a}\
C:\ClusterStorage\Volume6\
\?\Volume{32f02d6a-db8a-498d-8870-fc245b5b3356}\
C:\ClusterStorage\Volume15\
\?\Volume{dd3edde1-1f41-400e-89b9-140b87a557df}\
C:\ClusterStorage\Volume10\
\?\Volume{bd8b1f79-6c36-465b-8d64-d3b2ea8f1e9d}\
C:\ClusterStorage\Volume13\
\?\Volume{478dccf7-22b8-42ff-9363-e9ff654c0e8c}\
C:\ClusterStorage\Volume14\
\?\Volume{acd62c1f-d4a8-435a-98ec-0cc22a421cd3}\
C:\ClusterStorage\Volume11\
\?\Volume{1e2bc016-ae5d-4e17-8b83-f38c0ae33e15}\
C:\ClusterStorage\Volume1\
\?\Volume{e7e53ba5-70a8-4b2b-a39f-db48b15f709b}\
C:\ClusterStorage\Volume4\
\?\Volume{4e4c2447-2490-4631-bc78-0db0e164c447}\
C:\ClusterStorage.000\Volume7\
C:\ClusterStorage\Volume7\
\?\Volume{1eaa179d-5edf-4483-ad66-a45714397af9}\
C:\ClusterStorage\Volume16\
Osama Yotman Systems Consultant
Saturday, October 20, 2018 11:03 AM
As you can see one Volume 5 & 7 is marked twice:
\?\Volume{93a20086-e128-4641-8e34-e854833e8a21}\
C:\ClusterStorage\Volume5\
C:\ClusterStorage.000\Volume5\
\?\Volume{4e4c2447-2490-4631-bc78-0db0e164c447}\
C:\ClusterStorage.000\Volume7\
C:\ClusterStorage\Volume7\
On the problematic cluster node, could you also check the Microsoft\Windows\FailoverClustering log for any errors/warnings?
Also the cluster node that was reinstalled, are all the storage paths correct?
Blog: https://thesystemcenterblog.com LinkedIn:
Saturday, October 20, 2018 11:15 AM
All the error talks about and only
Error 2051
removing directory \?\C:\ClusterStorage\Volume3\ status 145
warning 2050
- Not a reparse point: C:\ClusterStorage\Volume3
- [DCM] DcmCreateDirectory: create of \?\C:\ClusterStorage\Volume3\ failed with error 183
- DCM] FSCTL_GET_REPARSE_POINT Failed 4390, \?\C:\ClusterStorage\Volume3\
warning 6286
- Failover Cluster WMI Provider could not retrieve the partition information for Cluster Shared Volume 'CSV3' because it was not online. Please make sure the volume is online before retrying the query.
Osama Yotman Systems Consultant
Monday, October 22, 2018 8:20 PM
Does the problematic cluster node see a Volume3? I don't see it listed in the Mountvol /L output.
But you stated that the problem is with Volume2, did you do a comparison of the permissions between a Windows Server 2012 R2 and a Windows Server 2016 cluster node?
Blog: https://thesystemcenterblog.com LinkedIn: