Changing virtual machine and witness disk storage within hyper-v failover cluster manager

Does the $clustername have full control on the remote share disk NTFS?
What are the share permissions?

on the parent folder on one of the cluster nodes (cluster storage) of the volumes:

ClusSvc (cluster service account) has special permissions

"virtual machines" account has permissions that are missing on the disks that I would like to switch to. This "virtual machines" account must have been used when the cluster was being setup, but I don't see that user account anywhere...

Where is FCM being run? On one of the cluster nodes or on a management machine/VM? If the latter, then Constrained Delegation needs to be set up for that management system to be allowed to pass the credentials used to open FCM on to the destination node.

Is the storage listed in FCM in C:\ClusterStorage\FolderName### ?

FCM is being run on cluster nodes (servers)...

On all nodes please post the results of:

Get-VMHost | fl VirtualHardDiskPath,VirtualMachinePath

Select allOpen in new window

First cluster server node
VirtualHardDiskPath : C:\ClusterStorage\Volume2\
VirtualMachinePath  : C:\ProgramData\Microsoft\Windows\Hyper-V

second cluster server node
VirtualHardDiskPath : C:\Users\Public\Documents\Hyper-V\Virtual Hard Disks
VirtualMachinePath  : C:\ProgramData\Microsoft\Windows\Hyper-V

Both nodes should be identical:

Set-VMHOST -computername Node1 -virtualharddiskpath 'C:\ClusterStorage\Volume2'
Set-VMHOST -computername Node1 -virtualmachinepath 'C:\ClusterStorage\Volume2
Set-VMHOST -computername Node2 -virtualharddiskpath 'C:\ClusterStorage\Volume2'
Set-VMHOST -computername Node2 -virtualmachinepath 'C:\ClusterStorage\Volume2

Select allOpen in new window

Ok, but at present this cluster is working fine, moving virtual machines between those two cluster nodes. But I need to move the virtual machines to a Volume5 disk, and that's where I am getting the permission error...

Are you moving both the VHDX and the configuration files to the same location?

yes, because the current host (storage) tends to reboot itself for some reason, and the iSCSI connections do not reconnect, but one of them stays in limbo...

It sounds like there's something else going on there than permissions.

Could you post events from the Hyper-V-VMMS  log?

Also check the other logs: https://blogs.msdn.microsoft.com/virtual_pc_guy/2009/02/03/looking-at-the-hyper-v-event-log/

Log Name:      Microsoft-Windows-Hyper-V-VMMS-Admin
Source:        Microsoft-Windows-Hyper-V-VMMS
Date:          4/24/2019 12:31:06 AM
Event ID:      20903
Task Category: None
Level:         Error
Keywords:      
User:          SYSTEM
Computer:      SRV02.domain.local
Description:
Failed to begin migration operation: the specified RASD not found 'Microsoft:514E647F-0279-4F28-A0C7-AA65858471B8\83F8638B-8DCA-4152-9EDA-2CA8B33039B4\1\1\L'.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Hyper-V-VMMS" Guid="{6066F867-7CA1-4418-85FD-36E3F9C0600C}" />
    <EventID>20903</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x4000000000000000</Keywords>
    <TimeCreated SystemTime="2019-04-24T04:31:06.741969500Z" />
    <EventRecordID>15254</EventRecordID>
    <Correlation />
    <Execution ProcessID="2732" ThreadID="4604" />
    <Channel>Microsoft-Windows-Hyper-V-VMMS-Admin</Channel>
    <Computer>SRV02.domain.local</Computer>
    <Security UserID="S-1-5-18" />
  </System>
  <UserData>
    <VmlEventLog xmlns:auto-ns2="http://schemas.microsoft.com/win/2004/08/events" xmlns="http://www.microsoft.com/Windows/Virtualization/Events">
      <Parameter0>Microsoft:514E647F-0279-4F28-A0C7-AA65858471B8\83F8638B-8DCA-4152-9EDA-2CA8B33039B4\1\1\L</Parameter0>
    </VmlEventLog>
  </UserData>
</Event>

where could I monitor the storage migration progress ?

apparently the migration started, even though I am not sure what I have changed except the permissions that I assigned yesterday

Well, we had to restart the storage server which became unresponsive this morning, maybe that's what was needed...

Hello

Did you modify your permissions at the level of the ctive directory?

Also validate that the events you indicated above do not appear in the event viewer.

I remain attentive to your comments

the migration of the storage succeeded. After applying permissions on the vm folders on the destination cluster disk, and storage server restart, the migration completed successfully.