1. Please take a little time for this simple survey! Thank you for participating!
    Dismiss Notice
  2. Dear Pleskians, please read this carefully! New attachments and other rules Thank you!
    Dismiss Notice
  3. Dear Pleskians, I really hope that you will share your opinion in this Special topic for chatter about Plesk in the Clouds. Thank you!
    Dismiss Notice

Urgent Help Needed - MySQL won't start.

Discussion in 'Plesk for Linux - 8.x and Older' started by Raydr, Dec 4, 2006.

  1. Raydr

    Raydr Guest

    0
     
    I'm a novice when it comes to FreeBSD and I need desperate help.

    I did a restart through the Plesk Web interface, and when the server came back up I was getting all sorts of mysql errors. I have no idea what to do at this point...

    Here is the log:


    Here's the log:
    061204 18:11:23 mysqld started
    061204 18:11:23 InnoDB: Database was not shut down normally!
    InnoDB: Starting crash recovery.
    InnoDB: Reading tablespace information from the .ibd files...
    InnoDB: Restoring possible half-written data pages from the doublewrite
    InnoDB: buffer...
    InnoDB: Error: tried to read 16384 bytes at offset 0 81920.
    InnoDB: Was only able to read -1.
    061204 18:11:24 InnoDB: Operating system error number 5 in a file operation.
    InnoDB: Error number 5 means 'Input/output error'.
    InnoDB: Some operating system error numbers are described at
    InnoDB: http://dev.mysql.com/doc/mysql/en/Operating_System_error_codes.html
    InnoDB: File operation call: 'read'.
    InnoDB: Cannot continue operation.
    061204 18:11:24 mysqld ended

    061204 18:14:23 mysqld started
    061204 18:14:23 InnoDB: Database was not shut down normally!
    InnoDB: Starting crash recovery.
    InnoDB: Reading tablespace information from the .ibd files...
    InnoDB: Restoring possible half-written data pages from the doublewrite
    InnoDB: buffer...
    InnoDB: Error: tried to read 16384 bytes at offset 0 81920.
    InnoDB: Was only able to read -1.
    061204 18:14:25 InnoDB: Operating system error number 5 in a file operation.
    InnoDB: Error number 5 means 'Input/output error'.
    InnoDB: Some operating system error numbers are described at
    InnoDB: http://dev.mysql.com/doc/mysql/en/Operating_System_error_codes.html
    InnoDB: File operation call: 'read'.
    InnoDB: Cannot continue operation.
    061204 18:14:25 mysqld ended
     
  2. wagnerch

    wagnerch Guest

    0
     
    Was there a particular reason you restarted the server? Performance issues? Slow?

    It appears that either a) mysql was not shut down properly, or b) there is corruption on your disk and/or disk failure. The reason I say this is because the InnoDB tablespace in mysql appears to be unreadable. Was there anything else changed? Perhaps, not recently? Are you sure your my.cnf file has not been adjusted?
     
  3. Raydr

    Raydr Guest

    0
     
    hi there.

    The hard drive was going bad. It has been replaced and the data put on the new drive.

    Here is the new problem:
    061208 23:25:12 mysqld started
    061208 23:25:12 InnoDB: Database was not shut down normally!
    InnoDB: Starting crash recovery.
    InnoDB: Reading tablespace information from the .ibd files...
    InnoDB: Restoring possible half-written data pages from the doublewrite
    InnoDB: buffer...
    061208 23:25:12 InnoDB: Starting log scan based on checkpoint at
    InnoDB: log sequence number 0 229352136.
    InnoDB: Doing recovery: scanned up to log sequence number 0 229352146
    InnoDB: Error: page n:eek: stored in the page read in is 3221225495, should be 5!
    InnoDB: Database page corruption on disk or a failed
    InnoDB: file read of page 5.
    InnoDB: You may have to recover from a backup.
    061208 23:25:12 InnoDB: Page dump in ascii and hex (16384 bytes):
    len 16384; hex c1123318c0000017a00000811f80002901c880100dbb92f500124000000000000124000500000000070000625104000045444250202300f2000021000004008200022000fff7e37f00030008f37ffbff00000000ffffffff00000002fffefff
    061208 23:25:12 InnoDB: Page checksum 3164658077, prior-to-4.0.14-form checksum 1830751922
    InnoDB: stored checksum 3239195416, prior-to-4.0.14-form stored checksum 0
    InnoDB: Page lsn 29917200 230396661, low 4 bytes of lsn at page end 0
    InnoDB: Page number (if stored to page already) 3221225495,
    InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 327680
    InnoDB: Database page corruption on disk or a failed
    InnoDB: file read of page 5.
    InnoDB: You may have to recover from a backup.
    InnoDB: It is also possible that your operating
    InnoDB: system has corrupted its own file cache
    InnoDB: and rebooting your computer removes the
    InnoDB: error.
    InnoDB: If the corrupt page is an index page
    InnoDB: you can also try to fix the corruption
    InnoDB: by dumping, dropping, and reimporting
    InnoDB: the corrupt table. You can use CHECK
    InnoDB: TABLE to scan your table for corruption.
    InnoDB: See also http://dev.mysql.com/doc/mysql/en/Forcing_recovery.html
    InnoDB: about forcing recovery.
    InnoDB: Ending processing because of a corrupt database page.
    061208 23:25:12 mysqld ended


    The original table files seem to be perfectly fine...so how can I get MysQL to start running again?
     
  4. Raydr

    Raydr Guest

    0
     
  5. Raydr

    Raydr Guest

    0
     
    Ah ****. So I guess Plesk uses innodb.

    Now I'm really lost. I don't have a backup of those files...I just have the corrupted ones, I guess.

    Any advice?
     
  6. wagnerch

    wagnerch Guest

    0
     
    I guess your screwed. I can't think of anything. This is why backups are important, especially for a non-RAID environment.

    It looks like your best hope is following the advice that MySQL put in the log:

    http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html

    The issue is that there will likely be a table or two that is corrupt and you would have to manually reconstruct the data. I can tell you that if Plesk has a table with a single row missing then it will be total hell when you are trying to remove domains, etc.
     
Loading...