Repolishing Lapis, I
July 23rd, 2010 at 9:40 AM (Desktop Support, Information Technology)
Software Rebuild. A phrase I have mixed feelings about. On one hand, it can be very effective at eliminating many problems that a machine has by the virtue of clearing out the chaff that accumulates on an active machine.
On the other hand, in an ideal world, we’d tackle each problem that the machine has, identify it precisely, affect a solution and document how we identified the problem and what steps we took to solve it…and add that to the collective knowledge.
Some problems are fairly elusive (particularly intermittent ones), hard to trace, and even if you narrow it down, sometimes hard to resolve. In short, the ideal practice I described is time-consuming, frustrating, and frequently fails (leading to a rebuild anyway).
I’ve done many software rebuilds on machines, with many flavors of windows, a few Linux boxes, and a few Macs. (The many vs. few doesn’t really reflect on the OSs in question, it merely reflects the percentage of machines running the respective OSs. Our network, for example is 3 windows, 2 Linux, 0 Mac at this time…).
So we have a machine whom we’ll call Lapis. It is need of a software rebuild, which will hopefully clear up the numerous problems we’re having with it.
The first step is always, always, always, … to backup the current machine. As entirely as possible. Fortunately, I have a great software application for generating images of hard drives or systems. Acronis TrueImage produces an image of a hard drive, that can be later restored to the drive, extracted if you want, or browsed as if it was a folder on the your hard drive (this last requires Acronis to be installed on the system in question). Great stuff.
The image of Lapis is 35GB. Not bad, considering the size of many modern systems. But…to wipe the drive, I have to have that backup on some other system or drive. There, the pain arrives. Lapis has difficulty communicating with our File-server. So I can’t just copy the 35GB file to the fileserver.
The easiest route would have been a external hard drive…which I don’t have and of course, I don’t want to spend the money. Then I remembered: I have a 80GB SATA drive on a shelf, that came out of another machine when its HDD was upgraded. Voila! The solution. We mount the drive as a second drive on Lapis, copy the image to the drive, mount the drive in the file-server, copy the file from the drive to the file-server. Presto! We have the backup image on the 80GB drive and on the file-server. Briefly, we browse the image file on the file server, opening some individual files from the image to make sure it is a good copy (ideally, I’d do a verification against the original drive…network issue, alas). And we’re in business.
Course, we’ve jumped through all of these hoops, and we haven’t even wiped the drive yet. joy.



