拷贝版的mysql起不来_求助.mysql起不来了

通过/usr/local/mysql/bin/mysqld_safe --user=myql 启动msql

日志信息：

121121 09:45:54 mysqld_safe Starting mysqld daemon with databases from /data2/mysqldata/data

121121  9:45:54 [Warning] The syntax '--log_slow_queries' is deprecated and will be removed in MySQL 7.0. Please use '--slow_query_log'/'--slow_query_log_file' instead.

121121  9:45:54 [Warning] Ignoring user change to 'myql' because the user was set to 'mysql' earlier on the command line

InnoDB: Log scan progressed past the checkpoint lsn 62 69804011

121121  9:45:54  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 doublewrite

InnoDB: buffer...

InnoDB: Doing recovery: scanned up to log sequence number 62 75046400

InnoDB: Doing recovery: scanned up to log sequence number 62 80289280

InnoDB: Doing recovery: scanned up to log sequence number 62 85532160

InnoDB: Doing recovery: scanned up to log sequence number 62 90775040

InnoDB: Doing recovery: scanned up to log sequence number 62 96017920

InnoDB: Doing recovery: scanned up to log sequence number 62 101260800

InnoDB: Doing recovery: scanned up to log sequence number 62 106503680

InnoDB: Doing recovery: scanned up to log sequence number 62 111746560

InnoDB: Doing recovery: scanned up to log sequence number 62 116989440

InnoDB: Doing recovery: scanned up to log sequence number 62 122232320

InnoDB: Doing recovery: scanned up to log sequence number 62 127475200

InnoDB: Doing recovery: scanned up to log sequence number 62 132718080

InnoDB: Doing recovery: scanned up to log sequence number 62 137960960

InnoDB: Doing recovery: scanned up to log sequence number 62 143203840

InnoDB: Doing recovery: scanned up to log sequence number 62 148446720

InnoDB: Doing recovery: scanned up to log sequence number 62 153689600

InnoDB: Doing recovery: scanned up to log sequence number 62 158932480

InnoDB: Doing recovery: scanned up to log sequence number 62 164175360

InnoDB: Doing recovery: scanned up to log sequence number 62 169418240

InnoDB: Doing recovery: scanned up to log sequence number 62 174661120

InnoDB: Doing recovery: scanned up to log sequence number 62 179904000

InnoDB: Doing recovery: scanned up to log sequence number 62 185146880

InnoDB: Doing recovery: scanned up to log sequence number 62 190389760

InnoDB: Doing recovery: scanned up to log sequence number 62 195632640

InnoDB: Doing recovery: scanned up to log sequence number 62 200875520

InnoDB: Doing recovery: scanned up to log sequence number 62 206118400

InnoDB: Doing recovery: scanned up to log sequence number 62 211361280

InnoDB: Doing recovery: scanned up to log sequence number 62 216604160

InnoDB: Doing recovery: scanned up to log sequence number 62 221847040

InnoDB: Doing recovery: scanned up to log sequence number 62 227089920

InnoDB: Doing recovery: scanned up to log sequence number 62 232332800

InnoDB: Doing recovery: scanned up to log sequence number 62 237575680

InnoDB: Doing recovery: scanned up to log sequence number 62 242818560

InnoDB: Doing recovery: scanned up to log sequence number 62 248061440

InnoDB: Doing recovery: scanned up to log sequence number 62 253304320

InnoDB: Doing recovery: scanned up to log sequence number 62 258547200

InnoDB: Doing recovery: scanned up to log sequence number 62 263790080

InnoDB: Doing recovery: scanned up to log sequence number 62 269032960

InnoDB: Doing recovery: scanned up to log sequence number 62 274275840

InnoDB: Doing recovery: scanned up to log sequence number 62 279518720

InnoDB: Doing recovery: scanned up to log sequence number 62 284761600

InnoDB: Doing recovery: scanned up to log sequence number 62 290004480

InnoDB: Doing recovery: scanned up to log sequence number 62 295247360

InnoDB: Doing recovery: scanned up to log sequence number 62 300490240

InnoDB: Doing recovery: scanned up to log sequence number 62 304395445

InnoDB: 1 transaction(s) which must be rolled back or cleaned up

InnoDB: in total 34897 row operations to undo

InnoDB: Trx id counter is 0 38919424

121121  9:46:31  InnoDB: Starting an apply batch of log records to the database...

InnoDB: Progress in percents: 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99

InnoDB: Apply batch completed

InnoDB: Last MySQL binlog file position 0 214794431, file name /data2/mysqllog/binlog.000554

InnoDB: Starting in background the rollback of uncommitted transactions

121121  9:47:21  InnoDB: Rolling back trx with id 0 38918918, 34897 rows to undo

InnoDB: Progress in percents: 1121121  9:47:21  InnoDB: Started; log sequence number 62 304395445

121121 09:47:21 mysqld_safe mysqld from pid file /data2/mysqldata/data/localhost.localdomain.pid ended

最后启动进程自动退出来了。

[root@localhost ~]# /usr/local/mysql/bin/mysqld_safe --user=myql  121121 09:45:53 mysqld_safe Logging to '/data2/mysqldata/data/localhost.localdomain.err'. chown: "myql": ????? 121121 09:45:54 mysqld_safe Starting mysqld daemon with databases from /data2/mysqldata/data /usr/local/mysql/bin/mysqld_safe: line 133: 11997 ????????                nohup /usr/local/mysql/libexec/mysqld --basedir=/usr/local/mysql --datadir=/data2/mysqldata/data --user=myql --log-error=/data2/mysqldata/data/localhost.localdomain.err --pid-file=/data2/mysqldata/data/localhost.localdomain.pid --socket=/data2/mysqldata/mysql.sock --port=3306 < /dev/null >> /data2/mysqldata/data/localhost.localdomain.err 2>&1 121121 09:47:21 mysqld_safe mysqld from pid file /data2/mysqldata/data/localhost.localdomain.pid ended

请教各位高手，是否有办法把mysql启动起来？

谢谢！