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

Thread 'Verifier #0' panicked at 'DB flush failed.: "Corruption: block checksum mismatch"', /checkout/src/libcore/result.rs:860 #6974

Closed
Beasta opened this issue Nov 2, 2017 · 1 comment
Labels
M4-core ⛓ Core client code / Rust. Z1-question 🙋‍♀️ Issue is a question. Closer should answer. Z7-duplicate 🖨 Issue is a duplicate. Closer should comment with a link to the duplicate.
Milestone

Comments

@Beasta
Copy link

Beasta commented Nov 2, 2017

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

I'm running:

  • Parity version: v1.8.0
  • Operating system: Linux
  • And installed: cant remember

Your issue description goes here below. Try to include actual vs. expected behavior and steps to reproduce the issue.


I'm running on digital ocean with Ubuntu. Using an external volume for storage.
got this:
2017-11-02 23:10:55 UTC Syncing #4464890 8a22…5001 0 blk/s 20 tx/s 1 Mgas/s 1162+ 0 Qed #4466053 2/25 peers 329 KiB chain 68 MiB db 41 MiB queue 419 KiB sync RPC: 0 conn, 0 req/s, 0 µs
2017-11-02 23:11:05 UTC Syncing #4464893 033f…4d39 0 blk/s 34 tx/s 1 Mgas/s 1159+ 0 Qed #4466053 3/25 peers 447 KiB chain 67 MiB db 40 MiB queue 419 KiB sync RPC: 0 conn, 0 req/s, 0 µs

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

stack backtrace:
0: 0x55f115e2717c -

Thread 'Verifier #0' panicked at 'DB flush failed.: "Corruption: block checksum mismatch"', /checkout/src/libcore/result.rs:860

This is a bug. Please report it at:

https://github.com/paritytech/parity/issues/new
@Office-Julia Office-Julia added F1-panic 🔨 The client panics and exits without proper error handling. Z0-unconfirmed 🤔 Issue might be valid, but it’s not yet known. labels Nov 3, 2017
@5chdn 5chdn added M4-core ⛓ Core client code / Rust. Z1-question 🙋‍♀️ Issue is a question. Closer should answer. and removed F1-panic 🔨 The client panics and exits without proper error handling. Z0-unconfirmed 🤔 Issue might be valid, but it’s not yet known. labels Nov 4, 2017
@5chdn 5chdn added this to the 1.9 milestone Nov 4, 2017
@5chdn
Copy link
Contributor

5chdn commented Nov 4, 2017

Your database is corrupted. You can reset it with parity db kill

Duplicate of #6960

Duplicate of #6905

Duplicate of #6798

Duplicate of #6790

Duplicate of #6670

Duplicate of #6506

Duplicate of #6501

Duplicate of #5837

Duplicate of #3634

Duplicate of #3432

Duplicate of #2830

Duplicate of #2640

Duplicate of #2603

Duplicate of #763

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
M4-core ⛓ Core client code / Rust. Z1-question 🙋‍♀️ Issue is a question. Closer should answer. Z7-duplicate 🖨 Issue is a duplicate. Closer should comment with a link to the duplicate.
Projects
None yet
Development

No branches or pull requests

3 participants