Segmentation Fault occurs in use external HDD

Hi,

I’m trying to running insight on MacBook with external HDD.
I placed blockchain data on external HDD, synced 100%, and run node.
After a short time, segmentation fault occurs.

What should I do?

debug.log is here, thank you.

2017-03-09 14:20:10 Bitcoin version v0.12.1-bitcore-4 (2016-09-20 10:16:42 -0400)
2017-03-09 14:20:10 InitParameterInteraction: parameter interaction: -whitelistforcerelay=1 -> setting -whitelistrelay=1
2017-03-09 14:20:10 Using BerkeleyDB version Berkeley DB 4.8.30: (April  9, 2010)
2017-03-09 14:20:10 Default data directory /Users/mizunotakahiro/Library/Application Support/Bitcoin
2017-03-09 14:20:10 Using data directory /Volumes/BitcoreFullnode/data
2017-03-09 14:20:10 Using config file /Volumes/BitcoreFullnode/data/bitcoin.conf
2017-03-09 14:20:10 Using at most 125 connections (10240 file descriptors available)
2017-03-09 14:20:10 Using 2 threads for script verification
2017-03-09 14:20:10 scheduler thread start
2017-03-09 14:20:10 Binding RPC on address 0.0.0.0 port 8332 failed.
2017-03-09 14:20:10 HTTP: creating work queue of depth 128
2017-03-09 14:20:10 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/rpcuser for rpcauth auth generation.
2017-03-09 14:20:10 HTTP: starting 4 worker threads
2017-03-09 14:20:10 Using wallet wallet.dat
2017-03-09 14:20:10 init message: Verifying wallet...
2017-03-09 14:20:10 CDBEnv::Open: LogDir=/Volumes/BitcoreFullnode/data/database ErrorFile=/Volumes/BitcoreFullnode/data/db.log
2017-03-09 14:20:10 Bound to [::]:8333
2017-03-09 14:20:10 Bound to 0.0.0.0:8333
2017-03-09 14:20:10 Block index database configuration:
2017-03-09 14:20:10 * Using 1000 max open files
2017-03-09 14:20:10 * Compression is enabled
2017-03-09 14:20:10 Cache configuration:
2017-03-09 14:20:10 * Max cache setting possible 16384MiB
2017-03-09 14:20:10 * Using 75.0MiB for block index database
2017-03-09 14:20:10 * Using 12.5MiB for chain state database
2017-03-09 14:20:10 * Using 12.5MiB for in-memory UTXO set
2017-03-09 14:20:10 init message: Loading block index...
2017-03-09 14:20:10 Opening LevelDB in /Volumes/BitcoreFullnode/data/blocks/index
2017-03-09 14:20:33 Opened LevelDB successfully
2017-03-09 14:20:33 Using obfuscation key for /Volumes/BitcoreFullnode/data/blocks/index: 0000000000000000
2017-03-09 14:20:33 Opening LevelDB in /Volumes/BitcoreFullnode/data/chainstate
2017-03-09 14:20:33 Opened LevelDB successfully
2017-03-09 14:20:33 Using obfuscation key for /Volumes/BitcoreFullnode/data/chainstate: 9399f1f5043364e5
2017-03-09 14:20:37 LoadBlockIndexDB: last block file = 797
2017-03-09 14:20:37 LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=22, size=20966268, heights=456442...456463, time=2017-03-09...2017-03-09)
2017-03-09 14:20:37 Checking all blk files are present...
2017-03-09 14:21:02 LoadBlockIndexDB: transaction index enabled
2017-03-09 14:21:02 LoadBlockIndexDB: address index enabled
2017-03-09 14:21:02 LoadBlockIndexDB: timestamp index enabled
2017-03-09 14:21:02 LoadBlockIndexDB: spent index enabled
2017-03-09 14:21:02 LoadBlockIndexDB: hashBestChain=0000000000000000013c3dae91f6e0140f4c7898930e8911658e80faf3ee5a47 height=456463 date=2017-03-09 14:03:12 progress=0.999996
2017-03-09 14:21:02 init message: Verifying blocks...
2017-03-09 14:21:02 Verifying last 288 blocks at level 3
2017-03-09 14:22:33 No coin database inconsistencies in last 2 blocks (1634 transactions)
2017-03-09 14:22:33  block index          143030ms
2017-03-09 14:22:33 init message: Loading wallet...
2017-03-09 14:22:33 nFileVersion = 120100
2017-03-09 14:22:33 Keys: 102 plaintext, 0 encrypted, 102 w/ metadata, 102 total
2017-03-09 14:22:33  wallet                   52ms
2017-03-09 14:22:33 init message: Activating best chain...
2017-03-09 14:22:33 mapBlockIndex.size() = 456464
2017-03-09 14:22:33 nBestHeight = 456463
2017-03-09 14:22:33 setKeyPool.size() = 101
2017-03-09 14:22:33 mapWallet.size() = 0
2017-03-09 14:22:33 mapAddressBook.size() = 1
2017-03-09 14:22:33 init message: Loading addresses...
2017-03-09 14:22:33 torcontrol thread start
2017-03-09 14:22:33 ERROR: Read: Failed to open file /Volumes/BitcoreFullnode/data/banlist.dat
2017-03-09 14:22:33 Invalid or missing banlist.dat; recreating
2017-03-09 14:22:33 Loaded 39354 addresses from peers.dat  194ms
2017-03-09 14:22:33 net thread start
2017-03-09 14:22:33 addcon thread start
2017-03-09 14:22:33 dnsseed thread start
2017-03-09 14:22:33 opencon thread start
2017-03-09 14:22:33 msghand thread start
2017-03-09 14:22:33 init message: Done loading
2017-03-09 14:22:34 ProcessMessages: advertizing address 219.124.136.80:8333
2017-03-09 14:22:34 receive version message: /Satoshi:0.13.1/: version 70014, blocks=456463, us=219.124.136.80:62816, peer=1
2017-03-09 14:22:34 AdvertizeLocal: advertizing address 219.124.136.80:8333
2017-03-09 14:22:35 ProcessMessages: advertizing address 219.124.136.80:8333
2017-03-09 14:22:35 receive version message: /BitcoinUnlimited:1.0.0.1(EB16; AD12)/: version 80002, blocks=456463, us=219.124.136.80:62818, peer=2
2017-03-09 14:22:35 AdvertizeLocal: advertizing address 219.124.136.80:8333
2017-03-09 14:22:35 connect() to [2001::9d38:6ab8:48c:1487:8341:fa92]:8333 failed: No route to host (65)
2017-03-09 14:22:40 ProcessMessages: advertizing address 219.124.136.80:8333
2017-03-09 14:22:40 receive version message: /Satoshi:0.13.1/: version 70014, blocks=456463, us=219.124.136.80:62832, peer=3
2017-03-09 14:22:40 AdvertizeLocal: advertizing address 219.124.136.80:8333
2017-03-09 14:22:44 ProcessMessages: advertizing address 219.124.136.80:8333
2017-03-09 14:22:44 receive version message: /Satoshi:0.13.1/: version 70014, blocks=456463, us=219.124.136.80:62837, peer=4
2017-03-09 14:22:44 AdvertizeLocal: advertizing address 219.124.136.80:8333
2017-03-09 14:22:44 P2P peers available. Skipped DNS seeding.
2017-03-09 14:22:44 dnsseed thread exit
2017-03-09 14:22:45 ProcessMessages: advertizing address 219.124.136.80:8333
2017-03-09 14:22:45 receive version message: /Satoshi:0.12.1/: version 70012, blocks=456463, us=219.124.136.80:62838, peer=5
2017-03-09 14:22:45 AdvertizeLocal: advertizing address 219.124.136.80:8333
2017-03-09 14:22:45 connect() to [2001::34e5:74cd:3ca7:2268:a0d2:9429]:8333 failed: No route to host (65)
2017-03-09 14:22:47 ProcessMessages: advertizing address 219.124.136.80:8333
2017-03-09 14:22:47 receive version message: /Satoshi:0.11.2/: version 70002, blocks=456463, us=219.124.136.80:62840, peer=6
2017-03-09 14:22:47 AdvertizeLocal: advertizing address 219.124.136.80:8333
2017-03-09 14:22:58 ProcessMessages: advertizing address 219.124.136.80:8333
2017-03-09 14:22:58 receive version message: /Satoshi:0.13.2/: version 70015, blocks=456463, us=219.124.136.80:62850, peer=7
2017-03-09 14:22:58 AdvertizeLocal: advertizing address 219.124.136.80:8333
2017-03-09 14:22:59 ProcessMessages: advertizing address 219.124.136.80:8333
2017-03-09 14:22:59 receive version message: /Satoshi:0.13.2/: version 70015, blocks=456463, us=219.124.136.80:62851, peer=8
2017-03-09 14:22:59 AdvertizeLocal: advertizing address 219.124.136.80:8333
2017-03-09 14:23:16 connect() to [2001::9d38:6abd:8ab:501:39e4:71a7]:8333 failed: No route to host (65)
2017-03-09 14:23:33 ProcessMessages: advertizing address 219.124.136.80:8333
2017-03-09 14:23:33 receive version message: /Satoshi:0.13.2/: version 70015, blocks=456463, us=219.124.136.80:62871, peer=9
2017-03-09 14:23:33 AdvertizeLocal: advertizing address 219.124.136.80:8333

Actually I think it might depend on many things.
However, reading the log, the first thing I notice is this line:

My guess is that Bitcore is not correctly bound to the Bitcoin client.
Check the Bitcoin Core config file (bitcoin.conf) and the Bitcore config file (bitcore-node.json)
Also, if you installed Bitcoin Core separately, you should ensure that Bitcore is actually using the right bitcoind executable, which is usually installed as a node_module.

Hope this helps

I have a full node,but when i installed first time on a HDD ,it took like a week to sync,so…i buy a 480Gb SSD and install it again Ubuntu and full node with insight/etc and it sync in 2 days + is working fine.

I have a Linux PC was installed Ubuntu 16 LTS and ran Bitcore and Insight on it without SegFault.
And I found same address in debug.log.
I think that is not a cause, but seems I’m sure have to check config files.

thanks.

Yes, that works on My Ubuntu PC too.
But it not works on MacBook with external HDD.
Tough already has a nearly full blockchain!
I want to a portable environment can work Bitcore and Insight.