Skip to content
This repository was archived by the owner on Nov 6, 2020. It is now read-only.

DB corrupted: Corruption: block checksum mismatch #9019

Closed
pluswave opened this issue Jun 30, 2018 · 4 comments
Closed

DB corrupted: Corruption: block checksum mismatch #9019

pluswave opened this issue Jun 30, 2018 · 4 comments
Labels
F1-panic 🔨 The client panics and exits without proper error handling. M4-core ⛓ Core client code / Rust.
Milestone

Comments

@pluswave
Copy link

Before filing a new issue, please provide the following information.

I'm running:

  • Which Parity version?: 0.0.0
    1.10.6
  • Which operating system?: Windows / MacOS / Linux
    Linux (ubuntu 16.04)
  • How installed?: via installer / homebrew / binaries / from source
    downloaded binary from the web
  • Are you fully synchronized?: no / yes
    yes
  • Which network are you connected to?: ethereum / ropsten / kovan / ...
    ethereum
  • Did you try to restart the node?: no / yes
    doing restart, not synced yet.

2018-06-30 06:50:48 Imported #5877341 daf5…0e19 (187 txs, 7.99 Mgas, 390.30 ms, 25.48 KiB)
2018-06-30 06:50:58 Imported #5877342 4e00…c792 (112 txs, 8.00 Mgas, 548.91 ms, 21.16 KiB)
2018-06-30 06:51:08 Imported #5877343 5d4f…adc7 (187 txs, 8.00 Mgas, 614.34 ms, 28.87 KiB)
2018-06-30 06:51:24 16/25 peers 6 MiB chain 124 MiB db 0 bytes queue 63 KiB sync RPC: 0 conn, 7 req/s, 1723 µs
2018-06-30 06:51:27 DB corrupted: Corruption: block checksum mismatch: expected 755318067, got 184657105 in /data-eth/parity-data/chains/ethereum/db/906a34e69aec8c0d/overlayrecent/db/1684649.sst offset 56776212 size 13432. Repair will be triggered on next restart

====================

stack backtrace:
0: 0x55737838081c -

Thread 'Verifier #2' panicked at 'DB flush failed.: Error(Msg("Corruption: block checksum mismatch: expected 755318067, got 184657105 in /data-eth/parity-data/chains/ethereum/db/906a34e69aec8c0d/overlayrecent/db/1684649.sst offset 56776212 size 13432"), State { next_error: None, backtrace: None })', libcore/result.rs:945

This is a bug. Please report it at:

https://github.com/paritytech/parity/issues/new
@pluswave
Copy link
Author

after restart with "parity -c config.toml"

Loading config file from config.toml
2018-06-30 14:45:32  Starting Parity/v1.10.6-stable-bc0d134-20180605/x86_64-linux-gnu/rustc1.26.1
2018-06-30 14:45:32  Keys path /data-eth/parity-data/keys/Foundation
2018-06-30 14:45:32  DB path /data-eth/parity-data/chains/ethereum/db/906a34e69aec8c0d
2018-06-30 14:45:32  Path to dapps /data-eth/parity-data/dapps
2018-06-30 14:45:32  State DB configuration: fast
2018-06-30 14:45:32  Operating mode: active
2018-06-30 14:45:32  Configured for Foundation using Ethash engine
2018-06-30 14:45:32  DB has been previously marked as corrupted, attempting repair
2018-06-30 14:45:37  Updated conversion rate to Ξ1 = US$451.23 (10553165 wei/gas)
2018-06-30 16:04:30  DB corrupted: Invalid argument: You have to open all column families. Column families not opened: col6, col4, col5, col3, col2, col0, col1, attempting repair


Client service error: Client(Database(Error(Msg("Received null column family handle from DB."), State { next_error: None, backtrace: None })))

@Tbaut
Copy link
Contributor

Tbaut commented Jun 30, 2018

This is a duplicate from #7748
This error indicates a DB corruption most likely due to a memory error. Could you please make sure that your memory passes a memtest?

@Tbaut Tbaut closed this as completed Jun 30, 2018
@Tbaut Tbaut added M4-core ⛓ Core client code / Rust. F1-panic 🔨 The client panics and exits without proper error handling. labels Jun 30, 2018
@Tbaut Tbaut added this to the 1.12 milestone Jun 30, 2018
@pluswave
Copy link
Author

pluswave commented Jun 30, 2018

This is on a cloud server (Aliyun). I run parity as a api service for local wallet.

@Tbaut
Copy link
Contributor

Tbaut commented Jun 30, 2018

Then there is probably nothing else you can do other than parity db kill and resync.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
F1-panic 🔨 The client panics and exits without proper error handling. M4-core ⛓ Core client code / Rust.
Projects
None yet
Development

No branches or pull requests

2 participants