Kết quả 1 đến 3 của 3
Chủ đề: MySQL bị lổi ai giúp với
-
18-12-11, 08:51 AM #1
- Ngày tham gia
- Feb 2010
- Bài viết
- 125
- Thanks
- 9
- Thanked 1 Time in 1 Post
MySQL bị lổi ai giúp với
chay start thì : [root@localhost ~]# Starting mysqld daemon with databases from /usr/local/mysql5.0.45/var
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):
len 16384; hex 29c67621000082320000822f000070de00000000ca510b4e45 bf000000000000000000000000009d396583012e3500720000 0005000002f90000000000f474310000000000000000009546 46303030303030303046464646464646463030010002001a69 6e66696d756d0005000b000073757072656d756d0000100013 81c9e2c78001800000000005a98d000018001381c9e2c78001 800000000005aa5e000020001381c9e2c78001800000000005 aa5f040028001381c9e2c78001800000000005aa6000003000 1381c9e2c78001800000000005aa61000038001381c9e2c780 01800000000005aa64000040001381c9e2c780018000000000 05aa65040048001381c9e2c78001800000000005aa70000050 001381c9e2c78001800000000005aa71000058001381c9e2c7 8001800000000005aa72000060001381c9e2c7800180000000 0005aa73040068001381c9e2c78001800000000005aa740000 70001381c9e2c78001800000000005ab07000078001381c9e2 c78001800000000005ab08000080001381c9e2c78001800000 000005acd3040088001381c9e2c78001800000000005acd400 0090001381c9e2c78001800000000005acd5000098001381c9 e2c78001800000000005acd60000a0001381c9e2c780018000 00000005acd70400a8001381c9e2c78001800000000005acd8 0000b0001381c9e2c78001800000000005acd90000b8001381 c9e2c78001800000000005acda0000c0234181c9e2c7800180 0000000005acdb0500c8002681c9e2c78001800000000005ad 5a0000d00df481c9e2c7800180000000000601840000d81c80 81c9e2c78001800000000005ae090000e0001381c9e2c78001 800000000005ae450400e8001381c9e2c78001800000000005 af4a0000f0001381c9e2c78001800000000005af4b0000f800 1381c9e2c78001800000000005af4d000100001381c9e2c780 01800000000005af4e040108001381c9e2c780018000000000 05b0a6000110001381c9e2c78001800000000005b0cd000118 001381c9e2c78001800000000005b11b000120001381c9e2c7 8001800000000005b14e040128001381c9e2c7800180000000 b0b660b1a0ace0a820a36099e0952090608ba086e082207d60 78a073e06f206a6065a059c052a04de0492044603ae0362031 602ca027e023201e6019a014e010200b60063faf26849ca4d1 a41; asc ) v! 2 / p Q NE 9e .5 r t1 FF00000000FFFFFFFF00 infimum supremum ^ _ ( ` 0 a 8 d @ e H p P q X r ` s h t p x #A & Z E J K M N N ( 0 8 @ ( H ] P ^ X ` h p & x Au T * [ ] ^ a b ! & T ( ~ 0 8 @ G H D Y P # X ` h p 6 x q r t u v w r # ( + 0 8 @ I H x P | X"] ` * h c p d x e l U X Y Z [ \ ] 1 Q g h i j k ( l 0 8 @ H P X ` h p x , - . X B U L )j N 9 b u ! _ = p q ( 0 ${ 8 $z @ E H P X ` M h N p O x P Q L R $ I 4f u " # $ % H $ ! ] " = ( 0 . 8 @ t H P X ` h p x # n $ $ ^ 'C g / L & 4< 3 & % W e f ( 0 8 @ H P X 2 ` h p x M C /L D F\ v $ :b p * V W X Y Z [ \ ] 5 V& c d ( q 0 r 8 s @ ; H a P ` X b ` h p x 1 S T U V 9 T U V U V W g ( ( > 0 K 8 X @ Y H Z P X ` h p o x p & 1 ?y 4 ^ _ ` a 9 3 } t 9 [ 0 ( y 0 B 8 ` @ $v H w , P X ` h p x & & , { s LR R " M I a ? M ` ( 9 ( 0 d 8 J @ H P ( X ` h B p ] *+ x F t ^ Z C_ g ( 5 4 u A B ( 0 8 & @ H P X ` h c p x y 6 7 # t Vo !z l D Y e ( 7 0 o R 8 { a @ W : H P :J X f ` > U h a p { 6 x _ s J | F $x c O X 6u # ? 3 6 - K 9 R A !y 'M P ( [ 0 8 Q : @ [ H Q< P :c X { = ` x h t p $y x Av 0 T u & +R n A + d L % K ,+ # " 4 " O ( U~ 0 | 8 c o @ H P $w X M ` h 0 p x Yg K C " 8 <q O` T 2 - 9 X S E 4 <r J ! 0 ^ o 6 ( ! * 0 , :I 8 , @ r | H P X ` N A h " p P x - r 8 y h t ~ q J < 4n 8 z M N Q 8b ` Vm @ " N T ( 0 O 8 , = @ @ H E E P ~ X g ` < h O p x " 0 n k F h 9 9 U ] 7 88 T X 4 *N U R O P Y ^ < M s Fr ( E 0 6 T 8 " :` @ H P Z X < ` R h & F p @ x GO O U { ;{ Z X t S L) T F H } D O B 9 ?z q ) \ PD s 1z 3 ( F 0 V 8 # 4m @ & H S P F X 9 ` ! ? h p } T x 4 * E Op R b 4 ` V Ms ] D L~ u f T J F p I 0V & c YC 4 - Y j J 4 ( . \ 0 F@ 8 M @ J L* H ^2 P m a X Oq ` v ( h UC p [ x S O[ ^ n ] b = [s D KM + V' R W ] (h :_ T O\ a b ! Qi b : ) ( PE 0 l 8 6 @ 5 H S P PG X @M ` O V% h <C p r R x { 5 Q; [d ] B Q R u ] N % D / 6 | @x 4 7 , <A | ^3 1{ O KN R ( 0 Yh 8 O N @ <B H 4 P ] X ( ` Sk h ] Vn p @y x Sj K> L 4; L , ` R C C 9 C :a D U > < PF 1 ( 4= 0 J 4> 8 ? @ H KO P <f X ` ` ^ h D p x 7 k 7 B >9 Q= ; O J & O_ + 4w + N b N N $ N [ [e 7 ( N N p p p . 3 / 1 ( + /R."4 8`2 ) + 9D/,4 &j/x ` $6 " 4%!8 +=5/"U (24K! , . - :# 5. 'N5 d$ ) v / % #&, # "/ 9 f I7 R! 6L H +P + c m 'a48 c (X b ~ 2 N % 't V 1-.5 B ^ z J f 6 R n " > Z * F b ~ 2 N c hI M A;InnoDB: End of page dump
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: [Only registered and activated users can see links. ]
InnoDB: about forcing recovery.
InnoDB: Ending processing because of a corrupt database page.
111218 08:20:29 mysqld endedKhách viếng thăm hãy cùng P0900 xây dựng diễn đàn CLBGAMESVN vững mạnh nhé!
-
18-12-11, 09:03 AM #2
- Ngày tham gia
- Apr 2011
- Đang ở
- 地獄
- Bài viết
- 3,991
- Thanks
- 369
- Thanked 4,069 Times in 1,403 Posts
Ðề: MySQL bị lổi ai giúp với
Chạy thử ./tlbb.sh xem... Cái Sv 4 lỗ nó lỗi lung tung nhưng vẫn khởi động + vào game đc...
Warning: Lần sau post câu hỏi vào mục hỏi đáp yêu cầu ko post vào ReleaseKhách viếng thăm hãy cùng Sói Đẹp Trai xây dựng diễn đàn CLBGAMESVN vững mạnh nhé!
-
Các thành viên gởi lời cảm ơn đến Sói Đẹp Trai vì bài viết này !
viking29 (20-12-11)
-
18-12-11, 09:23 AM #3
- Ngày tham gia
- Feb 2010
- Bài viết
- 125
- Thanks
- 9
- Thanked 1 Time in 1 Post
Ðề: MySQL bị lổi ai giúp với
uhm sr mod.
cái này star msql ko dc mà lệnh .SH cũng vậy thôi hicKhách viếng thăm hãy cùng P0900 xây dựng diễn đàn CLBGAMESVN vững mạnh nhé!
Các Chủ đề tương tự
-
Lỗi MySQL
Bởi sako1906 trong diễn đàn Hỏi Đáp/ Yêu CầuTrả lời: 0Bài viết cuối: 11-09-10, 10:16 AM -
Ai chỉ dùm mình cách cài MySQL
Bởi tritri0808 trong diễn đàn Cabal OnlineTrả lời: 0Bài viết cuối: 13-04-10, 09:26 PM -
help lổi gì đây (MYSQL)
Bởi longryu trong diễn đàn Hỏi Đáp/ Yêu CầuTrả lời: 0Bài viết cuối: 20-12-09, 03:27 PM -
Lỗi khi cài MySQL
Bởi langbat trong diễn đàn Hỏi Đáp/ Yêu CầuTrả lời: 2Bài viết cuối: 20-12-09, 03:23 PM