Востановить mysql (innodb) после падения

3 000 руб. за проект • электронные деньги
05 сентября 2014, 09:09 • 4 отклика • 26 просмотров

noDB: Cannot continue operation.
140905 9:04:36 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
140905 9:04:36 [Note] Plugin 'FEDERATED' is disabled.
140905 9:04:36 InnoDB: The InnoDB memory heap is disabled
140905 9:04:36 InnoDB: Mutexes and rw_locks use GCC atomic builtins
140905 9:04:36 InnoDB: Compressed tables use zlib 1.2.8
140905 9:04:36 InnoDB: Using Linux native AIO
140905 9:04:36 InnoDB: Initializing buffer pool, size = 54.0G
140905 9:04:38 InnoDB: Completed initialization of buffer pool
140905 9:04:38 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!
140905 9:04:38 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: Error: tried to read 16384 bytes at offset 0 4915200.
InnoDB: Was only able to read -1.
140905 9:04:42 InnoDB: Operating system error number 5 in a file operation.
InnoDB: Error number 5 means 'Input/output error'.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/operating-...
InnoDB: File operation call: 'read'.
InnoDB: Cannot continue operation.
140905 9:04:43 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.