Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I recall once copying a bad tgz file to my bootbank and specifying to load it in boot.cfg. Needless to say this was bad - Purple Screen of Death, no boot, bad - and I should have been more careful. But is there a way to check the consistency of your files in boot.cfg, as in simulating what would happen at that point, so that you know before hand whether there is a corrupt tgz file or invalid boot.cfg option?

share|improve this question
Problem with your media? I've never seen this. – ewwhite Oct 26 '12 at 20:28
@ewwhite It failed because it didn't like ghettoVCB.tgz specifically. It would not boot. After booting into with a live CD, removing the inclusion in boot.cfg and deleting the ghettoVCB.tgz file, it could boot. – tacos_tacos_tacos Oct 26 '12 at 20:29
Sounds pretty unsupported... – ewwhite Oct 26 '12 at 20:35
@ewwhite, it's absolutely unsupported, but I was just wondering if there is a consistency checking program in ESXi as it must do something like this when it is booting to figure out it cannot boot... – tacos_tacos_tacos Oct 26 '12 at 20:39
Erm have you tried something simple like installing ESXi in a VM, then simply trying your adding your tgz on a VM before adding it on production? – Zoredache Oct 26 '12 at 21:07

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.