Probably to start from the scratch is the best advice you have found so far as reindex-chainstate takes the painful time and doesn't guarantee that it will cope with the problem.
But the debug.log entry shows otherwise.
It specifically detected that a file in his chainstate folder is corrupted that should be fixed by rebuilding the chainstate as mentioned by achow101.
Your previous case may not be related to chainstate corruption that's why the command didn't worked.
And the time it takes to
--reindex-chainstate may not be fast but not as slow as
--reindex or IBD.