I think you still have problems. Only a few posts of the home page seem to be restored. All the links, the link to the next page, etc. show 404 errors.
I had changed the base directory so I could put up a temp static home page for the site. I need to move this back. But a backup I started using “Online Backup for WordPress” about 3 hours ago has been stuck at 83% most of that time. 🙁
I guess I need to let it run to see if it’s stuck due to the amount of data or not. The table that was broken but now “back” is 571 MB. Which is about 5 to 10 times the size of everything else.
The backup timed out too many times and no progress was made on any attempt. Your server may be running extremely slow at this time – try scheduling the backup during a quieter period.
Grumble Grumble.
I guess I’ll now try it via Godaddy’s backup process.
I think you still have problems. Only a few posts of the home page seem to be restored. All the links, the link to the next page, etc. show 404 errors.
Putting the .htaccess file back seems to have fixed that.
Just got off of a 30 minute call with Godaddy tech support. This guy was great. He was also confused with the differences between the support emails and what actually seemed to have been done. While at this time GD is not sure what happened he did promise to escalate it and have someone get back to me to try and figure out just how the table became corrupted in the first place.
The big thing was that he understood that a corrupted table such that phpMyAdmin could not display the table was NOT a WordPress or problem that I caused.
I just had this exact problem and wanted to contribute…
The solution offered above my GoDaddy worked beautifully. All of my tables were restored and my site is back up running. GoDaddy tech support offered a site security thing for $60/year, but I’m over them at this point. This is the second time this site has gone down and both times they were no help. I’ll be switching this site over to Network Solutions. However, GoDaddy rant aside, I followed these steps exactly…
You mentioned that you found a table showing “in use” and that you got a message stating that the wp_posts table had crashed. There’s a very simple way to fix this if you’re already in phpMyAdmin:
If you’re not already on the page where you see the tables listed, here’s a reminder of how to get there. From the phpMyAdmin homepage, click on your database name on the left (there’s probably two listed, “information_schema” and your database… don’t mess with the information_schema on). It should display a list of all the WordPress tables, including the the one that shows as “in use”. Once you’re on that page, all you have to do is check the box next to the line for the table that is listed as “in use”, and select the “Repair table” option from the drop-down window at the bottom of that page. phpMyAdmin will immediately perform that operation, and presuming there’s no other failure, the page will refresh and the table will be in a normal status again.
Hey Alon,
Thank you so much. You just saved me hours, probably days. Thanks for describing everything clearly.
– Matt
