I'm having a strange issue & wondered if anyone else had seen the same.
we have 3 NAS servers (one is a fresh build) with a 3 Hyper-V Node cluster & 2 Hyper-V nodes not clustered currently (fresh build)
All VMs are stored currently on NAS01 & NAS02, we are trying to migrate to NAS03 from NAS02
If we try to move a VM's storage the following error happens
Move-VMStorage : Storage migration for virtual machine 'RSV09' (59C775B7-FBCB-4A5D-9A49-7B01F5E5C3C3) failed witherror 'The device is not ready.' (0x80070015).
Migration did not succeed. Mirror operation failed for the source VHD file
'\\rs-nas01b\VMs\RS-Infrastructure\RSV09\Virtual Hard Disks\rsv09_disk_1_5EF6FC1B-0F9A-4ADA-8972-7A7CA20EB051.avhd' to
the destination file '\\rs-nas03\VMs\Infrastructure\RSV09\Virtual Hard
Disks\rsv09_disk_1_5EF6FC1B-0F9A-4ADA-8972-7A7CA20EB051.avhd': 'The device is not ready.'('0x80070015').
The system cannot process the request at this time.
At line:1 char:1
+ Move-VMStorage rsv09 -DestinationStoragePath \\rs-nas03\VMs\Infrastructure\RSV09
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (Microsoft.Hyper...VMMigrationTask:VMMigrationTask) [Move-VMStorage], Virt
ualizationOperationFailedException
+ FullyQualifiedErrorId : Unspecified,Microsoft.HyperV.PowerShell.Commands.MoveVMStorageCommand
If we try to create a new VM this error happens
This only happens on the Data volume of the server, if we try to do it to the C drive (as a test) it works fine, some people have suggested security but I don't think that is the issue
The ACL's aren't identical but there are no deny permissions & the only difference is that on the one that isn't working I have explicitly allowed the computer accounts access to the problem share.
Again as a test I have added the 'Everyone' object to both share & NTFS permissions & granted full control, this hasn't had any affect.
I wondered if constrained delegation in AD might help but I don't know what to set & i can't see it being that given the C drive works but not D i would have thought that would have been a machine wide setting. We have even tried installing Hyper-V on the NAS in case that helped, it didn't.
now where it gets stranger... I have managed to move 3 VMs to the problem share, they failed initially with the same error but when I tried them the next morning the first 3 all worked but I haven't been able to move any others since.
If I manually copy the VM & then try to import it to Hyper-V I get the following VM: