Hi,
Thanks for replying. It might be that the database and ib_logfile(s) are corrupted. And as a side note, I am now using MySQL Server 5.6 as this is the only version I can get to work, and I feel that this alone could be conflicting with data from the MySQL Server 5.5 database, although my knowledge doesn't stretch far enough to be sure.
Log file says:
120512 17:15:43 [Note] Plugin 'FEDERATED' is disabled.
120512 17:15:43 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.
120512 17:15:43 InnoDB: The InnoDB memory heap is disabled
120512 17:15:43 InnoDB: Mutexes and rw_locks use Windows interlocked functions
120512 17:15:43 InnoDB: Compressed tables use zlib 1.2.3
120512 17:15:43 InnoDB: CPU does not support crc32 instructions
120512 17:15:43 InnoDB: Initializing buffer pool, size = 473.0M
120512 17:15:43 InnoDB: Completed initialization of buffer pool
120512 17:15:43 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!
120512 17:15:43 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...
120512 17:15:43 InnoDB: Assertion failure in thread 5512 in file fsp0fsp.cc line 1964
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.