innoDB looping?

[Arthur Stephens]

Running version MySQL 5.1.73 on CentOS 6
The database crashed and the only way I could get it working again was to drop the current one remove ib_log files and ibdata then do a restore from backup.
But even with my buffer pool set to 13G which is 80% of available ram this message keeps repeating in mysqld.log which is 48MB in size and growing.

160917 22:18:31InnoDB: Warning: difficult to find free blocks from
InnoDB: the buffer pool (15448 search iterations)! Consider
InnoDB: increasing the buffer pool size.
InnoDB: It is also possible that in your Unix version
InnoDB: fsync is very slow, or completely frozen inside
InnoDB: the OS kernel. Then upgrading to a newer version
InnoDB: of your operating system may help. Look at the
InnoDB: number of fsyncs in diagnostic info below.
InnoDB: Pending flushes (fsync) log: 0; buffer pool: 0
InnoDB: 142 OS file reads, 0 OS file writes, 0 OS fsyncs
InnoDB: Starting InnoDB Monitor to print further
InnoDB: diagnostics to the standard output.

I can not consider increasing the buffer pool size.
I have no clue why it is doing this.
The old ibdata file was 43GB in size so I assumed that is why the system crashed twice today. I only have 16GB of ram.

And mysql shows InnoDB is supported when before I restored from back up it was missing from this list.

mysql> show engines;
+------------+---------+------------------------------------------------------------+--------------+------+------------+
| Engine | Support | Comment | Transactions | XA | Savepoints |
+------------+---------+------------------------------------------------------------+--------------+------+------------+
| MRG_MYISAM | YES | Collection of identical MyISAM tables | NO | NO | NO |
| CSV | YES | CSV storage engine | NO | NO | NO |
| MyISAM | DEFAULT | Default engine as of MySQL 3.23 with great performance | NO | NO | NO |
| InnoDB | YES | Supports transactions, row-level locking, and foreign keys | YES | YES | YES |
| MEMORY | YES | Hash based, stored in memory, useful for temporary tables | NO | NO | NO |
+------------+---------+------------------------------------------------------------+--------------+------+------------+
5 rows in set (0.00 sec)

I have no clue what to do to fix this...
Thanks