0
I have a lab setup on Hyper-V 2016. It was a few servers and two Domain Controllers. I had some issues with the host and noticed that my vm's rebooted randomly with a message unable to connect to VM Storage. The storage was a storage group with 2 1TB HDD's and 4 256 SSD's. I assumed that the Disk IO was just too much and caused the issue so to remove some of the IO load, i removed all the snapshots. (Big Mistake!)
I connect to the lab today and both domain controllers are unbootable, looks like they ungracefully shutdown during a windows update - the bit preboot.
Tried a couple of reboots, a fix about deleting pending.xml but can't get either of them to boot.
Is there anyway to recover a domain controller with no backup, just with access to the hard disk?
You could look at running SFC/ DISM from a recovery disk, see if that is able to detect the discrepencies and correct them. Best of luck with it, thankfully worst case scenario it was a lab! There may also be a way to transfer the sysvol folder? I will have a look. Very bodgy I imagine, but again its a lab and its your last controller. – Lister – 2017-02-01T19:24:09.503
Ye, as its a lab its not important - main thing i've learnt is to not use Storage Spaces with HDDs and SSD's very buggy... In the middle of backing up and changing to just normal fixed disks. Will try recovery later today or tomorrow. – leinad13 – 2017-02-02T13:29:10.050