asked on
vmdk empty after resizing Esxi 4.1
Hello,
We run out of space in 2 disks of a virtual machine (Windows Server 2008) that we have on a ESXI 4.1.
We looked in the VMWare Database for instructions on how to resize the vmdk files. We followed to the letter (removing the snapshots, applying the -X resize command) and it completed correctly. We did this with both disks (they were data disks, no OS disks).
After booting the VM, we found that the disks were empty!
We don't have an entire backup of the data (yeah, we know) and we tried to install programs to look for the data in the VM but found nothing.
Does anyone know if there is a way to recover this??
We run out of space in 2 disks of a virtual machine (Windows Server 2008) that we have on a ESXI 4.1.
We looked in the VMWare Database for instructions on how to resize the vmdk files. We followed to the letter (removing the snapshots, applying the -X resize command) and it completed correctly. We did this with both disks (they were data disks, no OS disks).
After booting the VM, we found that the disks were empty!
We don't have an entire backup of the data (yeah, we know) and we tried to install programs to look for the data in the VM but found nothing.
Does anyone know if there is a way to recover this??
VirtualizationDisaster RecoveryDatabasesVMware
Last Comment
Andrew Gates
ASKER
Hello Andrew,
First of all, thanks for the quick reply. Answering your questions:
- No, we didn't make a backup of the disks (we know, this was a great screw up).
- The vmdk files were there with the correct new size (the were 400GB and now 600GB).
- The disks were at NTFS and ok, but all the data inside of them is nowhere to be found (disk at 100% free space).
First of all, thanks for the quick reply. Answering your questions:
- No, we didn't make a backup of the disks (we know, this was a great screw up).
- The vmdk files were there with the correct new size (the were 400GB and now 600GB).
- The disks were at NTFS and ok, but all the data inside of them is nowhere to be found (disk at 100% free space).
so after the expansion the disk were still NTFS, and there should have been 200GB un-allocated ?
ASKER
Yes, and after the expansion they were (so I guess that the proccess was ok). The problem is that all the files in the disks were gone.
so did the files disappear, when the partition was expanded ?
ASKER
Yes, in both disks (.vmdk files)
if the files disappeared after the expansion of the OS partition, how did you expand the OS Partition in the OS ?
ASKER
We didn't expand the OS partition. The VM has:
- 1x 200GB vmdk (with OS partition).
- 2x 400GB (now 600GB with no files inside) vmdk (each of them only with data). These were the ones we expanded.
Sorry if I didn't explain myself correctly, I'm in a kind of nearly-heart-attack state.
- 1x 200GB vmdk (with OS partition).
- 2x 400GB (now 600GB with no files inside) vmdk (each of them only with data). These were the ones we expanded.
Sorry if I didn't explain myself correctly, I'm in a kind of nearly-heart-attack state.
Okay, so the VMDK wad expanded from 400GB to 600GB
and the 400GB OS Data Partition NTFS still is "as is" but with no files, so in Disk Management you should see 200GB unallocated ?
and the 400GB OS Data Partition NTFS still is "as is" but with no files, so in Disk Management you should see 200GB unallocated ?
ASKER
Exactly.
chkdsk on the volume does not spot anything irregular ?
ASKER
Nope. Also tried with a recovery software, but with no results.
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
Ok, will do that. Is there any other way?
I would hand over to experts.
ASKER
Ok, thanks for all the help anyway.
You made no backup before the changes ?
It might be worth, just try a VMware Conversion, and shrinking the disk back to the original size.
Was there a file system on the disk, after re-size ? What do you mean they were empty, not NTFS ?
you had to initialise the disk ? or did it state RAW ?
did you make sure you actually increased the disk, and not decreased the disk ?