Bitcoin package restart in a DAppNode over unRAID

Hello,

I am trying to run the Bitcoin package in a DAppNode VM over unRAID installed directly on a 2TB SSD using the passing-through option with virtIO as the vDisk Bus and it is like reached 20% sync, always restart from 0.

2020-11-04T17:53:28Z UpdateTip: new best=00000000000001099d01047bcb6fb6e1362fb8ea83eea21f279bb3664429ec60 height=138752 version=0x00000001 log2_work=65.773125 tx=1166132 date=‘2011-07-30T07:40:35Z’ progress=0.002013 cache=108.8MiB(801001txo)
2020-11-04T17:53:28Z UpdateTip: new best=000000000000078ab619e9a29285d419e72d6d7321cfae82605091c2b96343a4 height=138753 version=0x00000001 log2_work=65.773291 tx=1166238 date=‘2011-07-30T07:45:29Z’ progress=0.002014 cache=108.8MiB(801092txo)
2020-11-04T17:53:58Z Ignoring unknown configuration value rpcclienttimeout
2020-11-04T17:53:58Z Bitcoin Core version v0.20.0 (release build)
2020-11-04T17:53:58Z Assuming ancestors of block 0000000000000000000f2adce67e49b0b6bdeb9de8b7c3d7e93b21e7fc1e819d have valid signatures.
2020-11-04T17:53:58Z Setting nMinimumChainWork=00000000000000000000000000000000000000000e1ab5ec9348e9f4b8eb8154
2020-11-04T17:53:58Z Using the ‘sse4(1way),sse41(4way),avx2(8way)’ SHA256 implementation
2020-11-04T17:53:58Z Using RdRand as an additional entropy source
2020-11-04T17:53:58Z Default data directory /root/.bitcoin
2020-11-04T17:53:58Z Using data directory /root/.bitcoin
2020-11-04T17:53:58Z Config file: /root/.bitcoin/bitcoin.conf
2020-11-04T17:53:58Z Config file arg: dbcache=“512”
2020-11-04T17:53:58Z Config file arg: disablewallet=“1”
2020-11-04T17:53:58Z Config file arg: printtoconsole=“1”
2020-11-04T17:53:58Z Config file arg: prune=“0”
2020-11-04T17:53:58Z Config file arg: rpcallowip=“172.33.0.0/16”
2020-11-04T17:53:58Z Config file arg: rpcbind=****
2020-11-04T17:53:58Z Config file arg: rpcpassword=****
2020-11-04T17:53:58Z Config file arg: rpcport=“8332”
2020-11-04T17:53:58Z Config file arg: rpcuser=****
2020-11-04T17:53:58Z Config file arg: server=“1”
2020-11-04T17:53:58Z Config file arg: testnet=“0”
2020-11-04T17:53:58Z Config file arg: txindex=“1”
2020-11-04T17:53:58Z Config file arg: zmqpubhashblock=“tcp://0.0.0.0:28333”
2020-11-04T17:53:58Z Config file arg: zmqpubhashtx=“tcp://0.0.0.0:28333”
2020-11-04T17:53:58Z Config file arg: zmqpubrawblock=“tcp://0.0.0.0:28332”
2020-11-04T17:53:58Z Config file arg: zmqpubrawtx=“tcp://0.0.0.0:28333”
2020-11-04T17:53:58Z Command-line arg: conf=“/root/.bitcoin/bitcoin.conf”
2020-11-04T17:53:58Z Command-line arg: datadir=“/root/.bitcoin”
2020-11-04T17:53:58Z Using at most 125 automatic connections (1048576 file descriptors available)
2020-11-04T17:53:58Z Using 16 MiB out of 32/2 requested for signature cache, able to store 524288 elements
2020-11-04T17:53:58Z Using 16 MiB out of 32/2 requested for script execution cache, able to store 524288 elements
2020-11-04T17:53:58Z Script verification uses 5 additional threads
2020-11-04T17:53:58Z Wallet disabled!
2020-11-04T17:53:58Z scheduler thread start
2020-11-04T17:53:58Z WARNING: the RPC server is not safe to expose to untrusted networks such as the public internet
2020-11-04T17:53:58Z HTTP: creating work queue of depth 16
2020-11-04T17:53:58Z Config options rpcuser and rpcpassword will soon be deprecated. Locally-run instances may remove rpcuser to use cookie-based auth, or may be replaced with rpcauth. Please see share/rpcauth for rpcauth auth generation.
2020-11-04T17:53:58Z HTTP: starting 4 worker threads
2020-11-04T17:53:58Z init message: Loading banlist…
2020-11-04T17:53:58Z Using /16 prefix for IP bucketing
2020-11-04T17:53:58Z Cache configuration:
2020-11-04T17:53:58Z * Using 2.0 MiB for block index database
2020-11-04T17:53:58Z * Using 63.8 MiB for transaction index database
2020-11-04T17:53:58Z * Using 8.0 MiB for chain state database
2020-11-04T17:53:58Z * Using 438.2 MiB for in-memory UTXO set (plus up to 286.1 MiB of unused mempool space)
2020-11-04T17:53:58Z init message: Loading block index…
2020-11-04T17:53:58Z Opening LevelDB in /root/.bitcoin/blocks/index
2020-11-04T17:53:58Z Opened LevelDB successfully
2020-11-04T17:53:58Z Using obfuscation key for /root/.bitcoin/blocks/index: 0000000000000000
2020-11-04T17:53:58Z LoadBlockIndexDB: last block file = 0
2020-11-04T17:53:58Z LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=0, size=0, heights=0…0, time=1970-01-01…1970-01-01)
2020-11-04T17:53:58Z Checking all blk files are present…
2020-11-04T17:53:58Z Initializing databases…
2020-11-04T17:53:58Z Pre-allocating up to position 0x1000000 in blk00000.dat
2020-11-04T17:53:58Z Opening LevelDB in /root/.bitcoin/chainstate
2020-11-04T17:53:58Z Opened LevelDB successfully
2020-11-04T17:53:58Z Using obfuscation key for /root/.bitcoin/chainstate: d8fc88138cef8955
2020-11-04T17:53:58Z init message: Rewinding blocks…
2020-11-04T17:53:58Z block index 139ms
2020-11-04T17:53:58Z Opening LevelDB in /root/.bitcoin/indexes/txindex
2020-11-04T17:53:59Z Opened LevelDB successfully
2020-11-04T17:53:59Z Using obfuscation key for /root/.bitcoin/indexes/txindex: 0000000000000000
2020-11-04T17:53:59Z txindex thread start
2020-11-04T17:53:59Z txindex is enabled
2020-11-04T17:53:59Z txindex thread exit
2020-11-04T17:53:59Z UpdateTip: new best=000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f height=0 version=0x00000001 log2_work=32.000022 tx=1 date=‘2009-01-03T18:15:05Z’ progress=0.000000 cache=0.0MiB(0txo)
2020-11-04T17:53:59Z block tree size = 1
2020-11-04T17:53:59Z nBestHeight = 0
2020-11-04T17:53:59Z Failed to open mempool file from disk. Continuing anyway.
2020-11-04T17:53:59Z torcontrol thread start
2020-11-04T17:53:59Z AddLocal(172.33.0.3:8333,1)
2020-11-04T17:53:59Z Discover: IPv4 eth0: 172.33.0.3
2020-11-04T17:53:59Z Bound to [::]:8333
2020-11-04T17:53:59Z Bound to 0.0.0.0:8333
2020-11-04T17:53:59Z init message: Loading P2P addresses…
2020-11-04T17:53:59Z Loaded 0 addresses from peers.dat 0ms
2020-11-04T17:53:59Z init message: Starting network threads…
2020-11-04T17:53:59Z net thread start
2020-11-04T17:53:59Z dnsseed thread start
2020-11-04T17:53:59Z Loading addresses from DNS seed dnsseed.bluematt.me
2020-11-04T17:53:59Z init message: Done loading
2020-11-04T17:53:59Z addcon thread start
2020-11-04T17:53:59Z msghand thread start
2020-11-04T17:53:59Z opencon thread start
2020-11-04T17:53:59Z Loading addresses from DNS seed seed.bitcoinstats.com
2020-11-04T17:53:59Z Loading addresses from DNS seed seed.bitcoin.jonasschnelli.ch
2020-11-04T17:53:59Z Loading addresses from DNS seed seed.bitcoin.sprovoost.nl
2020-11-04T17:53:59Z Loading addresses from DNS seed dnsseed.bitcoin.dashjr.org
2020-11-04T17:53:59Z Loading addresses from DNS seed seed.btc.petertodd.org
2020-11-04T17:53:59Z Loading addresses from DNS seed dnsseed.emzy.de
2020-11-04T17:53:59Z Loading addresses from DNS seed seed.bitcoin.sipa.be
2020-11-04T17:53:59Z 117 addresses found from DNS seeds
2020-11-04T17:53:59Z dnsseed thread exit
2020-11-04T17:54:00Z New outbound peer connected: version: 70015, blocks=655409, peer=0 (full-relay)
2020-11-04T17:54:00Z Synchronizing blockheaders, height: 2000 (~0.32%)
2020-11-04T17:54:01Z Synchronizing blockheaders, height: 4000 (~0.64%)
2020-11-04T17:54:01Z Synchronizing blockheaders, height: 6000 (~0.97%)

Hi @luis,

It looks like you are a pioneer, no one in the team has tested DAppNode over unRAID :sweat_smile:

We have no clue either, and we no one else hase reported the same error. It may be related to unRAID, I’m afraid we don’t know.

Let’s see if anyone in the community has been through the same :pray:

I don’t know what else could I do :sweat_smile:

As @ruvenni said we don’t have experience in this setup. Maybe @Edu can help or you can post in the discord chat a question if someone has experience with unRAID

I’m afraid Edu has no experience with unRAID either.

@luis maybe you should post about this on discord and see what happens

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.