The archive https://matic-blockchain-snapshots.s3-accelerate.amazonaws.com/matic-mainnet/bor-fullnode-snapshot-2023-01-24.tar.gz appears to be broken, redownloaded it few times with the same result. Can you reupload it, please? Also, what happened to ‘snap’ syncmode in bor? It says it doesn’t support it and automatically switches to ‘full’ one. I’m pretty sure it used to work before 0.3.x.
1 Like
We have uploaded a new snapshot: https://matic-blockchain-snapshots.s3-accelerate.amazonaws.com/matic-mainnet/bor-fullnode-snapshot-2023-02-07.tar.gz
Please try again.
2 Likes
Will shall be uploading a new snapshot in a while; will update you once we are done.
1 Like
I have the same problem, tried syncing from multiple snapshots, but always fail, here is a recent failure:
Feb 08 23:02:17 ubuntu bor[30883]: DEBUG[02-08|23:02:17.411] Chain freezer table opened database=/data/bor/data/bor/chaindata/ancient table=headers items=37,661,232 size=1.10GiB
Feb 08 23:02:17 ubuntu bor[30883]: DEBUG[02-08|23:02:17.411] Chain freezer table opened database=/data/bor/data/bor/chaindata/ancient table=hashes items=37,661,232 size=1.12GiB
Feb 08 23:02:17 ubuntu bor[30883]: DEBUG[02-08|23:02:17.448] Chain freezer table opened database=/data/bor/data/bor/chaindata/ancient table=bodies items=37,661,232 size=1.13GiB
Feb 08 23:02:17 ubuntu bor[30883]: DEBUG[02-08|23:02:17.468] Chain freezer table opened database=/data/bor/data/bor/chaindata/ancient table=receipts items=37,661,232 size=1.19GiB
Feb 08 23:02:17 ubuntu bor[30883]: DEBUG[02-08|23:02:17.468] Chain freezer table opened database=/data/bor/data/bor/chaindata/ancient table=matic-bor-receipts items=37,661,232 size=2>
Feb 08 23:02:17 ubuntu bor[30883]: DEBUG[02-08|23:02:17.468] Chain freezer table opened database=/data/bor/data/bor/chaindata/ancient table=diffs items=37,661,232 size=1>
Feb 08 23:02:17 ubuntu bor[30883]: INFO [02-08|23:02:17.468] Opened ancient database database=/data/bor/data/bor/chaindata/ancient readonly=false
Feb 08 23:02:17 ubuntu bor[30883]: INFO [02-08|23:02:17.469] Persisted trie from memory database nodes=12 size=1.86KiB time="16.852µs" gcnodes=0 gcsize=0.00B gctime=0s livenodes=1 livesize=0.00B
Feb 08 23:02:17 ubuntu bor[30883]: INFO [02-08|23:02:17.469] Initialised chain configuration config="{ChainID: 137 Homestead: 0 DAO: <nil> DAOSupport: true EIP150: 0 EIP155: 0 EIP158: 0 Byzant>
Feb 08 23:02:17 ubuntu bor[30883]: ERROR[02-08|23:02:17.472] Error in block freeze operation err="block receipts missing, can't freeze block 37661243"
1 Like
– Yes that’s the current implementation. ‘snap’ syncmode was not functional even before.
1 Like
The new snapshot dated 2023-02-09 works fine, thanks.
2 Likes
Is there a way to get archival data snapshots for polygon using Bor rather than using erigon client? If not what’s the best way to increase the speed of archival node sync? My archival nodes are like 2 years behind. My machine has an IOPS of 10k and 10 TB SSD attached to it.