From c3e2be63a7065ba1f7577eb32e7582565234f59c Mon Sep 17 00:00:00 2001 From: Jason-W123 <147362502+Jason-W123@users.noreply.github.com> Date: Fri, 17 Jan 2025 15:07:39 +0800 Subject: [PATCH] Update arbitrum-docs/run-arbitrum-node/06-troubleshooting.mdx Co-authored-by: Pete --- arbitrum-docs/run-arbitrum-node/06-troubleshooting.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arbitrum-docs/run-arbitrum-node/06-troubleshooting.mdx b/arbitrum-docs/run-arbitrum-node/06-troubleshooting.mdx index a49ab13b6..18da270db 100644 --- a/arbitrum-docs/run-arbitrum-node/06-troubleshooting.mdx +++ b/arbitrum-docs/run-arbitrum-node/06-troubleshooting.mdx @@ -291,7 +291,7 @@ You can check logs by different log types: info, warn, and error. `Failed to load snapshot` err="head doesn't match snapshot: have a, want b” - This usually because corrupted database caused by an ungraceful shutdown, try re-start + This is usually because an ungraceful shutdown causes a corrupted database; try restarting the node without a prune flag, and after your node goes back to normal, then graceful shutdown it and restart to prune it.