Quantcast
Channel: VMware Communities: Message List - ESXi
Viewing all articles
Browse latest Browse all 28826

Re: Could not power on VM : Invalid metadata - storage

$
0
0

Hi,

My problem still persist. So I have installed extra Buffalo NAS with ISCSI connections. My configuration is now :

ESX1 server with local store

ESX2 server with local store

Both servers are HA ( cluster )

DELL MD3000 storage system connected via ISCSI

Buffalo NAS connected vi ISCSI.

ESX1 and ESX2 can view both storage systems.

 

I tested and move few VM to new NAS storage Buffalo. Everything was working perfectly ( shutdow, migrating from one host to other, turn on /off .... ). So I think there is problem in old store on DELL MD3000. Then I test copying VM from old store ( DELL ) to local store of ESX1. The procedure was OK. But when I try to copy VM back to old store ( DELL MD3000 ) error accured :

Error caused by file [esx1-Localstorage] hist/hist_analyzer.vmdk

Task : copy file

For other files the copy procedure was sucesfully, except for vmdk file ( cca. 41 Gb ). And I have enought space on store. So I have to copy file to new store ( buffalo ). This procedure was OK.

I run the same procedure from ESX2 and it was OK. I can copy from old store to local store of ESX2 and via verca.

I have also find the error log ( the store with problems is named VM_store - there are saved VM ) :

 

At least one corrupt resource metadata region was detected on volume 4d1c7cab-1c64ceea-1298-0010188b4918 (VM_Store). Other regions of the volume might be damaged too.

error

9.8.2013 13:40:15

esx2.xxxx.local

 

The same error is also for esx1.xxxx.local

 

From this logs I asume that something is wrong with VM_store ( on DELL MD3000) and the best way is to recreate it ( I think so). But before I do this I have a doubt.

- why everything work on ESX2 when they share the same store ( with ESX1 ) if there is problem with VM_store ? You can copy , migrate, turn on / off VM without any problems.

- why can I copy VM from VM_store to local store of ESX1 but via verca I can not ?

- the true is when I moved VM to new ( Buffalo ) storage everything worked OK.

- could be problem on ISCSI conected from ESX1 to DELL MD3000 ?

 

Regards, Alan


Viewing all articles
Browse latest Browse all 28826

Trending Articles



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