I am getting the following error and cannot login to the EE control panel. Any thoughts on what to do to fix this?

MySQL ERROR:

Error Number: 1016

Description: Can’t open file: ‘exp_referrers.MYD’. (errno: 145)

Query: SELECT count(ref_id) AS count FROM exp_referrers

Thanks!

Rayna, repair your referrer’s table. That’ll fix it.

I’m getting this error again and I cannot login into the control panel…...I need a quick fix a client is going nuts.

I did an update and upgraded the site to version 1.41 and I am still getting this error.

HELP! I can’t repair anything because I can’t login to the CP

Do you have access to phpmyadmin or something similar?

Yes I do….and I see this when I look at that table

MySQL said: Documentation
#1016 - Can’t open file: ‘exp_referrers.MYD’. (errno: 145)

No worries- go into it, click on the exp_referrers table, run a repair table.  I’ll look up the query for you, but by the time I do, it’ll probably be fixed.  phpmyadmin is pretty intuitive.

How did you repair your table the last time? I’d use PHPMyadmin or

EDIT: I see rob got you covered.

I don’t know how to repair the table…..could you walk me thru it?

THANK YOU!!!

Now my next question is how do I keep this from happening again…this is the 3rd time.

There’s nothing about EE itself that causes the table becoming corrupted- but if it’s happening somewhat routinely, it may be due to a fatigued area on the hard drive.  Here’s a post where someone had issues with the exp_throttle table needing to be repaired every couple of weeks.  That’s just not normal- as Rick noted in his advice:

bet his database is sitting on a fatigued area of his hard drive.  Tables don’t just need to be repaired for no reason.  You might have him drop the table, using…

Different table- but the basic advise would be the same.  I’d consider exporting that table, dropping the table, then adding it back.  But be careful and make sure you have a full backup before you go mucking about in the db.

There’s a pretty good explanation on the vbulletin forums, explaining the background in a bit more detail.

EDIT: Errno 145, by the way, means “Table was marked as crashed and should be repaired”. This is a server-side issue, I would guess.