Synchronization starts from the genesis block, not from the snapshot

[mb-gvidon]

Hi everyone!

I'm trying to run a full node from snapshot, but it seems that synchronization starts from the genesis block, not from the snapshot. I've already tried several guides including

• official one
• this comment

The official one simply doesn't work at all.

The second option (aka this comment) is more reasonable. It actually started the synchronization (thanks to @updatesvc), but I suppose the sync has started from the genesis. If I attach the node via ./geth_linux attach --datadir ./mainnet I see the following (after 3 days of synchronization):

> eth.syncing
{
  currentBlock: 7092885,
  highestBlock: 13735935,
  knownStates: 0,
  pulledStates: 0,
  startingBlock: 0
}

The value of currentBlock is increasing with with the speed 10 blocks/sec. At the beginning (currentBlock < 1000000) it was 5000 blocks/sec.

The list of my commands after downloading geth_linux of version 1.1.7, unpacking mainnet.zip and the snapshot:

./geth_linux --datadir mainnet init genesis.json
mv server/data-seed/geth/chaindata mainnet/geth/chaindata
mv server/data-seed/geth/triecache mainnet/geth/triecache
./geth_linux --config ./config.toml --datadir ./mainnet --cache 100000 --rpc.allow-unprotected-txs --txlookuplimit 0 --http --maxpeers 100 --ws --syncmode=full --snapshot=false --diffsync

Hardware specs

• 4nvme raid0
• 256 Gb RAM
• Ryzen Threadripper 3990 64 cores

Static IP and ports are opened without firewalls and so on.

Could anyone please help with the command that starts the node exactly from the snapshot? Does it exist actually?

[mb-gvidon]

Issue was solved.

I have copied the whole geth folder and the sync has started from the snapshot.

Finally, the following list of commands worked for me

mkdir mainnet
cp -R /server/data-seed/geth/ mainnet/geth/
unzip mainnet.zip
./geth_linux --config ./config.toml --datadir ./mainnet --cache 100000 --rpc.allow-unprotected-txs --txlookuplimit 0 --http --maxpeers 100 --ws --syncmode=full --snapshot=false --diffsync

The synchronization started from the snapshot.

Attaching to the node via ./geth_linux attach --datadir ./mainnet has the following results

> eth.syncing
{
  currentBlock: 13523532,
  highestBlock: 13615014,
  knownStates: 297473485,
  pulledStates: 297473485,
  startingBlock: 13523459
}

It took 40 hours for full sync.