I destroyed some files in TFS using destroy command. I did not run command with startcleanup as I did not want any unnecessary problem at that time .
I restarted TFS in odd ours so that no one is working and the clean should take effect. I restarted it from Hyper-V Server so that there should be proper merging .
Hyper-V Server started merging snapshots as expected but suddenly after 50% merger Hyper-V crashed Server .
I did not know what happened because I was working on VPN.
I had to rush early morning to office so that I can fix everything before team comes.
I opened Hyper-V Server and in server manager when I tried to run any virtual machine-It said it could not locate .vhd file.
My drive( D://) was visible all .vhd files were visible but VM were not able to load them and in fact I was not able to copy and backup these .vhd files .
I thought I would restart Hyper-V Server and everything would be fixed .
But the D drive itself disappeared after I rebooted the server .
I was scared because I lost all the servers .
I and my colleague struggled a lot but no result .
We tried to look what happened to our drive. We went to dis management under computer management
We found that it was showing Disk 0 unknown with drive size and not initialized .
This point became more scary for us because people were saying that all the data would be lost if we initialize the disk.
SOLUTION: We checked the physical hard drives in my Hyper-V Server and in one of my Hard drive light was not blinking. We dragged that drive out inserted again and rebooted the system and everything became alright.
Thought what more can Happen to you : I suppose this was so easy for me because my hard disks were in RAID.
RAID mirrors the data in another hard drive and restores when its destroyed from other hard disk
It may not happen in your case if your hard disks are not in RAID
Even if they are in RAID, you may face another issue that your Hyper-V Server may start rebuilding the hard disk and it may take hours for that but finally everything would become okay. Fortunately it did not happen in our case .
){kind=link}