MySQL启动报错 Starting MySQL.The server quit without updating PID file

启动日志如下，帮忙找下问题所在
161116 09:30:31 mysqld_safe Starting mysqld daemon with databases from /data/mysql
2016-11-16 09:30:31 0 [Note] /usr/local/mysql/bin/mysqld (mysqld 5.6.27-log) starting as process 12925 ...
2016-11-16 09:30:31 12925 [Note] Plugin 'FEDERATED' is disabled.
2016-11-16 09:30:31 12925 [Note] InnoDB: Using atomics to ref count buffer pool pages
2016-11-16 09:30:31 12925 [Note] InnoDB: The InnoDB memory heap is disabled
2016-11-16 09:30:31 12925 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2016-11-16 09:30:31 12925 [Note] InnoDB: Memory barrier is not used
2016-11-16 09:30:31 12925 [Note] InnoDB: Compressed tables use zlib 1.2.3
2016-11-16 09:30:31 12925 [Note] InnoDB: Using CPU crc32 instructions
2016-11-16 09:30:31 12925 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2016-11-16 09:30:31 12925 [Note] InnoDB: Completed initialization of buffer pool
2016-11-16 09:30:31 12925 [Note] InnoDB: Highest supported file format is Barracuda.
2016-11-16 09:30:31 12925 [Note] InnoDB: 128 rollback segment(s) are active.
2016-11-16 09:30:31 12925 [Note] InnoDB: Waiting for purge to start
2016-11-16 09:30:31 7ff87f3fa700 InnoDB: Operating system error number 13 in a file operation.
InnoDB: The error means mysqld does not have the access rights to
InnoDB: the directory.
2016-11-16 09:30:31 7ff87f3fa700 InnoDB: Assertion failure in thread 140705263494912 in file fil0fil.cc line 875
InnoDB: Failing assertion: ret
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
01:30:31 UTC - mysqld got signal 6 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed,
something is definitely wrong and this may fail.

key_buffer_size=16777216
read_buffer_size=2097152
max_used_connections=0
max_threads=1000
thread_count=0
connection_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 10269157 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 0 thread_stack 0x40000
/usr/local/mysql/bin/mysqld(my_print_stacktrace+0x2c)[0x90109c]
/usr/local/mysql/bin/mysqld(handle_fatal_signal+0x357)[0x6727c7]
/lib64/libpthread.so.0(+0xf130)[0x7ff894de9130]
/lib64/libc.so.6(gsignal+0x37)[0x7ff893df45d7]
/lib64/libc.so.6(abort+0x148)[0x7ff893df5cc8]
/usr/local/mysql/bin/mysqld[0xa6ee11]
/usr/local/mysql/bin/mysqld[0xa6f03e]
/usr/local/mysql/bin/mysqld[0xa76873]
/usr/local/mysql/bin/mysqld[0xa419f9]
/usr/local/mysql/bin/mysqld[0xa2a591]
/usr/local/mysql/bin/mysqld[0xa106c5]
/usr/local/mysql/bin/mysqld[0x9babd5]
/usr/local/mysql/bin/mysqld[0x9b7927]
/usr/local/mysql/bin/mysqld[0x9b94f7]
/usr/local/mysql/bin/mysqld[0x989bd2]
/usr/local/mysql/bin/mysqld[0x9dd72e]
/usr/local/mysql/bin/mysqld[0x9d06c7]
/lib64/libpthread.so.0(+0x7df5)[0x7ff894de1df5]
/lib64/libc.so.6(clone+0x6d)[0x7ff893eb51ad]
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
161116 09:30:31 mysqld_safe mysqld from pid file /data/mysql/mysql.pid ended