Mysql – Rebuilding corrupt slave by copying thesql folder

As previously suggested, look in the var directory for the .err file. If it shows nothing, what if you issue: show slave status\G, it should print a line with the error.

Further to this, if you have the SQL thread running but the IO thread stopped, this suggests there's a problem in the communication between your slave and your master. From you "CHANGE MASTER" line, you are not specifying the port number. MySQL defaults to 3306, but are you running the server on that port? Also, is that file you are specifying, mysql-bin.000011 available in the master? And the master can read it, right?

Last, did you grant permissions for the replication user? (as in, have you done it properly, as MySQL manual specifies).

And, apart from this, don't know what else to check, maybe would sniff the network to see if there's any traffic, or just execute mysqlbinlog mysql-bin.000011 to see everything is fine there at that position.

I think I see the problem

You have the following in your question:

Replicate_Do_DB: db1; db2

That is not supposed to be a semicolon-separated list. It is supposed to be a comma-separated list.

My guess is your have this in your slave's /etc/my.cnf

replicate-do-db=db1; db2

The correct way to set this up is

replicate-do-db=db1
replicate-do-db=db2

Please adjust this in the slave's /etc/my.cnf and restart mysql on the slave

Give it a Try !!!

UPDATE 2011-10-31 15:20 EDT

You may want to clear out the relay log by doing this

STOP SLAVE;
CHANGE MASTER TO master_log_file='mysql-bin.000008',master_log_pos-98;
START SLAVE;

then run SHOW SLAVE STATUS\G and make sure replication is running by making sure you see this

Slave_IO_Running: Yes
Slave_SQL_Running: Yes

just as you posted in your question