a stop job is running for LSB: ControlBlockService init script

petrockblog

You need to mount the SD card from another PC and edit the file form there, unfortunately.

Derekboy2000

@petrockblog said in a stop job is running for LSB: ControlBlockService init script:

You need to mount the SD card from another PC and edit the file form there, unfortunately.

euhm. but how? i cant find the file in /etc (on my pc)
i accidently installed it after updating Retropie..

or is it possible to delete controlblock while the sd is inserted in a pc. or ignore it during boot so i can manually uinstall it in Retropie?

mitu

@derekboy2000 You need a Linux installation to read the 2nd partition on the sdcard. Try booting in 'safe -mode' your RPI system to remove the ControlBlock service (https://raspberrypi.stackexchange.com/questions/61638/how-do-i-start-up-in-safemode).
While in safe-mode, remove the /etc/init.d/controlblockservice file and reboot into normal mode.

jonnykesh

@mitu This seems to be happening more and more. Why the hell are people installing drivers for hardware they don't have?
I wonder if there is any way we can get a warning / confirmation screen added before this is installed.

Derekboy2000

@mitu said in a stop job is running for LSB: ControlBlockService init script:

@derekboy2000 You need a Linux installation to read the 2nd partition on the sdcard. Try booting in 'safe -mode' your RPI system to remove the ControlBlock service (https://raspberrypi.stackexchange.com/questions/61638/how-do-i-start-up-in-safemode).
While in safe-mode, remove the /etc/init.d/controlblockservice file and reboot into normal mode.

thank you I'll try

edit:
I just ignores it, and keeps shutting off.
(got to go to Christmas dinner so I can't try anything else)

@jonnykesh said in a stop job is running for LSB: ControlBlockService init script:

@mitu This seems to be happening more and more. Why the hell are people installing drivers for hardware they don't have?
I wonder if there is any way we can get a warning / confirmation screen added before this is installed.

To be honest I don't even know how I installed it. I just updated RetroPie since it was a while ago the last time I updated everything. and during the reboot I noticed CB was installed.

I think it's a better idea to disable this function so you have to manually activate the option.

BuZz

Before the driver had to be "Enabled" from RetroPie-Setup. @petrockblog submitted a PR to enable this by default which I included with some changes. However the driver itself causes a reboot if you don't have the controlblock installed I think. A check in the service to see if the hardware is present would be best I guess, but we could switch back to the old functionality perhaps - what do you think @petrockblog ?

petrockblog

I have just created a pull request that makes that the service is not enabled with the installation anymore (https://github.com/RetroPie/RetroPie-Setup/pull/2240). I could have though about that before, sorry!

petrockblog

BTW: I hope all of you had nice a Christmas vacation!

Derekboy2000

@petrockblog
@mitu

I managed to acces the Controlblock service file(I installed raspbian on another SD card..).
Is there a way to edit the file so it will ignore the "shutdown/exit" command or even change it in something else.
I found this line:

//# Exit if the package is not installed
[ -x "$DAEMON" || exit 0]

Editing software isn't really my thing. but euhm..

mitu

@derekboy2000 You can just remove the file altogether, then remove the driver from RetroPie setup once the system starts up again.

Derekboy2000

@mitu said in a stop job is running for LSB: ControlBlockService init script:

@derekboy2000 You can just remove the file altogether, then remove the driver from RetroPie setup once the system starts up again.

negative. I can't delete it: "the file operation was completed with errors" that's why I'm asking how to edit it

mitu

@derekboy2000 You need to be root in order to be able to delete it. If you say you're able to edit it, just replace the line you referenced with

exit 0

and the script should exit without trying anything else.