Posts by bpr323

    SCENARIO:
    - On my current setup, the boot LibreElec 11 drive is a USB stick with limited 1Gb space.
    - The downloaded files are stored in /storage/downloads/on the boot USB drive, however I also have SSD drives attached to the motherboard, which are all automatically mounted to /media/ssd1 ...ssd2 at boot time.

    QUESTION 1:
    Is there a way to map this system folder to an external drive i.e.
    /storage/downloads/ >> symlink >>/media/ssd-x/)
    OR
    should I change the docker volume setup i.e.
    --volume=/media/ssd-x:/var/lib/transmission-daemon/downloads \ ?

    QUESTION 2:
    The PC with LibreElec boots from the USB and works fine, with USB persistence out of the box.
    Does this mean the "whole system" is loaded to, and runs from RAM after boot?

    Thank you!

    I want to clone my existing LE 10.02 setup for a friend - including all plugins, docker containers, etc. - i.e. exact carbon copy.

    I can create a disk image with gnome Disks on my main PC, but the image size will be 500Gb and the target NVME is only 256Gb

    I suspect Clonezilla will do the same, size wise, so:

    Q1 - what's the best way to transfer my system files to a new SSD especially of a smaller size?

    Q2 - what would be a terminal command to delete all logs, or alternatively just unwanted history logs with my personal data?

    Thanks!

    Problem solved - symlinks don't solve the 7.7GiB problem on LE, ... Buuut

    I'm actually using Krusader in a docker container on LE - and I get transfer rates up to 500Mb/s between my "downloads" folder and across external USB drives. For any file transfers outside LE server (e.g. from LE to my laptop) I use SMB

    All I had to do was to restart Krusader container and the new USB drive magically turned from 7.7Gib to 1Tb !!!

    thanks to this line -v /media:/media:rw \

    Docker Hub

    docker run -d --name=krusader \

    -p 5800:5800 \

    -p 5900:5900 \

    -v /storage/docker/krusader:/config:rw \

    -v /media:/media:rw \

    -v /storage/downloads:/storage/downloads:rw \

    -v /storage/docker:/storage/docker:rw \

    -e UMASK=000 \

    -e USER_ID=0 \

    -e GROUP_ID=0 \

    djaydev/krusader:latest

    Browse to http://your-host-ip:5800 to access the Krusader GUI.

    On LE, the /media folder is limited in size to 7.7Gib only

    I have four 2TB ext4 connected to my LE server and a few months back I managed to overcome this limitation by creating symlinks to each of the USB's in the /media folder

    But I foolishly didn't write down the exact ln -s command and when I plug in a new 1Tb USB drive it's limited to 7.7Gb

    In other words, LE mounts the USB drive into /media but its size is limited to 7.7Gib

    Other USB drives correctly open my "old" symlinks as full size 1.8Tb directrories.

    Could someone please help me with the right code syntax?

    I try

    $ ln -s /dev/sdf1 "/hp-music" and $ lsln -sT /dev/sdf1 "hp-music"

    but it still opens the 7.7GIB directory in /media

    I haven't found related errors at your log. We already had users, who suffered low speed on external devices. Often a better cable was the answer. If you already tested the cable, then advancedsettings.xml is worth to play with. Especially have a look at chapter 2.8.4 Cache.

    I fail to see how your response (looking at Kodi log) is related to slow copy speeds when Kodi is not even turned on??

    "a better cable was the answer" ?? Have you even read my post above regarding attaching the same SSD+enclosure+cable to a different device (MX Linux laptop) and getting speeds >300 mb/s ?? You've got to be joking, right?

    Hi Flex, thanks for replying!

    Here's the Kodi debug log attached.

    I doubt its a Kodi issue, rather a Linux programming error which you cannot see from the Kodi log.

    The most common are "large audio sync error", where Kodi doesn't get enough data bandwidth from the media source.

    Possibly, the clue for the underlying root cause is provided in the log here:

    [301] 2020-07-01 19:29:26.313 T:139930189871232 DEBUG: DBus method call to org.freedesktop.DBus.Peer.Ping at /org/freedesktop/UDisks2 of org.freedesktop.UDisks2 failed: org.freedesktop.DBus.Error.ServiceUnknown - The name org.freedesktop.UDisks2 was not provided by any .service files

    [302] 2020-07-01 19:29:26.314 T:139930189871232 DEBUG: DBus method call to org.freedesktop.UDisks.EnumerateDevices at /org/freedesktop/UDisks of org.freedesktop.UDisks failed: org.freedesktop.DBus.Error.ServiceUnknown - The name org.freedesktop.UDisks was not provided by any .service files

    2020-07-01 19:29:26.314 T:139930189871232 DEBUG: Selected UDev as storage provider

    UPDATE - I have 4 SSD's (1Tb 860 Evo) connected to external USB 3.1 Gen2 (USB-C Thunderbolt) ports on Lenovo, and 1 SSD (SSD-5) connected internally to SATA-III interface on the motherboard.

    If I copy/cut/paste large 10Gb file across different folders on the same internal disk (SSD-5) it goes flawlessly. But if I move same 10Gb file to one of the attached USB disks, or from one USB disks to another - that's when the first time file copy works fine, but on a second attempt the file copy slows down and grinds to a halt.

    Therefore, the problem appears to be caused by the way USB attached disks are mounted by UDEV on LE (etc/fstab has no entries at all).

    Maybe there's a missing driver in LE for USB 3.1 Gen2 PCIE interface? Gen2 increases the speed from 6Gb/s to 10Gb/s. There is no problem with the controller in the USB 3.1 enclosure. If I connect this enclosure with two SSD's to a USB 3.0 or USB 3.1 (-C) port on my MX Linux laptop, everything is super fast, no slowing or choking on large >10Gb files.

    Here's my LibreELEC DLNA Home Theatre conceptual diagram cook book.

    1) The USB disks are attached to LE Linux box, and LE is installed on a USB stick. The host is Lenovo M720g "Tiny" FF

    2) Transmission and Krusader run on the LE box, managed via WebUI remotely on my MX Linux laptop.

    All heavy traffic is offloaded from my laptop to LE host box.

    The reason I prefer MiniDLNA and don't use Kodi Library is that Kodi doesn't let me browse my audio as "folders".

    MiniDLNA is super-fast and piss easy to configure scraping your USB disks (when you know how).

    Furthermore, I control media browsing and playback from my Android phone - BubbleUPNP app has excellent UI including thumbnails and artwork. Basically, BubbleUPNP "tells" Kodi renderer which files to play from the MiniDLNA media server.

    Imagine, you can instantly play your music without turning on your TV or Laptop screen! No more fluffy dice :)

    LibreELEC = Linux + Kodi , so I'm a bit confused there since you stopped the Kodi application. All that remains is a Linux OS.


    But, I'll try and have a go with 2 SSDs here and see what comes out of my copy experience with a RPi-4B.

    Hi Klojum, thank you so much for responding!

    Libreelec = "just enough OS for Kodi" ... I don't know about other os platforms, but Linux in LE is definitely broken.

    I have no issues with Kodi, this is the best (and only) renderer for DLNA playback. I'm not using its "media server" at all, the disks are not used by Kodi library.

    I've outlined 3 use-cases for USB attached storage in my post, but to summarise:

    1) USB disks are attached to LE box, file manager is Dolphin (or Krusader) running in docker container on LE as native app, which I access using its webUI (browser) from my MX Linux laptop. File copy runs super fast the 1st time, the next file stalls and the whole system grinds to a halt - including MiniDLNA scraping.

    2) As above, but file copy is done from the MX Linux laptop using Thunar across SMB or SFTP. File copy runs steady at a slow, but reliable speed of 12-17 mb/sec

    3) The USB disks are attached directly to MX Linux laptop - crazy speeds up to 420 mb/sec

    4) Previously I've tried Midnight Commander running as native app on LE, but driven remotely from MX Linux laptop - same "crashing" issues.

    There's definitely something broken with the way linux on Libreelex mounts the disks and/or treats large files.