My blockchain corrupted some weeks ago too. Had to redownload it all
And no, i didn't power off the computer with the bitcoin client open
And no, Windows doesn't really suffer from a power loss... (at least, since XP)
Topic: Corrupted blkindex.dat (Read 1570 times)
invest $100 in a UPS (Un-interruptable Power Supply)
i'm the kind of person who always has a thousand windows open and a thousand tabs in each window... my recent ups purchase has been one of the best investments ever and has saved me at least once since i got it a few weeks ago. lightning storms are no longer much of an issue.
You could try downloading the blockchain here, and every time you need to delete the blockchain, simply copy those files over:
http://sourceforge.net/projects/bitcoin/files/Bitcoin/blockchain/
I know it says not to use it with an existing wallet, but I think you should be fine if you run the client with -rescan (I can't make any guarantees, though). Should save some time.
Edit: You can view/submit feature requests here: https://github.com/bitcoin/bitcoin/issues
http://sourceforge.net/projects/bitcoin/files/Bitcoin/blockchain/
I know it says not to use it with an existing wallet, but I think you should be fine if you run the client with -rescan (I can't make any guarantees, though). Should save some time.
Edit: You can view/submit feature requests here: https://github.com/bitcoin/bitcoin/issues
Very helpful! Thanks!
You could try downloading the blockchain here, and every time you need to delete the blockchain, simply copy those files over:
http://sourceforge.net/projects/bitcoin/files/Bitcoin/blockchain/
I know it says not to use it with an existing wallet, but I think you should be fine if you run the client with -rescan (I can't make any guarantees, though). Should save some time.
Edit: You can view/submit feature requests here: https://github.com/bitcoin/bitcoin/issues
http://sourceforge.net/projects/bitcoin/files/Bitcoin/blockchain/
I know it says not to use it with an existing wallet, but I think you should be fine if you run the client with -rescan (I can't make any guarantees, though). Should save some time.
Edit: You can view/submit feature requests here: https://github.com/bitcoin/bitcoin/issues
Trust me, they're working on it.
Not very helpful. Can you provide a link to the feature request so I can upvote it?
Trust me, they're working on it. No need to bother them with that.
It is not their problem, anyways.
Like you said, your power shut off.
There are many programs who can be severely affected by an instant power shut off. The windows operating system itself being one of them. And that is a multi-billion-dollar software engineering project. So don't get your hopes up for bitcoin any time soon.
Simply delete the block chain, re-download it, and invest $100 in a UPS (Un-interruptable Power Supply) so you have time to shut off your computer the next time your power goes out.
You shouldn't really be running the bitcoin client 24/7 open on a machine anyways. What happens when somebody decides to use your computer for a minute? They could transfer all of your funds away in a second.
It is not their problem, anyways.
Like you said, your power shut off.
There are many programs who can be severely affected by an instant power shut off. The windows operating system itself being one of them. And that is a multi-billion-dollar software engineering project. So don't get your hopes up for bitcoin any time soon.
Simply delete the block chain, re-download it, and invest $100 in a UPS (Un-interruptable Power Supply) so you have time to shut off your computer the next time your power goes out.
You shouldn't really be running the bitcoin client 24/7 open on a machine anyways. What happens when somebody decides to use your computer for a minute? They could transfer all of your funds away in a second.
When my Windows is turned off by a power loss, my blkindex.dat gets corrupted, I have to delete it (otherwise the client won't start) and wait hours to regenerate it.
Is there a faster solution?
Where can I post a feature request for the Bitcoin developers to handle this problem?
Is there a faster solution?
Where can I post a feature request for the Bitcoin developers to handle this problem?
Jump to: