bankwest
asked on
VMware Esxi crash
In the past 3 months, this has happened twice and I need to know if I have something configured incorrectly.
Esxi 4.1 running on Server 2008 box with 3 guests (VM's). Due to a storm our power went off and we have the server on a UPS so it can shutdown gracefully. The other servers on the same UPS work fine. But on the console for Esxi, we get an error: PANIC: error reading file -3 s.z and after researching I found I had to boot from the CD and do a repair. Then we have to add back datastore to inventory, add the license key again, reassign the correct IP, etc.
So, I learned how to recover from this, but why does it become corrupt after a power outage. Once we repair Esxi etc...we are good to go.
Esxi 4.1 running on Server 2008 box with 3 guests (VM's). Due to a storm our power went off and we have the server on a UPS so it can shutdown gracefully. The other servers on the same UPS work fine. But on the console for Esxi, we get an error: PANIC: error reading file -3 s.z and after researching I found I had to boot from the CD and do a repair. Then we have to add back datastore to inventory, add the license key again, reassign the correct IP, etc.
So, I learned how to recover from this, but why does it become corrupt after a power outage. Once we repair Esxi etc...we are good to go.
ASKER
Installed with the Esxi CD to a drive called Kingston Drive on the box
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
hanccocka
Ok...I am really green in this area.
The FlashDrive (Kingston) is installed inside the machine for the live version of Esxi to run from.
Ok...I am really green in this area.
The FlashDrive (Kingston) is installed inside the machine for the live version of Esxi to run from.
I would investigate and use a new flash drive. (PNY/SanDisk), it could be a faulty unit.
It's possible it's causing a write issue, and causing corruption to ther bootbank - where the ESXi files are stored to boot the server.