-
Notifications
You must be signed in to change notification settings - Fork 20.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fatal: extra db err: leveldb/storage: corrupted or incomplete CURRENT file #1601
Comments
Your database is corrupted. You can fix this issue by removing the databases and syncing again. |
Just delete the |
Issue solved. May I suggest adding this to the error? Or make deleting these folders part of the 'geth recover' protocol? |
|
Hi, |
The exact location is OS dependent and can be overwritten if you specify a custom datadir. You can see where the default location is with Keep in mind that this datadir directory also contains the keystore for mainnet and testnet. If you want to keep these keys don't delete the keystore sub-directories (each net has its own keystore). The safest way to delete data and keep keys is to run |
ok |
@actuallymentor hello, out of interest how you resolved that issue? |
@ijunaid8989 please see @fjl's answer. |
@actuallymentor Actually, I am not using |
release: add another two patches into v1.2.3
What I did:
Download geth 1.0.1
Put gets in the chocolatey\geth-stable\tools folder
What happened:
Geth/eth pair mining setup worked fine for a while
Computer crashed (full freeze, no BSOD)
Upon restart trying to run geth any way gives a "Fatal: extra db err: leveldb/storage: corrupted or incomplete CURRENT file"
The contents of the CURRENT files in C:\Users\Mentor\AppData\Roaming\Ethereum* is: "0000 0000 0000 0000 0000 0000 0000 0000"
EDIT: OS Windows 8.1, AMD r9 290, git bash console, previous crashes without repercussions occurred when geth+eth mining.
The text was updated successfully, but these errors were encountered: