Alistar's Posts

Then a vmkernel.log dump is neccessary to see what is going wrong - can you provide it?
Unfortunately using flash-based "pluggable drives" - USB Keys and Memory Cards as your local storage doesn't allow you to save state information to your host bydefault and that information is sav... See more...
Unfortunately using flash-based "pluggable drives" - USB Keys and Memory Cards as your local storage doesn't allow you to save state information to your host bydefault and that information is saved on a ramdisk, because the frequent writing to scratch directory would kill the storage pretty quickly. Although I was not aware it would also forget the state information for your ESXi host - maybe that is because the "default" scratch partition is set to be 4GB and the space on plugged storage is not large enough? Try this VMware KB for remediation and create a scratch partition yourself: VMware KB:    Creating a persistent scratch location for ESXi 4.x and 5.x
Hi guys, can you please check vmkernel.log for Machine Check Errors and post output of this? # grep MCE /var/log/vmkernel.log also a dump of vmkwarning.log would be helpful We had host... See more...
Hi guys, can you please check vmkernel.log for Machine Check Errors and post output of this? # grep MCE /var/log/vmkernel.log also a dump of vmkwarning.log would be helpful We had hosts crashing under random loads as well and eventualy it was pointing out to a hardware failure - this is 99% the case when an ESXi crashes on you without any PSOD.
Can you please describe the path from your ESXi host to the NFS server in more detail (NICs/LACP configuration if any/model, etc.)? Can you see any active connection from the ESXi on your array w... See more...
Can you please describe the path from your ESXi host to the NFS server in more detail (NICs/LACP configuration if any/model, etc.)? Can you see any active connection from the ESXi on your array when it has booted back up? Edit: There is a thread pretty similar to yours - maybe you can find some help there as well? Re: NFS datastores inactive after reboot
Can you ping the ESXi host while the datastore gets disconnected from it? Are the other VMs on the same array and if so are they somehow IO intensive? Are you using thin or thick provisioning on ... See more...
Can you ping the ESXi host while the datastore gets disconnected from it? Are the other VMs on the same array and if so are they somehow IO intensive? Are you using thin or thick provisioning on the storage/VMs? Is your MTU set to 9000 on the array, switch and vmkernel port (if you use jumbo frames)? Also, could you SSH to the ESXi, assume root privileges with su - (the dash must be there), and doing tail -f /var/log/vmkernel.log. Then just go through the process of VM creation and observe the output in SSH session and post a screenshot of it here? Cheers!
Hi there, with the feedback in this post so far I'd say this issue may be hardware related - is it possible for you to have a short downtime settings and disabling all power saving features in... See more...
Hi there, with the feedback in this post so far I'd say this issue may be hardware related - is it possible for you to have a short downtime settings and disabling all power saving features in BIOS? Such as: Intel SpeedStep C1E Enhanced Halt State And also set the power profile to Maximum Performance. Or maybe, since the guest has been running fine for some time, perhaps overheating might be an issue. Can you check the internals to ensure that the CPU heatsink is dust-free and airflow isn't blocked in any way? If you want to test that the CPU is performing correctly, try Intel Burn Test - this will give them a full whirl so you can see if you have solved the problem or not:) Cheers! - Ali