Topic: Is restore from digital backup working in .95.1? (Read 694 times)

Did you create this backup from the GUI or just copied the wallet file? If it's from the GUI, then this is possibly a bug on Armory's end and I need to go over it.


The website is in dire need of tutorials and a FAQ. I'd be glad to merge in your contributions if you feel so inclined. You can submits PR directly to the gh-pages branch or coordinate with achow101 on the IRC channel (#bitcoin-armory at freenode)

Thanks for this, I looked at the backup in Notepad++ and all it is is nil values, so I guess the backup wasn't done correctly or was corrupted.

So I guess no point trying for this, but hopefully the exercise showed a few things.

I do have the CSV transaction exports, so I'll load up the paper backups again, and see if it's missing any of the wallet addresses between the two.

Cheers goatpig, and i'm happy to volunteer with the website if noone else is!

Thanks

Jamie

That file is basically empty from the looks of it. If the repair tool couldn't pick anything and the header is all 0s, this is my current conclusion. Do you have other backups (that were not on the device you saved these files on?)


Restoring from a paper backup creates a 1000 address lookup. Regular wallets start with a 100 address lookup, and rarely do users go over that. It is highly unlikely 1000 address won't cover your entire history. At any rate, you can create 10k addresses just to make sure.


MAX_PATH on Windows is 32768. Length is probably not the issue. Look out for non ascii characters in the path instead.


You saying trying to run the repair tool with no wallet loaded hangs?


Refer to the first comment.

Yes, definitely. I used Armory for years before, transferred to Trezor but now I see the project is back up and running I wanted to re-load it back up.

The blockchain loading part is still a pain, but there are massive improvements on the armory side on this machine which is pretty modestly speced.

Logs are at http://pastebin.com/v2X75Br8 and I did a step by step here to show you what I'm seeing for both the import and repair tools. I have the paper backups which restored fine, so focusing on the digital backups I guess that have my notes and all the wallets (even if they weren't used), and I'd like to compare if the paper backups are missing anything that the digital have (ie derivative addresses using that aren't loaded in the paper backup, that either had transactions and a nil balance now, or some small balance left over).

I also tried it on the .wallet files and the rootpubkey ones too, same results

From blank armory all up to speed with blockchain loaded and .13.1





After this, there is nothing happening. I tried to reload Armory to see if it loaded something, which it didn't and then did the repair as suggested. When I do the paper backup at the same point,



After this I get failed to fix, invalid path or file isn't a valid armory wallet.

Also, I noticed that when you have no wallets set up and try and load a wallet, this happens






I hope this helps!

I also noticed something else. I have the first attempt in a sub folder on my desktop, so I thought that it might be to do with the path length, as I was getting error 1, so I put it in c:\ and it then gave me an i/o error asking me if I had valid credentials, and error 2.

So two different errors for the same file.

I then opened armory as administrator, and tried again and got the error 1 file instead.


Thanks

Jamie

Are you sure this wallet is for Bitcoin mainnet? You should run it through the wallet repair tool and post the output log here.

Sure, it's at http://pastebin.com/Wc9ZH3fb

The thing that jumps out is

2016-12-19 08:03 (ERROR) -- PyBtcWallet.pyc:2018 - Requested wallet is for a different blockchain!
2016-12-19 08:03 (ERROR) -- Traceback (most recent call last):
  File "qtdialogs.pyc", line 12197, in clickedOkay
  File "ArmoryQt.py", line 3591, in execGetImportWltName
  File "armoryengine\Timer.pyc", line 99, in inner
  File "armoryengine\PyBtcWallet.pyc", line 2121, in readWalletFile
  File "armoryengine\PyBtcWallet.pyc", line 2019, in unpackHeader
KeyError: '\x00\x00\x00\x00'


Also, just a thought, old armory was on something like version 10 of core, whereas the new one is with everything up to date.

let's see armorylog.txt

Hi Goatpig,

I'm trying to compare the bitcoin addresses from a paper backup I have, with a digital backup I found at last, as I couldn't see some addresses I knew I had.

After getting everything up and running with the new version of Armory (good work!), I thought I'd test around a few things, and was able to import my paper backup, generate a couple of hundred addresses, and see some of the main ones with some small change in them and balances. However, I know some addresses had no balances, but still transactions.

So I found my digital backups, and am having a problem doing the following steps (and I nuked the paper backups for the moment).

Open armory (expert mode), let it load up and get up to date.

Import or restore wallet

Select import digital backup or watching-only wallet

click continue

the import wallet file dialog opens

I select one of my digital backup files (I have the *.wallet.rootpubkey and *.wallet files)

Then nothing happens.

Now when I did this with the paper wallet, it then computed the addresses etc, but for the digital backup it isn't.

Am I doing something wrong?

Thanks

Jamie

P.S. I was reading through some threads on the forum, I'm not a coder but willing to volunteer to tidy up some of the screens as I've spotted a few links to bitcoin.org which don't work, and also willing to test some of the features especially related to backups, message signing etc, wallet repair