因为机房断电，
再次打开的机器，用MYSQL -U 用户名 -P密码登录的时候就提示：
ERROR 2002: Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (111)INNODB的格式，不知道如何恢复数据，网上查看了一些mysql。sock报错的解决方法，不太管用，如果有兄弟处理过类似问题，请教小弟一把，不甚感谢
再次打开的机器，用MYSQL -U 用户名 -P密码登录的时候就提示：
ERROR 2002: Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (111)INNODB的格式，不知道如何恢复数据，网上查看了一些mysql。sock报错的解决方法，不太管用，如果有兄弟处理过类似问题，请教小弟一把，不甚感谢
下面是我/var/log/mysqld.log
请兄弟们帮忙看看
100504 17:01:14 mysqld started
100504 17:01:15 InnoDB: Database was not shut down normally.
InnoDB: Starting recovery from log files...
InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 0 1376708
InnoDB: Doing recovery: scanned up to log sequence number 0 1376708
InnoDB: Page directory corruption: supremum not pointed to
100504 17:01:15 InnoDB: Page dump in ascii and hex (16384 bytes):
len 16384; hex ;InnoDB: End of page dump
100504 17:01:15 InnoDB: Page checksum 1575996416, prior-to-4.0.14-form checksum 1371122432
InnoDB: stored checksum 0, prior-to-4.0.14-form stored checksum 0
InnoDB: Page lsn 0 0, low 4 bytes of lsn at page end 0
InnoDB: Error: trying to access a stray pointer 0x37f4fff8
InnoDB: buf pool start is at 0x9ff5c000, number of pages 24576
100504 17:01:15InnoDB: Assertion failure in thread 16198480 in file ../../innobase/include/buf0buf.ic line 282
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. See section 6.1 of
InnoDB: http://www.innodb.com/ibman.php about forcing recovery.
mysqld got signal 11;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help diagnose
the problem, but since we have already crashed, something is definitely wrong
and this may fail.key_buffer_size=16777216
read_buffer_size=258048
max_used_connections=0
max_connections=300
threads_connected=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 245581 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.100504 17:01:15 mysqld ended