On May 25, 2005, at 9:34 AM, David Brewster wrote:
A client of ours has experienced some rather serious hardware
failures resulting in disk errors and therefore corrupted InnoDB
files.
We could not get mysql to restart unless the innodb_force_recovery
was set to 5. In this situation we encountered failure when
attempting to read from various tables even using the mysql command
prompt.
At this stage we decided to try restoring from backups. Now mysqld
seems to start but then die perpetually but restart itself each
time. This means that if you try something from the mysql command
prompt, it usually gives you, for example something like:
What does the .err log say? It should be in the data directory.
--Ware
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
