I ran it again after deleting the chainstate as well. So a different, but same looking (to me) output. As far as I can see in the log file (I guess it only captures the tail end of it), it all seems to be variations of the first line of the above snippet, with the just the date increasing. Would the most recent date allow me to figure out the block that I should be deleting?:
2017-06-20 23:56:11 UpdateTip: new best=00000000000000000781bcb70bb508ec057746cd99c5d1de40b3214a868c2e0d height=316718 version=0x00000002 log2_work=80.287983 tx=45003211 date='2014-08-21 00:55:02' progress=0.194825 cache=313.0MiB(246087tx)
2017-06-20 23:56:11 UpdateTip: new best=00000000000000000cd5fc1fe02bcbb3ef3474d475353eb98e64e48fdc5584e9 height=316719 version=0x00000002 log2_work=80.288083 tx=45004039 date='2014-08-21 01:18:20' progress=0.194828 cache=313.1MiB(246651tx)
2017-06-20 23:56:18 Corruption: block checksum mismatch
2017-06-20 23:56:18 *** System error while flushing: Database corrupted
I've tried running it several times and everytime it aborts. Does this indicate hardware issue?
The issue likely lies with the block data already on disk. Since you are not deleting any of it, the error will keep appearing as it hits the corrupted data repeatedly. Again, try deleting the blocks folder too in order to resync the entire blockchain. If you get the same error after doing that, then you likely have a hardware error.