Monerod.exe did start the synchronization, en then only fails to get data.

[LateAtNight25]

Monerod.exe did start the synchronization, en then only fails to get data.
This is what I get:

2025-01-16 20:56:36.949 I SYNCHRONIZATION started
2025-01-16 20:56:37.889 E Error adding block with hash: <5321b0d7537456fde7d6e1208a66bb67ee16a53d6accd33f20256ddcafd59213> to blockchain, what = Attempting to add transaction that's already in the db (tx id 2690000)
2025-01-16 20:56:39.556 E Failed to get tx meta from txpool
2025-01-16 20:56:39.557 E Failed to get tx meta from txpool
2025-01-16 20:56:39.557 E Failed to get tx meta from txpool.....
and ends with
2025-01-16 21:12:47.065 E Error adding block with hash: <5321b0d7537456fde7d6e1208a66bb67ee16a53d6accd33f20256ddcafd59213> to blockchain, what = Attempting to add transaction that's already in the db (tx id 2690000)
2025-01-16 21:12:47.066 I Host 54.36.174.4 blocked.
2025-01-16 21:12:50.427 E Error retrieving blocks, missed 16 transactions for block with hash:

Finding a solution for this problem on the internet is horrific. Like moving through a swamp of unrelevant information with very, very slow progress. Especially after many years reinstalling and restarting a fresh monero GUI, version 0.18.3.4-unknown (Qt 5.15.14). But this seems the only place where there is hope..
I also don't know why there is "unkown" in the description. When does that happen?

Monero GUI is installed in C:\programs. The Blockchain data in E:\BlockM

[selsta]

Did you have a power outage during sync? It seems the blockchain is corrupted.

[LateAtNight25]

Thanks for reacting. I don't exactly know how it happened, but after an hour or two, it started synchronizing. Maybe because I disabled the VPN Op vr 17 jan. 2025 05:55 schreef selsta ***@***.***>:

…

Did you have a power outage during sync? It seems the blockchain is corrupted. — Reply to this email directly, view it on GitHub <#9714 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BONT7CFWVBGJYLTGREO4Y5D2LCELZAVCNFSM6AAAAABVKR3Z5CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKOJXGQZTGNRUG4> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[LateAtNight25]

But it is nice to know that there are still people who cares about Monero and the user. Op vr 17 jan. 2025 10:24 schreef John Schubert ***@***.***>:

…

Thanks for reacting. I don't exactly know how it happened, but after an hour or two, it started synchronizing. Maybe because I disabled the VPN Op vr 17 jan. 2025 05:55 schreef selsta ***@***.***>: > Did you have a power outage during sync? It seems the blockchain is > corrupted. > > — > Reply to this email directly, view it on GitHub > <#9714 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/BONT7CFWVBGJYLTGREO4Y5D2LCELZAVCNFSM6AAAAABVKR3Z5CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKOJXGQZTGNRUG4> > . > You are receiving this because you were mentioned.Message ID: > ***@***.***> >