HDD failure, viruses, HDD bad sectors, things like that only
Yes, but also add hardware disfunctions to that, that is a common problem.
Agree. For example bad DRAM chip can cause very strange errors (ECC is therefore highly recommended).
Topic: What could get your wallet.dat corrupted? (Read 1479 times)
Yes, but also add hardware disfunctions to that, that is a common problem.
Agree. For example bad DRAM chip can cause very strange errors (ECC is therefore highly recommended).
HDD failure, viruses, HDD bad sectors, things like that only
Yes, but also add hardware disfunctions to that, that is a common problem.
Do you guys think there is other way to fix the wallet if bitcoind autofix fails?
pywallet can scan a file (or a hard drive) for mkeys and ckeys (everything required to recover encrypted private keys/addresses), try decrypting them in various combinations, and then reconstruct a wallet.dat file. It almost works, except that the reconstructed wallet.dat doesn't work right unless you choose for it to be unencrypted (which is an undocumented feature). I've submitted a patch which will hopefully be included one day, because aside from that last step it works quite well.
HDD failure, viruses, HDD bad sectors, things like that only
Do you guys think there is other way to fix the wallet if bitcoind autofix fails?
About 20GB free space was left at the time of corruption.
We had 10s of thousands of keys generated because of the nature of the service, and the wallet was over 90mb.
Thoughts?
20GB free space is not much. Do you have bitcoind installed into / partition? Maybe you should create larger separate partition and move bitcoin data files there.
Is it enough to backup the wallet.dat file once or do you need to do it on a regular basis and why?
Depending on the Bitcoin client that you're using, change from a sent transaction may be sent to a newly generated change address. For example, let's say that you have 1 whole Bitcoin as an unspent input. If you send 0.5 of that to someone else's address, then the remaining 0.5 will be sent back to an address in your Bitcoin wallet. I'm not familiar with all the Bitcoin clients that currently exist, but I know that some Bitcoin clients generate new change addresses on-the-fly. In those cases, your previous backup file would not contain the newly generated private-public key pairing, which would mean that your remaining 0.5 Bitcoin is inaccessible using that file. Ideally, you should make a new backup of your wallet.dat file after every time that you send out a new transaction.
Well I just had wallet.dat corrupted so bad that even the bitcoind restore process upon launch couldn't fix it.
Of course I have a back-up, but would be interesting to discuss what usually causes that so we can avoid it in future.
It was latest version bitcoind running on a fairly powerful dedicated server with centOS.
About 20GB free space was left at the time of corruption.
We had 10s of thousands of keys generated because of the nature of the service, and the wallet was over 90mb.
Thoughts?
Of course I have a back-up, but would be interesting to discuss what usually causes that so we can avoid it in future.
It was latest version bitcoind running on a fairly powerful dedicated server with centOS.
About 20GB free space was left at the time of corruption.
We had 10s of thousands of keys generated because of the nature of the service, and the wallet was over 90mb.
Thoughts?
Like most files, your wallet.dat file will have its data corrupted if an application is currently writing to it (your Bitcoin client, for example) and it abruptly closes. Running out of hard drive and memory space also risks the possibility of corrupting your wallet.dat file if it is currently being processed during that time. And of course, there's always the self-inflicted case of improperly writing onto your wallet.dat file either intentionally or unintentionally.
To be honest I haven't. I thought it must be something with bitcoind done wrong, but now that you are saying it it very well might be a trivial reason.
Looking it up now.
If you guys have more ideas in the meantime, please let me know
Also did someone have his wallet corrupted but bitcoind manged to fix it upon launch?
Looking it up now.
If you guys have more ideas in the meantime, please let me know
Also did someone have his wallet corrupted but bitcoind manged to fix it upon launch?
Server run out of virtual memory?
Have you already checked log files for possible error messages?
Have you already checked log files for possible error messages?
Well I just had wallet.dat corrupted so bad that even the bitcoind restore process upon launch couldn't fix it.
Of course I have a back-up, but would be interesting to discuss what usually causes that so we can avoid it in future.
It was latest version bitcoind running on a fairly powerful dedicated server with centOS.
About 20GB free space was left at the time of corruption.
We had 10s of thousands of keys generated because of the nature of the service, and the wallet was over 90mb.
Thoughts?
Of course I have a back-up, but would be interesting to discuss what usually causes that so we can avoid it in future.
It was latest version bitcoind running on a fairly powerful dedicated server with centOS.
About 20GB free space was left at the time of corruption.
We had 10s of thousands of keys generated because of the nature of the service, and the wallet was over 90mb.
Thoughts?
Possible it was the hardrive itself that got corrupted? sounds like it and lucky you had backup.
Well I just had wallet.dat corrupted so bad that even the bitcoind restore process upon launch couldn't fix it.
Of course I have a back-up, but would be interesting to discuss what usually causes that so we can avoid it in future.
It was latest version bitcoind running on a fairly powerful dedicated server with centOS.
About 20GB free space was left at the time of corruption.
We had 10s of thousands of keys generated because of the nature of the service, and the wallet was over 90mb.
Thoughts?
Of course I have a back-up, but would be interesting to discuss what usually causes that so we can avoid it in future.
It was latest version bitcoind running on a fairly powerful dedicated server with centOS.
About 20GB free space was left at the time of corruption.
We had 10s of thousands of keys generated because of the nature of the service, and the wallet was over 90mb.
Thoughts?
Jump to: