Hey there,
I have recently imported the database files from a crashed server and I am currently trying to get the new server running with the old data. However, after starting the MySQL Server, I only get the following error message: 091214 20:51:46 mysqld started InnoDB: The user has set SRV_FORCE_NO_LOG_REDO on InnoDB: Skipping log redo InnoDB: Error: page n:o stored in the page read in is 538976288, should be 3! InnoDB: Database page corruption on disk or a failed InnoDB: file read of page 3. InnoDB: You may have to recover from a backup. 091214 20:51:47 InnoDB: Page dump in ascii and hex (16384 bytes): len 16384; hex 2020202020202020202020202020202020202020202020202020202020202020202020202020 20202020202020202020202020202020202020202020202020202020202$ 091214 20:51:47 InnoDB: Page checksum 1605920614, prior-to-4.0.14-form checksum 3161919040 InnoDB: stored checksum 538976288, prior-to-4.0.14-form stored checksum 236985105 InnoDB: Page lsn 538976288 538976288, low 4 bytes of lsn at page end 10651 InnoDB: Page number (if stored to page already) 538976288, InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 538976288 InnoDB: Database page corruption on disk or a failed InnoDB: file read of page 3. 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. After that, the following error message is looped: 091214 20:51:47 InnoDB: Error: trying to access tablespace 538976288 page no. 538976288, InnoDB: but the tablespace does not exist or is just being dropped. The MySQL server then is unusable and is taking 99% CPU ressources. I tried to use the innodb_force_recovery option in the my.cfg file, but that did not change this behavior. Does anyone have an idea for me to restore the databases? I have no backup and rely on getting this files back to work. Any help is appreciated, thanks in advance, Lukas ________________________________ Lukas C. C. Hempel Delux Group - Approaching future. <http://www.delux.me/> www.delux.me Postfach 10 02 10 D-48051 Münster This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorised copying, disclosure or distribution of the material in this e-mail is strictly forbidden. Delux Credit: <http://www.delux-credit.com/> www.delux-credit.com Delux Host: <http://www.delux-host.com/> www.delux-host.com Delux Software: <http://www.delux.me/> www.delux.me Admin panel: <http://admin.delux-host.com/> http://admin.delux-host.com Paypal: <mailto:pay...@delux-host.com> pay...@delux-host.com Delux is a company of Lukas Hempel, Tax ID: 337/5105/2023
