Forums

Can't open file: 'wp_posts.MYI' (errno: 145)? (7 posts)

  1. nemock
    Member
    Posted 6 years ago #

    I'm running 1.5.2. I just did a post and now I'm getting this error all over the place.

    WordPress database error: [Can't open file: 'wp_posts.MYI' (errno: 145)]
    SELECT DISTINCT * FROM wp_posts WHERE 1=1 AND ID = 60 AND post_date_gmt <= '2006-05-16 16:45:59' AND (post_status != "static") GROUP BY wp_posts.ID ORDER BY post_date DESC

    What does this mean and what can I do to resolve it?

    -Dave

  2. webwalrus
    Member
    Posted 6 years ago #

    If it's not your server, try contacting the server admin. It's possible the database went wonky and locked your posts table. Otherwise, try restarting MySQL.

  3. Chris_K
    Member
    Posted 6 years ago #

    Definitely a mysql error - contact your host.

  4. costmary68
    Member
    Posted 5 years ago #

    If using CPANEL, go to MySQL databases, select your WordPress database, click "check." Below is the result I received when I clicked "check" for the same error as you describe (I have ###'d out my actual database name). Clicking "Repair" fixed it. I'm not sure how this happened but will upgrade (I was nervous about doing so dreading some similar situation as came about without):

    Checking MySQL Database
    ### is now being checked.

    ###.wp_categories
    warning : 2 clients are using or haven't closed the table properly
    status : OK
    ####_comments
    warning : 3 clients are using or haven't closed the table properly
    status : OK
    ####_linkcategories OK
    ####_links OK
    ###_options OK
    ###_post2cat
    warning : 2 clients are using or haven't closed the table properly
    status : OK
    ###_postmeta OK
    ###_posts
    warning : Table is marked as crashed
    warning : 4 clients are using or haven't closed the table properly
    error : Found 167 keys of 168
    error : Corrupt
    ###_users
    warning : 1 client is using or hasn't closed the table properly
    status : OK

  5. eddyj
    Member
    Posted 5 years ago #

    So basically to put it in a NUTSHELL this issue can happen at any time. its not your fault as the BLOGGER

    Its someone at your host who messed it up

    SOlution is. Go into Cpanel Go to DAtabase click on CHECK then click on REPAIR

    that will fix it! Worked for me

  6. jrjm
    Member
    Posted 5 years ago #

    Wow, this just happened on my main content site and it was pretty scary since I depend on it for close to a thousand dollars a month in revenue.

    Good thing WordPress support archives are always here when I need them. :D

  7. rustyellis
    Member
    Posted 5 years ago #

    You guys just completely saved my life with this post!!! Glad I started here for the fix. I almost started messing with my backups and trying to figure out what to do to upload them (I am in no way a database person).

    Thank you again!!!

Topic Closed

This topic has been closed to new replies.

About this Topic

Tags

No tags yet.