Once again, my "Blocks Remaining" has come to a standstill, even though the Wallet GUI says it's synchronizing. And here is the latest from the daemon:
←[0m
2017-07-25 16:44:16.798 [P2P6] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:293
[80.232.241.110:18080 OUT] Sync data returned a new top block candidate: 202154 → 1362286 [Your node is 1160132 blocks <1049 days> behind]
SYNCHRONIZATION started
2017-07-25 16:44:47.123 [P2P6] ERROR blockchain
src/cryptonote_core/blockchain.cpp:3383 Error adding block with hash:
<6f0dca866420b58864282e662d39cd298543103d6f6e7013f8996befa8da647e>
to blockchain, what = Error adding spent key image to db transaction: MDB_CORRUPTED: Located page was wrong type
2017-07-25 16:44:02.491 [P2P6] WARN blockchain.db.lmdb
src/blockchain_db/lmdb/db_lmdb.cpp:71
Failed to query m_blocks: MDB_BAD_TXN:
Transaction must abort, has a child, or is invalid
2017-07-25 16:45:02.491 [P2P6] WARN blockchain.db.lmdb
src/blockchain_db/lmdb/db_lmdb.cpp:71
DB error attempting to fetch block index from hashMDB_BAD_TXN:
Transaction must abort, has a child, or is invalid
2017-07-25 16:45:08.156 [P2P6] WARN blockchain.db.lmdb
src/blockchain_db/lmdb/db_lmdb.cpp:71
DB error attempting to fetch block index from hashMDB_BAD_TXN:
Transaction must abort, has a child, or is invalid
2017-07-25 16:45:16.188 [P2P6] WARN blockchain.db.lmdb
src/blockchain_db/lmdb/db_lmdb.cpp:71
Failed to query m_blocks: MDB_BAD_TXN:
Transaction must abort, has a child, or is invalid
Error messages similar to the above kept coming while my "Blocks Remaining" were counting down as in my last report.
I can only assume that these are not fatal errors, but just temporary.
I have tried restarting the daemon several times and also just left it alone for hours on end.
I would really appreciate a response from someone in-the-know.