Comment 12 for bug 1676537

I remove the file:
 rm ib_logfile0

and restart, but see this in log now:
2017-03-27 20:26:40 139672482883520 [Note] InnoDB: Initializing buffer pool, size = 6.0G
2017-03-27 20:26:40 139672482883520 [Note] InnoDB: Completed initialization of buffer pool
2017-03-27 20:26:40 139672482883520 [Note] InnoDB: Setting log file ./ib_logfile101 size to 1024 MB
InnoDB: Progress in MB: 100 200 300 400 500 600 700 800 900 1000
2017-03-27 20:26:43 139672482883520 [Note] InnoDB: Setting log file ./ib_logfile1 size to 1024 MB
InnoDB: Progress in MB: 100 200 300 400 500 600 700 800 900 1000
2017-03-27 20:26:46 139672482883520 [Note] InnoDB: Renaming log file ./ib_logfile101 to ./ib_logfile0
2017-03-27 20:26:46 139672482883520 [Warning] InnoDB: New log files created, LSN=17321439244
2017-03-27 20:26:46 139672482883520 [Note] InnoDB: Highest supported file format is Barracuda.
2017-03-27 20:26:46 7f0808ba27c0 InnoDB: Error: page 7 log sequence number 18661007654
InnoDB: is in the future! Current system log sequence number 17321439756.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-03-27 20:26:46 7f0808ba27c0 InnoDB: Error: page 2 log sequence number 18660851037