Posts by GDPR-7

    I guess it's a install on an Pi ?

    a raw answer would be:

    1. create a backup via LE config tool

    2. install on the new SD a fresh LE (and maybe configure keyboard, time/date, ssh/samba)

    3. install the addon's you had on the old sdcard [1]

    4. copy (not move) the backup from the old sdcard to the newer into the folder named /storage/backup

    5. restore the backup via LE config tool

    6. copy (not move) your media from the old sdcard to the new sdcard (same folder name(s))

    7. restart

    8. check your settings, media, etc.

    hint: "not move" is for backup reason: keep the elder sdcard intact until the newer is working as you expect !

    [1]

    I'm unsure here !

    I currently don't know if the addon's are included in the backup - I guess yes, but I'm unsure -

    Question for me is (if not):

    when no addons are installed at all and you restore the backup (included the config files for a addon) before you have the addon's itself installed I could imagine that the config files for that addon's (which came from the backup) getting overwritten or resetted with the default config files during installation.

    or somewhat shorter:

    when a addon is updated the config files for this addon remain unchanged !

    but what happen if I have only the config files from a addon, but the addon itself isn't installed.

    What happens now with the config file of the addon when I install it ?

    reset to defaults or user adjustments remain unchanged ?

    to be on a save(r) side I do step 3. before 5.

    maybe unnecessary at all ?!

    but you kept the elder sdcard intact, didn't you ? ;)

    1. are reboots in general problematic ?

    2. are your reboots always at the same time ?

    and if yes:

    3. What happens at that time ?

    I could think of a DSL internet router doing a reconnect within 24 h ... and your Pi is doing something needing a internet connection at that time and then crash, reboot, stuck at boot ...

    switch debug on, reboot and post the link to the log file after the nightly reboot occurred !

    see:

    https://wiki.libreelec.tv/support/log-files

    Intel NUC (Haswell based. Don't remember the NUC version)

    from your logfile:

    D54250WYK

    what happens if you connect the Nuc directly to the TV ?

    btw:

    your Bios is old too:

    old: BIOS WYLPT10H.86A.0028.2014.0814.1906 08/14/2014

    new: BIOS WYLPT10H.86A.0054.2019.0902.1752

    see:

    BIOS Update [WYLPT10H]
    Options for updating the BIOS of Intel® NUC Kit D54250WY and D34010WY, and Intel® NUC Board D54250WYB and D34010WYB.
    www.intel.com

    apart from CPU security fixes, there are some graphic related fixes too.

    where *I* don't exactly get where they what repair, e.g. Bios 41:

    cit.:

    "Updated Visual BIOS to version 2.2.17. Fixes include:

    o Refactored graphics resolution algorithm to find closest supported resolution to 1024x768. This should correct scaling issues with 4K monitors."

    Visual Bios GUI or GPU ???

    ... until 20 is stable

    running nightly over month now, *I* would declare it as "stable".

    I'm convinced that changes in nightly are tested by the developers/maintainers (kudo's ! ;) ) before a nightly even hit the download page.

    but not all addon's available, though ...

    btw.:

    you could sorta speed up "LE 20 becoming stable and released" by running nightly and report the bugs you maybe find.

    that's how communtity/open source software works: a OS for free in the exchange of the bugs you find

    And if you're doing so and think a bit of it more, you'll find out it's just a sort of "self help" !

    but I don't understand why

    see in this thread here my links in comment #4 and further, being in the linked thread, comment #7 and esp. #13

    alas, I couldn't find a Block Diagram, but I guess you also have a "LSPCon" between DSP and HDMI on your Nuc.

    if you also read this thread:

    HorzaSe
    January 11, 2022 at 2:44 PM

    you'll see all Nuc's there connected via HDMI (cable), but DSP is active, on a Nuc7, Nuc8 and Nuc11, so I guess the same goes for your Nuc10

    @Joe

    wow, this is a lot amount of information!

    Why is it all so complicated ;)

    well, my intention was that you learn something that you're able to help yourself next time.

    complicated ?

    well, for the first time(s) only, afterwards it becomes common.

    And this HD was the one which stucked from time to time (maybe some bad blocks!?)

    stuck:

    as said I own a 5 TB WD disk.

    compared to another 500 GB WD disk I see some stuckering (?) too during weekly backup via rsync.

    I haven't exactly figured out why, it could be that the compare the rsync does is somehow slower, but why ?...

    The disk speed is okay, as the the above dd commands showed.

    anyway, the main differences is that the smaller disk uses SMR and the bigger CMR

    https://www.reichelt.com/magazin/en/guide/smr-cmr-which-hard-drive-is-best-for-which-purpose/

    but the bigger one is able to do TRIM (a garbage ~remover~ of delete data) usually for SSD's.

    with the attached disk to the Pi:

    fstrim -va

    should TRIM your disk

    more to read:

    https://en.wikipedia.org/wiki/Trim_(computing)

    ===

    bad blocks ?

    if you find some on the disk: backup the disk, ASAP and go for another disk !

    to check the disk and with the external disk attached to the Pi:

    usually a

    smartctl -a /dev/sdX

    (adjust X with b ?)

    outputs what's up with bad blocks and other attributes (usually) the disk log's:

    consult:

    https://en.wikipedia.org/wiki/S.M.A.R.T.

    you could run self-tests on the disk to fresh up the attributes with

    smartctl -t short /dev/sdX

    or

    smartctl -t long /dev/sdX

    both commands will output when they're done.

    afterwards a smartctl -a ... should show the current attributes.

    btw.: the "-a" switch also shows - to get an idea - how long each self-test lasts:

    search for "recommended polling time:"

    be aware:

    the disk should be under power as long the self-test runs.

    means: sleep mode (suspend, hibernate) or power down shouldn't happen.

    background: some disk continues the self-test after sleep mode/power down, some do not, at least my 5TB WD disk does not

    ===

    As i mentioned, the mkfs.ext4 command led to a stuck of the formatting process with the message "creating journal" by 1 of my 3 HDs.

    So i had to format this HD with the external tool, which produced the 36GB.

    And this HD was the one which stucked from time to time (maybe some bad blocks!?)

    "creating journal" is normal with ext4 (journaling file system) and should last for a 5 TB max ~3 minutes.

    what was the "external tool" ?

    usually one uses the tools the OS, where the disk later does it's job, offers.

    you're better off with them

    a differences in space is common and should be minus ~7 %

    the cause is manufacturer calculate in powers of 10 and not of 2, so for a nominal 5 TB the real size is ~4656 GB only.

    calc:

    (5*10^9) / (5*2^30) =0,931

    Is there a way to fix this at all, is there a previous 'nightly' build that may fix the audio, without updating the database version?

    sorry, I've very little/none experiences with MySQL stuff

    and no, there are (currently) no elder nightlies, only the one from the last build (usually daily)

    a homebrewed kernel and the exchange in Matrix might be a way...

    but a howto and if it works: no idea !

    I have a NUC10 i3FNKN, running Libreelec 10.0.1

    was this nuc ever playing well with LE release or is it a newly gotten box ?

    if the last is true:

    I guess the kernel (5.10.x) in LE 10.x is too old or has no sufficing support for your NUC10

    try nightly

    Index of /

    - key in "gen" into the top box

    - download the *.tar

    - and place it in ~/.update on your nuc

    - reboot

    - reset BIOS to it's default

    you now should see HDMI options for audio...

    be aware:

    not all addon's are currently available for nightly