P0900
18-12-11, 08:51 AM
<b><font color=red>[Chỉ có thành viên mới xem link được. <a href="register.php"> Nhấp đây để đăng ký thành viên......</a>]</font></b>
STOPPING server from pid file /usr/local/mysql5.0.45/var/localhost.cham5.pid
111218 08:36:22 mysqld ended
vào xem thì nó vầy: có thể sửa hay backup lại dc ko hic :((:((
111218 08:20:27 mysqld started
111218 8:20:27 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...
111218 8:20:28 InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 0 3394195325.
InnoDB: Doing recovery: scanned up to log sequence number 0 3394316735
111218 8:20:28 InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 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 InnoDB: Database page corruption on disk or a failed
InnoDB: file read of page 33330.
InnoDB: You may have to recover from a backup.
111218 8:20:29 InnoDB: Page dump in ascii and hex (16384 bytes):
<b><font color=red>[Chỉ có thành viên mới xem link được. <a href="register.php"> Nhấp đây để đăng ký thành viên......</a>]</font></b>
111218 8:20:29 InnoDB: Page checksum 1649016949, prior-to-4.0.14-form checksum 3698514391
InnoDB: stored checksum 700872225, prior-to-4.0.14-form stored checksum 4210190409
InnoDB: Page lsn 0 3394308942, low 4 bytes of lsn at page end 3394050625
InnoDB: Page number (if stored to page already) 33330,
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 149
InnoDB: Database page corruption on disk or a failed
InnoDB: file read of page 33330.
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 InnoDB: <b><font color=red>[Chỉ có thành viên mới xem link được. <a href="register.php"> Nhấp đây để đăng ký thành viên......</a>]</font></b>
InnoDB: about forcing recovery.
InnoDB: Ending processing because of a corrupt database page.
111218 08:20:29 mysqld ended
STOPPING server from pid file /usr/local/mysql5.0.45/var/localhost.cham5.pid
111218 08:36:22 mysqld ended
vào xem thì nó vầy: có thể sửa hay backup lại dc ko hic :((:((
111218 08:20:27 mysqld started
111218 8:20:27 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...
111218 8:20:28 InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 0 3394195325.
InnoDB: Doing recovery: scanned up to log sequence number 0 3394316735
111218 8:20:28 InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 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 InnoDB: Database page corruption on disk or a failed
InnoDB: file read of page 33330.
InnoDB: You may have to recover from a backup.
111218 8:20:29 InnoDB: Page dump in ascii and hex (16384 bytes):
<b><font color=red>[Chỉ có thành viên mới xem link được. <a href="register.php"> Nhấp đây để đăng ký thành viên......</a>]</font></b>
111218 8:20:29 InnoDB: Page checksum 1649016949, prior-to-4.0.14-form checksum 3698514391
InnoDB: stored checksum 700872225, prior-to-4.0.14-form stored checksum 4210190409
InnoDB: Page lsn 0 3394308942, low 4 bytes of lsn at page end 3394050625
InnoDB: Page number (if stored to page already) 33330,
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 149
InnoDB: Database page corruption on disk or a failed
InnoDB: file read of page 33330.
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 InnoDB: <b><font color=red>[Chỉ có thành viên mới xem link được. <a href="register.php"> Nhấp đây để đăng ký thành viên......</a>]</font></b>
InnoDB: about forcing recovery.
InnoDB: Ending processing because of a corrupt database page.
111218 08:20:29 mysqld ended