Storage node synchronization always fails after applying flow_db snapshot without data_db (following docs)

[hubofvalley]

Issue Summary

After applying a snapshot by copying only the flow_db directory (without data_db)—as suggested in the official documentation—the storage node fails to sync and shuts down with errors.

Steps to Reproduce

1. On Node A (synced zgs node), take a snapshot and compress only the flow_db directory.
2. On Node B, delete both flow_db and data_db directories (to ensure a clean state).
3. Transfer and decompress the flow_db from Node A to Node B.
4. Start the storage node.

Expected Behaviour

Node B should sync properly using the provided snapshot from Node A, even without the data_db, as per documentation.

Actual Behaviour

Sync always fails and logs the following errors:

ERROR zgs_node: Failed to start zgs node reason=Fail to submit miner id request: "Mempool/timeout error, no maxGasPrice set => aborting"

ERROR zgs_node: Failed to start zgs node reason=Fail to submit miner id request: "Transaction failed: (code: -32000, message: invalid nonce; got 26, expected 27, 0g1gela3jtnmen0dmj2q5p0pne5y45ftshzn99dnv: invalid sequence: invalid sequence, data: None)"

Notes

• The process follows the instructions in the [official documentation](link to the exact doc if available).
• The issue seems to suggest that data_db might be required even though it's not mentioned.
• This could potentially be a bug or a documentation oversight.

Environment

• Storage Node version: v0.8.7
• OS: Ubuntu 24.04
• Snapshot method: Manual transfer/restore of flow_db only

Request

Please clarify:

• Whether data_db is actually required when restoring from a snapshot.
• If not required, could this be a bug in the syncing process?