MySQL (InnoDB) failure

Received SMS alarm, is a R710 hard disk (Raid5 8 block) Bad 1, contact room replacement hard disk, because of the slot problem   changed a few new hard drive after the bright yellow light, and the original 1 hard disk after the change, bright green, after a few minutes machine downtime .... After the analysis is the motherboard problem, it also found 1 new r710  will not light the machine on the hard drive to unplug the new R710, the Raid information import   card in a place, found that the hard drive has a bright yellow light, again replace the bad hard drive, can enter the system, After entering the system to find the MySQL process, 3306 port is not listening, MySQL error log has been output innodb: log scan progressed past the  checkpoint lsn 1613 2401579069150613 20:34:29  InnoDB: Database  was not shut down normally! Innodb: starting crash recovery. Innodb: reading tablespace information from the .ibd files ... innodb: restoring possible half-written data pages from the  Doublewriteinnodb: buffer ... innodb: doing recovery: scanned up to log sequence number 1613  2406821888InnoDB: Doing recovery: scanned up to log sequence  Number 1613 2412064768innodb: doing recovery: scanned up to log sequence number 1613  2417307648innodb: doing recovery: scanned up to log sequence number  1613 2422550528InnoDB: Doing recovery: scanned up to log  Sequence number 1613 2427793408innodb: doing recovery: scanned up to  log sequence number 1613 2433036288innodb: doing recovery: scanned  up to log sequence number 1613 2438279168innodb: doing recovery:  scanned up to log sequence number 1613 2443522048innodb: doing  recovery: scanned up to log sequence number 1613  2448764928innodb: doing recovery: scanned up to log sequence number  1613 2454007808innodb: doing&nbSp;recovery: scanned up to log sequence number 1613 2459250688innodb:  Doing recovery: scanned up to log sequence number 1613  2464493568innodb: doing recovery: scanned up to log sequence number  1613 2469736448ps aux |grep mysqlroot      2011   0.0  0.0  17332  1468 ?         S    20:34   0:00 /bin/sh /usr/bin/mysqld_safemysql      2042 75.9 32.0 11650168 10559232 ?   Rl    20:34  15:15 /usr/sbin/mysqld --basedir=/usr --datadir=/opt/mysql -- user=mysql --pid-file=/opt/mysql/1.1.1.1.pid --skip-external-locking --open-files-limit=8192  --port=3306 --socket=/var/run/mysqld/mysqld.socknetstat -tupnl |grep 3306 processing Results   continued 

This article is from the "7928217" blog, please be sure to keep this source http://7938217.blog.51cto.com/7928217/1661657

MySQL (InnoDB) failure