0

Geth seems to be always near reaching the highest block but never actually reaching the same number, so it never starts syncing states. knownStates is always 0.

Using geth attach there is always a small difference between currentBlock and highestBlock:

> eth.syncing
{
  currentBlock: 12903364,
  highestBlock: 12903434,
  knownStates: 0,
  pulledStates: 0,
  startingBlock: 12900170
}

BTW I am running an SSD, so no need to suggest that.

Martin Massera
  • 121
  • 4
  • because geth has not synced yet. when you sync you will see false as output and not the counters – Nulik Jul 14 '21 at 15:31
  • you didn't even download the first account of the state yet – Nulik Jul 14 '21 at 15:32
  • How come "I" didn't download the first state, when it says currentBlock 12M? What should I do to have it download states? – Martin Massera Jul 15 '21 at 16:09
  • because when you download the state you will have knownState set to something larger than 0, but apparently you are downloading via state snapshots, anyway this node hasn't synced yet – Nulik Jul 15 '21 at 19:02
  • Aynthing I can do to change this? Current block always seems 100 blocks behind no matter when I look – Martin Massera Jul 16 '21 at 14:30
  • get an SSD disk with M2 PCI express v3 or v4 interface, geth executes about 1000 random IOPs per second – Nulik Jul 16 '21 at 17:18
  • I am using an SSD. I was using it as an external disk, and now that I'm using it internally it is still always 100 blocks behind. Any more wisdom? – Martin Massera Jul 26 '21 at 18:30
  • these low end SATA SSD disks are slow, you will have to get a lot of patience and wait, check out the disk growth, current size is 400GB if you sync in 1 day. If you sync in many days for each day add like 500MB of garbage data (these are intermediate states) to these 400GB to estimate how much time is left for completion – Nulik Jul 26 '21 at 21:12

0 Answers0