http://www.tat-webhost.com

Notice that when you try to enter most of the forums there, there is a MySQL error. How do I fix this?

mySQL error: Can't open file: 'ibf_posts.MYI' (errno: 145)

WOW, that's some error, looks like your MySQL server is crashed.

Is this on your own dedicated server?

without quite a bit more info, the only thing I could suggest is try rebooting the server and cross your fingers.

I got this:

mySQL query error: SELECT pid FROM ibf_posts WHERE topic_id=473 and queued=0 ORDER BY pid asc LIMIT 0,20

mySQL error: Can't open file: 'ibf_posts.MYI' (errno: 145)
mySQL error code:
Date: Monday 18th of July 2005 03:52:06 AM


Ok Im newb but maybe the ibf_posts dont exist? Or MySQL thing are not correctly setup? Maybe update the boards aswell..
Think some others will need to help as I'm very beginner at this area.. can't tell much more :\ gl

This is on a VPS. When I check in cPanel, it says all systems are running smoothly... :/

$ perror 145
Error code 145: Unknown error 145
145 = Table was marked as crashed and should be repaired


maybe this is why? found on google..

Okay. Thanks...
All I need to know now is how

this is something your probably going to have to fix directly from the ssh command prompt.

I would start here: http://dev.mysql.com/doc/mysql/en/using-mysqlcheck.html

Thanks, mate. I'll give it a go.

You should be able to use 'REPAIR TABLE ibf_posts' from MySQL. I don't recommend using mysqlcheck to repair tables while the SQL server is running, although it would be fine after you stop MySQL.

UrlGuy: Table doesn't exist is a separate error. This error means the table exists, but the index file doesn't correspond correctly to the data in the data file.

Looks like you got it fixed :)

Originally posted by innova
Looks like you got it fixed :)

Not quite, I just got:

mySQL query error: SELECT pid FROM ibf_posts WHERE topic_id=866 and queued=0 ORDER BY pid asc LIMIT 0,20

mySQL error: Can't open file: 'ibf_posts.MYI' (errno: 145)
mySQL error code:
Date: Tuesday 19th of July 2005 07:45:48 AM

I've got it fixed now... thanks everyone ;)