VM failed to start

[lostsoul]

Hi people

 

In real need of some help with this one. Had power outage last night, and now our moodle server vm wont boot. Have backup of all moodle data, but not the machine, want to avoid rebuilding if I can help it.

 

 

All files seem to be in the correct locations. Could permissions be corrupt? Google has not revealed much, any ideas?

 

Thanks

 

Nathan

[round2it]

Do gpupdate /force

 

Sounds stupid but one of my vms would not spin up until I did it.

 

Worth a go

[kevin_lane]

i've had something similar to this i couldn't sort it but i think it has something to do with the permissions of the server i.e the host vm does have access to start the vm that being said your disks should be ok and you should be able to create a new vm and just attach the disk

[rob_coles]

Delete the vm and attach the existing disk. Only way I could resolve same error

[lostsoul]

Thanks for the ideas. I was going to go with the new VM idea and attach existing disk, but this is a efi gen 2 vm, so unfortunately it's not that simple. Will pick it up in the morning, and let you know how I get on.

[round2it]

how did you get on

[TwistedHelixis]

Never having needed to do this, why is it a problem to attach a GEN 2 disk???

[kevin_lane]

Not being rude but it is a gen 2 vm your adding the gene disk to yea?

[glen_j]

had something similar could be a permissions problem give this a try https://support.microsoft.com/en-gb/kb/2249906

[lostsoul]

Sorry for not updating sooner. The issue was that the gen 2 machine was using uefi, and the boot info is stored on the uefi firmware of the virtual machine. If you attach the disk to a new vm, it will fail to boot. This is fixable by using a rescue disk to rewrite the boot information to the new VM.

 

After working that bit out, found another problem. Turns out this moodle vm had a long chain of snapshots. With the VM dead I had to redo the chain, and then merge the snapshots manually. After doing that the disk would still not boot, was getting kernel panic messages.

 

In the end I manually rebuilt the server, all back up and running now:). Important lesson learnt, don't use hyper-v snapshots in production!

[cpjitservices]

Have you got more than one Hyper-V server if so you could always enforce replication.

[kevin_lane]

Or use veeam glad your back up and running