Hi, I have 2 units that both had the problem “Raspberry Pi Booting…” pls see the screen shots to explain all of the services that are not started. Could someone point me to a post that will help me get started. Note I decided not to rescue old install and I downloaded the 2022 image and trying to start from scratch.
I assume these Pi’s have been up and running fine for a while?
And now when you reboot/restart them you are getting those errors during the boot process?
If so, it’s probably a worn out SD card. I suggest you buy a new, decent quality SD card, image it with a fresh copy of EmonSD, then (hopefully) import the data from the old card (using a SD card to USB adapter). It works like a charm, all old settings and data are pulled into the new install.
The other possibility is a poor/failing power supply, replace them with a decent quality item, the official Pi PSU’s are best and pretty cheap.
Hi Lee
The history here is that both units were working until last year when I noticed that they were showing “Raspberry Pi Booting” on their screens and I was unable to login. I tried a few things to fix with no luck.
So I decided to buy 2 new SD cards, download the latest image and reprogram the units from scratch with all the latest features.
I have just tried another power supply on each unit - no change. FYI I have tested power supply with a scope and they are good.
I am not trying to import any old settings. It appears to me that there is something stopping the first 4 services from starting. It seems unlikely that both hardware units have the same fault. Is it possible that my hardware is not compatible with the latest image ?? FYI with an SSH login I am able to get to the prompt and login in but the screen on the unit still says “Raspberry Pi Booting…”
Regards John
This information may also help
Emonhub config
#######################################################################
####################### emonhub.conf #########################
#######################################################################
### emonHub configuration file, for info see documentation:
### https://github.com/openenergymonitor/emonhub/blob/emon-pi/configuration.md
#######################################################################
####################### emonHub settings #######################
#######################################################################
[hub]
### loglevel must be one of DEBUG, INFO, WARNING, ERROR, and CRITICAL
loglevel = DEBUG
autoconf = 1
### Uncomment this to also send to syslog
# use_syslog = yes
#######################################################################
####################### Interfacers #######################
#######################################################################
[interfacers]
### This interfacer manages the RFM12Pi/RFM69Pi/emonPi module
[[EmonPi2]]
Type = EmonHubOEMInterfacer
[[[init_settings]]]
com_port = /dev/ttyAMA0
com_baud = 38400
[[[runtimesettings]]]
pubchannels = ToEmonCMS,
subchannels = ToRFM12,
[[USB0]]
Type = EmonHubOEMInterfacer
[[[init_settings]]]
com_port = /dev/ttyUSB0
com_baud = 115200
[[[runtimesettings]]]
pubchannels = ToEmonCMS,
subchannels = ToRFM12,
nodename = emonTx4
[[SPI]]
Type = EmonHubRFM69LPLInterfacer
[[[init_settings]]]
nodeid = 5
networkID = 210
[[[runtimesettings]]]
pubchannels = ToEmonCMS,
[[MQTT]]
Type = EmonHubMqttInterfacer
[[[init_settings]]]
mqtt_host = 127.0.0.1
mqtt_port = 1883
mqtt_user = emonpi
mqtt_passwd = emonpimqtt2016
[[[runtimesettings]]]
pubchannels = ToRFM12,
subchannels = ToEmonCMS,
# emonhub/rx/10/values format
# Use with emoncms Nodes module
node_format_enable = 0
node_format_basetopic = emonhub/
# emon/emontx/power1 format - use with Emoncms MQTT input
# http://github.com/emoncms/emoncms/blob/master/docs/RaspberryPi/MQTT.md
nodevar_format_enable = 1
nodevar_format_basetopic = emon/
# Single JSON payload published - use with Emoncms MQTT
node_JSON_enable = 0
node_JSON_basetopic = emon/
[[emoncmsorg]]
Type = EmonHubEmoncmsHTTPInterfacer
[[[init_settings]]]
[[[runtimesettings]]]
pubchannels = ToRFM12,
subchannels = ToEmonCMS,
url = https://emoncms.org
apikey = xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
senddata = 1 # Enable sending data to Emoncms.org
sendnames = 1 # Send full input names (compression will be automatically enabled)
interval = 30 # Bulk send interval to Emoncms.org in seconds
#######################################################################
####################### Nodes #######################
#######################################################################
## See config user guide: https://github.com/openenergymonitor/emonhub
## If autoconf is enabled above, node configuration will automatically
## populate based on templates listed in available.conf
[nodes]
Regards John
[Edited for presentation - Moderator (RW)]
Hi John,
Have you tried the advice in the box -
I ask as there’s a sporting chance that it may fail if the SD card has gone into failed/self-defense/read-only mode.
Looking at the slightly fuzzy boot screen, it looks like most of the errors are the PiLCD service erroring, do you have an official EmonPi with the LCD screen?
The other messages seems to be EmonHub failing to start (I think), that’s a problem. Is new data appearing in the graphs?
Hi Lee
Yes I have tried the 2 lines of code suggested - no joy.
Both Pi units were purchased from the store. In 2015 and 2016 I think
Also when the units boot up 1 says emonpi V2.81 and the second says V2.84
Also here is a better screen shot of the faults
Hi Lee
The Raspberry Pis were both purchased from the OpenEnergy store with software installed back around 2015 I think.
Yes I have tried the commands suggested – no joy
But, John says:
There’s always the chance the two new cards are not good.
But the odds on that seem to suggest other issues are at play here.
Given the age of both emonPis, opening them, reseating the daughtercard
on the GPIO connector and inspecting the boards for cold solder joints
wouldn’t be a bad idea.
Hi Bill thanks for suggestions
Ihave taken both apart and checked for dry joints etc… - All good I believe
Just tried a 3rd card - same result
Thanks
More Information
Is it possible that my hardware will not run this latest Image ??
On the pc board it says emonPi v1.6 Jun2015.
Is there some code that needs to be run to transition this board to run the latest Image ??
I have found a 24Jul2020 image and it appears to work
When you say no joy, what exactly happens when you type those commands?
Prior to the notice in the last day or few about the ‘new’ emonPi, which is on the way (AVR-DB: emonTx V4, new hardware in progress - #298 by TrystanLea), V1.6 was the latest version. It also depends on the Raspberry Pi itself, as far as I know, every version after 2B works, I’m not sure of anything before this.
How are you writing the image to the card? Problems have been reported with Raspberry Pi Imager. (Login Problems - #17 by RichardOwen)
Does the checksum on the download match?
(Long shots, I know)
Unlikely, I don’t have an EmonPi, I have an RFM69Pi which is an older but similar idea without the screen attached to a Pi2. It’s running the latest image EmonCMS/EmonSD image with lots of further updates pulled from GitHub.
Hi Lee
When I put the commands in they were accepted without error but nothing had appeared to change
John
Hi Robert
I was more focused on the Raspberry Pi imager verifying the image on the SD card.
The results are below
I:\EmonPi>certutil -hashfile emonSD-10Nov22_16gb.zip MD5
MD5 hash of emonSD-10Nov22_16gb.zip:
271d8d502e822e3703500a5762519c1d
CertUtil: -hashfile command completed successfully.
I:\EmonPi\emonSD-10Nov22_16gb>certutil -hashfile emonsd-10nov22_16gb.img MD5
MD5 hash of emonsd-10nov22_16gb.img:
f5d7963ffa585231210a5b4f560fc39e
CertUtil: -hashfile command completed successfully.
Which means that this is likely the problem. I have redone the download from 3 different browsers and gotten the same result.
Is there another server I can get a download from ?? I also put the checksum for the .img file as well.
John
Hi Robert
Imeant to say that I did download the 21Jul21 file and the checksum is correct .
As well as this I checked the system and this time the emonhub service will start but the following services did not and will not start
emoncms_mqtt
feedwriter
service-runner
redis-server
emonPiLCD
This could be the issue. Earlier this year there were some problems getting the image to work on a PiZero. I think @TrystanLea and @borpin made some changes to the scripts that create the image to make it work. So the scripts now work but the image which was created with the scripts with the problem might not have been updated. At the time, there was a suggestion that a note be attached to the image information about possible incompatibility. Don’t know if this was ever done.
Given the 2020 image works, is it possible to do an update from that to get to the latest version? I don’t know the answer to that and can’t check. @TrystanLea @borpin is this possible?
Simon
Hi Lee, Robert & Simon
Even thou the checksum was wrong for the EmonSD_10Nov22_16db.zip file I decided to take Robert’s suggestion and use another Imager ->Etcher Tool.
The rewsult was that everything works perfectly. Whilst I haven’t programmed all the feeds yet it seemlessly did a full update and all services are Green.
Thankyou everybody for your help.
John
[RPi Imager settings used were]
allow SSH
Username & Password
Configure wireless LAN
Local settings Australia - keyboard US [locale settings?]
(Moderator - RW)
Hi John,
Good news that’s it’s working. I’m slightly concerned the checksum of the iso was wrong though.
I’ve just downloaded it again, and md5sum’ed it and you are indeed correct.
The published checksum is -
(.zip) MD5: d4d27fcc553996768366662709307dda
The newly computed checksum is -
lee@workstation:~/Downloads$ md5sum emonSD-10Nov22_16gb.zip
271d8d502e822e3703500a5762519c1d emonSD-10Nov22_16gb.zip
Is the website just out of date (which may confuse newcomers), or more worryingly is a supply chain attack in progress?
Can @TrystanLea have a look please?
