raspiblitz: error code: -28 error message: Verifying blocks...

I try to setup my first Raspiblitz V0.99 RC3 and get in the initial setup these errors:

Linux RaspiBlitz 4.14.79-v7+ #1159 SMP Sun Nov 4 17:50:20 GMT 2018 armv7l

The programs included with the Debian GNU/Linux system are free software; the exact distribution terms for each program are described in the individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent permitted by applicable law. Last login: Fri Jan 25 21:31:23 2019 from 192.168.178.39 Starting the main menu … ls: cannot access ‘/mnt/hdd/raspiblitz.conf’: No such file or directory setup still in progress - setupStep(60) checking bitcoind - please wait … can take longer if device was off or first time

./80scanLND.sh: line 1: /mnt/hdd/raspiblitz.conf: No such file or directory
usage: sudo -h | -K | -k | -V usage: sudo -v [-AknS] [-g group] [-h host] [-p prompt] [-u user] usage: sudo -l [-AknS] [-g group] [-h host] [-p prompt] [-U user] [-u user] [command] usage: sudo [-AbEHknPS] [-r role] [-t type] [-C num] [-g group] [-h host] [-p prompt] [-u user] [VAR=value] [-i|-s] [<command>] usage: sudo -e [-AknS] [-r role] [-t type] [-C num] [-g group] [-h host] [-p prompt] [-u user] file … tail: cannot open ‘/mnt/hdd/lnd/logs//net/lnd.log’ for reading: No such file or directory tail: cannot open ‘/mnt/hdd/lnd/logs//net/lnd.log’ for reading: No such file or directory tail: cannot open ‘/mnt/hdd/lnd/logs//net/lnd.log’ for reading: No such file or directory (standard_in) 1: syntax error tail: cannot open ‘/mnt/hdd/lnd/logs//net/lnd.log’ for reading: No such file or directory

│ Lightning Filtering Blockchain │
│ Progress: ?/ │
│ Please wait - this can take some long time. │
│ Its OK to close terminal and ssh back in later.│

and this is the error log:

275258 tx=376354398 date=‘2019-01-25T05:32:07Z’ progress=0.999624 cache=28.7MiB(251960txo) 2019-01-25T21:55:58Z UpdateTip: new best=0000000000000000000151c058f378dbeb404128f1a6ff42ff48a26983338c0a height=560009 version=0x20800000 log2_work=90.275282 tx=376357033 date=‘2019-01-25T05:46:04Z’ progress=0.999629 cache=29.1MiB(255692txo) 2019-01-25T21:56:03Z UpdateTip: new best=00000000000000000013c0e71833d36470b534426b14d9a8515f6b239589f274 height=560010 version=0x20000000 log2_work=90.275307 tx=376357569 date=‘2019-01-25T05:47:03Z’ progress=0.999629 cache=29.1MiB(256473txo) 2019-01-25T21:56:09Z UpdateTip: new best=000000000000000000215433f785712219fafec623ff47e51d727a9c7105474d height=560011 version=0x20000000 log2_work=90.275331 tx=376357831 date=‘2019-01-25T05:47:53Z’ progress=0.999630 cache=29.2MiB(257321txo) 2019-01-25T21:56:23Z UpdateTip: new best=00000000000000000012417a471016ac78528db9bdc40ddd8cdb28404cd822a4 height=560012 version=0x2fffc000 log2_work=90.275355 tx=376360260 date=‘2019-01-25T06:13:30Z’ progress=0.999639 cache=29.6MiB(260477txo) 2019-01-25T21:56:40Z UpdateTip: new best=00000000000000000011edbaf5b9a5938f13d118c15a4ce609f8c448fd6cb353 height=560013 version=0x20000000 log2_work=90.27538 tx=376362844 date=‘2019-01-25T06:32:41Z’ progress=0.999647 cache=30.4MiB(268461txo) 2019-01-25T21:56:40Z Syncing txindex with block chain from height 559899 2019-01-25T21:56:58Z UpdateTip: new best=0000000000000000000bbf7009ae95e503b2da886bec815fb53f43eb3db28364 height=560014 version=0x20000000 log2_work=90.275404 tx=376365757 date=‘2019-01-25T06:37:38Z’ progress=0.999648 cache=30.7MiB(271132txo) 2019-01-25T21:57:07Z UpdateTip: new best=0000000000000000002cef360991fef60f3ff63fb57b912bc6a28567ff11cef0 height=560015 version=0x20000000 log2_work=90.275428 tx=376367200 date=‘2019-01-25T06:38:11Z’ progress=0.999649 cache=30.9MiB(272507txo) 2019-01-25T21:57:20Z UpdateTip: new best=00000000000000000010b4273b4e4dbcb09ba06977d6243e70847694c7689f29 height=560016 version=0x20000000 log2_work=90.275453 tx=376370133 date=‘2019-01-25T06:54:45Z’ progress=0.999655 cache=31.2MiB(275909txo) 2019-01-25T21:57:26Z UpdateTip: new best=0000000000000000001b82a50c54dd6a38d6184afd710cbde95bf6d8b6735a37 height=560017 version=0x20400000 log2_work=90.275477 tx=376370859 date=‘2019-01-25T06:55:03Z’ progress=0.999655 cache=31.3MiB(276493txo) 2019-01-25T21:57:44Z UpdateTip: new best=0000000000000000002c80dbf4b948b537ffba28e76086145d487e8003e5dd3f height=560018 version=0x3fff0000 log2_work=90.275501 tx=376373798 date=‘2019-01-25T07:21:18Z’ progress=0.999665 cache=31.9MiB(281881txo) 2019-01-25T21:58:04Z UpdateTip: new best=00000000000000000015be549b1572212b19b31526cc8063e6bb178a6aef42ec height=560019 version=0x20000000 log2_work=90.275526 tx=376376824 date=‘2019-01-25T07:53:22Z’ progress=0.999677 cache=32.5MiB(287858txo) 2019-01-25T21:58:18Z UpdateTip: new best=00000000000000000022518ee30d70ca6d6956fdec1ee6c6eb5a338902a7723b height=560020 version=0x2323c000 log2_work=90.27555 tx=376379821 date=‘2019-01-25T07:59:35Z’ progress=0.999679 cache=32.8MiB(291093txo) 2019-01-25T21:58:35Z UpdateTip: new best=00000000000000000001fdfb3d465d4fecc96c2d0880c54a85f36e8e6db09f86 height=560021 version=0x20c00000 log2_work=90.275574 tx=376382751 date=‘2019-01-25T08:10:55Z’ progress=0.999683 cache=33.3MiB(295136txo) 2019-01-25T21:58:52Z UpdateTip: new best=0000000000000000001dfdb76805898d368d3fbb3a099b8f447423c1880d2baa height=560022 version=0x20000000 log2_work=90.275599 tx=376385628 date=‘2019-01-25T08:26:09Z’ progress=0.999689 cache=33.8MiB(299776txo) 2019-01-25T21:59:16Z UpdateTip: new best=00000000000000000020da230946a85b561e1f5e9f04e4de2561e8ae53617b4a height=560023 version=0x20000000 log2_work=90.275623 tx=376387997 date=‘2019-01-25T08:30:18Z’ progress=0.999691 cache=34.2MiB(303449txo)

*** LND SYSTEMD STATUS *** ● lnd.service - LND Lightning Daemon Loaded: loaded (/etc/systemd/system/lnd.service; enabled; vendor preset: enabled) Active: active (running) since Fri 2019-01-25 21:31:18 GMT; 28min ago Main PID: 725 (lnd) CGroup: /system.slice/lnd.service └─725 /usr/local/bin/lnd --externalip=

Jan 25 21:31:19 RaspiBlitz lnd[725]: 2019-01-25 21:31:19.826 [INF] RPCS: password gRPC proxy started at [::]:8080 Jan 25 21:31:19 RaspiBlitz lnd[725]: 2019-01-25 21:31:19.831 [INF] LTND: Waiting for wallet encryption password. Use lncli create to creat… unlock it. Hint: Some lines were ellipsized, use -l to show in full.

*** LAST 20 LND LOGS *** – Logs begin at Fri 2019-01-25 21:31:06 GMT, end at Fri 2019-01-25 21:59:27 GMT. – Jan 25 21:31:18 RaspiBlitz systemd[1]: Started LND Lightning Daemon. Jan 25 21:31:19 RaspiBlitz lnd[725]: 2019-01-25 21:31:19.719 [INF] LTND: Version: 0.5.1-beta commit=, build=production, logging=default Jan 25 21:31:19 RaspiBlitz lnd[725]: 2019-01-25 21:31:19.720 [INF] LTND: Active chain: Bitcoin (network=mainnet) Jan 25 21:31:19 RaspiBlitz lnd[725]: 2019-01-25 21:31:19.750 [INF] CHDB: Checking for schema update: latest_version=7, db_version=7 Jan 25 21:31:19 RaspiBlitz lnd[725]: 2019-01-25 21:31:19.826 [INF] RPCS: password RPC server listening on [::]:10009 Jan 25 21:31:19 RaspiBlitz lnd[725]: 2019-01-25 21:31:19.826 [INF] RPCS: password gRPC proxy started at [::]:8080 Jan 25 21:31:19 RaspiBlitz lnd[725]: 2019-01-25 21:31:19.831 [INF] LTND: Waiting for wallet encryption password. Use lncli create to create a wallet, lncli unlock to unlock an existing wallet, or lncli changepassword to change the password of an existing wallet and unlock it.

  • RTL is OFF by config

Is there something false with the hdd not getting hocked up to the sd card? Or is there some conection problem to the internet, maybe coused by ipv6?

About this issue

  • Original URL
  • State: closed
  • Created 5 years ago
  • Comments: 64 (34 by maintainers)

Commits related to this issue

Most upvoted comments

After that error I ran manually the script 30initHDD.sh and now it is working ok, the torrent is downloading and seems to be working ok

I added more options to fix a corrupted blockchain for v1.0 release today. So can go to terminal and call either “/home/admin/50copyHDD.sh” to replace blockchain with fresh data from another computer by SCP or you can call “/home/admin/50torrentHDD.sh” to download a fresh prepared blockchain by torrent - once torrent is finished it will replace old data.

With taken these measures I think we are good to close this issue for the v1.0 release. If you have further problems, please open a fresh issue. Much thanks to all working thru this.

@theotherside I did the copy of the LND directory to a fresh raspiblitz once - worked. But cannot garantue that this is a fail safe way.

Making progress: needed to use sudo in line 78 and 94 of 70initLND.sh #244 (comment)

@rootzoll FYI he’s using Odroid/Dietpi in this case.

The idea was that during setup selections/data will be written in the SD card /home/admin/raspiblitz.info first (because HDD might not exist in the beginning) and at the end of the setup the final raspiblitz.conf gets written to the HDD. Maybe I have to rethink this idea.

Why the raspiblitz.conf is missing … I can see three scenarios I will check for:

  1. the raspiblitz.conf gets never created (somehow the line 23 never gets reached or fails)
  2. the raspiblitz.conf gets created but not on the HDD (some mounting prob)
  3. the raspiblitz.conf gets deleted (like bootstrap is messing up stuff)

You might also have to look at which scripts are depending on the existence of it (sourcing the values in it) before it exists, and maybe those values should be put/pulled from raspiblitz.info instead of the .conf file.

The idea was that during setup selections/data will be written in the SD card /home/admin/raspiblitz.info first (because HDD might not exist in the beginning) and at the end of the setup the final raspiblitz.conf gets written to the HDD. Maybe I have to rethink this idea.

Why the raspiblitz.conf is missing … I can see three scenarios I will check for:

  1. the raspiblitz.conf gets never created (somehow the line 23 never gets reached or fails)
  2. the raspiblitz.conf gets created but not on the HDD (some mounting prob)
  3. the raspiblitz.conf gets deleted (like bootstrap is messing up stuff)

I gave some scripts a quickfix, that they should be able handel situations where the raspiblitz.conf is missing. To test these use on the terminal: ./XXsyncScripts.sh dev -clean

Why the scripts run into this situation I have still to find out … in my test runs, this never happens.