Quantcast
Channel: VMware Communities : Discussion List - ESXi
Viewing all articles
Browse latest Browse all 8132

Object reference not set to an instance of an object

$
0
0

Need help!

 

ESX i4.0.0 208167

 

Found the VM was paused, with a big sign saying it doesn't had enough disk space. I shut the VM down then I deleted the *vmware*.log files, to make some space, at least to let it continue running. Now VM fails to boot. I googled for my problem and one of the suggestions was to remove the VM from the inventory and recreate using custom and point to .vmdk.

 

While trying to add .vmdk I get the following error message: Object reference not set to an instance of an object

 

I have been exploring the web and seems like my problem has to do with snapshoting. Yes, there were couple of snapshots I had taken in the past.

 

In Jan 2015 I had taken a complete backup of the folder in which VM files resided. So I do have the *vmware*.log files if they can be useful in troubleshooting this issue.

 

For illustration purposes:

hamza1.vmdk and hamza1_1.vmdk are the two base ( or main disks ) an I have

 

hamza1-00001.vmdk

hamza1-00002.vmdk

hamza1-00003.vmdk

and hamza1-00004.vmdk

 

I also have the 4 snapshot files hamza1-snapshot1.vmsn,...........hamza1-snapshot4.vmsn

 

In the virtual machine properties the hard disk1 path was pointing to hamza1-00004.vmdk.

In the virtual machine properties the hard disk2 path was pointing to hamza1_1-00002.vmdk

 

Hard disk1 is the windows 2003 boot disk which I need access to or probably boot to as it contains the data folder I am interested in recovering.

 

 

Sorry for a lame problem description. Please let me know what I need to attach/upload in order for someone to help. Or if there are any suggestions or KB articles already out there from other folks running into a similar problem?

 

 

Thanks,

Hamza


Viewing all articles
Browse latest Browse all 8132

Trending Articles



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