Cleaning soot out of a server

Solution 1:

I actually have salvaged computers from a fire. Isopropyl alcohol and cotton swabs will help you tremendously.

Edit:

Now that I have a second to post, here's some backstory. About 14 years ago a friend's apartment building caught fire while I was visiting. He lived on the second story and his hallway was blocked by a large pile of flaming debris. He and I jumped out a second-story window onto a mattress that the downstairs neighbors were nice enough to drag out onto the sidewalk. My friend was unhurt. I broke both bones in my lower left leg.

It was a small town, and people knew that I was "into computers", so I did a short but steady business of cleaning up machines that were in the various units around my friend's apartment. (I didn't have much else to do-- I was on break from college and unable to walk effectively.)

The worst machine was probably the computer hosting a dial-up bulletin board system that was in the adjacent unit to the fire and running during the fire. It inhaled quite a bit of smoke and was a sooty, tarry mess inside when I got started on it.

I always warn Customers about fires, and I often cite my own fire experience as reasons for off-site backup. A little over a year ago I received an email from a server computer that I'd installed as part of a subcontract job for a small local IT service provider. I'd configured my email address as a test recipient for hardware notifications and the provider or the Customer never bothered to put in their own addresses. I forwarded the fan failure message to the IT support firm with a note that they should remove my address from the hardware notification service.

The next day I learned that the Customer's building caught fire the prior night and that the email I received came, undoubtably, from a server computer that was inhaling smoke and experiencing fan failures-- running on its UPS (which was keeping the router at the end of the T1 line up) while the building burned up around it. They weren't really big enough to have an EPO attached to their fire suppression system-- we're talking two (2) server computers in a small rack in a closet kinda sized.

I won't make this post any longer, but here are some Cisco switches (and one no-name something-or-other at the top of the picture) post fire. (Click for a larger image)

_{(source: wellbury.com)}

Solution 2:

I'm not sure what the best solution to your problem is but using a vacuum cleaner on a server or pc is not a good idea, due to the amount of static they generate. You may not see the effects immediately, but many of the components on the motherboard are easily damaged by ESD.

Solution 3:

I would recommend dilute isopropyl alcohol (cut with distilled water about 60/40) and a natural-bristle paint brush. Don't use paper towels/napkins as they will shed fibers. When done, make sure you let it dry completely.

Before you start on a particularly nasty machine, where you might need to remove the motherboard:

1. Reboot to the CMOS settings screen
2. Write down EVERYTHING
3. Remove the motherboard
4. Take out the CMOS battery
5. Clean completely
6. Let dry
7. Reinstall the CMOS battery
8. Reinstall the motherboard
9. Use those settings you wrote down.

If it is really bad, you can use the dishwasher trick, but please:

• No soap
• Air dry (turn off the heat-dry feature)
• No "extra heat" (some dishwashers will double-heat the water you don't want that)
• Let it dry a WHILE.