Byte Jar - Software Lessons Learned the Hard Way
A public service catalog of solutions to annoying software development problems, or
a sporadically updated rant chamber hosted by the code grunts of a tiny software company. Thanks for tuning in.
Be Prepared, the famous Boy Scout motto, is also valuable advice for administrators who could find themselves pitted against a misbehaving computer. Having a prepared, well-stocked jump-kit saves crucial time in an emergency, leading to less down-time and less aggravated users.
Recently, we needed to make an emergency visit to a clients' server room to investigate a potential hardware problem on their AERES server. We suspected a faulty memory module, so we planned to run Memtest86+ against the server to identify if any SIMMs had failed.
Running this simple test required a host of tools:
The situation on the ground was complicated by a couple of factors. The first is that our AERES servers don't have CD-ROM drives, so we use thumb drives running a customized version of pen-drive Linux. The second is that the crash cart had such short cables that they couldn't reach our server. Fortunately, everything we needed was in our jump-kit.
Normally, my jump-kit sits in my office closet, collecting dust but when an emergency arises, that bag stands ready to assist my diagnostic, forensic, and repair needs. Every one of our ideacode employees, who invariably gets some duty on server repair, has a jump kit. All sitting around, collecting dust, until the day they're called upon.
Our standard-issue jump kits contain:
The outer bag choice is left to personal preference, but I love my Targus bag -- plenty of pockets and compartments, roomy enough for a 17" laptop, comfortable, and durable.
When the time comes, you're going to need some or all of the things you have in your jump kit. Save yourself a lot of headaches (and cussing) by keeping all the gear you need together and ready.