Node Upgrade Issue

[mayank-daga]

Hi after upgrading my sui archival node to v1.60.1 and getting following error:

025-12-05T05:02:41.244510Z INFO sui_node: Started Prometheus HTTP endpoint at 0.0.0.0:9184

2025-12-05T05:02:41.244789Z INFO sui_node: Initializing sui-node listening on /dns/localhost/tcp/8080/http node=k#8c8dbbb17feee8072e4943751822e4b66a22b77a91c205be574052b2b29236bf4b0d090a266a6c29216a33af791a866b04f1f72450e8d9cd7db496e96cb6f35928e9b86d89af9b1d677c4ad856fed28633692e1bcfc7f69ee19a70c6aba70d0b

2025-12-05T05:02:41.245680Z INFO mysten_metrics::thread_stall_monitor: Starting thread stall monitor watchdog thread

2025-12-05T05:02:41.380997Z INFO mysten_metrics::thread_stall_monitor: Spawning future crates/mysten-metrics/src/thread_stall_monitor.rs:ThreadStallMonitor

2025-12-05T05:02:41.381031Z INFO mysten_metrics::thread_stall_monitor: Starting thread stall monitor update task

2025-12-05T05:02:43.857804Z ERROR typed_store::rocks: error=rocksdb error: Corruption: unknown WriteBatch tag

thread 'sui-node-runtime' panicked at crates/sui-core/src/authority/authority_store_tables.rs:53:10:

Cannot open DB at "/sui/suidb/live/store/perpetual": RocksDBError("Corruption: unknown WriteBatch tag")

note: run with RUST_BACKTRACE=1 environment variable to display a backtrace

2025-12-05T05:02:43.865593Z ERROR telemetry_subscribers: panicked at crates/sui-core/src/authority/authority_store_tables.rs:53:10:

Cannot open DB at "/sui/suidb/live/store/perpetual": RocksDBError("Corruption: unknown WriteBatch tag") panic.file="crates/sui-core/src/authority/authority_store_tables.rs" panic.line=53 panic.column=10

Any help would be highly appreciated

[github-actions]

Thank you for opening this issue, a team member will review it shortly. Until then, please do not interact with any users that claim to be from Sui support and do not click on any links!

[stefan-mysten]

Hey @mayank-daga sorry to hear you're having issues. Would it be possible to try with the latest version, 1.61.2?

[mayank-daga]

Hi @stefan-mysten wouldn't it break if i skip one version and move to higher version?

[stefan-mysten]

@mayank-daga from the error it looks like your DB is corrupted. This can happen if the machine loses power and has a hard restart. I am not sure what to suggest here; does it work fine with your previous node version (can you share which one was that)?

RocksDB has some repair tool but I have no experience using it. You may give it a try, if you'd like: https://github.com/facebook/rocksdb/wiki/RocksDB-Repairer