11

My home server's been down for a couple of days while I do some upgrades.

I'd had Geth running in one of the terminal windows, but shut it down gracefully using exit before taking the server offline.

On trying to restart it, I'm seeing the below error:

I0208 14:31:27.219469 26346 downloader.go:267] Synchronisation failed: leveldb/table: corruption on data-block (pos=650747): checksum mismatch, want=0x2dd4b443 got=0x9fb5cf2f [file=286265.ldb]

How do I go about investigating and fixing this problem? Is there a way to remove the offending part of the data and force it to resync that particular part? I clearly don't want to have to re-sync everything from scratch...

(Note: I've run fsck on the (unmounted) disk without finding any problems. The upgrades didn't touch the disks. Everything was shut down gracefully.)

Improve this question
1
  • Note that if deleting the chaindata folder isn't enough, try deleting the nodes folder as well. Commented Jun 18, 2017 at 6:57

2 Answers 2

Reset to default
10

Can't really say what could have gone wrong, but your database is corrupted at the LevelDB storage engine level. Something seems to have modified the flat data files that leveldb uses to store its stuff in. There isn't much you can do to recover them I'm afraid.

You should be able to fast sync back to the network fairly quickly. It usually takes about half an hour for me to sync from scratch. Just start geth with --fast --cache=512.

Improve this answer
2
  • So literally remove everything and start from nothing? (I've asked a separate question about how --fast works.) Commented Feb 8, 2016 at 15:31
  • Only remove the chaindata folder. The rest should remain. Commented Feb 8, 2016 at 17:47
2

Note: I've run fsck on the (unmounted) disk without finding any problems.

fsck is a good tool to check for filesystem level problems, but not hardware level. I'd always start at the hardware level and move up from there.

Have you checked the SMART status on your hard drives recently? http://www.howtogeek.com/134735/how-to-see-if-your-hard-drive-is-dying/

I'd also check your memory for problems. http://windows.microsoft.com/en-us/windows7/diagnosing-memory-problems-on-your-computer

(There are different ways to accomplish the same thing in Linux. smartctl, memtest86, and fsck.)

After you've determined no errors from above, only then would I take the advice of clearing out chaindata and resyncing using --fast

Improve this answer

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.