Yes, the other way is force a full population of the full text index, just make sure there will be no more (planned) failovers before the FTS Crawl finishes.
I once encountered a 10 TB Table almost completely covered by FTS. Once we started the full population of the FT Index it took 18 hours to complete (it was an AFA, so storage on this one for once was not the culprint of performance). During that time expect a lot of micro blockings on the Tables which are covered by FTS. Ideally this is something to be done during weekends. If FTS is quite important for you, make yourself some FTS Maintenance Jobs for at least once a month (if time constraints permit) full population and depending on your maintenance window between daily and weekly update populations.
You will not see any blocking / deadlock messages by the way from FTS full population, your application might just slow down to completely unresponsive on those tables. If you run a SQL Trace you can see those micro blockings appearing.