Then, when I tried to view a dynamically-generated page, and I'd get the following error:
CODE
SQL/DB Error -- [Table './captains_mt/mt_comment' is marked as crashed and should be repaired]
Warning: Cannot modify header information - headers already sent by (output started at /home/captains/public_html/cgi-bin/mt/php/extlib/ezsql/ezsql_mysql.php:109) in /home/captains/public_html/cgi-bin/mt/php/mt.php on line 554
The requested page could not be found.
Cannot modify header information - headers already sent by (output started at /home/captains/public_html/cgi-bin/mt/php/extlib/ezsql/ezsql_mysql.php:109)
Warning: Cannot modify header information - headers already sent by (output started at /home/captains/public_html/cgi-bin/mt/php/extlib/ezsql/ezsql_mysql.php:109) in /home/captains/public_html/cgi-bin/mt/php/mt.php on line 554
The requested page could not be found.
Cannot modify header information - headers already sent by (output started at /home/captains/public_html/cgi-bin/mt/php/extlib/ezsql/ezsql_mysql.php:109)
I was obviously a little concerned at this point!
I went into my website administration panel (vDeck) to see if it was simply a matter of choosing to "Repair Database" or something like that. vDeck does have a built-in "check/repair" table function, but the "mt_comments" table was nowhere to be found in the list of tables displayed under this function (most other MT tables seem to be there, though).
Finally, I ventured into phpMyAdmin, and selected the MT database. I got another error message immediately thereafter:
CODE
Error
SQL query:
SELECT COUNT( * ) AS num
FROM `captains_mt`.`mt_comment`
MySQL said:
#145 - Table './captains_mt/mt_comment' is marked as crashed and should be repaired
SQL query:
SELECT COUNT( * ) AS num
FROM `captains_mt`.`mt_comment`
MySQL said:
#145 - Table './captains_mt/mt_comment' is marked as crashed and should be repaired
However, I'm not sure how I can repair the comments table as it doesn't even show up in the list of tables (I see "mt_author", "mt_blog", "mt_category", and then nothing else afterwards -- it's presumably stalling after the crash on "mt_comments").
Sorry for the long-winded explanation, but I thought I'd try to get all the info I could up here right away. Does anyone have any suggestions on what I can do to recover my database?
Thanks!
~Geoff