Brion Vibber wrote:
A RAM test needs to be done; that's a highly
likely source of errors
(over 32 billion bits of memory; if just _one_ is defective, it can
cause data corruption or a crash).
Early next week, Jason is going to be delivering the new machine, and
it can be pressed into service while we take the opteron out of
service for testing and parts swapping, if that's what the problem is.
We *really should* get database replication going, if
at some point we
have two working machines with enough disk space to handle the
database, so a dead database server can be taken over by the slave.
And then perhaps once we get rolling again, this is what we can do
with the $4000 in the bank... buy a machine to be the secondary DB
server?
--Jimbo