Posts by beredim

    Actually it was hardware problems (combined with my lack on experience on EXT4) that led me back to NTFS after a catastrophic loss of data that even PhotoRec couldn't save in the end. (about 8TB worth).

    So now I'm trying to move whatever else I have on EXT4, back to NTFS, so that I can more easily work with them on Windows in case of problems.

    In the end, after a lot of trial and error, I managed to create new NTFS partitions (using GParted) that mount fine both on LibreELEC and Windows 10.

    Something in my setup, causes Windows 10 created GPT/NTFS partitions to be problematic on linux.


    Again, thanks to everyone for their help.


    Regarding the actual fix/patch discussed earlier, as I said, I can't offer any advice because it would appear my problems originate elsewhere. Unless someone can verify the fix actually works (or at least doesn't introduce new issues) I would advice against merging it.

    Big thanks to everyone for their help.

    Unfortunately, it seems my problems may be different than what I thought.


    I tried both the builds provided, and also a Fedora 28 live CD.

    In all three I failed to mount my NTFS drives.

    So I can't really comment on the fix (maybe it works, maybe it doesn't, maybe it solves some problems and causes others), but it would seem something else is wrong with my NTFS drive.


    If anyone has any more pointers on how to research my problem I would appreciate it. What I have until now:

    - External enclosure with 4TB NTFS drive

    - Windows 10 Home fully updated

    - Fast boot is disabled, and powercfg /h is set to off

    - Windows 10 sees the drive perfectly well, chkdsk reports no errors

    - fdisk -l claims "The primary GPT table is corrupt, but the backup appears OK, so that will be used."

    - gdisk output

    Sorry for reviving this old thread, but it seems to me that:

    a. This problem still persists & I think I'm facing the same issue. NTFS disks without errors from fully updated Windows 10 system that fail to mount on LibreELEC

    b. Windows 7 installation base is constantly decreasing (and I do not have access to a Windows 7 system atm, only fully updated Windows 10 systems)
    c. There seems to be a bugfix available for this exact issue at Bug 1527231 – Linux cannot mount NTFS filesystem from Windows 10 creators update 1709

    If (c) indeed corresponds with the issue described, I'll be happy to test a build (if someone can port the fix).

    Intel has released a security advisory about a series of critical vulnerabilities that can lead to loading and executing code even outside the visibility of the operating system.

    Intel® Management Engine Critical Firmware Update (Intel SA-00086)
    Intel® Product Security Center


    Alongside the advisory they have also released a diagnostic tool that allows you to check your system:

    Download Intel-SA-00086 Detection Tool

    This also comes in a Linux flavor that appears to run in the LibreELEC shell.


    So check your systems, ask your manufacturer for BIOS updates if needed, and stay safe.

    *A number of Intel NUCs (a favorite for LibreELEC) appear to be vulnerable --> SA-00086 for Intel® NUC, Intel® Compute Stick and Intel® Compute Card

    with BIOS updates scheduled for December.

    Just wanted to shout out a giant

    THANK YOU to kszaq

    I just used this build to revive a crappy (Amlogic S805 based) OEM android box that I once purchased on a whim, and has effectively been gathering dust ever since (thanks to crappy chinese firmware, no Play store etc)


    I'll just write down here "Turbo-X Media Player Android Box" so that hopefully the google gods can help to bring more people to salvation.

    I haven't tested it extensively, but if I find any problems I'll get back to you.

    Now off to read the 28 pages of this thread, and to think about what to do with my newest (4th) member of my LibreELEC family...

    I've actually done it.

    WIll post the procedure when I find some time.


    Thank you both again.

    [edit]

    Ok here it is.
    1. Setup a ddns provider and an updater for it (through your router, another device on your LAN, a LibreELEC add-on etc, whatever works for you)
    2. Make sure your ISP allows you to use port 443 and forward it to the LibreELEC machine. Let's Encrypt requires port 443 to complete the challenge that generates the ssl certificates.*

    3. Download the linuxserver.io Nginx Letsencrypt docker image add-on (as suggested above). (I am not going to go into details about setting this up as it is out of scope for this thread).
    4. Once you have verified the the nginx letsencrypt container is running correctly you have to edit the default configuration file for nginx. This file is accessible over LibreELEC samba on the path below:


    Code
    1. Userdata\addon_data\docker.linuxserver.letsencrypt\config\nginx\site-confs\default

    Edit it to make it look like the following:

    Pay extra attention on the line where you define the IP:port for the transmission service. You have to use the LibreELEC LAN IP there. This means LibreELEC should have a static LAN IP, but you have probably set it up like this if you are forwarding ports to it.**

    5. Restart the nginx letencrypt container (either through the command line or restart LibreELEC)

    6. From inside your LAN, open a browser to https://192.168.1.21/transmission (use your own LibreELEC LAN IP of course). You should receive a bad certificate warning (this is expected as the certificate is signed for your ddns url), ignore it, enter your username/password and you should see the Transmission web interface. Test that everything works as expected (add a .torrent, remove it, etc)

    7. Now open a browser to https://myexample.ddns.com/transmission (use your own ddns url of course). There is a case that this URL will fail (if your router does not support NAT loopback, or maybe you haven't enabled it) , in that case you'll have to test it from outside your LAN. The browser should show the certificate is valid (green lock etc). Again make sure that everything works as expected.

    8. Setup your favorite transmission remote client to use SSL and verify everything works as expected. For example for Transmission Remote GUI:

    Code
    1. Remote host: myexample.ddns.com
    2. Port: 443
    3. Use SSL
    4. Authentication Required
    5. [username]
    6. [password]
    7. RPC path: /transmission/rpc


    * If your ISP does not allow you to use port 443, all is not lost. You can opt to use the simple Nginx docker image add-on with another port and self-signed certificates or maybe look about buying an SSL certificate.


    ** I tried using 127.0.0.1, but it wouldn't work. I was scratching my head as to why, until I realised that, from inside the docker container, 127.0.0.1 refers to the container itself (and not the LibreELEC host). There is probably some docker-ish way to get the host IP that the container interface sees and use that, and you'll probably have to find out how to do that if you want to setup something similar with the dockerized transmission add-on.

    Thanks to both of you.

    I have about 1500 torrents that I'll have to migrate if I change clients, so I guess I'll try the docker approach first.


    It's just that I haven't really used docker (especially not in LibreELEC) apart from some tutorials here and there in the past. But I feel I'll be able to do it.

    Maybe I'll write a post if I get it working.

    PS. I've setup dynamic dns through my ISP provided router (It supports some of the free services out there, like noip.com which I've chosen). Do I gain something by switching to a LibreELEC add-on for dynamic dns (like duck dns suggested above) ?

    I have a question about the transmission add-on.


    I have successfully used for quite some time now, and even forwarded the remote port so that I can access it from outside my LAN without trouble.


    However, I feel the simple unencrypted authentication is not enough, and I would like to use SSL.

    From a quick search I undestand that transmission itself doesn't offer SSL, and I would have to setup some kind of reverse proxy (possibly something light like nginx since I'm running LibreELEC on a Celeron NUC) or an SSH tunnel.


    1. Does this make sense?


    2. Has anyone done something like that on LibreELEC? Any pointers, tutorials, guides for it?

    I checked the BIOS on my NUC5CPYH and although there is a 'Configure' option for the LAN controller it only displays some non-diagnostic non-helpful info.

    I would suggest flashing (or reflashing) the latest BIOS (0062) and checking with a different cable
    (don't count on the fact that other devices using the same cable claim 1Gbps)
    If BIOS and/or another cable also fails to fix the issue do an RMA (don't bother to check on Windows).


    PS BIOS has an option to select the type of OS (Windows, Linux, etc) installed. Although this should only have to do with booting, you never know. Make sure 'Linux' is selected.