SQL: Warning Size of indexfile, Keyblock size, Incorrect key file and Corrupt

  • Hello friends,

    Please, can you give me with this database problem?

    When I run this SQL command:
    REPAIR table wp_posts;CHECK table wp_posts;

    I see an error that I don’t know how to fix it:
    lutytami_t21.wp_posts repair status OK
    lutytami_t21.wp_posts check warning Size of indexfile is: 144977920 ? ? ?Should be: 14…
    lutytami_t21.wp_posts check error Keyblock size at page 5823488 is not correct. ?Blo…
    lutytami_t21.wp_posts check Error Incorrect key file for table ‘./lutytami_t21/wp_po…
    lutytami_t21.wp_posts check error Corrupt

    Hosting support said:

    “I apologize for the troubles that this has caused, and I am happy to provide clarification in this matter.

    Upon review of the screenshots provided, what you are actually seeing is not an error, and the REPAIR query is running successfully. What is showing on your page is that the REPAIR is being told by your database index file that there are a different number of rows versus how many rows there actually are.

    This is something that is common after having database corruption – data can be added or rows dropped and that changes the total number of rows available, versus what has been logged in the past. This is not something that can be fixed by the REPAIR query, but is reported by it. This will not prevent your database from functioning as intended.

    If you have any further questions concerning your database, I would recommend reaching out to a SQL developer for further assistance”.

    Thank you.

Viewing 7 replies - 1 through 7 (of 7 total)
  • Moderator Steven Stern (sterndata)

    (@sterndata)

    Volunteer Forum Moderator

    What I’d try is to export the table using PHPMYADMIN or mysqldump, dropping the table, then recreating/importing what you exported.

    Failing that, fall back to a database backup from before things went wonky.

    Thread Starter blackhatpro

    (@blackhatpro)

    Steve, thank you for your reply.

    Unfortunely, I don’t have a database backup before this problem. My bad. The website shows all the posts, media, pages, looks like work fine, but I know that in the database exist this error.

    I exported all contents to XML file with:
    URL/wp-admin/export.php

    After that I’m imported the XML file to another URL:
    URL2/wp-admin/import.php

    I see that URL2 has Media files, posts and pages but load post slowly, I don’t know if is necessary wait something from the server.

    Use the “XML file” solution was a good idea or isn’t good really?

    Thank you very much.

    • This reply was modified 4 years, 10 months ago by blackhatpro.
    Moderator Steven Stern (sterndata)

    (@sterndata)

    Volunteer Forum Moderator

    That’s not the way to do it. Work in the database, as I suggested. Make sure you get a full backup of the db first, just in case.

    Thread Starter blackhatpro

    (@blackhatpro)

    Dear Steve,

    Thank you for your reply. I really don’t know about SQL that’s a big problem for me. If someone can help me with to fix it, I will very thankful ??

    Moderator Steven Stern (sterndata)

    (@sterndata)

    Volunteer Forum Moderator

    It’s all doable via PHPMYADMIN, as noted above.

    Moderator Steven Stern (sterndata)

    (@sterndata)

    Volunteer Forum Moderator

    I got your email. To get mine, you must have read the contact page on my site that says not to contact me regarding forum matters. NOT AT ALL, EVER, NOT EVEN ONCE.

    If you need a developer to help you, I recommend visiting a local WordPress meetup group or checking jobs.wordpress.net.

    Thread Starter blackhatpro

    (@blackhatpro)

    I’m sorry Steve,

    I didn’t read it. My bad.

    Thank you for you help I will try to fix this problem. I’m sorry again.

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘SQL: Warning Size of indexfile, Keyblock size, Incorrect key file and Corrupt’ is closed to new replies.