SEO

We have a mysql database that we had setup on a second partition, our first
partition went haywire and had to reinstall the server os. We reinstalled
the os and mysql but when we reattached the data folder that was already
there on the second drive it will not recognize the database. It is setup
as Innodb database and have the frm files and two log files and one
datafile. Running mysqlcheck shuts downs the mysql service. Any help
would be greatly appreciated.

== Quote from Chico Che (jsisk24@yahoo.com)'s article
> We have a mysql database that we had setup on a second partition, our first
> partition went haywire and had to reinstall the server os. We reinstalled
> the os and mysql but when we reattached the data folder that was already
> there on the second drive it will not recognize the database. It is setup
> as Innodb database and have the frm files and two log files and one
> datafile. Running mysqlcheck shuts downs the mysql service. Any help
> would be greatly appreciated.

copy the log files out of the data directory and try to start the server. don't
delete them just copy them to a different location.


--
POST BY: lark with PHP News Reader

lark <hamzee@scglobal.net> wrote in
news:cxBbi.3231$c06.1230@newssvr22.news.prodigy.ne t:

> == Quote from Chico Che (jsisk24@yahoo.com)'s article
>> We have a mysql database that we had setup on a second partition, our
>> first partition went haywire and had to reinstall the server os. We
>> reinstalled the os and mysql but when we reattached the data folder
>> that was already there on the second drive it will not recognize the
>> database. It is setup as Innodb database and have the frm files and
>> two log files and one datafile. Running mysqlcheck shuts downs the
>> mysql service. Any help would be greatly appreciated.
>
> copy the log files out of the data directory and try to start the
> server. don't delete them just copy them to a different location.
>
>
> --
> POST BY: lark with PHP News Reader
>

I get the following on the err.log
070612 21:30:17 InnoDB: Log file .\ib_logfile0 did not exist: new to be
created
InnoDB: Setting log file .\ib_logfile0 size to 10 MB
InnoDB: Database physically writes the file full: wait...
070612 21:30:18 InnoDB: Log file .\ib_logfile1 did not exist: new to be
created
InnoDB: Setting log file .\ib_logfile1 size to 10 MB
InnoDB: Database physically writes the file full: wait...
InnoDB: Cannot initialize created log files because
InnoDB: data files are corrupt, or new data files were
InnoDB: created when the database was started previous
InnoDB: time but the database was not shut down
InnoDB: normally after that.
070612 21:30:19 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin
\mysqld-nt: ready for connections.
Version: '5.0.15-nt' socket: '' port: 3306 Official MySQL binary

Is the data file unfixable?

Chico Che wrote:
> lark <hamzee@scglobal.net> wrote in
> news:cxBbi.3231$c06.1230@newssvr22.news.prodigy.ne t:
>
>> == Quote from Chico Che (jsisk24@yahoo.com)'s article
>>> We have a mysql database that we had setup on a second partition, our
>>> first partition went haywire and had to reinstall the server os. We
>>> reinstalled the os and mysql but when we reattached the data folder
>>> that was already there on the second drive it will not recognize the
>>> database. It is setup as Innodb database and have the frm files and
>>> two log files and one datafile. Running mysqlcheck shuts downs the
>>> mysql service. Any help would be greatly appreciated.
>> copy the log files out of the data directory and try to start the
>> server. don't delete them just copy them to a different location.
>>
>>
>> --
>> POST BY: lark with PHP News Reader
>>
>
> I get the following on the err.log
> 070612 21:30:17 InnoDB: Log file .\ib_logfile0 did not exist: new to be
> created
> InnoDB: Setting log file .\ib_logfile0 size to 10 MB
> InnoDB: Database physically writes the file full: wait...
> 070612 21:30:18 InnoDB: Log file .\ib_logfile1 did not exist: new to be
> created
> InnoDB: Setting log file .\ib_logfile1 size to 10 MB
> InnoDB: Database physically writes the file full: wait...
> InnoDB: Cannot initialize created log files because
> InnoDB: data files are corrupt, or new data files were
> InnoDB: created when the database was started previous
> InnoDB: time but the database was not shut down
> InnoDB: normally after that.
> 070612 21:30:19 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin
> \mysqld-nt: ready for connections.
> Version: '5.0.15-nt' socket: '' port: 3306 Official MySQL binary
>
> Is the data file unfixable?

What messages do you get when the correct log files are in the directory
and you try to start it?

--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstucklex@attglobal.net
==================

Chico Che wrote:
> lark <hamzee@scglobal.net> wrote in
> news:cxBbi.3231$c06.1230@newssvr22.news.prodigy.ne t:
>
>> == Quote from Chico Che (jsisk24@yahoo.com)'s article
>>> We have a mysql database that we had setup on a second partition, our
>>> first partition went haywire and had to reinstall the server os. We
>>> reinstalled the os and mysql but when we reattached the data folder
>>> that was already there on the second drive it will not recognize the
>>> database. It is setup as Innodb database and have the frm files and
>>> two log files and one datafile. Running mysqlcheck shuts downs the
>>> mysql service. Any help would be greatly appreciated.
>> copy the log files out of the data directory and try to start the
>> server. don't delete them just copy them to a different location.
>>
>>
>> --
>> POST BY: lark with PHP News Reader
>>
>
> I get the following on the err.log
> 070612 21:30:17 InnoDB: Log file .\ib_logfile0 did not exist: new to be
> created
> InnoDB: Setting log file .\ib_logfile0 size to 10 MB
> InnoDB: Database physically writes the file full: wait...
> 070612 21:30:18 InnoDB: Log file .\ib_logfile1 did not exist: new to be
> created
> InnoDB: Setting log file .\ib_logfile1 size to 10 MB
> InnoDB: Database physically writes the file full: wait...
> InnoDB: Cannot initialize created log files because
> InnoDB: data files are corrupt, or new data files were
> InnoDB: created when the database was started previous
> InnoDB: time but the database was not shut down
> InnoDB: normally after that.
> 070612 21:30:19 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin
> \mysqld-nt: ready for connections.
> Version: '5.0.15-nt' socket: '' port: 3306 Official MySQL binary
>
> Is the data file unfixable?


i can't answer that question right now! however, there is one more thing
you can do. innodb has an auto-recovery option that must be turned on in
the configuration file for it to recover and repair the files. so
include this in your "my.ini" file:
--innodb-force_recovery = 4
start the server after this without the log files in the data directory.
if the server comes and you can access the table, take a backup of your
table and make sure you take frequent backups from now on.

if the server does not start and spits out error messages, try starting
it with the log files in the data directory and the
--innodb_force_recovery =4 in the "my.ini" file.

if none of these works, i don't know what else you can do except try to
recover them from previous backups (if you have any).

good luck.

lark <hamzee@sbcdeglobalspam.net> wrote in news:qATbi.3690$bP5.1885
@newssvr19.news.prodigy.net:

> --innodb-force_recovery = 4

received a bunch of errors

070614 9:14:03 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...
070614 9:14:03 InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 0 10387270.
InnoDB: Doing recovery: scanned up to log sequence number 0 10418688
070614 9:14:03 InnoDB: Error: page 7 log sequence number 0 13341729
InnoDB: is in the future! Current system log sequence number 0 10418671.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
http://dev.mysql.com/doc/mysql/en/backing-up.html for more information.
InnoDB: Database page corruption on disk or a failed
InnoDB: file read of page 11.
InnoDB: You may have to recover from a backup.
070614 9:14:03 InnoDB: Page dump in ascii and hex (16384 bytes):


and then a bunch ascii data followed by:

InnoDB: stored checksum 1575180971, prior-to-4.0.14-form stored checksum
1527615986
InnoDB: Page lsn 0 13347710, low 4 bytes of lsn at page end 9222184
InnoDB: Page number (if stored to page already) 11,
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 3
InnoDB: (index CLUST_IND of table SYS_INDEXES)
InnoDB: Database page corruption on disk or a failed
InnoDB: file read of page 11.
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.
070614 9:14:03 InnoDB: Error: page 5 log sequence number 0 14450097
InnoDB: is in the future! Current system log sequence number 0 10418671.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
http://dev.mysql.com/doc/mysql/en/backing-up.html for more information.
070614 9:14:03 InnoDB: Error: page 6 log sequence number 0 14453295
InnoDB: is in the future! Current system log sequence number 0 10418671.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
http://dev.mysql.com/doc/mysql/en/backing-up.html for more information.
070614 9:14:03 InnoDB: Error: page 45 log sequence number 0 14453076
InnoDB: is in the future! Current system log sequence number 0 10418671.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
http://dev.mysql.com/doc/mysql/en/backing-up.html for more information.
070614 9:14:03 InnoDB: Error: page 551 log sequence number 0 14453295
InnoDB: is in the future! Current system log sequence number 0 10418671.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
http://dev.mysql.com/doc/mysql/en/backing-up.html for more information.
070614 9:14:03 InnoDB: Starting an apply batch of log records to the
database...
InnoDB: Progress in percents: 21 22 23 24 25 26 27 28 29 30 31 32 33 34
35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58
59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82
83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 070614 9:14:03
InnoDB: Error: page 8 log sequence number 0 13347750
InnoDB: is in the future! Current system log sequence number 0 10418671.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
http://dev.mysql.com/doc/mysql/en/backing-up.html for more information.
070614 9:14:03 InnoDB: Error: page 9 log sequence number 0 13347745
InnoDB: is in the future! Current system log sequence number 0 10418671.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
http://dev.mysql.com/doc/mysql/en/backing-up.html for more information.
070614 9:14:03 InnoDB: Error: page 10 log sequence number 0 13347740
InnoDB: is in the future! Current system log sequence number 0 10418671.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
http://dev.mysql.com/doc/mysql/en/backing-up.html for more information.
070614 9:14:03 InnoDB: Error: page 55 log sequence number 0 14453320
InnoDB: is in the future! Current system log sequence number 0 10418671.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
http://dev.mysql.com/doc/mysql/en/backing-up.html for more information.
070614 9:14:03 InnoDB: Error: page 58 log sequence number 0 14452095
InnoDB: is in the future! Current system log sequence number 0 10418671.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
http://dev.mysql.com/doc/mysql/en/backing-up.html for more information.
InnoDB: Database page corruption on disk or a failed
InnoDB: file read of page 59.
InnoDB: You may have to recover from a backup.
070614 9:14:03 InnoDB: Page dump in ascii and hex (16384 bytes):

and so on....

== Quote from Chico Che (jsisk24@yahoo.com)'s article
> lark <hamzee@sbcdeglobalspam.net> wrote in news:qATbi.3690$bP5.1885
> @newssvr19.news.prodigy.net:
> > --innodb-force_recovery = 4
> received a bunch of errors
> 070614 9:14:03 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...
> 070614 9:14:03 InnoDB: Starting log scan based on checkpoint at
> InnoDB: log sequence number 0 10387270.
> InnoDB: Doing recovery: scanned up to log sequence number 0 10418688
> 070614 9:14:03 InnoDB: Error: page 7 log sequence number 0 13341729
> InnoDB: is in the future! Current system log sequence number 0 10418671.
> InnoDB: Your database may be corrupt or you may have copied the InnoDB
> InnoDB: tablespace but not the InnoDB log files. See
> http://dev.mysql.com/doc/mysql/en/backing-up.html for more information.
> InnoDB: Database page corruption on disk or a failed
> InnoDB: file read of page 11.
> InnoDB: You may have to recover from a backup.
> 070614 9:14:03 InnoDB: Page dump in ascii and hex (16384 bytes):
> and then a bunch ascii data followed by:
> InnoDB: stored checksum 1575180971, prior-to-4.0.14-form stored checksum
> 1527615986
> InnoDB: Page lsn 0 13347710, low 4 bytes of lsn at page end 9222184
> InnoDB: Page number (if stored to page already) 11,
> 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 3
> InnoDB: (index CLUST_IND of table SYS_INDEXES)
> InnoDB: Database page corruption on disk or a failed
> InnoDB: file read of page 11.
> 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.
> 070614 9:14:03 InnoDB: Error: page 5 log sequence number 0 14450097
> InnoDB: is in the future! Current system log sequence number 0 10418671.
> InnoDB: Your database may be corrupt or you may have copied the InnoDB
> InnoDB: tablespace but not the InnoDB log files. See
> http://dev.mysql.com/doc/mysql/en/backing-up.html for more information.
> 070614 9:14:03 InnoDB: Error: page 6 log sequence number 0 14453295
> InnoDB: is in the future! Current system log sequence number 0 10418671.
> InnoDB: Your database may be corrupt or you may have copied the InnoDB
> InnoDB: tablespace but not the InnoDB log files. See
> http://dev.mysql.com/doc/mysql/en/backing-up.html for more information.
> 070614 9:14:03 InnoDB: Error: page 45 log sequence number 0 14453076
> InnoDB: is in the future! Current system log sequence number 0 10418671.
> InnoDB: Your database may be corrupt or you may have copied the InnoDB
> InnoDB: tablespace but not the InnoDB log files. See
> http://dev.mysql.com/doc/mysql/en/backing-up.html for more information.
> 070614 9:14:03 InnoDB: Error: page 551 log sequence number 0 14453295
> InnoDB: is in the future! Current system log sequence number 0 10418671.
> InnoDB: Your database may be corrupt or you may have copied the InnoDB
> InnoDB: tablespace but not the InnoDB log files. See
> http://dev.mysql.com/doc/mysql/en/backing-up.html for more information.
> 070614 9:14:03 InnoDB: Starting an apply batch of log records to the
> database...
> InnoDB: Progress in percents: 21 22 23 24 25 26 27 28 29 30 31 32 33 34
> 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58
> 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82
> 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 070614 9:14:03
> InnoDB: Error: page 8 log sequence number 0 13347750
> InnoDB: is in the future! Current system log sequence number 0 10418671.
> InnoDB: Your database may be corrupt or you may have copied the InnoDB
> InnoDB: tablespace but not the InnoDB log files. See
> http://dev.mysql.com/doc/mysql/en/backing-up.html for more information.
> 070614 9:14:03 InnoDB: Error: page 9 log sequence number 0 13347745
> InnoDB: is in the future! Current system log sequence number 0 10418671.
> InnoDB: Your database may be corrupt or you may have copied the InnoDB
> InnoDB: tablespace but not the InnoDB log files. See
> http://dev.mysql.com/doc/mysql/en/backing-up.html for more information.
> 070614 9:14:03 InnoDB: Error: page 10 log sequence number 0 13347740
> InnoDB: is in the future! Current system log sequence number 0 10418671.
> InnoDB: Your database may be corrupt or you may have copied the InnoDB
> InnoDB: tablespace but not the InnoDB log files. See
> http://dev.mysql.com/doc/mysql/en/backing-up.html for more information.
> 070614 9:14:03 InnoDB: Error: page 55 log sequence number 0 14453320
> InnoDB: is in the future! Current system log sequence number 0 10418671.
> InnoDB: Your database may be corrupt or you may have copied the InnoDB
> InnoDB: tablespace but not the InnoDB log files. See
> http://dev.mysql.com/doc/mysql/en/backing-up.html for more information.
> 070614 9:14:03 InnoDB: Error: page 58 log sequence number 0 14452095
> InnoDB: is in the future! Current system log sequence number 0 10418671.
> InnoDB: Your database may be corrupt or you may have copied the InnoDB
> InnoDB: tablespace but not the InnoDB log files. See
> http://dev.mysql.com/doc/mysql/en/backing-up.html for more information.
> InnoDB: Database page corruption on disk or a failed
> InnoDB: file read of page 59.
> InnoDB: You may have to recover from a backup.
> 070614 9:14:03 InnoDB: Page dump in ascii and hex (16384 bytes):
> and so on....

what this with or without the log files in the data directory?
--
POST BY: lark with PHP News Reader

with log files in there

== Quote from Chico Che (jsisk24@yahoo.com)'s article
> with log files in there

did you try it without the log files in the data directory?
--
POST BY: lark with PHP News Reader

lark <hamzee@sbcglobal.net> wrote in news:rwfci.25503$YL5.7283
@newssvr29.news.prodigy.net:

> == Quote from Chico Che (jsisk24@yahoo.com)'s article
>> with log files in there
>
> did you try it without the log files in the data directory?
> --
> POST BY: lark with PHP News Reader
>

I get the same error I posted before