HyperV VM Refuses to Power up Following a Power Loss in HyperV Cluter.

Goodnight,

If the vm can not turn on it can be for several reasons, one is that the files of the vm, have been corrupted or are damaged, first validate in the path where you store the vm, find the server folder that you can not turn on and validate if all your files are.

You can also validate the properties of the vm, check if you have all your disks connected together with their storage controllers (IDE or SCSI)

I do not recommend that you delete a configuration file.

Try to validate the points I am indicating and let us know the results.

Regards...

OK so the error I am getting is:
Event ID 21502
'Virtual Machine Configuration 'CREATIVE_FAP' failed to register the virtual machine with the virtual machine management service.

Event ID 1069
Cluster resource 'Virtual Machine Configuration CREATIVE_FAP' of type 'Virtual Machine Configuration' in clustered role 'CREATIVE_FAP' failed. The error code was '0x48f' ('The device is not connected.').

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.

Event ID 1205
The Cluster service failed to bring clustered role 'CREATIVE_FAP' completely online or offline. One or more resources may be in a failed state. This may impact the availability of the clustered role.

Event ID 1254
Clustered role 'CREATIVE_FAP' has exceeded its failover threshold.  It has exhausted the configured number of failover attempts within the failover period of time allotted to it and will be left in a failed state.  No additional attempts will be made to bring the role online or fail it over to another node in the cluster.  Please check the events associated with the failure.  After the issues causing the failure are resolved the role can be brought online manually or the cluster may attempt to bring it online again after the restart delay period.

I went into the following folder:
C:\ClusterStorage\Volume1\HyperV\CREATIVE_FAP-Clone-2017-05-08 22-03

And found bunch of AVHDX files which I assume are snapshots, perhaps from Altaro backup. The last file is:
creative_fap_78F9B7F5-BF10-4593-9D09-F08B3AB10299.avhdx

I tried to create a new VM and load this file into it instead of create a new VHDK.

I can also see the main "hard drive" file there.

Any suggestions on how to boot this dead VM?

I really appreciate your help.

Remove the VM from the cluster, delete the VM on the Hyper-V node that owns it, and then recreate a new HA VM and use the existing VHDX files.

A few tweaks for networking will need to be done post VM boot.

EDIT: Do not delete the VHDX files.

EDIT 2: Before doing the above, remove any and all DVD mounted ISOs and any other VHDX mounted via SCSI except the VM's own. The error indicates something may have been attached at one time that is no longer there.

Remove the DVD from the new VM or old? I have no access to the old, I cannot access its settings...

Merge the AVHDX files into the parent oldest to newest.

Then, create a new HA VM and bind the VHDX file(s) to it. Boot, fix the network setup.

That should do it.

Hello,

Create a new vm, and then connect the vhdx to this new vm and validate if it can turn on.

Do not delete the files of the vm that is causing problems, it is not recommended yet.

Status update please?

Good night

Status update please?

Hello

Could you perform the tests mentioned?

regards..