none of the answers was correct to my issue, indeed there are few issues but not related to powering on any VM after upgrade to 6.5
here was the problem: /bin/vmx I have just copied it from another good working host and viola ====> al vms are powering on now
thank you all
There is no log attached. Also attach hostd.log and vmkwarning.log as well.
I have few question to help understand the issue better:
1) Can you please let us know the hardware version of the VM
2) Is the issue occurring on all the VMs on the Host or select few?
sorry, I have attached all requested logs in this post. regarding:
1) Can you please let us know the hardware version of the VM
For example this one:
2) Is the issue occurring on all the VMs on the Host or select few?
yes this issue is happening to all VMs listed on this host
I have found a similar post but I don't understand how they resolved that issue
Did you upgrade VMFS version on datastores as well? Do your VMs have snapshots?
What is exact 6.5 build number you use?
I'd open a case with support if you haven't. According to some things I've seen like this
the host is out of space, which I've seen from an upgrade before, especially using the custom install isos. I've seen this with IBM blades after lenevo took over. I had to clear out a bunch of log files to get everything working.
As well it looks like your FreeNAS configuration is wrong as it reports unsupported block size
2018-03-27T14:13:06.435Z cpu3:66536)WARNING: ScsiPath: 4399: The Physical block size "65536" reported by the path vmhba64:C1:T0:L1 is not supported. The only supported physical blocksizes are 512 and 4096
2018-03-27T14:13:06.435Z cpu20:70089)WARNING: ScsiDeviceIO: 6462: The Physical block size "65536" reported by the device naa.6589cfc000000105b9d5a244d16123ac is not supported. The only supported physical blocksizes are 512 and 4096
2018-03-27T14:13:06.561Z cpu3:66536)WARNING: ScsiPath: 4399: The Physical block size "16384" reported by the path vmhba64:C1:T0:L2 is not supported. The only supported physical blocksizes are 512 and 4096
2018-03-27T14:13:06.561Z cpu20:70089)WARNING: ScsiDeviceIO: 6462: The Physical block size "16384" reported by the device naa.6589cfc000000e24c9affb92d101faab is not supported. The only supported physical blocksizes are 512 and 4096
2018-03-27T14:13:06.562Z cpu3:66536)WARNING: ScsiPath: 4399: The Physical block size "16384" reported by the path vmhba64:C1:T0:L2 is not supported. The only supported physical blocksizes are 512 and 4096
2018-03-27T14:13:06.562Z cpu20:70089)WARNING: ScsiDeviceIO: 6462: The Physical block size "16384" reported by the device naa.6589cfc000000e24c9affb92d101faab is not supported. The only supported physical blocksizes are 512 and 4096
2018-03-27T14:13:06.583Z cpu3:66536)WARNING: ScsiPath: 4399: The Physical block size "16384" reported by the path vmhba64:C1:T0:L2 is not supported. The only supported physical blocksizes are 512 and 4096
2018-03-27T14:13:06.583Z cpu20:70089)WARNING: ScsiDeviceIO: 6462: The Physical block size "16384" reported by the device naa.6589cfc000000e24c9affb92d101faab is not supported. The only supported physical blocksizes are 512 and 4096
2018-03-27T14:13:06.585Z cpu3:66536)WARNING: ScsiPath: 4399: The Physical block size "16384" reported by the path vmhba64:C1:T0:L2 is not supported. The only supported physical blocksizes are 512 and 4096
2018-03-27T14:13:06.585Z cpu20:70089)WARNING: ScsiDeviceIO: 6462: The Physical block size "16384" reported by the device naa.6589cfc000000e24c9affb92d101faab is not supported. The only supported physical blocksizes are 512 and 4096
It's more than likely your datastores couldn't be mounted at the moment.
And according to these messages, probably you run ot of space on datostore named - FreeNAS-MAIN
2018-03-27T14:08:32.146Z info hostd[ECC1B70] [Originator@6876 sub=Hostsvc.VmkVprobSource] VmkVprobSource::Post event: (vim.event.EventEx) {
--> key = 70399,
--> chainId = 791707782,
--> createdTime = "1970-01-01T00:00:00Z",
--> userName = "",
--> datacenter = (vim.event.DatacenterEventArgument) null,
--> computeResource = (vim.event.ComputeResourceEventArgument) null,
--> host = (vim.event.HostEventArgument) {
--> name = "vmhost6",
--> host = 'vim.HostSystem:ha-host'
--> },
--> vm = (vim.event.VmEventArgument) null,
--> ds = (vim.event.DatastoreEventArgument) {
--> name = "FreeNAS-MAIN",
--> datastore = 'vim.Datastore:58768d13-263d8429-65a7-a0369f1464a8'
--> },
--> net = (vim.event.NetworkEventArgument) null,
--> dvs = (vim.event.DvsEventArgument) null,
--> fullFormattedMessage = <unset>,
--> changeTag = <unset>,
--> eventTypeId = "esx.problem.scsi.device.thinprov.atquota",
--> severity = <unset>,
--> message = <unset>,
--> arguments = (vmodl.KeyAnyValue) [
--> (vmodl.KeyAnyValue) {
--> key = "1",
--> value = "naa.6589cfc000000105b9d5a244d16123ac"
--> },
--> (vmodl.KeyAnyValue) {
--> key = "2",
--> value = (vim.event.DatastoreEventArgument) {
--> name = "FreeNAS-MAIN",
--> datastore = 'vim.Datastore:58768d13-263d8429-65a7-a0369f1464a8'
--> }
--> }
--> ],
--> objectId = "58768d13-263d8429-65a7-a0369f1464a8",
--> objectType = "vim.Datastore",
--> objectName = "FreeNAS-MAIN",
--> fault = (vmodl.MethodFault) null
none of the answers was correct to my issue, indeed there are few issues but not related to powering on any VM after upgrade to 6.5
here was the problem: /bin/vmx I have just copied it from another good working host and viola ====> al vms are powering on now
thank you all
regarding FreeNas I am disabling Disable Physical Block Size Reporting which should fix the above errors - no need to change anything else
I have noticed after restarting the host I have to recreate VMX file every time - is there any better option to that?