LinuxQuestions.org
Help answer threads with 0 replies.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Server
User Name
Password
Linux - Server This forum is for the discussion of Linux Software used in a server related context.

Notices


Reply
  Search this Thread
Old 03-07-2015, 06:58 PM   #1
!! hack-back !!
Member
 
Registered: Nov 2009
Posts: 183

Rep: Reputation: 2
mysql wont start


InnoDB: Page lsn 7 3803765998, low 4 bytes of lsn at page end 3803751733
InnoDB: Page number (if stored to page already) 12121,
InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 0
InnoDB: Page may be an index page where index id is 0 42
InnoDB: Also the page in the doublewrite buffer is corrupt.
InnoDB: Cannot continue operation.
InnoDB: You can try to recover the database with the my.cnf
InnoDB: option:
InnoDB: innodb_force_recovery=6
150308 09:43:50 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended




also i dont have backup for my database and i dont want to lose any data its to emergency !!
what i can do ???
Thanks
 
Old 03-07-2015, 07:19 PM   #2
mkmety
LQ Newbie
 
Registered: Mar 2015
Location: USA
Posts: 3

Rep: Reputation: Disabled
Have you tried forcing a recovery by adding innodb_force_recovery = 1 to the mysqld section of your conf file?

Also, not having a backup of your database may cause you to have data loss if a recovery does not work.
 
Old 03-07-2015, 07:43 PM   #3
!! hack-back !!
Member
 
Registered: Nov 2009
Posts: 183

Original Poster
Rep: Reputation: 2
adding innodb_force_recovery = 1>5
not make it start
but when i put innodb_force_recovery = 6
the error in log changed


150308 13:42:43 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
/usr/libexec/mysqld: Can't find file: './mysql/plugin.frm' (errno: 13)
150308 13:42:43 [ERROR] Can't open the mysql.plugin table. Please run mysql_upgrade to create it.
150308 13:42:43 InnoDB: Initializing buffer pool, size = 8.0M
150308 13:42:43 InnoDB: Completed initialization of buffer pool
InnoDB: The user has set SRV_FORCE_NO_LOG_REDO on
InnoDB: Skipping log redo
150308 13:42:43 InnoDB: Started; log sequence number 0 0
InnoDB: !!! innodb_force_recovery is set to 6 !!!
150308 13:42:43 [ERROR] /usr/libexec/mysqld: Can't find file: './mysql/host.frm' (errno: 13)
150308 13:42:43 [ERROR] Fatal error: Can't open and lock privilege tables: Can't find file: './mysql/host.frm' (errno: 13)
150308 13:42:43 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended

---------- Post added 03-07-15 at 08:43 PM ----------

adding innodb_force_recovery = 1>5
not make it start
but when i put innodb_force_recovery = 6
the error in log changed


150308 13:42:43 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
/usr/libexec/mysqld: Can't find file: './mysql/plugin.frm' (errno: 13)
150308 13:42:43 [ERROR] Can't open the mysql.plugin table. Please run mysql_upgrade to create it.
150308 13:42:43 InnoDB: Initializing buffer pool, size = 8.0M
150308 13:42:43 InnoDB: Completed initialization of buffer pool
InnoDB: The user has set SRV_FORCE_NO_LOG_REDO on
InnoDB: Skipping log redo
150308 13:42:43 InnoDB: Started; log sequence number 0 0
InnoDB: !!! innodb_force_recovery is set to 6 !!!
150308 13:42:43 [ERROR] /usr/libexec/mysqld: Can't find file: './mysql/host.frm' (errno: 13)
150308 13:42:43 [ERROR] Fatal error: Can't open and lock privilege tables: Can't find file: './mysql/host.frm' (errno: 13)
150308 13:42:43 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
 
Old 03-07-2015, 07:57 PM   #4
!! hack-back !!
Member
 
Registered: Nov 2009
Posts: 183

Original Poster
Rep: Reputation: 2
using innodb_force_recovery = 6
now i see a lot


InnoDB: mysqld and edit my.cnf so that newraw is replaced
InnoDB: with raw, and innodb_force_... is removed.
InnoDB: A new raw disk partition was initialized or
InnoDB: innodb_force_recovery is on: we do not allow
InnoDB: database modifications by the user. Shut down
InnoDB: mysqld and edit my.cnf so that newraw is replaced
InnoDB: with raw, and innodb_force_... is removed.
InnoDB: A new raw disk partition was initialized or
InnoDB: innodb_force_recovery is on: we do not allow
InnoDB: database modifications by the user. Shut down
InnoDB: mysqld and edit my.cnf so that newraw is replaced
InnoDB: with raw, and innodb_force_... is removed.
InnoDB: A new raw disk partition was initialized or
InnoDB: innodb_force_recovery is on: we do not allow
InnoDB: database modifications by the user. Shut down
InnoDB: mysqld and edit my.cnf so that newraw is replaced
InnoDB: with raw, and innodb_force_... is removed.
InnoDB: A new raw disk partition was initialized or
InnoDB: innodb_force_recovery is on: we do not allow
InnoDB: database modifications by the user. Shut down
InnoDB: mysqld and edit my.cnf so that newraw is replaced
InnoDB: with raw, and innodb_force_... is removed.
InnoDB: A new raw disk partition was initialized or
InnoDB: innodb_force_recovery is on: we do not allow
InnoDB: database modifications by the user. Shut down
InnoDB: mysqld and edit my.cnf so that newraw is replaced
InnoDB: with raw, and innodb_force_... is removed.
 
Old 03-09-2015, 02:33 AM   #5
ChooseLife
Member
 
Registered: May 2007
Distribution: Ubuntu, RHEL, Slackware
Posts: 49

Rep: Reputation: 17
Quote:
Originally Posted by !! hack-back !! View Post
also i dont have backup for my database and i dont want to lose any data its to emergency !!
what i can do ???
Before you do anything next, take a proper backup of your data!
 
Old 03-09-2015, 02:42 AM   #6
astrogeek
Moderator
 
Registered: Oct 2008
Distribution: Slackware [64]-X.{0|1|2|37|-current} ::12<=X<=15, FreeBSD_12{.0|.1}
Posts: 6,269
Blog Entries: 24

Rep: Reputation: 4206Reputation: 4206Reputation: 4206Reputation: 4206Reputation: 4206Reputation: 4206Reputation: 4206Reputation: 4206Reputation: 4206Reputation: 4206Reputation: 4206
!!!STOP DOING ANYTHING UNTIL YOU KNOW WHAT EFFECT IT WILL HAVE!!!

You have probably already lost data... from the MySQL Manual...

Quote:
Warning

Only set innodb_force_recovery to a value greater than 0 in an emergency situation, so that you can start InnoDB and dump your tables. Before doing so, ensure that you have a backup copy of your database in case you need to recreate it. Values of 4 or greater can permanently corrupt data files. Only use an innodb_force_recovery setting of 4 or greater on a production server instance after you have successfully tested the setting on separate physical copy of your database. When forcing InnoDB recovery, you should always start with innodb_force_recovery=1 and only increase the value incrementally, as necessary.
Read that page in full before continuing...

Make a filesystem backup of the data directories before doing anything else - that will be your only recovery path beyond this point I think.

Last edited by astrogeek; 03-09-2015 at 02:53 AM.
 
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Freshly installed Mysql (mysql-community-server) fails to start cpartsenidis Linux - Software 2 02-12-2015 12:41 AM
Mysql Key buffer size: Timeout error occurred trying to start MySQL Daemon. postcd Linux - Server 0 03-13-2014 08:45 PM
Problem changing mysql uid,gid: mysql start fails gjatute Linux - Newbie 7 02-25-2010 01:38 AM
I have RHEL 5.0 and MySQL start problem, my MySQL server doesn't start rsatya Linux - Enterprise 4 02-03-2009 12:04 PM
mysql wont start dave`2005 Slackware 10 06-01-2006 09:06 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Server

All times are GMT -5. The time now is 07:38 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration