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

DB flush failed.: "Corruption: block checksum mismatch" #6670

Closed
mtbitcoin opened this issue Oct 7, 2017 · 1 comment
Closed

DB flush failed.: "Corruption: block checksum mismatch" #6670

mtbitcoin opened this issue Oct 7, 2017 · 1 comment
Labels
Z1-question 🙋‍♀️ Issue is a question. Closer should answer.

Comments

@mtbitcoin
Copy link

I'm running:

  • Parity version: 1.7.2 beta
  • Operating system: Windows

Issue appears on windows build of parity fairly consistently

C:>"C:\Program Files\Parity\Parity\parity.exe" --tracing on --jsonrpc-port 8547 --db-compaction ssd --cache-size 2000 --tx-queue-gas off --no-ws
2017-10-07 23:45:03 Starting Parity/v1.7.2-beta-9f47909-20170918/x86_64-windows-msvc/rustc1.19.0
2017-10-07 23:45:03 Keys path C:\Users\XX\AppData\Roaming\Parity\Ethereum\keys\Foundation
2017-10-07 23:45:03 DB path C:\Users\XX\AppData\Local\Parity\Ethereum\chains\ethereum\db\906a34e69aec8c0d
2017-10-07 23:45:03 Path to dapps C:\Users\XX\AppData\Roaming\Parity\Ethereum\dapps
2017-10-07 23:45:03 State DB configuration: fast +Trace
2017-10-07 23:45:03 Operating mode: passive
2017-10-07 23:45:03 Configured for Foundation using Ethash engine
2017-10-07 23:45:05 Public node URL: enode://XXX..@127.0.0.1:30303
2017-10-07 23:45:10 Syncing #4332258 ed10…986d 0 blk/s 0 tx/s 0 Mgas/s 0+ 0 Qed #4332258 1/25 peers 115 KiB chain 59 MiB db 0 bytes queue 158 KiB sync RPC: 0 conn, 0 req/s, 0 µs
2017-10-07 23:45:21 Syncing #4332369 b5ea…6fd4 10 blk/s 1079 tx/s 63 Mgas/s 168+ 270 Qed #4333020 11/25 peers 2 MiB chain 63 MiB db 39 MiB queue 654 KiB sync RPC: 0 conn, 0 req/s, 0 µs
2017-10-07 23:45:30 Syncing #4332473 f37b…6af7 11 blk/s 1184 tx/s 64 Mgas/s 0+ 546 Qed #4333020 11/25 peers 4 MiB chain 66 MiB db 60 MiB queue 654 KiB sync RPC: 0 conn, 0 req/s, 0 µs
thread 'IO Worker #3' panicked at 'DB flush failed.: "Corruption: block checksum mismatch"', src\libcore\result.rs:860
stack backtrace:
0: hid_error
1: hid_error
2: hid_error
3: hid_error
4: hid_error
5: hid_error
6: hid_error
7: hid_error
8: hid_error
9:
10:
11:
12: hid_error
13:
14: hid_error
15: BaseThreadInitThunk


@5chdn 5chdn added the Z1-question 🙋‍♀️ Issue is a question. Closer should answer. label Oct 9, 2017
@5chdn
Copy link
Contributor

5chdn commented Oct 9, 2017

Your probably only option is a parity db kill and try again. If this keeps happening again after a reset of the db, your disk might be corrupted

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Z1-question 🙋‍♀️ Issue is a question. Closer should answer.
Projects
None yet
Development

No branches or pull requests

2 participants