Problem
I have two running VM in a failed storage migration state on a cluster (scvmm plus seven hosts, all 2012r2, Equallogic iscsi SAN).
Looking at the storage folder dates this happened prior to the oldest VMM log entries so I cannot see the error messages.
The previous support is uncontactable.
I'd like to know how to get these VM back to the normal state and then investigate the cause.
1st VM
On what i think was the original LUN I have the VM XML files and the folder containing the bin and vsv files but no vhdx
On what i think was the target LUN I have another VM XML file with the same name and timestamp but the accompanying folder has no bin or vsv file, it does however have the vhdx
In VMM the server has job status failed, and if i look in the properties it thinks the vhdx is on the original LUN
In failover cluster manager the VM is not visible
In Hyper-V Manager the VM is running but the values on the tabs are None, Unknown, Unavailable, Load Failure, etc
On the host itself Get-VM shows Storage migration - synchronizing files and operational status of StorageMigrationPhaseTwo
2nd VM
Just like the 1st VM the apparent original LUN has the VM XML files and the folder containing bin and vsv and the apparent target LUN has another XML with same name and timestamp, no bin or vsv but has the vhdx
In VMM the server has job status failed, and if i look in the properties it thinks the vhdx is on the original LUN
In failover cluster manager the VM is running (locked)
In Hyper-V Manager the VM is running but the values on the tabs are None, Unknown etc like the 1st VM
On the host itself Get-VM shows Storage migration - synchronizing files and operational status of StorageMigrationPhaseTwo
Additional
I'm normally a VMWare guy, These servers are semi-production but with maintenance windows available, I can't find a detailed breakdown of the hyper-v storage migration process to determine where in the process these migrations failed
Once i'm comfortable in recovering these VM i will kick off a storage migration to see what happens, get error codes, and hopefully identify the cause but i would rather not start any until that point
Thanks
Ed