so, what does the latest crawl log at the very end state why it didn't finish yet?

 I have seen cases where AAGs with FTS on DBs did not finish population when failover during that time happened.
Last but not least: Did you try to force a full population for all FTS Indexes which haven't updated in a while by themselves yet without restarting SQL Server Engines?