Upgrade may see ERROR: readStartingCheckpoint on subsequent startstone with tranlogs
When upgrading to 3.7.4, under some conditions when the repository extent originated on an earlier version and was previously restored, the tranlogs may have sequence ids that do not match what the Stone is expecting.
Version 3.7.4 added validation of tranlogs to avoid fork-in-time restore corruption, and these unexpected tranlog sequence ids cause startstone to fail. Startstone will work if there are no tranlogs present or when using -N option, but this does not correct the problem.
Last updated: 5/22/25