raspiblitz: Litecoind.service failure
I returned home to my Raspberry Pi with this error message on the screen. It has previously been working perfectly.
The EXT4-fs error pops up for a brief second at the bottom about every minute. I have not interacted with the Pi in over a day, so I’m assuming the only thing that may have caused the issue was a possible brief loss of power. Here’s the messages I get when I SSH into the device.


I’m assuming there was some sort of data corruption on the hard drive due possibly to a power loss. I’ll note that the drive is roughly 2 months old and was brand new for this project. Also, I believe this same issue occurred probably a month ago, but at the time I reformatted the drive and started everything from scratch.
Here are the error logs
*** RASPIBLITZ LOGS *** blitzversion: 0.99 chainnetwork: litecoin / main 14:51:28 up 19 min, 2 users, load average: 0.93, 0.93, 0.70
*** CHAINNETWORK SYSTEMD STATUS *** ● litecoind.service - Bitcoin daemon Loaded: loaded (/etc/systemd/system/litecoind.service; enabled; vendor preset: enabled) Active: activating (auto-restart) (Result: exit-code) since Sat 2019-01-26 14:51:19 GMT; 9s ago Process: 12678 ExecStart=/usr/local/bin/litecoind -daemon -conf=/home/bitcoin/.litecoin/litecoin.conf (code=exited, status=1/FAILURE) Main PID: 12678 (code=exited, status=1/FAILURE) CGroup: /system.slice/litecoind.service └─12363 /usr/local/bin/litecoind -daemon -conf=/home/bitcoin/.lite…nf
Jan 26 14:51:19 Hermes systemd[1]: litecoind.service: Failed with result ‘e…de’. Hint: Some lines were ellipsized, use -l to show in full.
*** LAST 20 CHAINNETWORK LOGS *** 2019-01-26 14:50:48 Using the ‘standard’ SHA256 implementation 2019-01-26 14:50:48 Default data directory /home/bitcoin/.litecoin 2019-01-26 14:50:48 Using data directory /mnt/hdd/litecoin 2019-01-26 14:50:48 Using config file /home/bitcoin/.litecoin/litecoin.conf 2019-01-26 14:50:48 Using at most 40 automatic connections (1024 file descriptors available) 2019-01-26 14:50:48 Using 16 MiB out of 32/2 requested for signature cache, able to store 524288 elements 2019-01-26 14:50:48 Using 16 MiB out of 32/2 requested for script execution cache, able to store 524288 elements 2019-01-26 14:50:48 Using 4 threads for script verification 2019-01-26 14:50:48 scheduler thread start 2019-01-26 14:50:48 HTTP: creating work queue of depth 16 2019-01-26 14:50:48 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. 2019-01-26 14:50:48 HTTP: starting 4 worker threads 2019-01-26 14:50:48 Cache configuration: 2019-01-26 14:50:48 * Using 12.5MiB for block index database 2019-01-26 14:50:48 * Using 8.0MiB for chain state database 2019-01-26 14:50:48 * Using 79.5MiB for in-memory UTXO set (plus up to 47.7MiB of unused mempool space) 2019-01-26 14:50:48 init message: Loading block index… 2019-01-26 14:50:48 Opening LevelDB in /mnt/hdd/litecoin/blocks/index 2019-01-26 14:50:49 Opened LevelDB successfully 2019-01-26 14:50:49 Using obfuscation key for /mnt/hdd/litecoin/blocks/index: 0000000000000000
*** LND SYSTEMD STATUS *** ● lnd.service - LND Lightning Daemon Loaded: loaded (/etc/systemd/system/lnd.service; enabled; vendor preset: enabled) Active: active (running) since Sat 2019-01-26 14:29:08 GMT; 22min ago Main PID: 605 (lnd) CGroup: /system.slice/lnd.service └─605 /usr/local/bin/lnd --externalip=172.90.117.120
Jan 26 14:29:10 Hermes lnd[605]: 2019-01-26 14:29:10.262 [INF] RPCS: passwo…8080 Jan 26 14:29:10 Hermes lnd[605]: 2019-01-26 14:29:10.263 [INF] LTND: Waitin… it. Hint: Some lines were ellipsized, use -l to show in full.
*** LAST 20 LND LOGS ***
– Logs begin at Thu 2016-11-03 17:16:43 GMT, end at Sat 2019-01-26 14:51:29 GMT. –
Jan 26 14:29:08 Hermes systemd[1]: Started LND Lightning Daemon.
Jan 26 14:29:10 Hermes lnd[605]: 2019-01-26 14:29:10.111 [INF] LTND: Version: 0.5.1-beta commit=, build=production, logging=default
Jan 26 14:29:10 Hermes lnd[605]: 2019-01-26 14:29:10.111 [INF] LTND: Active chain: Litecoin (network=mainnet)
Jan 26 14:29:10 Hermes lnd[605]: 2019-01-26 14:29:10.250 [INF] CHDB: Checking for schema update: latest_version=7, db_version=7
Jan 26 14:29:10 Hermes lnd[605]: 2019-01-26 14:29:10.262 [INF] RPCS: password RPC server listening on [::]:10009
Jan 26 14:29:10 Hermes lnd[605]: 2019-01-26 14:29:10.262 [INF] RPCS: password gRPC proxy started at [::]:8080
Jan 26 14:29:10 Hermes lnd[605]: 2019-01-26 14:29:10.263 [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
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Comments: 19 (6 by maintainers)
It’s been a few hours and progress is actually displaying on screen now. It must have just needed some time. I’ll update when it appears to have finished.
It’s the Toshiba HDTB410XK3AA Canvio Basics 1TB Portable External suggested in the current US shopping list.
I’ll work on this later today and post results.
What kind of drive is this, a normal HDD? Search for how to use the
fsck
command to test and fix HDD corruption problems. You’ll have to stop the bitcoind and lnd services and unmount sda1 to run fsck.