Posts by Awaredev

Derp-

I forgot the original setup was doen on Windows using mklink /j. The Junctions were interpreted as bound mounts in Linux.

To make it cleaner, I just used mount --bind and will be setting up a udev rule to make sure it sets up the mounts each time the external drive is recognized.

Sorry- didn't get notification of a reply.

The symlinks are pointing to directories on the same external drive. The actual directories are grouped to be backed up to ONE DRIVE family accounts (1TB@), with the Symlinks providing direct access to the directories in a more direct fashion.

DRIVEROOT

-Symlink:Directory1

-Symlink:Directory2

-Symlink:Directory3

-Symlink:Directory4

-Symlink:Directory5

-Symlink:Directory6

-OtherDirectory

--SubDirectory

---BackupA

----Directory1

----Directory3

----Directory5

---BackupB

----Directory2

----Directory4

----Directory6

What's odd is that I can't access files in the directories remotely either (although I can see them - I get an error saying the file does not exist.

I'm running V11.03 on rPi3b+. I've got everything running as I want except that Samba is not giving access to subfolders of symlinks.

Currently, all my media is on an external drive. The root of the drive has symlinks pointing to directories deeper in the drive's directory structure. I can access these directories via the symlinks locally with no issue. However, when accessing remotely via samba share (which is the root of the external drive), I can go into the symlinked directories and see their subdirectories, but any attempt to open these subdirectories fails (Windows says the content is not available, X-plore on Android says 'object path not found)). I can access these subdirectories if I navigate through the drive normally via samba (without the symlinks).

I tried doing this in /storage/.config/samba.conf (My Book is the share):

GNU nano 7.1 samba.conf                         
[global]
follow symlinks = yes
wide links = yes
allow insecure wide links = yes

[My Book]
path = "/storage/media/My Book"
follow symlinks = yes
wide links = yes
allow insecure wide links = yes

Can anyone tell me what I'm missing? This worked on an earlier librelec install (8.2), but I can't recall what I did to get it working.

Thanks!

Ahh- Thanks! that clears it up.

Hi All-

Just upgraded my LE install on my RPi3b from LE 9.2 to 10.0.3.

On 9.2, I was able to watch 10bit h.265 without much issue (sometimes video would drag, but rebooting would fix this). Now, with 10.0.3, I have the following issue:

1. If 'allow DRM Prime decoding' is on (with or without hardware support), then the screen goes black, then shows the spinning busy icon over the library for a few seconds before the spinner freezes and audio starts to play. If I stop the playing, then the screen goes black for a second again and the audio stops.

2. Without 'allow DRM Prime decoding', the video and audio play, but the video is extremely slow and choppy.

I've checked the logs and there are NO errors or warnings or significant events around the times I tried to play the h.256 video.

Any idea what might be out of sorts here?

Thanks

Weirdest thing just happened-

We just finished watching a movie, and the folder suddenly showed as empty. I checked via SSH, the Videos menu, and the Kodi File Manager, plus via SMB on a WIndows PC remotely.

Every other folder on the attached external hard drive is fine (RP3 running Librelec 9.2).

However, if we look for the movies in Kodi's Movie library- they play fine. Going into Information I can see the path and it is to the folder that shows everything else.

Anyone have any ideas what may be causing this?

Powercycling everything did nothing.

Thanks-

I was afraid of that- I do have a lot of modifications .

However, as it will be a while before I upgrade, I'll do an audit of my setup and try to do up a document to rebuild it.

Hi Everyone-

I have a Libreelec install (no NOOBS) running on RPI3b+ and am planning to upgrade to an RPI4b.

Would it be enough to upgrade my Libreelec install to Leia 9.2a and swap the SD card over to the new RPI4b? Or are there more hoops I need to jump through to get this to work?

Thanks in advance!