I just bought myself a Dell Power edge T30 server a couple of weeks ago and the goal was to put ESXi on it and run one VM with pfSense and one VM with Win 2012 server.
The setup follows:
* ESXi ((Updated) Dell-ESXi-6.5.0-4564106-A01 (Dell)) - running on a USB stick (Sandisk Ultra Fit 16GB)
* 1x SSD drive divided in two partitions; one partition with pfSense and the second partition as the system disk of the Win 2012 server operating system.
* 3x Western Digital drives used for storage
* One I350-T4 Lenovo Ethernet adapter; 2 ports assigned to the pfSense VM (WAN and LAN), 1 port assigned to Win 2012 server VM
* Integrated NIC is used for administration of ESXi host
Everything works flawlessly so far BUT except one thing; when the machine has been running for approx. 3 days, it is inpossible to connect to the ESXi host and the VMs. It is like everything has been frozen.
* pfSense is dead since all internal network is offline (all my devices at home is disconnected, no IP released to the devices)
* Win 2012 server does not respond to remote desktop connection queries nor the web server installed on this VM.
* ESXi console is not possible to access; my TV connected to the computer does not receive any signal from the server. The Num Lock and Caps Lock is working on the keyboard connected to the machine (lamp is switching on and off when pushing the buttons) but the TV is still black. Even if I try any of the combinations Alt+F1, Alt+F2...
* When trying to access ESXi using Putty and SSH protocol, I am asked to enter the user name BUT when i enter my password correctly the SSH session closes?!
So the question is, why does my host freeze after 3 days? I have tried to find any information in the logs but I can't find anything useful. But I am kind of new to ESXi so I might have missed something.
What I have done so far to restart everything is to push the power button for 5 seconds - the server is powered off (hard reset) - push the power button and the server boot - VM boot and everything is back to normal. I know that this is not a good way to restart the machine but what to do? I cannot access anything on that machine during this "freeze-period". I am so worried about my data being corrupted by doing this.
So do you have any suggestions on how to proceed? Have you heard about this before?
See my logs below (the time when it got frozen is 2017-12-31 13:41 I think):