Actually your user's table was corrupt - and when I ran the repair table command, the record count was off by one. Which usually either means the record count was off.... or there was one record that it couldn't be repaired. That happens from time to time when a table get's corrupt, that's what the repair table command does, remove the corrupt data.
The mysql logs were probably huge because MySQL on the box you were on did go down briefly yesterday- so you might not be able to open them through admin, you'd probably have to open them directly. But they won't really have any clues.... lots of unable to connect to messages, because MySQL wasn't running while everything had to get rebooted.
If you know who the user was - and if we can figure his usernumber, we can simply recreate him (with the same user number) and all shoudl be fine (he'll still have all his posts etc....)
If you know who he was, and can help me figure out his usernumber etc.... PM me the details and I'll recreate him.
