Topic: Keep getting database errors (from windows updates, I think) (Read 1023 times)
Tell a lie... actually the block chain is on the hdd!
Have an SSD, and i7 processor 16GB ram. Still takes a up to a week.
The issue with windows updates it that it indiscriminately resets the machine when it feels like it, before the client has time to shut down properly. corrupts the block chain which then needs re-indexing.
The issue with windows updates it that it indiscriminately resets the machine when it feels like it, before the client has time to shut down properly. corrupts the block chain which then needs re-indexing.
something wrong with that, is your ssd in good state? because it should only take few hours in the worst case
windows update usually tells the user when he want to restart(from 10 minutes up to hours), it should not restart at random, anyway try my previous suggestion, disable windows update, or just let it finish
Have an SSD, and i7 processor 16GB ram. Still takes a up to a week.
The issue with windows updates it that it indiscriminately resets the machine when it feels like it, before the client has time to shut down properly. corrupts the block chain which then needs re-indexing.
The issue with windows updates it that it indiscriminately resets the machine when it feels like it, before the client has time to shut down properly. corrupts the block chain which then needs re-indexing.
hmm, can you try closing the bitcoin(d) before taking an update? Btw, I occasionally just kill bitcoin instance, but still don't get any database errors. that's linux anyways.
Have an SSD, and i7 processor 16GB ram. Still takes a up to a week.
The issue with windows updates it that it indiscriminately resets the machine when it feels like it, before the client has time to shut down properly. corrupts the block chain which then needs re-indexing.
The issue with windows updates it that it indiscriminately resets the machine when it feels like it, before the client has time to shut down properly. corrupts the block chain which then needs re-indexing.
why do you think it's related to windows updates? if it's, then this should be reported.
well if the problem is windows update couldn't you just disable it for a week? otherwise if you can afford a ssd, it would sync much faster, it should rebuild in 1-2 hours
Thanks worked for me.
well if the problem is windows update couldn't you just disable it for a week? otherwise if you can afford a ssd, it would sync much faster, it should rebuild in 1-2 hours
The very latest v0.10.0.
I wouldn't mind if I just needed to re-index a few weeks or something, but every time it's the full 6+ years!
I wouldn't mind if I just needed to re-index a few weeks or something, but every time it's the full 6+ years!
What version of the core are you using?
The 3rd in a couple of months and it's getting to be a right pain in the ass as it takes a week to re-scan everything!
How do I configure the core to survive this sort of thing?
How do I configure the core to survive this sort of thing?
Jump to: