Event ID 1254 and 1069.
I came across with issue of unable to start VM. The affected resource was Virtual machine configuration file was “lost”
The event shows that Event ID 1254 and 1069.
The details show that cluster roles failed to bring online.
(Cluster resource ‘Virtual Machine Configuration Test1’ of type ‘Virtual Machine Configuration’ in clustered role ‘Test1’ failed. The error code was ‘0x2’ (‘The system cannot find the file specified.’).
Based on the failure policies for the resource and role, the cluster service may try to bring the resource online on this node or move the group to another node of the cluster and then restart it. Check the resource and group state using Failover Cluster Manager or the Get-ClusterResource Windows PowerShell cmdlet.)
I had a storage controller outage and since they are redundant, the storage failover to standby controller. The failover went OK, and everything was running as it should be, except one HyperV cluster, among 3 other clusters and file servers.
So, the outcome was that machines couldn’t be powered on. Trying to repair via SCVMM was unsuccessful and that part of troubleshooting was unusable.
The log from failover console was just informative, with no suggestion what to do.
It just indicates that some configuration files could not be found.
As you can see from picture above, the VHDX is online but the configuration of VM is missing. If we try to power on VM you would get error like this:
If you have all VMs affected by this issue, it would be good to run CSV check disk.
On this site is nice how to achieve this link..
The easiest way is to import VM through HyperV manager console on Host itself, since most likely, you will have all what you need for importing VM.
The first step would be to remove VMs it from Failover console.
Please note that removing VMs from HyperV manager or Cluster Failover console does not delete the content of VMs, so VHDX and configuration files would be intact, and it you will be able to import them in HyperV manager console.
If you remove/delete VMs thorough SCVMM (System Center Virtual Machine Manager) it will delete all associated files (VHDX, configuration files, snapshots etc…)
So, the configuration files and VHDX files are present, and HyperV manager is smart enough to import them.
Navigate to C:\clusterstorage\*\ and click next.
After this step, you should be able to see your VMs and to be able to import it in HyperV manager console.
Next step is making imported VM Highly available in failover Cluster console.
Press Configure Role in failover management console.
New window will be displayed, click next and select from the list Virtual Machine
On next screen, you should be able to see your imported virtual machine and since its already on CSV, its ready to be highly available.
Now, you will be able to see your VM in Failover console.
If you can not solve the mentioned issue with this method, the last resort would be restoring backup or recreating VMs but using same VHDX.
Hope it will help someone.