Fatal error: 33 (Inconsistent data) Posted on 2019/02/04 by Kyle McDonald — 1 Comment ↓ After a recent power outage that lasted longer than my UPS runtime, I found that one of my ESXi hosts wasn’t online. Fatal error: 33 (Inconsistent data) Posted on 2019/02/04 by Kyle McDonald — 1 Comment ↓ After a recent power outage that lasted longer than my UPS runtime, I found that one of my ESXi hosts wasn’t online. A quick look at the console screen showed that ESXi had attempted to boot and failed with Fatal Continue reading.
I have build a home server with the following hardware:
- Supermicro X10SLL-F
- Intel Xeon E3-1230v3
- 32 GB RAM
- Logilink firewire PCIe card
- Intel PRO/1000 PT dual port PCIe NIC
- 4GB USB stick to boot ESXI
The problem is that ESXi 5.1 will not boot when the machine is connected to the home LAN on any of the 4 available NICs!
The ESXi boot process starts and it will stop right after loading 's.v00' with a fatal error 33 (inconsistent data). If the network cable is not connected, this never happens and ESXi 5.1 boots like it should. The same happens when running the ESXi 5.1U1 installer (ISO downloaded from the VMware site)
I have tried different USB sticks, even installed ESXi on a harddrive, but always with the same result.
ESXi 5.5 does not give those errors, but this version is not usable for me, because the PCIe passthrough seems broken. VMs will not boot when the PCIe card is passed.
My workaround for now is that I unplug the network cable during the boot process and insert it once the boot process loaded all the files and the yellow screen appears. Always works, but would be nice to restart the server in a lights out environment without this hassle.
Paul.
Fatal Error 33 Inconsistent Data Sb.v00
One of the most annoying things about the vSphere Thick Client, is the fact that you cannot copy and paste things between your local computer and the VM by default. I know that VMware is pushing us to use the Web Client, but let’s face it, 95% of their customers are still using the Windows Client that they have become accustomed to.
For those customers, this one’s for you!
Esxi Fatal Error 33 Inconsistent Data
Esxi Fatal Error 33 Inconsistent Data
In order to enable Copy and Paste through the console, you will need add a custom config to EACH VM. (This is not a global setting).
Fatal Error 33 Inconsistent Data
- Edit the Settings of a VM using vSphere Thick or Web Client
- Select the Options > Advanced > General > Configuration Parameters
- Click Add Row for each of the following settings
Name: isolation.tools.copy.disable
Value: falseName: isolation.tools.paste.disable
Value: false - Click OK and reboot VM (or if set while VM is off, boot VM)
Comments are closed.