So I've been using bitcore to sync the blockchain on Ubuntu 16. After running out of space on a 250Gb HD I've moved it to a 1Tb external HD. It came up with syncing errors so decided to just restart from scratch with this external HD.
The other week it finally reached 100% however a couple days ago I accidentally pulled out the external HD USB lead
I next put the USB lead back in but on a different USB port to make sure I didn't accidentally pull it out again in future.
This seemed to change the mapping from
/media/myhd/mydir/[b]blockchain[/b]
to
/media/myhd/mydir/[b]blockchain1[/b]
Argh! So I changed the bitcore.json file to reflect the new data directory but it gives the following result
warn: Verifying blocks...
warn: Verifying blocks...
warn: Verifying blocks...
...
warn: Verifying blocks...
error: Failed to start servicees
error: RPCError: Verifying blocks.
<callstack in bitcoind.js>
error: Failed to stop services: Error: bitcoind spawned process exited with status code 1.
I tried adding the reindex=1 into the bitcoin.conf file (Is this the right place??) to try to reindex it but this doesn't appear to be picked up. Looking in bitcoin.js it appeared as though some help text should appear saying reindexing flag has been noticed.
Anyone know how I can prevent yet another weeks delay in needing to redownload the entire blockchain again???
There are no obvious corrupt files on the disk (unlike the disk full scenario which did exhibit this)
I love bitcoin but this setup/usability of bitcore is a nightmare if the db (not even sure if this is bitcoin or bitcore's db) is really this fragile. My current concern is when in production if we have a HD crash or power cut we need to somehow fix the db and can't afford to do a full resync each time.
I'm pretty sure this is just because I'm new to bitcore and ubuntu but I have no idea how to resolve this Verifying blocks error now so any advice is really appreciated!