- Esxi Installer Fatal Error 33 Free
- Esxi Installer Fatal Error 33 1
- Esxi Installer Fatal Error 339
- Loading Esxi Installer Fatal Error 33
- Install Esxi 6.5
After a server restart the server fails to boot with Error loading /s.v00 Fatal error: 33 (Inconsistent data). The VMware knowledgebase would suggest reinstalling the ESXi OS. I don't have much information. Its a Dell Power Edge t410. Perc h700 adapter raid 5 with 2 virtual 1800 GB and 433.5 gb drives.
In some previous posts here at mobiletiger I explained how to use different ways to install ESXi, mostly to get a workaround for some N3150/J3160 systems, which „freeze their screen“ after outputting the message „relocating modules …“
|
1. Kickstart overview
I’m showing here, how to modify an ESXi ISO file, so that the installation runs completely automatically from USB.
This can be used in principle on all systems, of course also on the above described or on „headless systems“ without connecting a display.
This can be used in principle on all systems, of course also on the above described or on „headless systems“ without connecting a display.
To get a complete overview or to get a detailed list of installation methods and commands, please read the original document from vmware:
https://pubs.vmware.com/vsphere-65/topic/com.vmware.ICbase/PDF/vsphere-esxi-vcenter-server-65-installation-setup-guide.pdf
https://pubs.vmware.com/vsphere-65/topic/com.vmware.ICbase/PDF/vsphere-esxi-vcenter-server-65-installation-setup-guide.pdf
2. ISO image preparation
You’ll need a server with more than 4 GB RAM, at least two cores, SSD/harddisk and an empty USB stick (>=8GB).
CAUTION: DATA WILL BE OVERWRITTEN on USB stick and on your server. So use this procedure at your own risk!
CAUTION: DATA WILL BE OVERWRITTEN on USB stick and on your server. So use this procedure at your own risk!
First of all you’ll need an ESXi ISO file, perhaps a modified file which contains custom drivers for your system. Read my other article for some tips how to create your own custom installation ISO file or have a look here: http://www.v-front.de/p/esxi-customizer-ps.html
I made a custom ISO file with this command (see v-front.de for details):
.ESXi-Customizer-PS-v2.5.1.ps1 -v65 -vft -load net55-r8168,net51-r8169,sata-xahci
.ESXi-Customizer-PS-v2.5.1.ps1 -v65 -vft -load net55-r8168,net51-r8169,sata-xahci
This image currently contains additional drivers for some ASRock and similar systems, e.g. Q1900/N3150/J3160/J3455-ITX
Download link is here: https://esxi.jorba.de/ESXi-6.5.0-20171204001-standard-customized.zip
(Updated Image 2018/02/03)
Download link is here: https://esxi.jorba.de/ESXi-6.5.0-20171204001-standard-customized.zip
(Updated Image 2018/02/03)
Than create a bootable USB stick (size >= 8GB), for example use portable Rufus for this task.
Download portable Rufus from here: https://rufus.akeo.ie/?locale=en_US
Insert an empty USB stick, use the above parameters and select your ESXi ISO image, than click on Start button to create a bootable USB installation.
(Again the warning not to overwrite some important data!)
(Again the warning not to overwrite some important data!)
Download boot.cfg and ks-nowipe.cfg from my blog and copy (replace) them on the USB stick. These are the kickstart files.
Download links:
https://esxi.jorba.de/ipxe/ESXi-6.5.0-20170304101/usbboot/boot.cfg
https://esxi.jorba.de/ipxe/ESXi-6.5.0-20170304101/usbboot/ks-nowipe.cfg
Download links:
https://esxi.jorba.de/ipxe/ESXi-6.5.0-20170304101/usbboot/boot.cfg
https://esxi.jorba.de/ipxe/ESXi-6.5.0-20170304101/usbboot/ks-nowipe.cfg
3. Boot from USB and start installation
Insert USB stick into your server, boot from USB
–> BIOS needs to be setup in legacy boot / compatibility mode (not UEFI).
–> Installation will need about 10 minutes to complete, there will be a reboot
–> Installation will need about 10 minutes to complete, there will be a reboot
Wait for completion!
Post installation customization
Embedded host client
After installation, you can manage the system with the embedded host client inside your browser: http://<ip-address>/ui
You will find the ip address inside your router’s DHCP status table.
You will find the ip address inside your router’s DHCP status table.
Login credentials
The managing user is „root“, the initial password can be set in the ks-nowipe.cfg installation file.
If you use my above file without changes, the login it is simply „root/password„, so change it immediately ?
If you use my above file without changes, the login it is simply „root/password„, so change it immediately ?
ESXi shell / ssh
My kickstart files enable ESXi shell and ssh.
This are useful management tools, but if don’t need them, switch them off using the management client.
This are useful management tools, but if don’t need them, switch them off using the management client.
Direct console (DCU)
If the „direct console (DCU)“ is not working on your server due to missing video output or because you use the server „headless“, is can be accessed via SSH (if you leave it enabled).
Start putty or another ssh-tool, connect to your ESXi Server and enter the following commands:
![Error Error](https://communities.vmware.com/servlet/JiveServlet/showImage/2-2551032-54334/Untitled.jpg)
export TERM=linux
dcui
dcui
ESXi console via SSH
Esxi Installer Fatal Error 33 Free
Periodic Backup
A really good free backup script for ESXi is ghettoVCB:
http://www.virtuallyghetto.com/2015/05/ghettovcb-vib-offline-bundle-for-esxi.html
http://www.virtuallyghetto.com/2015/05/ghettovcb-vib-offline-bundle-for-esxi.html
Feedback
This post was updated several times and will be updated periodically in the future.
Feedback welcome.
Feedback welcome.
Antonio Jorba
Esxi Installer Fatal Error 33 1
I’m trying to upgrade a 5.0 host to 6.0 and get the following error:
error loading /sb.v00
Esxi Installer Fatal Error 339
fatal error: 33 inconsistent data
I’m upgrading using Update Manager. I’ve tried several ISOs as research suggests. MD5 checks out no issues. I’ve tried replacing the file with one from a running host in the ISO and repackaging it as well, but I cannot import that image into Update Manager as it gives an error. Not sure if noteworthy, but the error plastered all over the internet is for s.v00 instead of sb.v00. I’m not sure if there’s any significance to that. I don’t have access to the server physically unless it’s to address critical issues (this isn’t as this host isn’t in production), but do have KVM access and I’m able to recover back to 5.0 from a failed upgrade. The update logs show that the PACKAGE_COMPLIANCE check is failing. That’s the dead end I’ve hit. I don’t know how to address that.