Forums

[resolved] WordPress database error: [Can't open file: 'wp_posts.MYI' (errno: 145)] (5 posts)

  1. joecool200
    Member
    Posted 2 years ago #

    Just upgraded to 2.2 today. Everything went smooth, and later this evening as I wanted to fiddle about with a scheduled post I went into Manage Posts, and nothing turned up. I olly got this error:

    WordPress database error: [Can't open file: 'wp_posts.MYI' (errno: 145)]
    SELECT ID, post_title FROM wp_posts WHERE post_type = 'post' AND post_status = 'draft' AND post_author = 1 ORDER BY ID DESC

    WordPress database error: [Can't open file: 'wp_posts.MYI' (errno: 145)]
    SELECT ID, post_title FROM wp_posts WHERE post_type = 'post' AND post_status = 'draft' AND post_author IN (1,3) AND post_author != '1'

    WordPress database error: [Can't open file: 'wp_posts.MYI' (errno: 145)]
    SELECT SQL_CALC_FOUND_ROWS wp_posts.* FROM wp_posts WHERE 1=1 AND (post_type = 'post' AND (post_status = 'publish' OR post_status = 'future' OR post_status = 'draft' OR post_status = 'private')) ORDER BY post_date DESC LIMIT 0, 15

    I can see WP-admin and everything, but can't do much else.

    At first the blog seemed to work fine except this one menu, but when I tried to make a new test post, everything went wrong. I thought it was the Sticky plugin since this was mentioned in the php error, but disabling it didn't help at all.

    Now my blog looks like this: http://www.joe-cool.dk/blog

    Anyone here have a clue what is wrong? Should I put my money on my host having a problem, og should I go for an old backup and start over? I fear my last backup is some months old, so it's kinda worth a good cry.

  2. moshu
    Member
    Posted 2 years ago #

    You can google for "errno: 145"...
    Better: in case of any 'numbered error' like that - contact immediately your host.

  3. joecool200
    Member
    Posted 2 years ago #

    Tnx Moshu. Thaats quick helping :-)

    Googled it and it was a corrupt table.

    Solved the issue by logging into MyPHP. Then clicking SQL and writing a query that goes like this:

    REPAIR TABLE wp_posts

    That fixed it. Tnx a lot. Almost had a good sweat going there.

  4. joecool200
    Member
    Posted 2 years ago #

    Oh, btw, I did contact my host, but they didn't really care much as their DB servers was working "as usually".

    Anyway, hope others with same problem can use this topic to fix it if they encounter the same problem. :-)

  5. sdickert
    Member
    Posted 1 year ago #

    By the way, this "repair table" was a quick solution. Thanks!

    And, what should I set the permissions to the wp-config.php to?

Topic Closed

This topic has been closed to new replies.

About this Topic