Topic: Speed up block reindexing? (Read 2994 times)
The problem is my battery on my Laptop. When the charger is unplugged it shuts off. It's not a big deal I just noticed that sometimes if you shutdown unexpectedly Bitcoin-QT will give an error on the next start and reindex.
As a repair tech, I would say take a look at whether or not you're overclocking and then, if you are, verify that your CPU isn't causing errors by extensive testing with IntelBurnTest. If it fails, turn down the clock speed and try again.
If it passes, check your memory. Don't bother with the Windows Memory test as it won't give accurate results. There's a version of MemTest 86+ that's like version 5 (unofficial) RC1 that actually works with 64-bit systems properly. http://forum.canardpc.com/threads/68001-NEW-!!-Memtest86-5.00-RC1-available-!-Need-betatesters-! It's not perfect, but it's better than Windows Memory Test in my opinion.
Then, look at your GPU. If you mine with it, see how many unaccepted hashes there are. If you get a lot of them just before a crash, your GPU could be causing the problem. You can also tell this from bluescreens sometimes. It'll say hardware error of some sort.
Finally, look at your Power Supply. This would take some more extensive testing, so I left it for last. You'll have to unplug it from everything in your computer and short the power on leads to activate it. From there, take a volt meter and check power levels and fluctuations. If it's not steady (or if it's a bit old) you should replace it before you blow everything in the computer.
And don't forget to run chkdsk on your system after each crash. It will sometimes fix errors in the filesystem. Using a live DVD of Ubuntu or something similar to SMART test your hard drives every now and then is also a good idea since a failing drive will fail the entire system as well.
If it passes, check your memory. Don't bother with the Windows Memory test as it won't give accurate results. There's a version of MemTest 86+ that's like version 5 (unofficial) RC1 that actually works with 64-bit systems properly. http://forum.canardpc.com/threads/68001-NEW-!!-Memtest86-5.00-RC1-available-!-Need-betatesters-! It's not perfect, but it's better than Windows Memory Test in my opinion.
Then, look at your GPU. If you mine with it, see how many unaccepted hashes there are. If you get a lot of them just before a crash, your GPU could be causing the problem. You can also tell this from bluescreens sometimes. It'll say hardware error of some sort.
Finally, look at your Power Supply. This would take some more extensive testing, so I left it for last. You'll have to unplug it from everything in your computer and short the power on leads to activate it. From there, take a volt meter and check power levels and fluctuations. If it's not steady (or if it's a bit old) you should replace it before you blow everything in the computer.
And don't forget to run chkdsk on your system after each crash. It will sometimes fix errors in the filesystem. Using a live DVD of Ubuntu or something similar to SMART test your hard drives every now and then is also a good idea since a failing drive will fail the entire system as well.
If my computer is shutdown unexpectedly almost always when I turn on I get a message from Bitcoin-QT that the blockchain is corrupted and to reindex. Unfortunately this takes all day is there a way to speed this up or bypass it completely?
If this happens a lot you have a serious stability problem with your system, which is the first I would take a look at
.A crash should in noy way result always in the need to reindex, that is also true and problem if it is like that.
Dia
Yes, I have one idea for you, if you are taking timely backups.
As I've mentioned here I have experienced frequent LevelDB corruption issues with the bitcoin-qt Mac client, both with the 0.8.1 release (which had known bugs) and also now with 0.8.2 (where bugs are supposed to be resolved).
Since trying out this "new and improved" 0.8.2 release I've had 5 crash/corruption issues, but since Macs are good about getting backed up regularly with Time Machine, I've found that I can avoid the dreaded block reindexing by simply restoring from the last good backup these files:
(on Mac all in: ~/Library/Application Support/Bitcoin)
/chainstate/*
/blocks/index/*
/blocks/blk00006.dat
/blocks/rev00006.dat
The restore just takes a few moments and is MUCH faster than reindexing the entire block database.
As I've mentioned here I have experienced frequent LevelDB corruption issues with the bitcoin-qt Mac client, both with the 0.8.1 release (which had known bugs) and also now with 0.8.2 (where bugs are supposed to be resolved).
Since trying out this "new and improved" 0.8.2 release I've had 5 crash/corruption issues, but since Macs are good about getting backed up regularly with Time Machine, I've found that I can avoid the dreaded block reindexing by simply restoring from the last good backup these files:
(on Mac all in: ~/Library/Application Support/Bitcoin)
/chainstate/*
/blocks/index/*
/blocks/blk00006.dat
/blocks/rev00006.dat
The restore just takes a few moments and is MUCH faster than reindexing the entire block database.
You know I had one but sold it. Unfortunately that will not speed up block reindexing.
It won't? Dang. I really hoped buying a UPS would help the computer. Wouldn't it make the computer feel more secure in it's power supply and therefore go faster and not be scared of a distupred power supply or (god forbid) a power surge of 0.1 volts? 
You know I had one but sold it. Unfortunately that will not speed up block reindexing.
Buy a UPS?
If my computer is shutdown unexpectedly almost always when I turn on I get a message from Bitcoin-QT that the blockchain is corrupted and to reindex. Unfortunately this takes all day is there a way to speed this up or bypass it completely?
Jump to: