- Joined
- Nov 28, 2001
Looks like something went bonkers in my ESXi box and I'm going to re-install everything fresh with a slightly different config to better suit my future networking setup. But hey, maybe someone has experienced this before and might have some idea what I should try to adjust before I go and redo the whole machine.
Symptoms: ESXi management IP is pingable, but none of the VMs are. Cannot connect to anything on the ESXi host, including the host itself.
This problem will randomly popup, and hours later, randomly go away. When this first started, it was only the VMs that would have trouble accessing the network and each other, then eventually within days it escalated to the current point of a seemingly locked up ESXi box.
Cause: No idea, but it did start to give trouble after I had to redo my ZFS setup because the pool was set to ashift=9 instead of 12, and the replacement drive could not be used as a replacement untill I redid the pool with ashift=12.
Because of redoing the ZFS pool, I had to move everything stored on the ZFS pool off, which included the VMs that were installed on it. I did a simple copy from the ZFS pool to the ESXi boot drive/storage, redid my ZFS setup, then moved a couple of the VMs back to the ZFS pool. Everything seemed ok at first, except for the random network drops in the VMs. I tried all kinds of different fixes in the various VMs to try and cure the problem (removing the NIC and reinstalling in the VM, redoing the IP addresses, redoing the vSwitch and vNICs in ESXi, etc), and the problem only seemed to get worse. I was doing a re-install on one of the VMs to see if that would solve the problem (I was thinking that something in the VM OS got corrupted) and it locked up again with the same issue; ESXi management IP pingable, but nothing else worked.
Only causes I can think of are:
a)ESXi boot/storage drive is going belly up and possible corrupted some files or VMs.
b)During transferring the VMs to and fro, something got corrupted which is affecting the whole system, even ESXi itself.
c)Something in the network side of ESXi is really really fubared (for whatever reason) which is causing all the issues.
Anyone ever have this issue or some possible reason/resolution?
Symptoms: ESXi management IP is pingable, but none of the VMs are. Cannot connect to anything on the ESXi host, including the host itself.
This problem will randomly popup, and hours later, randomly go away. When this first started, it was only the VMs that would have trouble accessing the network and each other, then eventually within days it escalated to the current point of a seemingly locked up ESXi box.
Cause: No idea, but it did start to give trouble after I had to redo my ZFS setup because the pool was set to ashift=9 instead of 12, and the replacement drive could not be used as a replacement untill I redid the pool with ashift=12.
Because of redoing the ZFS pool, I had to move everything stored on the ZFS pool off, which included the VMs that were installed on it. I did a simple copy from the ZFS pool to the ESXi boot drive/storage, redid my ZFS setup, then moved a couple of the VMs back to the ZFS pool. Everything seemed ok at first, except for the random network drops in the VMs. I tried all kinds of different fixes in the various VMs to try and cure the problem (removing the NIC and reinstalling in the VM, redoing the IP addresses, redoing the vSwitch and vNICs in ESXi, etc), and the problem only seemed to get worse. I was doing a re-install on one of the VMs to see if that would solve the problem (I was thinking that something in the VM OS got corrupted) and it locked up again with the same issue; ESXi management IP pingable, but nothing else worked.
Only causes I can think of are:
a)ESXi boot/storage drive is going belly up and possible corrupted some files or VMs.
b)During transferring the VMs to and fro, something got corrupted which is affecting the whole system, even ESXi itself.
c)Something in the network side of ESXi is really really fubared (for whatever reason) which is causing all the issues.
Anyone ever have this issue or some possible reason/resolution?