Motherfrocker

Despite the fact that my fileserver is not actually online, I nevertheless use it to compose and backlog posts so that when I do go online, it will all be finished for me.

Earlier today, I was adding a post when the entire machine stalled and rebooted of its own accord.

Now, this isn't the first time that this has happened. Earl (the fileserver) is generally pretty damned stable, but I did run in to a bunch of problems when I added the sixth hard drive. I've been running it here in Seattle with the side covers on (something I couldn't due in New Mexico due to the heat) but it's been fine since last Wednesday.

But, it crashed. And it took the DB with it.

Thankfully, none of the data files seem to be damaged. An index file is borked, however, and I need to rebuild it before MySQL will recognize the DB again. So that's kind of a bummer.

And even if the DB files were damaged, a static-file version of the entire blog is built every time I hit the submit button. I commented on this earlier at some point, and it seems now that it's a pretty nice lifeline—an extra automatic backup copy of the DB is kept me from flipping out earlier. Bonus.

It's times like this that I realize how useful the internet is. I don't actually have the MySQL reference manual with me (although I do own it, oddly) and I had to come over to Layla's place to look it up online.

But, whatever. I think I have all the information necessary to make the DB rebuild the indices.