For me it is the first time to hear of such a behaviour. Does the PowerBlock work fine afterwards or has it become just unreliable at all?
Maybe there was some sort of voltage transient that caused the malfunction of the PowerBlock IC.
Hello, we recently identified a bug in the ControlBlock driver. I am very sorry for that!
Your observations see to match the symptoms caused by that. We released an update yesterday and that should also fix your problems.
The power switch on the ControlBlock lead to a small voltage-drop at the switching component (as does every electronically component). From other projects I know that especially additional USB devices can be problematic. I guess that when you disconnect, one or both USB devices (SSD, converter) the under voltage disappears. Alternatively, you could get an active USB hub that powers the additional USB devices and keep the connection between the RPi and the USB devices.
@petrockblog It appears that I can get the service running by commenting out the line "[ -x "$DAEMON" ] || exit 0" and then starting the service. This also allows the service to run on boot.
So, why does this line need to be commented out? I'm confused why this would work for everyone else and not my setup (even though I started from a completely fresh RetroPi 4.5).
So, I have mounted the PowerBlock and I have tested it for some days. It works almost as expected, spordically it shows unexpected behaviour. I will create a separate thread explaining my observations.
Anyway, thanks for supplying me with a replacement device.
Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.