Topic: Database corrupted (Read 523 times)
Depending on you hard drive it could take longer than 48 hours, so don't panic if it takes awhile.
Thanks. Should peers.dat be deleted too?
It seems stuck on 270 weeks. Don't the early weeks go fast, usually?
EDIT: NVM there it goes. I deleted everything a second time and started over. This time deleting the chainstate folder also as you said to. Didn't do that last time and it was stuck on 270.
It seems stuck on 270 weeks. Don't the early weeks go fast, usually?
EDIT: NVM there it goes. I deleted everything a second time and started over. This time deleting the chainstate folder also as you said to. Didn't do that last time and it was stuck on 270.
You have let it sit. Depending on your connection it can take up to 24 to 48 hours to download the blockchain.
Thanks. Should peers.dat be deleted too?
It seems stuck on 270 weeks. Don't the early weeks go fast, usually?
EDIT: NVM there it goes. I deleted everything a second time and started over. This time deleting the chainstate folder also as you said to. Didn't do that last time and it was stuck on 270.
It seems stuck on 270 weeks. Don't the early weeks go fast, usually?
EDIT: NVM there it goes. I deleted everything a second time and started over. This time deleting the chainstate folder also as you said to. Didn't do that last time and it was stuck on 270.
The blocks and chainstate folders and any files named block***.dat in the bitcoin directory. (the files, if you have them, are left over from the old blockchain format)
Having a Database corrupted issue with Armory. I deleted the databases folder there in roaming but that doesn't seem to be the issue. I think the issue is in Qt itself.
Would someone know what files I need to delete from Roaming/Bitcoin to resync? Blocks folder? Chainstate folder? Bunch of other .dat files in there too.
Never had this happen before...
Thanks.
Would someone know what files I need to delete from Roaming/Bitcoin to resync? Blocks folder? Chainstate folder? Bunch of other .dat files in there too.
Never had this happen before...
Thanks.
Jump to: