Re: Corruptions like crazy

[Andrew Grimo]

Hi John,

Answer to question 1: Yes..you're right, I incorrectly named the file, it should be database-data.sql. In reality the files could be named anything, my naming was to give the files relevance to their contents.

You can test logging in to gain some confidence by just using the first portion of the command as below. This is simply using the 'mysql' command line client to access the database.
# mysql -uroot -p
mysql> show schemas;
mysql> use [any-database/schema-name];
mysql> select count(*) from [table-name]; (this will select the table named for the database you are "use"ing)
mysql> quit (to exit)

Answer to question 2: Disk is probably fine, your handling of things was reasonable for what you had to work with. Innodb tables are much more resilient to abuse. MyISAM tables need more care and precise fixes. For all your efforts, the tables weren't really getting fixed....switching to Innodb should solve things for you. Innodb is the right way to go anyhow.

I'm not sure how your Web Builder builds out a database, but you should also look at the parameters to make sure it creates Innodb based tables going forward. There may be an option in your configuration for it. If not, this should solve things for now.

Oh...also, correction on my upgrade instructions....use these below

The database should be running when you run your upgrade. Stop and start it after the upgrade though.

# mysql_upgrade -uroot -p
# service mysqld stop
# service mysqld start

Give this a try!

Andrew