Rasplex 1.0.0 powering off with RemotePi Board 2015 does not complete

Hi,

Hardware: Raspberry Pi2 with RemotePi Board 2015, 1GB RAM
Software: 1.0.0

My problem with the new image is following: I have plugged the remotepi board (2015). I did use it already with the 0.7.1 and it run very stable. Since the update to 1.0.0 I have problems with shutting down the raspberry pi2. I press the power off button: What happens than is, the green LED turns to red and is blinking. This is the same behavior as before. But it does not power off then. It seems that something is waiting for something.
Then I ssh into rasplex and do execute shutdown -h now. Then the board powers down finally.

I want to provide log files, but I don’t see a upload option below.

Best regards,

Frank

Some more information,

up-to now I used the Logitech Harmony to power down all at one single press. So I didn’t saw what actually happened with the Pi2.

So I powered down the Pi2 only (via press button on remote control) and I see, that the Pi2 reboots instead of powering down. It is mentioning: Please reference crash id: 234

The power off happens at 13.40 (time).

Archiv.zip contains:

plexhometheater.old.log
11560ebd-bfb9-7618-3395ce31-0ae57aac-v-1.0.0.dmp (from the latest CrashReports directory).

Frank

Make sure you have you got the power lead plugged into the RemotePi Board and not the RPi itself, I once made that mistake after moving my RPi.

Regards

Hi,

thanks for the advice.

But I think I found a solution. I suspected already earlier, that with changing to 1.0.0 the enabling of the remotepi has to be redone in terms of changing scripts in the setup. Therefore I just disabled the support and immediately re-enabled it. The didn’t make the trick.

But: Disable the support -> restart the system -> re-enable the support and it works again.

Hope this is useful for other as well.

Frank

No reason why that should work, nothing has changed. I have three of these set up on various RPi’s (in addition to my Dev and test RPi’s), all continued working fine after updating via the auto-updater.

Glad you have it working again.

Regards