[SOLVED] InnoDB trouble after 5.0 to 5.5 upgrade (1 reply)

Hello,

I recently upgraded mysql 5.0.90 to 5.5.20.

After the upgrade mysqld would not start without innodb_force_recovery. Without this directive, the following errors occur:

120208 13:40:35 InnoDB: Error: trying to access tablespace 1 page no. 252,
InnoDB: but the tablespace does not exist or is just being dropped.
120208 13:40:35 InnoDB: Error: trying to access tablespace 1 page no. 252,
InnoDB: but the tablespace does not exist or is just being dropped.

I tried stopping the service, removing ib_logfile* and restarting. This allows the server to start without innodb_force_recovery.

However, there are CREATE TABLE errors, and when the service is restarted the original tablespace errors return. Creation of MyISAM tables is succesful, creation of InnoDB tables fails with error:

120209 11:06:42 [ERROR] Cannot find or open table maia/users from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.



I'm getting phpMyAdmin control user errors and when I attempt to change the pma user password an eror occurs:

SET PASSWORD FOR 'pma'@'localhost' = PASSWORD( '*********' )
MySQL said: #1133 - Can't find any matching row in the user table

Prior to the upgrade, all tables where MyISAM.

Any suggestions to correct this issue would be greatly appreciated! We're currently limping along with the innodb_force_recovery set and unable to update user permissions and run CREATE TABLE sql.

Thank You!