I have a private network based on geth v1.9.25. I upgraded from v1.8.27. Recently, I saw that I'm unable to access the previous blocks at all. Like, e.g.
eth.getBlockByNumber(1) gives me
null, even though I can get the latest blocks just fine. I have a few questions regarding that:
Does this have anything to do with the ancient deep freezing of the previous blocks? If so, is it possible to a, disable it (can't find anything relevant in the configurations) and b, recover/bring the frozen blocks back/thaw them out into active db from the ancient db? I'm looking into the
debugoptions but I can't seem to find anything like what I'm looking for.
Does this mean that "full" sync doesn't keep track of the blocks? I understand that
gcmode=archiveis required for complete state persistence but I was under the impression that
syncmode=fullwill at least persist the entire blockchain (all blocks). I have read up on EVM tracing and haven't found anything contradictory to my understanding.
Update @ Apr 29
This doesn't seem to be normal behavior for geth. I've confirmed with experiments with geth v1.9.25 and rinkeby chain. So there's something wrong with my version (I've brought in consensus from Quorum to v1.9.25).