Topic: Armory Tx failures; BTC Core stuck on (corrupt?) block 378056. (Read 536 times)
There is nothing you can do to speed up the sync, and if you think you have corrupted blocks then it would be best that you do a full resync. Also make sure that all of your software is fully up to date.
December 17, 2015, 02:20:27 AM
Hi there,
After a long period w/out using BTC what so ever, i found my blockchain had become corrupt and in a way I didn't understand.
So, i re-scanned/synced the lot again - seemingly without any errors according to Armory everything seems OK, however, whenever no transaction would finalise, in fact after Select rcpt address/amnt > confirm TX >enter passphrase > The window would immediately close, giving zero feedback and take me back to the original Send Tx window, only exception being when i entered my pass-phrase incorrectly, in which case i re-enter it to be sure, and get the same non-result, back to original Send Tx screen. At least security and basic functionality was intact, which lessened the stress, but i was puzzled.
Frustrated, I took a Ticket with Armory Tech and through in my debug. It seems the actual Core client never fully updated and was stuck on Block 378056! Though Armory didn't detect and report and problems, except in debug.log of course.
So, now i'm using my QT and restarting the BC dload again, now knowing the problem was block 378056 (emitted on October 8th).
Is it possible to speed this up?? e.g Let the QT sync up to block ~378056 and then just c/paste the rest of the blocks from backup, post 378056 (assuming they aren't also corrupt) into my .bitcoin/blocks directory? Is this possible? I can't see why not, yet i'm a solid novice. Correlating blocks/datab maybe problematic?
Alternatively, is there another way or client (I've only ever used Core & Armory) where i can just drop the relevant wallet.dat into that doesn't require a local copy of BC? as another 'quicker' work around? I wonder if possible? As i understand (may be wrong) 'some' wallet.dat files are interoperable with a number of other (not all) clients?
Thanks for any help/hints everyone
Cheers,
PS: This shit always seems to happen when i need immediate access to coins or at end of a long period of sideways movement. Bloody limbo coins
After a long period w/out using BTC what so ever, i found my blockchain had become corrupt and in a way I didn't understand.
So, i re-scanned/synced the lot again - seemingly without any errors according to Armory everything seems OK, however, whenever no transaction would finalise, in fact after Select rcpt address/amnt > confirm TX >enter passphrase > The window would immediately close, giving zero feedback and take me back to the original Send Tx window, only exception being when i entered my pass-phrase incorrectly, in which case i re-enter it to be sure, and get the same non-result, back to original Send Tx screen. At least security and basic functionality was intact, which lessened the stress, but i was puzzled.
Frustrated, I took a Ticket with Armory Tech and through in my debug. It seems the actual Core client never fully updated and was stuck on Block 378056! Though Armory didn't detect and report and problems, except in debug.log of course.
So, now i'm using my QT and restarting the BC dload again, now knowing the problem was block 378056 (emitted on October 8th).
Is it possible to speed this up?? e.g Let the QT sync up to block ~378056 and then just c/paste the rest of the blocks from backup, post 378056 (assuming they aren't also corrupt) into my .bitcoin/blocks directory? Is this possible? I can't see why not, yet i'm a solid novice. Correlating blocks/datab maybe problematic?
Alternatively, is there another way or client (I've only ever used Core & Armory) where i can just drop the relevant wallet.dat into that doesn't require a local copy of BC? as another 'quicker' work around? I wonder if possible? As i understand (may be wrong) 'some' wallet.dat files are interoperable with a number of other (not all) clients?
Thanks for any help/hints everyone
Cheers,
PS: This shit always seems to happen when i need immediate access to coins or at end of a long period of sideways movement. Bloody limbo coins
Jump to: