raspiblitz: Stuck at "i2c /dev entries driver"

My raspiblitz is refusing to boot up after working perfectly for two months. I tried to reinstall a new copy on a NEW SD card and still having the same issue. It was able to only connect to the network via ethernet at theinitial install process but then when it rebooted it just hangs and does nothing. No network. No SSH. Nothing.

This is a log from the 1st install before it shuts down and never boot up again:

OK - a restart is needed: sudo shutdown -r now
Provisioning UPS - not active
Provisioning LNbits - keep default
Provisioning JoinMarket - keep default
Provisioning Specter - keep default
Provisioning Faraday - keep default
Provisioning Balance of Satoshis - keep default
Provisioning ThunderHub - keep default
Provisioning letsencrypt - keep default
Provisioning kindle-display - keep default
Provisioning Stacking Sats Kraken - keep default
Running the custom install script ..
'/mnt/hdd/app-data/custom-installs.sh' -> '/home/admin/custom-install.sh'
There are no custom user installs so far.
Done

*** Replay backup of LND conf/tls
*** Repair Bitcioin Conf (if needed)
Aligning lnd.conf & bitcoin.conf
Not setting local network hostname
Prepare fstab for permanent data drive mounting ..
datadisk --> sda
DONE - Give raspi some cool off time after hard building .... 5 secs sleep
END Provisioning
rebooting
shutdown in 1min

Broadcast message from root@raspberrypi (Sun 2020-10-04 01:06:05 BST):

The system is going down for reboot at Sun 2020-10-04 01:07:05 BST!

Now it just powers up and shows “i2c /dev entries driver” as a last message on the HDMI screen.

Tried:

new SD card
reinstall raspiblitz
connect HDD to USB2 instead of USB3
installed default Raspberry Pi OS (works perfectly)

About this issue

Original URL
State: closed
Created 4 years ago
Comments: 52 (13 by maintainers)

Most upvoted comments

So far zero such issues. Zero issues at all, in fact. Outside of the usual blockchain download wait, it took plenty of time to type and/or paste commands, but it’s been up and running solidly.

But yes, definitely will stay in thread with any related such thing.

On Tue, Oct 27, 2020 at 5:34 AM ChuckNorrison notifications@github.com wrote:

@argentoblitz https://github.com/argentoblitz Can you please keep this updated if your bolt is running over time? Maybe the RaspiBolt will show you this issue too. Would be very helpful to know. Good Luck.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/rootzoll/raspiblitz/issues/1618#issuecomment-717077716, or unsubscribe https://github.com/notifications/unsubscribe-auth/ARMZBTTKCIRIVOZHRK2K5SDSM2AZNANCNFSM4SDSMKOA .

argentoblitz on Oct 27, 2020

For the ext4 HDD is switched to the fstab options (including nofail) recommended by RaspiBolt guide for a lucky chance that this will ease some pain with the Control-D … but to be tested. Will merge PR #1761

TODO: Retest fresh install with HDD and then push this issue to v1.7 for next iteration.

rootzoll on Nov 11, 2020

No issues after all the tweaks above and updating to 1.6.1. Several reboots and install/uninstall RTL, lnbits successful. Even lnd 0.11 is running fine.

Maybe we could add some advice on using USB 2.0 and free up all available USB ports. Further disable unused connections in config.txt could free up some power consumption.

updated mine to 1.6.1 and wiped the entire drive for a fresh install. Blockchain progress is at 87% will update once it’s done and stable!

amir0ff on Nov 4, 2020

No issues after all the tweaks above and updating to 1.6.1. Several reboots and install/uninstall RTL, lnbits successful. Even lnd 0.11 is running fine.

Maybe we could add some advice on using USB 2.0 and free up all available USB ports. Further disable unused connections in config.txt could free up some power consumption.

ChuckNorrison on Nov 3, 2020

@ChuckNorrison My Blitzes work fine … but I can see the “control-d” things gets pretty anoying for some people. I will try to put higher priority on booting from SSD feature 1235 - moving away from booting from sd card.

rootzoll on Oct 26, 2020

Hi, it boots now with 1.6.1. Sorry for the trouble guys, I forgot to copy the hdmi file into the boot section of the sd card. I run a raspberry pi 4 without lcd.

michaelWuensch on Oct 17, 2020

I did it 👍

you need to edit your /etc/fstab and add nofail to your usb hdd options

this results in a boot without Control-D. Its currently in the Upgrade/Recover/Provision mode. ssh is refused

ChuckNorrison on Oct 15, 2020

@ChuckNorrison the UAS / UASP issue with RPi4-s have been discussed extensively. Check the issues labeled hardware : https://github.com/rootzoll/raspiblitz/issues?q=is%3Aissue+label%3Ahardware : https://github.com/rootzoll/raspiblitz/issues/708#issuecomment-518850854 https://github.com/rootzoll/raspiblitz/issues/691#issuecomment-520526004

openoms on Oct 15, 2020

This should not be closed, this is essential to build this blitz up properly. So maybe the docs needs to get changed if SSD is not affected or we can get deeper into the USB3.0 HDD Limitations of a PI 4

I understand we got a power supply issue on the Pi in some circumstances, maybe only while booting?

ChuckNorrison on Oct 14, 2020

/home/admin/config.scripts/blitz.touchscreen.sh: line 129: /mnt/hdd/raspiblitz.conf: Input/output error sed: can’t read /mnt/hdd/raspiblitz.conf: Input/output error

This does not look good. You seem to have I/O errors on your HDD. I would call (if possible) repair and run BACKUP-LND to download the rescue-file to your laptop - so that you have your LND funds+channels safe. After that your RaspiBlitz will turn off. Make sure that rescue-file is a TAR file you can unzip on your laptop and also contains the channel.backup file.

Then you can give the HDD another chance by fresh formatting it on another computer and then start with a fresh sd card - setting up a complete fresh RaspiBlitz (with resyncing the blochchain) and the choose “OLD” LND wallet and reupload that the rescuefile.

rootzoll on Oct 6, 2020