<p>You're on the right track -- in fact you're already using the correct command line switch, which is "-rescan".  But your mistake is thinking this is a quick solution.  It's not.  Rescanning the blockchain will take <em>hours</em>, depending on your processor speed.</p>

<p>This is a task you'll want to leave running overnight.  If the problem persists even then, record the error message you get once the rescanning has completed, and ask another question with that error message.</p>

<p>Your next option would probably be to actually transfer the Bitcoins using a tool like pywallet, but I'd wait until you've left this rescanning overnight before you try that, and seek guidance on how to use pywallet.</p>

CC BY-SA 3.0
2014-02-19T05:10:20.077Z
I just did this. It didn't finish overnight. And as stupid as I am, I stopped the rescanning right before I went to this site to see your answer... I will rescan again for a full day and will report back then.
brgr
CC BY-SA 3.0
2014-02-19T13:46:20.050Z
It worked now, just as you said. I would upvote your answer, but I cannot yet, sorry :/
brgr
CC BY-SA 3.0
2014-02-19T04:24:27.987Z
2014-02-19T04:24:27.987Z
Eric S
<p>my situation is the following: I have a laptop with not much space on disk and therefore using bitcoin on a stick (I start bitcoin-qt with the argument "-datadir=location/to/stick). Now I wanted to transfer some bitcoins from my mobile phone to that account. Accidentaly I typed in a wrong directory (which doesnt exist) and bitcoin-qt lead me to the standard bitcoin directory (which is ~/.bitcoin). I didn't realize this and transferred the bitcoins to that address.</p>

<p>Now I would like to change the wallet.dat file from the ~/.bitcoin/ directory with the wallet.dat file from the directory on my stick, because my stick has all the blockchain already loaded. Is this possible?</p>

<p>What I have tried so far:</p>

<ul>
<li>simply changing the wallet.dat files: when I now start bitcoin-qt it goes in a very very long loop (probably even an endless-loop). It just says "Dursuche erneut..." (german), what means translated: "Researching..."</li>
<li>doing the above, but with the additional argument "-rescan" ("bitcoin-qt -rescan -datadir=/location/of/stick"): it happens the same as above</li>
<li>trying to backup the relevant wallet.dat file inside the console of bitcoin-qt: when trying to back it up i get the error: "Error: Wallet backup failed! (code: -4)"</li>
</ul>

<p>Can someone help me with this problem? Thanks in advance!</p>

<p>Edit: I wanted to rewrite my problem in another (probably easier understandable) way: I would like to overwrite the wallet.dat file inside the ~/.bitcoin/ folder. But doing so, bitcoin-qt doesnt stop loading (it just says "Researching...". Is there another way to do what I want?</p>

CC BY-SA 3.0
2014-02-18T21:32:06.127Z
Could you raise an issue on Github with that stupid translation? It should say "rescanning" which would make a lot more sense.
user13413
CC BY-SA 3.0
2014-02-18T22:50:44.100Z
»Durchsuche erneut« actually means »rescanning«. The translation is correct, I think.
erik
<wallet><bitcoin-core><backup><linux><wallet.dat>
I want to use another wallet.dat file with bitcoin-qt. Is this possible?
brgr
# I want to use another wallet.dat file with bitcoin-qt. Is this possible?

(Asked by: username_0 on 2014-02-18)

my situation is the following: I have a laptop with not much space on disk and therefore using bitcoin on a stick (I start bitcoin-qt with the argument "-datadir=location/to/stick). Now I wanted to transfer some bitcoins from my mobile phone to that account. Accidentaly I typed in a wrong directory (which doesnt exist) and bitcoin-qt lead me to the standard bitcoin directory (which is ~/.bitcoin). I didn't realize this and transferred the bitcoins to that address.

Now I would like to change the wallet.dat file from the ~/.bitcoin/ directory with the wallet.dat file from the directory on my stick, because my stick has all the blockchain already loaded. Is this possible?

What I have tried so far:

* simply changing the wallet.dat files: when I now start bitcoin-qt it goes in a very very long loop (probably even an endless-loop). It just says "Dursuche erneut..." (german), what means translated: "Researching..."
* doing the above, but with the additional argument "-rescan" ("bitcoin-qt -rescan -datadir=/location/of/stick"): it happens the same as above
* trying to backup the relevant wallet.dat file inside the console of bitcoin-qt: when trying to back it up i get the error: "Error: Wallet backup failed! (code: -4)"

Can someone help me with this problem? Thanks in advance!

Edit: I wanted to rewrite my problem in another (probably easier understandable) way: I would like to overwrite the wallet.dat file inside the ~/.bitcoin/ folder. But doing so, bitcoin-qt doesnt stop loading (it just says "Researching...". Is there another way to do what I want?

**Tags:** wallet, bitcoin-core, backup, linux, wallet.dat

> **Comments:**
> **username_1**: Could you raise an issue on Github with that stupid translation? It should say "rescanning" which would make a lot more sense.  
> **username_2**: »Durchsuche erneut« actually means »rescanning«. The translation is correct, I think.  

---

## 1 answers

### Answer by username_3 on 2014-02-19. Score: 0 | Accepted answer

You're on the right track -- in fact you're already using the correct command line switch, which is "-rescan". But your mistake is thinking this is a quick solution. It's not. Rescanning the blockchain will take *hours*, depending on your processor speed.

This is a task you'll want to leave running overnight. If the problem persists even then, record the error message you get once the rescanning has completed, and ask another question with that error message.

Your next option would probably be to actually transfer the Bitcoins using a tool like pywallet, but I'd wait until you've left this rescanning overnight before you try that, and seek guidance on how to use pywallet.

> **Comments:**
> **username_0**: I just did this. It didn't finish overnight. And as stupid as I am, I stopped the rescanning right before I went to this site to see your answer... I will rescan again for a full day and will report back then.  
> **username_0**: It worked now, just as you said. I would upvote your answer, but I cannot yet, sorry :/  

---

