I spent most of Tuesday driving home. Checked my email before I left; there seemed to be a network issue with my server, but I didn't bother checking until the evening, when I got home.
The box this blog runs on threw a kernel panic some time late on Monday night/early on Tuesday, and panicked repeatedly on reboot. Diagnostics demonstrated that (a) the RAID array was hosed, and (b) the machine's memory had gone bad ... right as it was handling probably 30-50,000 emails and 50-100,000 http requests a day.
After a brisk disk transplant into a new machine, we spent the whole of Wednesday fscking the hell out of the main filesystem, which showed worrying signs of bit rot. This morning, the filesystem was recovered, so I spent another few hours pulling the contents down my home ADSL line (all 39Gb of them; it took about four hours). If you can read this blog entry, it means I've finally succeeded in un-gunking the MySQL database enough to post via Movable Type, which is a Good Thing. Hopefully we haven't lost anything (but cloud backups are going to start happening in the near future, i.e. just as soon as the new machine gets a clean bill of health).
We're not out of the woods yet. The mail transport daemon is squatting in a corner and gibbering to itself (metaphorically, I hope). If you use a mailing list hosted on my machine, it won't be back until we've got exim sorted out. (This means you.) There's probably other stuff I've forgotten about. It's not beyond the realm of possibility that there's hidden damage to some subsystem or other and we're going to have to rebuild from scratch on a new Debian system.
But if you can see this, we're on the way back.