Quantcast
Channel: VMware Communities: Message List
Viewing all articles
Browse latest Browse all 49146

Re: Unable to move VM to new datastore

$
0
0

Hi there,

 

Have you tried by changing the target format, i.e. thin to thick if you are using these. Given it's going to NFS this might already be happening.

 

Another thing you could try is to use VMware converter. Might not have any better fortune but there are a couple of options you could try:

 

  1. "Convert" the VM by using block level (the default)
  2. "Convert" the VM by reducing the size of the disks which switches you to file level

 

You might have some fortune by trying this as if its a block level issue which doesn't contain data then it might move round it. On that note you could also try a chkdsk /f within the VM on all the drives to see if the inconsistency can be flagged at an OS level.

 

Also is the source VMFS? If then try this from the ESXi shell:

voma -m vmfs -f check -d /vmfs/devices/disk/<DiskId>

The DiskId needs to include the partition number with the device name, e.g. naa.00000000000000000000000000000703:3

 

If there are any inconsistency on the datastore then this will report them. Doesn't mean the VM is unrecoverable just a little more work


Viewing all articles
Browse latest Browse all 49146

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>