Dell 2950 Server with Windows Server 2012 R2 Essentials
MySQL 5.6.22
Cannot start MySQL this am after having to force machine shutdown last night due to funky Win update error.
log message shows the following (below) What do I do?
2015-03-14 09:03:22 - Starting server...
2015-03-14 09:03:27 - Server start done.
FROM P1.err:
2015-03-14 09:03:25 6528 Note Plugin 'FEDERATED' is disabled.
2015-03-14 09:03:25 1a88 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2015-03-14 09:03:25 6528 Note InnoDB: Using atomics to ref count buffer pool pages
2015-03-14 09:03:25 6528 Note InnoDB: The InnoDB memory heap is disabled
2015-03-14 09:03:25 6528 Note InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-03-14 09:03:25 6528 Note InnoDB: Memory barrier is not used
2015-03-14 09:03:25 6528 Note InnoDB: Compressed tables use zlib 1.2.3
2015-03-14 09:03:25 6528 Note InnoDB: Not using CPU crc32 instructions
2015-03-14 09:03:25 6528 Note InnoDB: Initializing buffer pool, size = 20.0G
2015-03-14 09:03:27 6528 Note InnoDB: Completed initialization of buffer pool
2015-03-14 09:03:27 6528 Note InnoDB: Highest supported file format is Barracuda.
2015-03-14 09:03:27 6528 Note InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 51076516224 in the ib_logfiles!
2015-03-14 09:03:27 6528 Note InnoDB: Database was not shutdown normally!
2015-03-14 09:03:27 6528 Note InnoDB: Starting crash recovery.
2015-03-14 09:03:27 6528 Note InnoDB: Reading tablespace information from the .ibd files...
2015-03-14 09:03:27 6528 Note InnoDB: Restoring possible half-written data pages
2015-03-14 09:03:27 6528 Note InnoDB: from the doublewrite buffer...
2015-03-14 09:03:27 1a88 InnoDB: Assertion failure in thread 6792 in file fsp0fsp.cc line 1887
InnoDB: Failing assertion: inode
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. Please refer to
InnoDB:
http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
2015-03-14 09:03:29 - Checking server status...
2015-03-14 09:03:29 - Trying to connect to MySQL...
2015-03-14 09:03:29 - Can't connect to MySQL server on '127.0.0.1' (10061) (2003)
2015-03-14 09:03:29 - Assuming server is not running
2015-03-14 09:03:29 - Checking server status...
2015-03-14 09:03:29 - Trying to connect to MySQL...
2015-03-14 09:03:29 - Can't connect to MySQL server on '127.0.0.1' (10061) (2003)
2015-03-14 09:03:29 - Assuming server is not running