Problem with 01Feb24 emonCMS image with emonPi V1 and RaspberryPi3

Emoncms
1

Dear all,

I recently encountered a similar issue with my EmonPi, which I suspect was due to an SD card failure. After unplugging and restarting the device, it became stuck on the boot screen. I attempted to resolve this by installing the latest image (01Feb24) on a new 32GB SD card. However, this resulted in a continuous stream of “sysrq: HELP: …” messages, interspersed with occasional boot messages. Despite waiting for the check process to complete, the issue persisted and the EmonPi stayed in this status.

I then tried a different approach: I flashed the 10Nov22 image on the same new SD card. This image only required 16GB, so I created a temporary partition to allow for future data partition expansion. After inserting the card back into the EmonPi, it booted without any problems.

Encouraged by this success, I shut down the device and installed the 20Nov23 image on the same SD card, again creating a temporary partition. The EmonPi started up without any issues.

However, when I repeated the same process with the 01Feb24 image, the “sysrq: HELP: …” flood messages reappeared. Given that the SD card is new and functions correctly with previous images, and there are no apparent issues in the logs with those images, I suspect there might be a problem with the 01Feb24 image or when flashing the image (?).

FYI, I used BalenaEtcher 1.18.11 to flash the image.

2

Maybe @TrystanLea needs to look into this.

3

Hi. I am wondering whether there has been any resolution for this. I have just undertaken a similar processes - moving from an older emonsd image to the 01Feb24 image on a RPi3+. RPi boots fine without the emonpi board installed, but get continuous stream of “sysrq: HELP: …” messages, interspersed with occasional boot messages when booting with the board attached. Have flashed image twice, one with BalenaEtcher and also with Raspberry Pi Imager with the same result. Many thanks

4

I’ve heard or seen nothing relevant. @TrystanLea

1 Like
5

Apologies, found the issue and fix for this, it seems to only effect emonPi v1 with a RaspberryPi 3 B+ and not the emonPi2 for some reason.

After flashing the image, edit /boot/cmdline.txt and remove the first part "console=serial0,115200 "

console=serial0,115200 console=tty1 root=PARTUUID=567d5380-02 rootfstype=ext4 fsck.repair=yes rootwait sysrq=0

Replace with:

console=tty1 root=PARTUUID=567d5380-02 rootfstype=ext4 fsck.repair=yes rootwait

It will then boot fine.

6

I’ve added a note to the download page for now:

image
image773×208 29 KB

1 Like