Heh, interesting- now everything's beginning to piece together.
This same error (28) got a repair operation to crash, leaving my database down for almost 2 days...after patching up the DB, I contacted my host, and they seem to have gotten the server problem under control.
Thanks for the info
