<p>With bitcoind 0.10 (current release candidate) you don't need bootstrap at all anymore as it downloads faster and more efficient than bittorrent would. Bootstrap is probably going to disappear soon. So you might not want to bother at all.</p>

CC BY-SA 3.0
2015-01-06T00:50:10.097Z
You don't say, I'll remove the bootstrap part anyway, since it's kind of awkward.
tlehman
CC BY-SA 3.0
2015-01-06T00:18:04.663Z
2015-01-06T00:18:04.663Z
Jannes
<p>I am working on a bitcoin development environment in a box, and I've got the bitcoin reference implementation compiling and running so far in this vagrant environment: <a href="https://github.com/tlehman/bitcoin-vagrant" rel="nofollow">https://github.com/tlehman/bitcoin-vagrant</a></p>

<p>Another feature I would like to add is an optional script in /home/vagrant that can download the bootstrap.dat file to speed up downloading the blockchain. My first stab at this problem was to use transmission-cli to download  <a href="https://bitcoin.org/bin/blockchain/bootstrap.dat.torrent" rel="nofollow">https://bitcoin.org/bin/blockchain/bootstrap.dat.torrent</a>, and then copy it to ~/.bitcoin/, and then fire up <code>bitcoind</code> for the first time. This works, but it fills up the virtual machine, and it still takes a long time to get imported. On top of that, a <code>vagrant destroy</code> command would blow away all the blockchain data, which is not desirable, I'd like to decouple the data from the program and it's dependencies.</p>

<p>The way I tried to solve this was to mount ~/.bitcoin/ as /vagrant/data/ (which is mounted to a folder in the host filesystem). The problem I am having is that when I run <code>bitcoind -daemon</code>, I get an error saying</p>

<pre><code>Bitcoin server starting
vagrant@precise64:~$ : Error opening block database.

Do you want to rebuild the block database now?
</code></pre>

<p>My first guess was that the ~/.bitcoin/bootstrap.dat file was corrupted, but the SHA256 of the file is <code>d05062052be4dd6fbaeac5f17598e52f7ad545f9f938acefaf7067ecce1d7b5a</code>, which matches the SHA256 in the <a href="https://bitcoin.org/bin/blockchain/bootstrap.txt" rel="nofollow">torrent's readme</a>.</p>

<p>My second guess was that LevelDB needs some filesystem feature that isn't present in VirtualBox's synced directories, but I am not sure what that would be.</p>

<p>What can I do to fix this or work around it?</p>

CC BY-SA 3.0
2015-01-05T15:55:19.380Z
Can you create/edit files in that directory from the guest system? My hunch is that it doesn't have write permission.
Nick ODell
CC BY-SA 3.0
2015-01-05T17:22:26.727Z
@NickODell Yes, I can create and delete files as vagrant user.
tlehman
CC BY-SA 3.0
2015-01-06T09:48:44.227Z
are you running the vagrant box on a Windows machine or Linux? I've encountered strange problems before due to the difference in file-structures on the mounted directories
OACDesigns
CC BY-SA 3.0
2015-01-06T17:12:34.653Z
@OACDesigns I'm running vagrant on Mac OS X, using HFS (case sensitive).
tlehman
<bitcoind><bootstrap.dat>
Bitcoind running in vagrant can't import bootstrap.dat from external directory
tlehman
# Bitcoind running in vagrant can't import bootstrap.dat from external directory

(Asked by: username_0 on 2015-01-05)

I am working on a bitcoin development environment in a box, and I've got the bitcoin reference implementation compiling and running so far in this vagrant environment: <https://github.com/username_0/bitcoin-vagrant>

Another feature I would like to add is an optional script in /home/vagrant that can download the bootstrap.dat file to speed up downloading the blockchain. My first stab at this problem was to use transmission-cli to download <https://bitcoin.org/bin/blockchain/bootstrap.dat.torrent>, and then copy it to ~/.bitcoin/, and then fire up `bitcoind` for the first time. This works, but it fills up the virtual machine, and it still takes a long time to get imported. On top of that, a `vagrant destroy` command would blow away all the blockchain data, which is not desirable, I'd like to decouple the data from the program and it's dependencies.

The way I tried to solve this was to mount ~/.bitcoin/ as /vagrant/data/ (which is mounted to a folder in the host filesystem). The problem I am having is that when I run `bitcoind -daemon`, I get an error saying

```
Bitcoin server starting
vagrant@precise64:~$ : Error opening block database.

Do you want to rebuild the block database now?

```

My first guess was that the ~/.bitcoin/bootstrap.dat file was corrupted, but the SHA256 of the file is `d05062052be4dd6fbaeac5f17598e52f7ad545f9f938acefaf7067ecce1d7b5a`, which matches the SHA256 in the [torrent's readme](https://bitcoin.org/bin/blockchain/bootstrap.txt).

My second guess was that LevelDB needs some filesystem feature that isn't present in VirtualBox's synced directories, but I am not sure what that would be.

What can I do to fix this or work around it?

**Tags:** bitcoind, bootstrap.dat

> **Comments:**
> **username_1**: Can you create/edit files in that directory from the guest system? My hunch is that it doesn't have write permission.  
> **username_0**: @username_1 Yes, I can create and delete files as vagrant user.  
> **username_2**: are you running the vagrant box on a Windows machine or Linux? I've encountered strange problems before due to the difference in file-structures on the mounted directories  
> **username_0**: @username_2 I'm running vagrant on Mac OS X, using HFS (case sensitive).  

---

## 1 answers

### Answer by username_3 on 2015-01-06. Score: 1

With bitcoind 0.10 (current release candidate) you don't need bootstrap at all anymore as it downloads faster and more efficient than bittorrent would. Bootstrap is probably going to disappear soon. So you might not want to bother at all.

> **Comments:**
> **username_0**: You don't say, I'll remove the bootstrap part anyway, since it's kind of awkward.  

---

