VM is crashed and data is scattered

Let me see if I understand this,

1. The machine ran out of space due to a copy that exceeded the disk capacity and the machine would not boot.
2. So you moved the VHD to another area of the server? Now you have the VHD residing on more than one drive on the server?

Or please correct me?

Yes you are right, Now i have more than one copy of VM and I dont know on which copy it is running?

what are you using ESX or Hyper-V?


VMware = launch VMware Console
Hyper-V = Launch Hyper-V Manager

In any case, the easiest way to be able to tell is right click on the VM going to manage or settings, and view the Harddisk. you should be able to see the location right there.

Hyper-V, Yes I already checked it. Its showing another drive but I am afraid. Is there any possibility that causes any problem to VM.

is this VM currently running or is it still offline?


IF VM is OFFLINE and will not boot:
If it is still offline I would take another copy of the VHDX and store it somewhere safe. Then I would increase the disk space on the failed VM by expanding the drive. After which I would see if the VM would boot.

IF VM is in a Running state or will boot:
If the VM is online, then the drive you see in Hyper-V manager is the active drive and is functioning properly. I would backup the OLD VM VHDX and then move the existing running VHDX to the same container that the machine is in.
(NOTE DO THIS AFTER HOURS) if it is a production machine as it will require a reboot

It will not hurt the VM if the drives are in two different locations on the same physical box.
IE.
If the C: Drive is in a location like c:\Virtual Machines\ServerName\disks\cdrive.VHDX

if the D:\Drive is in a location like s:\Virtual Machines\ServerName\disks\D_drive.VHDX

As long as the Management Utility in Hyper-V manager reflects the location of the files the Host doesn't care where the drives are located as long as permissions are set appropriately for access to the VHDX file.

VM is currently running.

My big worries is now it has 2 copies of VMs and when I checked it its showing E: Drive. But  I allotted it D: drive (on Physical machine). I am assuming my colleague copied it on E: drive (Physical machine).  So if I format the D: drive (Physical machine) will it also affect the VM functioning.

The programs that was installed lets say AutoCad. Is showing on F: drive (Physical machine).

Its wierd situation VM is scattered over D:, E: and F: on (Physical machine)

Now I understand the issue:

You have a VM that crashed due to the Hard Drive running out of space.

You copied the VHDX for that VM to another server.

After which you most likely expanded the drive that was at capacity. Then remounted that drive in the "wrong Order"



If this is the case, then you could have serious application issues depending on what was on that drive. If it was just a data Drive, then you are probably ok. you just need to resync the data. If it houses application executables, then you would probably be better off rebuilding that server as you probably have several applications which are failing. If it is the OS partition I would probably recommend rebuilding the server as well.

Please correct me if this is not the case..

I think I didn’t explain my scenario properly. Let me explain it once again. Give me little time I am on the way. BTW thanks for ur suggestions. I will write it again

Here lets look at it this way:

Original Configuration :

• Server 1: VM that is down
  • Drive 1 c:\temp\c_drive.vhdx
  • Drive 2 c:\temp\d_drive.vhdx
  • Drive 3 c:\temp\e_drive.vhdx
• Current Configuration:
  • Server 1: VM that is down
  • Drive 1 c:\temp\c_drive.vhdx
  • Drive 2 s:\temp\d_drive.vhdx
  • Drive 3 v:\temp\e_drive.vhdx

Fill out the table that I submitted above. Doesn't have to contain server name just appropriate drive information. Also make note of copied information and where it was copied to.

Dear ITguy565, Many Many thanks, I figured it out by other means. But definitely your suggestion helps me alot.