Slow boot

  • Hello,


    I just migrated from OpenELEC 8.0.4 to LibreELEC 8.2.0 on my Wetek Core.


    I love the HDMI-CEC add-on and the fact that the Kodi version is always up-to-date.


    However, I noticed that the boot time is about 20-30 seconds longer than when on OpeneELEC. Is this normal?


    Thank you!

  • no idea


    post the output of the following commands

    Code
    1. journalctl -b 0 | pastebinit
    2. systemd-analyze blame | pastebinit
  • You have the "wait for network" option enabled which holds the boot for 10s. Other than that I don't see anything else out of the ordinary.

  • You have the "wait for network" option enabled which holds the boot for 10s. Other than that I don't see anything else out of the ordinary.

    Actually, "Wait for network" was disabled (in LibreELEC settings). I enabled it and now the first 2 lines of systemd-analyze blame are these:


    10.152s network-online.service

    10.139s kodi-waitonnetwork.service


    So, there's an extra 10s when "Wait for network" is enabled (kodi-waitonnetwork.service)


    When I disable the option, I get the output which I uploaded to pastebin, with 10s for network-online.service


    Time between LibreELEC boot and Kodi start is about 25 seconds

  • ah, Do you have some systemd service that mounts something? The examples depend on Requires=network-online.service which will pull in that dependency.


    So that could be it

  • Inaccessible mounts will trigger a timeout, I had that too. Offline servers, that sort of thing.

  • That's it then! I have an external USB drive with an EXT4 and a Journaled HFS+ partition.


    So it must be something related to external USB (specifically EXT4 and/or HFS+ partitions) that's causing the delay. I suspect the HFS+ partition.


    But, like I said, boot time was definitely faster on OE 8.0.4 with this same setup.


    Is there a way to dig deeper into this and see what exactly changed that triggers the extra delay?


    Thank you!

    ah, Do you have some systemd service that mounts something? The examples depend on Requires=network-online.service which will pull in that dependency.


    So that could be it

  • I just found this in dmesg output.


    LibreELEC runs from microSD on the Wetek Core. I am constantly having problems with Android on NAND. Could this be connected?


    [ [email protected]] EXT4-fs (mmcblk0p2): mounting with "discard" option, but the device does not support discard

    [ [email protected]] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)

    [ [email protected]] Connect Timeout

    [ [email protected]] Device Not Connected/Responding

    [ [email protected]] WARN::hc_xfer_timeout:2723: hc_xfer_timeout: timeout on channel 3

    [ [email protected]] WARN::hc_xfer_timeout:2725: start_hcchar_val 0x01188a00

    [ [email protected]] WARN::hc_xfer_timeout:2730: chn-3,ep1-IN:type:2,speed:2,len:4096,addr4


    I also see this error:


    [ [email protected]] [aml_sdio_timeout] time_start_cnt:999

    [ [email protected]] [aml_sdio_print_err] sdio: Timeout error, Cmd52 arg 0xc00, Xfer 0 Bytes, host->xfer_step=12, host->cmd_is_stop=0, pdata->port=0, virqs=0x13, virqc=0x3f001f00, conf->cmd_clk_divide=177, pdata->clkc=177, conf->bus_width=0, pdata->width=0, conf=0x416270b1, clock=397940

    [ [email protected]]

    [ [email protected]] [aml_sdio_timeout] time_start_cnt:999

    [ [email protected]] <4>[ [email protected]] sdio: queuing unknown CIS tuple 0x80 (2 bytes)

    [ [email protected]] sdio: queuing unknown CIS tuple 0x80 (3 bytes)

    [ [email protected]] sdio: queuing unknown CIS tuple 0x80 (3 bytes)

    [ [email protected]] sdio: queuing unknown CIS tuple 0x80 (7 bytes)

    [ [email protected]] sdio: new high speed SDIO card at address 0001, clock 35416666, 4-bit-bus-width

    [ [email protected]] [sdio_reinit] finish

  • Code
    1. systemctl list-dependencies --reverse network-online.service

    Thank you!


    Here is the output..


    network-online.service

    ● └─network-online.target

    ● ├─kodi.service

    ● ├─kodi.target

    ● └─kodi.target

  • No current dependencies, looks safe to disable it:

    Code
    1. systemctl disable network-online.service

    and reboot to test.

  • UPDATE:


    I started clean with a hard reset, set everything as usual, populated my library and startup time is now normal at about 23s


    Weirdly enough, network-online.service doesn't appear anymore under systemd-analyze


    I haven't installed a few add-ons that I had on my other install, so one of them might be the problem:


    - Youtube v5.4.5

    - nfowatchedstateupdater v1.1.12 (axbmcuser mod)

    - I/O benchmark

    - CPU benchmark


    I also noticed there were a lot of add-on script modules in the other install, probably installed by one of these add-ons. Also, the OpenELEC repository was still there after I migrated.


    So, the issue seems to be resolved, it's still weird though that I had normal boot times with this same setup on OpenELEC 8.0.2

  • No current dependencies, looks safe to disable it:

    Code
    1. systemctl disable network-online.service

    and reboot to test.

    Thank you! Made a clean install and the service doesn't show up anymore.