pull down to refresh

10 sats \ 1 reply \ @billytheked OP 21 Aug \ parent \ on: node directions bitcoin
Tried a reindex chainstate and got checksum mismatch errors -- went for full reindex and got this:
[error] A fatal internal error occurred, see debug.log for details: Corrupt block found indicating potential hardware failure. 2025-08-21T01:37:02Z [error] ConnectTip: ConnectBlock 000000000000005d0566652b2549637192d8830bcf524349f074c3eaa7d0b4da failed, bad-txnmrklroot, hashMerkleRoot mismatch
now im at a loss
write
preview
0 sats \ 0 replies \ @Filiprogrammer 21 Aug
Seems like your block 251415 is corrupted and possibly others aswell. This might be some leftover file system corruption from before. Did you run a file system check (fsck)? Even if that does not return any errors, some of the bitcoin block files have gotten corrupted. The safest way to completly get rid of the corruption would be to reformat the drive and redownload the blockchain. (as annoying as that sounds)
Also when formatting the drive, make sure to use a journaling file system or ZFS. This helps detect file system corruption and also repair it in some cases.
reply