Posts by Pantalaimon

    I've been backing up my media disk to prevent data loss in case the disk is faulty. Then I repeated the steps to try to reproduce the described problem. Somehow the transfer was able to complete without issues this time.

    In my case it's not an USB drive but internal SATA (Seagate Barracuda XT), and I know the device node hadn't changed after the event.

    If this problem occurs again, I'll check the dmesg output.

    Thanks for your input.

    I've just updated to LibreElec 8.0.2 from 8.0.0 today, and suddenly ran into this problem:

    I transfer my media files through Samba to my LE setup, and today, when I tried to transfer a 5Gb media file, it just stops at approx. 10%, and after a minute it gives me an 'Access denied' error. Trying to remove the file gives me the same error.

    I logged into LE with SSH, and tried to remove the broken file from there. This gives me the following response:

    rm: can't remove 'xxx': Read-only file system

    I never made this change myself, my media share should always be writable... I rebooted, once again logged in with SSH and was then able to remove the file.

    Once again, I tried to copy the same file the same way I did before - and again it stopped, a little sooner than before. Same problem: disk becomes read-only, until I reboot again.

    I've checked the logs, but there are no error reports whatsoever to be found in there.

    Is there something in LibreElec that can trigger this, as a safety measure of some sorts? Could this be that my media disk is 93% full (of 3TB) ?

    I copied a few smaller files just before this, and those went without a problem.

    Apparently the AV receiver was at fault here. I gave up, ready to go to bed, and turned off the AV receiver first. Seconds later, Kodi suddenly appeared on my screen and all seemed well.
    This morning, trying to reproduce the problem, I first booted LE with AV receiver OFF - No errors. Then I booted LE with AV receiver ON again - Still no errors...

    I guess it somehow got messed up by my pet, whose sweet relaxing spot is right on top of the receiver when I'm not looking, and probably triggered something :dodgy:

    Thanks for the help anyways !

    I've used LibreElec for a couple of months now, and as of today, LibreElec won't start anymore.

    I left it on in screensaver mode, forgot to turn it off, and when I checked today the screen was black and couldn't wake it up. So I rebooted.
    Now, when it tries to boot into Kodi, I get the following error message:

    Code
    [FAILED] Failed to start Xorg Server.
    See 'systemctl status xorg.service' for details
    [DEPEND] Dependency failed for FluxBox Window Manager

    systemctl status xorg.service returns the following:

    Code
    Dec 30 02:08:30 HTPC xorg-launch[1185]: (EE)
    Dec 30 02:08:30 HTPC xorg-launch[1185]: Fatal server error:
    Dec 30 02:08:30 HTPC xorg-launch[1185]: (EE) no screens found(EE)
    Dec 30 02:08:30 HTPC xorg-launch[1185]: (EE)
    Dec 30 02:08:30 HTPC xorg-launch[1185]: Please consult the The X.Org Foundation support
    Dec 30 02:08:30 HTPC xorg-launch[1185]:          at http://wiki.x.org
    Dec 30 02:08:30 HTPC xorg-launch[1185]:  for help.
    Dec 30 02:08:30 HTPC xorg-launch[1185]: (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
    Dec 30 02:08:30 HTPC xorg-launch[1185]: (EE)
    Dec 30 02:08:30 HTPC xorg-launch[1185]: (EE) Server terminated with error (1). Closing log file.

    Log file reads:

    Apparently, it can't find any screens?
    I've tried reinstalling LibreElec, but the problem persists.

    How can this happen all of a sudden? I hope you guys can shed some light on this problem.