zXi_Gamer's Posts

>Hi, >I switched the port on the switch and vMotion now work perfectly! The original port was configured as an uplink port. Make me look really silly right? So can I assume that your problem... See more...
>Hi, >I switched the port on the switch and vMotion now work perfectly! The original port was configured as an uplink port. Make me look really silly right? So can I assume that your problem has been solved after the above step HTH, zXi
Hmmm,. that is interesting. Like @dhabbetichandra noted, you may want to disconnect and add the storage again. Also, when I said, rescan, I wanted to mention on the storage adapters, not on the s... See more...
Hmmm,. that is interesting. Like @dhabbetichandra noted, you may want to disconnect and add the storage again. Also, when I said, rescan, I wanted to mention on the storage adapters, not on the storage, my bad. Also, if you do not have data on your datastore2, you can delete the datastore2 and click on Add storage and add Datastore2 again. Since I do not have your logs to find out the reason for the input/output error, my bet would be on the storage controller has a lock on the drive and is not released yet. This could have happened during adding of datastore2 or datastore2 is being used by any RDMs.. HTH, zXi
Can you make sure that you can write to Datastore2 by touch /vmfs/volumes/Datastore2/Sample Also, a rescan might tell you if the storage is still detected from the controller and is lost
Is your Ext HDD detected by your host??. Can you check by lsusb? btw, can you tell us which ESX are you using 5.0 or 4.x ESXi HTH, zXi
I just wanted to confirm if your ESX are all of same version. i.e 5.0 or 4.X. The reason I am asking is that when I look at the logs, I wanted to confirm if you have enabled any 5.0 feature on a ... See more...
I just wanted to confirm if your ESX are all of same version. i.e 5.0 or 4.X. The reason I am asking is that when I look at the logs, I wanted to confirm if you have enabled any 5.0 feature on a VM that is not supported on 4.X ESX, and hence the Vmotion might fail, if you are migrating from 5.0 to 4.X with a feature of 5.0 in a VM. HTH, zXi