Error: Can't open file: 'customprofilepic.MYI'. (errno: 145)

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Byron
    Senior Member
    • Nov 2000
    • 525
    • 3.0.0 Beta 6

    Error: Can't open file: 'customprofilepic.MYI'. (errno: 145)

    OPTMIZE
    ===========
    customprofilepic Optimize Error: Can't open file: 'customprofilepic.MYI'. (errno: 145)


    REPAIR
    ========
    customprofilepic Check Warning: Table is marked as crashed
    customprofilepic Check Error: Found wrong record at 5533788
    customprofilepic Check Error: Corrupt


    Database error in vBulletin 3.6.5:

    Invalid SQL:
    REPAIR TABLE `customprofilepic`;

    MySQL Error : Lost connection to MySQL server during query
    Error Number : 2013
    .
  • Colin F
    Senior Member
    • May 2004
    • 17689

    #2
    Ask your host to try repairing that table using myisamchk
    Best Regards
    Colin Frei

    Please don't contact me per PM.

    Comment

    • Byron
      Senior Member
      • Nov 2000
      • 525
      • 3.0.0 Beta 6

      #3
      Are there any other options?
      .

      Comment

      • Boxy
        Senior Member
        • Oct 2002
        • 3139

        #4
        Have you tried running the repair again or do you get that error everytime you run repair? If so, you'll need to ask you host to lookin to this for you.

        This error is a generally caused by a server issue, see this page for possible causes of that error: http://www.vbulletin.com/docs/html/t...mysql_goneaway

        Comment

        • Byron
          Senior Member
          • Nov 2000
          • 525
          • 3.0.0 Beta 6

          #5
          Same error when repairing again.
          .

          Comment

          • Boxy
            Senior Member
            • Oct 2002
            • 3139

            #6
            You'll need to contact your host and have them resolve this for you.

            Comment

            • Byron
              Senior Member
              • Nov 2000
              • 525
              • 3.0.0 Beta 6

              #7
              What should my host do?
              .

              Comment

              • Boxy
                Senior Member
                • Oct 2002
                • 3139

                #8
                They will need to investigate why you are losting connectivity to the MySQL database whilst running repair. As a host they should be aware of what do do when you explain the problem.

                Comment

                • Byron
                  Senior Member
                  • Nov 2000
                  • 525
                  • 3.0.0 Beta 6

                  #9
                  My host tried. But things turn out disastrous. I would really appreciate if someone can give me specific instructions on what I can do or tell my host to do.


                  Response from my host
                  ---------------------------
                  It appears your mysql version is error'ing out:
                  May we upgrade you to mysql 4.0 to 4.1 ?


                  response
                  ------------------
                  It appears that your database is not compatible with what you are trying to do:

                  run myisamchk on a mysql table

                  myisamchk: error: 'customavatar.MYD' is not a MyISAM-table
                  myisamchk: error: 'customavatar.MYD' is not a MyISAM-table

                  Additionally, I believe it would be best to restore your database from a date when your database had not gone corrupt.

                  Tue 2007-04-03 11:01:59 -0400 (EDT)

                  The latest available backups will not work as they are too recent. Please let us know if you would like to proceed.


                  response
                  ---------------
                  Mysql has crashed. A restore of your entire server is in progress. This will take some time. However, this is required to get your server back up and running. Additionally, after the restore you will need to decide weather or not you would like to restore that corrupt database from backup.
                  Last edited by Byron; Thu 12 Apr '07, 5:15am.
                  .

                  Comment

                  • Boxy
                    Senior Member
                    • Oct 2002
                    • 3139

                    #10
                    The error 'myisamchk: error: 'customavatar.MYD' is not a MyISAM-table' may be caused by a bad upgrade of MySQL. There's no way for us to tell.

                    You can restore the just corrupt tables (customavatar and customprofilepic) the try these queries:

                    REPAIR TABLE 'customprofilepic' EXTENDED;
                    REPAIR TABLE 'customavatar' EXTENDED;

                    Comment

                    • Byron
                      Senior Member
                      • Nov 2000
                      • 525
                      • 3.0.0 Beta 6

                      #11
                      Server has restored.

                      I am still getting 2013 error when I try to repair the customprofilepic table.

                      On the repair page, the "Index Length" of customprofilepric says 0.

                      It is the only one that says 0 while all the other tables says ... KB.

                      It's Data Length is also 0.


                      wait_timeout was already set to 28800.
                      .

                      Comment

                      • Byron
                        Senior Member
                        • Nov 2000
                        • 525
                        • 3.0.0 Beta 6

                        #12
                        repeat repair of that table still says:

                        customprofilepic Optimize Error: Can't open file: 'customprofilepic.MYI'. (errno: 145)
                        .

                        Comment

                        • Wayne Luke
                          vBulletin Technical Support Lead
                          • Aug 2000
                          • 73981

                          #13
                          Another method of repairing a database that has crashed is via ssh telnet using the mysqlcheck command http://dev.mysql.com/doc/mysql/en/using-mysqlcheck.html. Mysqlcheck allows you to repair databases while MySQL server is still running unlike Myisamchk which requires MySQL server to be shutdown before running Myisamchk.
                          Mysqlcheck, is alot faster than running via phpMyAdmin and the preferred way of repairing databases.
                          There are a few basic commands to run if you have ssh telnet access and the correct mysqlusername permissions to run mysqlcheck.
                          1. Check the database for errors:
                          2. mysqlcheck -s -u mysqlusername -p dbname
                            Ignore session and cpsession table messages.
                          3. Repair the database using quick repair:
                            mysqlcheck -r -q -u mysqlusername -p dbname
                          4. Then recheck the database:
                          5. mysqlcheck -s -u mysqlusername -p dbname
                          6. If there are still corruption errors that aren't related to session tables, then run the standard repair method: mysqlcheck -r -u mysqlusername -p dbname
                          Note about all of the above mysqlcheck commands:
                          If you want to do one table at a time then add tablename(s) to end of commandline: Code:
                          mysqlcheck -s -u mysqlusername -p dbname tablename1 tablename2 tablename3
                          Translations provided by Google.

                          Wayne Luke
                          The Rabid Badger - a vBulletin Cloud demonstration site.
                          vBulletin 5 API

                          Comment

                          • Steve Machol
                            Former Customer Support Manager
                            • Jul 2000
                            • 154488

                            #14
                            Note: Please do not post in multiple threads.

                            This is still a corrupted table. It need to be repaired. Check out this thread for other ways to repair a db:

                            Steve Machol, former vBulletin Customer Support Manager (and NOT retired!)
                            Change CKEditor Colors to Match Style (for 4.1.4 and above)

                            Steve Machol Photography


                            Mankind is the only creature smart enough to know its own history, and dumb enough to ignore it.


                            Comment

                            • Byron
                              Senior Member
                              • Nov 2000
                              • 525
                              • 3.0.0 Beta 6

                              #15
                              Originally posted by Wayne Luke
                              Another method of repairing a database that has crashed is via ssh telnet using the mysqlcheck command http://dev.mysql.com/doc/mysql/en/using-mysqlcheck.html. Mysqlcheck allows you to repair databases while MySQL server is still running unlike Myisamchk which requires MySQL server to be shutdown before running Myisamchk.
                              Mysqlcheck, is alot faster than running via phpMyAdmin and the preferred way of repairing databases.
                              There are a few basic commands to run if you have ssh telnet access and the correct mysqlusername permissions to run mysqlcheck.
                              1. Check the database for errors:
                              2. mysqlcheck -s -u mysqlusername -p dbname
                                Ignore session and cpsession table messages.
                              3. Repair the database using quick repair:
                                mysqlcheck -r -q -u mysqlusername -p dbname
                              4. Then recheck the database:
                              5. mysqlcheck -s -u mysqlusername -p dbname
                              6. If there are still corruption errors that aren't related to session tables, then run the standard repair method: mysqlcheck -r -u mysqlusername -p dbname
                              Note about all of the above mysqlcheck commands:
                              If you want to do one table at a time then add tablename(s) to end of commandline: Code:
                              mysqlcheck -s -u mysqlusername -p dbname tablename1 tablename2 tablename3

                              Wayne,

                              These are the results from running mysqlcheck.

                              1)

                              dbname_vb.cpsession
                              error : The handler for the table doesn't support check
                              dbname_vb.customprofilepic
                              warning : Table is marked as crashed
                              error : Found wrong record at 5533788
                              error : Corrupt
                              dbname_vb.session
                              error : The handler for the table doesn't support check



                              2)

                              dbname_vb.access OK
                              dbname_vb.adminhelp OK
                              dbname_vb.administrator OK
                              dbname_vb.adminlog OK
                              dbname_vb.adminutil OK
                              dbname_vb.announcement OK
                              dbname_vb.attachment OK
                              dbname_vb.attachmenttype OK
                              dbname_vb.attachmentviews OK
                              dbname_vb.avatar OK
                              dbname_vb.bbcode OK
                              dbname_vb.calendar OK
                              dbname_vb.calendarcustomfield OK
                              dbname_vb.calendarmoderator OK
                              dbname_vb.calendarpermission OK
                              dbname_vb.cpsession
                              error : The handler for the table doesn't support repair
                              dbname_vb.cron OK
                              dbname_vb.cronlog OK
                              dbname_vb.customavatar OK
                              mysqlcheck: Got error: 2013: Lost connection to MySQL server during query when ex
                              ecuting 'REPAIR TABLE ... QUICK'



                              3)

                              dbname_vb.access OK
                              dbname_vb.adminhelp OK
                              dbname_vb.administrator OK
                              dbname_vb.adminlog OK
                              dbname_vb.adminutil OK
                              dbname_vb.announcement OK
                              dbname_vb.attachment OK
                              dbname_vb.attachmenttype OK
                              dbname_vb.attachmentviews OK
                              dbname_vb.avatar OK
                              dbname_vb.bbcode OK
                              dbname_vb.calendar OK
                              dbname_vb.calendarcustomfield OK
                              dbname_vb.calendarmoderator OK
                              dbname_vb.calendarpermission OK
                              dbname_vb.cpsession
                              error : The handler for the table doesn't support repair
                              dbname_vb.cron OK
                              dbname_vb.cronlog OK
                              dbname_vb.customavatar OK
                              mysqlcheck: Got error: 2013: Lost connection to MySQL server during query when ex
                              ecuting 'REPAIR TABLE ... QUICK'


                              4)

                              dbname_vb.access OK
                              dbname_vb.adminhelp OK
                              dbname_vb.administrator OK
                              dbname_vb.adminlog OK
                              dbname_vb.adminutil OK
                              dbname_vb.announcement OK
                              dbname_vb.attachment OK
                              dbname_vb.attachmenttype OK
                              dbname_vb.attachmentviews OK
                              dbname_vb.avatar OK
                              dbname_vb.bbcode OK
                              dbname_vb.calendar OK
                              dbname_vb.calendarcustomfield OK
                              dbname_vb.calendarmoderator OK
                              dbname_vb.calendarpermission OK
                              dbname_vb.cpsession
                              error : The handler for the table doesn't support repair
                              dbname_vb.cron OK
                              dbname_vb.cronlog OK
                              dbname_vb.customavatar OK
                              mysqlcheck: Got error: 2013: Lost connection to MySQL server during query when ex
                              ecuting 'REPAIR TABLE ... '

                              5)

                              dbname_vb.customprofilepic
                              warning : Table is marked as crashed and last repair failed
                              error : Can't read indexpage from filepos: -1
                              error : Corrupt
                              .

                              Comment

                              widgetinstance 262 (Related Topics) skipped due to lack of content & hide_module_if_empty option.
                              Working...