After a poweroff (ungraceful shutdown), upon reboot of ESXi, I get the following screen dump:
Kernel: vmkerkel.gz bootUUID=7b00...........................................................
Loading vmkernel.gz
Module: binmod.tgz
Loading binmod.tgz
Module: environ.tgz
Loading environ.tgz
Module: cim.tgz
Loading cim.tgz
Module: oem.tgz
Loading oem.tgz
Module: license.tgz
Loading license.tgz
Module: state.tgz
Loading state.tgz
PANIC: Error while reading file: -3, state.tgz
boot:
If I press <ENTER> it starts to reload the HyperVisor and loops again loading the above files.
Any idea what this is or how to correct this? I've found only one other site on a google search that references the same error posted by another admin. No answer to his query about why this happened.
This server is a Dell PowerEdge 4600 running dual 2.4GHz 2GB RAM, Perc3/DC using 2 mirrored 18GB SCSI drives (ESX OS), and 6 36GB SCSI for the local datastore (VMFS).
Running ESXi Update 2, build 110271. No other patches installed.
Thanks to anyone that responds.
State.tgz contains all the configuration files for your ESXi host. A few options:
1) restore a configuration backup (i.e. a backup taken with the RCLI command vicfg-cfgbackup.pl
2) You could boot with "LiveCD" and see if there is a older copy of state.tgz on the altboot bank partition. This would apply if you have ever patched the system.
3) Run a recovery install of ESXi. This will wipe the configuration of the host, but the VMFS partition will be perserved.
In any case, there is a bartPE CD that you can boot and then access the VMFS partitions with. This would give you a chance to copy your VMs to other storage just in case.
State.tgz contains all the configuration files for your ESXi host. A few options:
1) restore a configuration backup (i.e. a backup taken with the RCLI command vicfg-cfgbackup.pl
2) You could boot with "LiveCD" and see if there is a older copy of state.tgz on the altboot bank partition. This would apply if you have ever patched the system.
3) Run a recovery install of ESXi. This will wipe the configuration of the host, but the VMFS partition will be perserved.
In any case, there is a bartPE CD that you can boot and then access the VMFS partitions with. This would give you a chance to copy your VMs to other storage just in case.
Excellent, thank you. 2 of those options would have worked in my situation.
I choose the "easy" method by booting with the installation CD and choosing the "Repair" option. It corrected the problem withing 3 minutes. I was backup and running in 15 minutes with my VM's.
I do have a question about the BartsPE (CD) option you mentioned. What program or executable do I need in order to access the local VMFS on the 3i server? Obviously this won't be seen by default, so what is required for this partition/filesystem to be accessed?
Thanks for the quick reply!
The tool is MOA and can be found here - http://sanbarrow.com/moa.html. There's an option to boot the CD, the start an ESXi VM and mount local drives.
Try to reinstall ESXi. In the installer select repair, this will be save your vmfs with all vm´s.
chris
EDIT: Sorry for my answer, the question has been answered correctly ...
Gracias.
Hi folks,
I have nearly the same error in ESXI embedded (USB) after installing the latest patches. (Drivers + Kernel, I think)
PANIC: Error while reading file: -5, binmod.tgz
what the hell means this?
I try to reinstall the ESXI on USB now.
Any hints?
Thank you David, thank you very much
Exactly the same problem for me after an abrupt power outage (gotta get me a BBU). I also used the installation CD and did a Repair. Had to remove all the VMs from Inventory and re-add them and recreate the automatic power on/off order configuration. Probably a few more things I need to recreate, but all the VMs are running. Thanks.
Regards - Glen
Please follow the link below to resolve the issue
http://ftejeda69.blogspot.com/2009/08/panic-error-while-reading-file-5.html
Ran into the EXACT same error as .
Rebooting seemed to work for me, but the consensus on the web seems to be that if a reboot does not help, do a repair install.
Running the following:
Dell Poweredge 1750 dual 2.4GHz 2GB RAM; ESXi 3.5 U5 build 207095