Last Tuesday, I visited my server (it lives in a friend’s office) to remove a DVD writer from it. The idea was to install that DVD burner at home, so I could start backing up all my photos; since I don’t normally have physical access to my server, I handle its backups over the network. Before heading up to perform the server surgery, I backed up my web site and gallery, something I’d been meaning to do for a while (I did not, however, back up the system disk, which houses Sarah’s website and the database).
DVD drive removal went fine. But when I hit the power button again, I got the dreaded error message:
BOOT DRIVE FAILURE
Hmm. Ben and I were both rather stumped, since the drives had both been working just fine 30 seconds ago. We tried again, with the same result. We tried switching the drives – no luck. We tried hooking them up one at a time to Ben’s computer, but it couldn’t see EITHER of them. Now I was really starting to panic; what were the odds that both of my hard drives died at once?
I took them home that night and continued trying to revive them. Linux rescue mode was no good (it claimed it couldn’t find any linux partitions on either disk), and I couldn’t bring either of them up on another computer, either.
After a while, the drive that houses my website (let’s call it “Fred”) started making a really terrible noise when it started up – kind of a “TICK-tock-TICK-tock-PING,” over and over until it gave out. Ok, I told myself, Fred’s clearly dead – but surely drive #2 (we’ll call it “Bob”) couldn’t also be completely ruined.
I set Fred aside and continued to attempt to rescue Bob. I had Bob set up as a slave on the primary IDE controller, with a perfectly good boot disk as the master. I hit the power button, heard a loud POP – and Bob began to smoke!
Being the calm, collected person that I am, I immediately jumped back about 5 feet and yelled for Jeff, who simply yanked the power cord out of the back of the server.
So, that was it – everything was lost – except, thankfully, for my website/gallery which I’d just backed up that morning! Jeff made a late-night Fry’s run for a new hard drive while I prepared to re-install the system and restore as much as possible from earlier backups (the last one was in January) and Netscape caches. I spent the rest of the week rebuilding thelaitys.com, and finally got it hooked back up in Ben’s office this afternoon.
Bob’s innards:

Makes a pretty good mirror:

Bob was actually rather an old drive, which had passed through several hands (and computers) before landing in my server. Our best guess is that Bob had been overheating for a while now, and damaged something crucial – and since it was sitting right on top of Fred, the heat may have gotten to Fred too. I guess they were both just barely hanging in there, and the power-down/power-up finished them off. As to what finally made Bob CATCH FIRE, I have absolutely no idea – but the new drive has been running just fine in there without incident, so I think I’m willing to believe that the root of the problem was the drive, and not the power supply in the server. (If I’m wrong, I hope Ben’s office has good smoke detectors!)
It’s going to take a little while before everything is back to normal; I need to re-enter all my dive logs, and Sarah has a lot of restoration to do for alphasarah.com. But GOOD GRIEF, have I learned my lesson about backups! (And about the wisdom of just backing up from one drive to another, as I often do on my home PC, since surely BOTH drives would never fail at the same time…)