Yes, I ran into this this morning as well. With MyISAM, you only need to move the database files, but because InnoDB was involved this time, simply doing that caused the tables to stop being recognized. When this happens, the installation screen seems to appear. You must not install anything here. Somehow, the database has to be restored.
I also found online that it might be enough to bring over /var/lib/mysql/ibdata1 and similar files, but that did not seem appropriate where other sites were already running. It looked as though the sites that were working safely now might stop working.
With no other choice, I tried dumping the original database with mysqldump 1 and then importing it again, but that also stopped working. Apparently, one of the tables had become corrupted. In fact, checktable produced an error in one database. That table did not appear to be in use, so I used drop table, and mysqldump then completed successfully. It looks like this.
$ /usr/bin/mysqldump -u root -p hogehoge > ./hogehoge.sql
On the destination host, I used drop database hogehoge and created the database again. After importing the dump, I successfully escaped the installation screen, and the site displayed properly.
Related posts
Localizing the WordPress Theme Minimal Xpert into Japanese
One WordPress theme I have recently come to like is Minimal Xpert. I had been using it for some time on the Cimbalom World Association website,…
If You’re Making a Presentation, gamma.app May Be the Way to Go
Yesterday, information saying, “If you’re making a presentation, use gamma.app,” reached me from 2 independent directions. So I started by trying the free version. To give…
Why Doesn’t Apache Apply DefaultCharSet Even When It Is Specified?!
I got a little stuck on this... Have you ever migrated an old EUC-JP or Shift JIS site to a new server and ended up with…