Posts by soyxan

    milhouse I will wait for the USB booting then. I was wondering if I can use the following method (I guess it should be faster):

    1. Download RPi4 image and manually upgrade my RPi3 with it (update folder).
    2. After rebooting my RPi3 should show the rainbow screen (firmware not right)
    3. Activate USB boot on my RPi4 (when available)
    4. Plug in my USB HDD in the RPi4 and cross fingers

    What do you think?

    I have ordered a RPi4. In the meantime I want to prepare for the upgrade.

    Right now I am using LibreELEC 9.0.2 (RPi2.arm) on my RPi3. Only official addons and one docker image (domoticz).

    The only thing that is not usual is that I am not using SD at all, the boot process is done entirely from my USB HDD (program_usb_boot_mode=1).

    Please can you suggest the steps for migration once my RPi4 arrives?


    After you create domoticz container do you run it from console to initialize it? Because I can run it just fine.

    docker start domoticz
    # look if completely started with
    docker logs domoticz

    Yes, after creating the container I run for the first time with "docker start domoticz".

    Later, anytime I run from the console with "docker start domoticz" it works perfectly, that is why I do not know why is not working as a service.

    When creating docker try without --restart unless-stopped.

    I have created the docker container removing that parameter but nothing changes.

    It seems that domoticz is started but then somehow it exits/gets killed.

    If I run the command "systemct start domoticz.service" and just after that I run "systemctl status domoticz" I get the following:

    ● domoticz.service - Domoticz Container
    Loaded: loaded (/storage/.config/system.d/domoticz.service; enabled; vendor preset: disabled)
    Active: active (running) since Wed 2019-05-22 10:24:01 CEST; 1s ago
    Process: 1998 ExecStop=/storage/.kodi/addons/service.system.docker/bin/docker stop domoticz (code=exited, status=0/SUCCESS)
    Main PID: 2274 (docker)
    Memory: 5.2M
    CGroup: /system.slice/domoticz.service
    └─2274 /storage/.kodi/addons/service.system.docker/bin/docker start domoticz
    May 22 10:24:01 kodi systemd[1]: Started Domoticz Container.

    Just after that one I run the same command and I get:

    And if I run the same command again:

    ● domoticz.service - Domoticz Container
    Loaded: loaded (/storage/.config/system.d/domoticz.service; enabled; vendor preset: disabled)
    Active: inactive (dead) since Wed 2019-05-22 10:25:09 CEST; 2s ago
    Process: 2889 ExecStop=/storage/.kodi/addons/service.system.docker/bin/docker stop domoticz (code=exited, status=0/SUCCESS)
    Process: 2716 ExecStart=/storage/.kodi/addons/service.system.docker/bin/docker start domoticz (code=exited, status=0/SUCCESS)
    Main PID: 2716 (code=exited, status=0/SUCCESS)
    May 22 10:25:06 kodi systemd[1]: Started Domoticz Container.
    May 22 10:25:07 kodi docker[2716]: domoticz
    May 22 10:25:09 kodi docker[2889]: domoticz

    And domoticz container is not running ("docker ps -a"):

    CONTAINER ID        IMAGE                  COMMAND             CREATED             STATUS                     PORTS               NAMES
    c7cf291ef6b6        linuxserver/domoticz   "/init"             15 minutes ago      Exited (0) 5 minutes ago                       domoticz

    What can I do?


    Hello I am trying to run domoticz on boot as a docker container, so I have the following "domoticz.service" file in /storage/.config/system.d

    After a reboot the domoticz container starts (I can see it running from "docker ps" command), but after some seconds it suddenly stops. If I enable the parameter "Restart" to "Allways" the docker container keeps starting and stopping in a loop.

    If I check the container logs with the command "docker logs domoticz", I get the following:

    If I run the ExecStart command manually it works perfectly. What is wrong?


    Deleting the Database Addons27.db solved the issue.

    After the reboot I have checked that all my add-ons are now disabled, just enabling them will be enough?

    What are other consequences of deleting this file? Do I need to do anything else in order to get my add-ons work properly?

    I am not using a SD card at all, not even for the boot. Both storage and boot are stored on an USB hard disk drive.

    I am also considering a database corruption (as the Clean Video Library command got frozen and a reboot was needed). Can I just delete the Video database and force a rebuild? If so, which files do I need to remove from the database folder? Do I need to do anything else?

    If the above does not work, is it possible to do a fresh install maintaining my video and music files? And maintaining my add-ons settings?



    I am planning to use the option on the RPi3 to boot directly from an external 2.5" USB HDD (no SD at all) and I am wondering if it is possible to prepare the HDD just using the LE USB-SD creator utility.

    What I am planning to do is:

    1. Activate the bit (program_usb_boot_mode=1) with a bootable SD
    2. Prepare the HDD with the USB-SD creator utility
    3. change config.txt to point to sda on boot

    I am right? Do I need to do anyhing else?