php newbie Posted February 24, 2013 Report Share Posted February 24, 2013 uzkaras skripts un MySQL serveri nevar piestartēt: 130224 13:11:28 [Note] Plugin 'FEDERATED' is disabled. InnoDB: The InnoDB memory heap is disabled InnoDB: Mutexes and rw_locks use Windows interlocked functions InnoDB: Compressed tables use zlib 1.2.3 130224 13:11:28 InnoDB: Initializing buffer pool, size = 16.0M 130224 13:11:28 InnoDB: Completed initialization of buffer pool 130224 13:11:28 InnoDB: highest supported file format is Barracuda. InnoDB: The log sequence number in ibdata files does not match InnoDB: the log sequence number in the ib_logfiles! 130224 13:11:28 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: Database page corruption on disk or a failed InnoDB: file read of page 245. InnoDB: You may have to recover from a backup. InnoDB: End of page dump 130224 13:11:30 InnoDB: Page checksum 2870860906, prior-to-4.0.14-form checksum 372330996 InnoDB: stored checksum 1529325762, prior-to-4.0.14-form stored checksum 372330996 InnoDB: Page lsn 0 682665087, low 4 bytes of lsn at page end 682665087 InnoDB: Page number (if stored to page already) 245, InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 0 InnoDB: Page may be a system page InnoDB: Database page corruption on disk or a failed InnoDB: file read of page 245. 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/refman/5.1/en/forcing-recovery.html InnoDB: about forcing recovery. InnoDB: Ending processing because of a corrupt database page. sanāca piestartēt ar innodb_force_recovery = 5, kas nozīmē: Do not look at undo logs when starting the database: InnoDB treats even incomplete transactions as committed.Un kā izlabot? Quote Link to comment Share on other sites More sharing options...
php newbie Posted February 24, 2013 Author Report Share Posted February 24, 2013 ar check table dabūju: InnoDB: The B-tree of index 'artist_id' is corrupted.Drošivien vajadzēs nonest to tabulu? Quote Link to comment Share on other sites More sharing options...
marrtins Posted February 24, 2013 Report Share Posted February 24, 2013 Ar to force_recovery uztaisi dump, pārliecinies vai viss kārtībā (ieimportē citā serverī) un tad uz salauztā servera vnk nodropo kas dropojams un ieimportē pa jaunam. Quote Link to comment Share on other sites More sharing options...
php newbie Posted February 24, 2013 Author Report Share Posted February 24, 2013 (edited) nodropoju db ar kuru laikam bija problēma (citas db sen neesmu izmantojis), bet nekā. man ir tur kopā 12 db... edit: nodropoju visas db. vienalga neiet Edited February 24, 2013 by php newbie Quote Link to comment Share on other sites More sharing options...
marrtins Posted February 24, 2013 Report Share Posted February 24, 2013 Nu tad iespējams ir beigts galvenais innodb fails? Izdzēs visu nafig un uzstādi pa jaunam :D Škiet Debian pietika izdzēst /var/lib/mysql un startup skripts izveidos sākuma installu pa jaunam. Quote Link to comment Share on other sites More sharing options...
php newbie Posted February 24, 2013 Author Report Share Posted February 24, 2013 man ir xampp uz usb flash :) nobekapoju visu mysql folderi. iemetu mysql folderi no tiras xampp instalācijas. ieimporteju db un tagad viss strādā. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.