Sorry to bump an older thread, 3 questions.
1, does this still work in version 9 (probably)
2, does this backup manual mapping of SMB folders (storage-(foldername).mount in the system.d folder
3, does it backup docker / docker configs (in my case, Plex server configuration)
Anyone?
Does anyone do this?
I'm in the middle of a discussion with Intel support about it.
I can *NOT* get the Intel NUC to ***AUTOMATICALLY*** boot LibreElec.
I can press F10, use it without issues from a USB key, but I can't reboot my LibreElec without having to press F10 and choose the USB boot device.
Has anyone here got 7 or 8 series Intel Bean Canyon NUC and able to do this?
Am I making the bootlable key wrong? I tried Win32DiskImager and the official bootable tool from LibreElec as well.
Yes, the system CAN boot Windows 10 bootable keys (UEFI) automatically.
It boots LibreElec USB fine, *IF* I press F10.
Video of the issue.
https://www.dropbox.com/s/s0h26sx0lq842of/Intel%20NUC.mp4?dl=0
Sorry to bump an older thread, 3 questions.
1, does this still work in version 9 (probably)
2, does this backup manual mapping of SMB folders (storage-(foldername).mount in the system.d folder
3, does it backup docker / docker configs (in my case, Plex server configuration)
and in the interest of helping others, it's fixed - it was indeed quotation marks for the complicated password.
Also please bear in mind, you need to put the password AND the username in quotation marks, if a quotation mark is required.
Thanks for enduring my posts, hopefully google indexes and helps people 
I have googled and found the command:
systemctl start <filename>.mount
LibreELEC:~/.config/system.d # systemctl start storage-MoviesOnARRAY.mount
Job for storage-MoviesOnARRAY.mount failed.
See "systemctl status storage-MoviesOnARRAY.mount" and "journalctl -xe" for details.
Which spat this out for me:
systemctl status storage-MoviesOnARRAY.mount
● storage-MediaOnARRAY.mount - test cifs mount script
Loaded: loaded (/storage/.config/system.d/storage-MediaOnARRAY.mount; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Sat 2019-02-09 16:55:13 AEDT; 7min ago
Where: /storage/MediaOnARRAY
What: //192.168.0.9/media
Feb 09 16:55:11 LibreELEC systemd[1]: Mounting test cifs mount script...
Feb 09 16:55:13 LibreELEC mount[800]: mount: mounting //192.168.0.9/media on /storage/MediaOnARRAY failed: Permission denied
Feb 09 16:55:13 LibreELEC systemd[1]: storage-MediaOnARRAY.mount: Mount process exited, code=exited status=255
Feb 09 16:55:13 LibreELEC systemd[1]: storage-MediaOnARRAY.mount: Failed with result 'exit-code'.
Feb 09 16:55:13 LibreELEC systemd[1]: Failed to mount test cifs mount script.
This makes no sense, the password is 1000% the correct one?
I've even remade a new file and tried again, no go.
My password has punctuation in it, does it not like ! ^ # % etc?
I'm having trouble and I'm flowing instructions to the letter at this point?
cd /storage/.config/system.d
nano storage-MediaOnARRAY.mount
[Unit]
Description=test cifs mount script
Requires=network-online.service
After=network-online.service
Before=kodi.service
[Mount]
What=//192.168.0.9/media/
Where=/storage/MediaOnARRAY/
Options=username=XXXX,password=YYYY
Type=cifsFilename I've even done, case sensitive!
LibreELEC:~/.config/system.d # systemctl enable storage-MediaOnARRAY.mount
Created symlink /storage/.config/system.d/multi-user.target.wants/storage-MediaOnARRAY.mount → /storage/.config/system.d/storage-MediaOnARRAY.mount.
Bear in mind also! This exact command works flawlessly, for a temporary mapping. So clearly the path and credentials and permissions are all correct:
"mount -t cifs -o username=XXXXX,password=YYYYYY //192.168.0.9/media /storage/MediaOnARRAY"
So where to now? I'm lost, any tips?
Well I've got my answer, I switched even to a regular, SATA 2.5" HDD in the NUC and it's working fine. Scanned the entire Plex library in under an hour AND Kodi at the same time (I did a fresh install)
I really hope this thread helps others.
Only thing that's a bit annoying / sad, is that LibreElec (Kodi) really did work wonderfully, even off USB, which surprises me - very handy feature. None the less, long term I do need Plex Server so I'm fine using an Internal disk.
It could be a number of things. Your media may not be named in the style Plex likes it so it may be having issues identifying. Or you may have been having internet connectivity issues and requests may have been timing out, or you may have been getting throttled by the metadata provider.
The one thing I can think of with regards to usb drives is that flash drives usually have pretty awful write speeds. Plus, plex libraries can grow to hundreds of thousands of files easily and to hundreds of gigabytes (especially if you turn on video preview thumbnails). I really wouldn't recommend hosting the Plex library on a flash drive.
With that said, there are no issues with the Plex docker container. Many people use with very large libraries (on ssds mostly) and scans are fairly quick.
I can definitely confirm the media filenames are in perfect condition, scanning fine via LibreElec / Kodi on the same network..... at a much higher speed.
I totally agree about the USB write speeds ,but I'd just expect it to either fail or spit out an error (or take even longer....) rather than just do the job poorly (not identifying all content)
Also, Kodi scanned the data perfectly and quickly, (honestly I was surprised)
Does LibreElec somehow make some kind of large container file for the thumbnails and then write into it? Reducing some disk load?
Regardless, it's impressively reliable and fast, for a USB key.
I will I guess, have no choice but to switch drive for testing I guess.
Thank you for the response!
For testing, I'm sticking with USB, but a few questions:
Are there known issues with USB? can it be used for quite large libraries?
Have you ever seen very very slow scanning for Plex on a USB key? (4c, 8t i5) brand new Bean Canyon NUC?
Note that even when it finished, unfortunately Plex managed to miss many thumbnails (See: ykrrlri.png )
It also missed episode title/synopsis / general detail information for example: (See: 3pdffz0.png )
Yet some episodes scanned in fine: (See: oyu07p4.png )
(This Scan for 2900 episodes, 69 shows took in excess of 12 hours)
I'm really, really liking LibreElec so far, this feels very well designed and written, stable, fast - but the Plex (server) addon is giving me a hard time and I gotta admit, I do like to stream from time to time when away from home (Hence the need for Plex)
Anyone else also welcome to reply.
Finally figured out how to manually map an SMB path. (Need to fix it on reboot, but anyhow...)
Scanning 69 TV shows, maybe 2900 episodes.
Kodi for Windows and LibreElec, can scan these in, maybe 30 to 60 minutes at most?
Plex for Windows, around the same time.
Plex (Docker) 'under' LibreElec took nearly 24 hours, not completed,....
Many shows were identified (Show thumbnail, Show name, Season count, episode count) but actual EPISODE definitions, not pulled in, like episode title name, 'actual' episode thumbnail.
Where are these thumbnails saving, is there a space limit? Is it a disk IO issue?
Has anyone else seen this?
I'm running LibreElec from USB key (god, this is very well designed, I'm very impressed)
I just need to nail a few small issues and I can switch to this indefinitely.
Long story short:
Has anyone else had 'anomalies' scanning into the Plex server (docker) in the background, under LibreElec?
Does anyone else run from USB key reliably, with a huge library for Plex? (because generally, performance on USB key has been astoundingly surprisingly good for Kodi)
Read post #24 again. Follow the comments in the files.
I'm asking what the syntax is, to manually mount them, just temporarily for testing, without a reboot.
Following the standard process using the mount command regular syntax is resulting in
"invalid argument"
Is this not possible?
Kodi can use SMB from within Kodi. Plex (in docker) cannot access mounts via Kodi. So mount in the OS and then configure both Kodi and Plex to use the same /storage/mountpoint(s) for the remote SMB/NFS shares.
Thank you for replying again!
Sorry for more dumb questions,......... I've found a tuturial on how to mount an SMB, including editing several files and rebooting.
However, I'm curious if I can just do testing first and mount an SMB share, without a reboot? (initially)
I've tried this command, which IS working on my Raspberry Pi.
mount -t cifs //192.168.0.9/testsmb /tmp/bob
It's not working on LibreElec though 
It's spitting back "invalid argument" at me.
So I figure the synatx for the mount command, in LibreElec is different (slightly) to the syntax of mount command in tutorials I'm finding across the web, for Linux.
Hopefully this thread helps someone else too.
Thanks both of you guys, to clarify, I imagine this means there's no way to do this (currently) in LibreElec front end interface, need to be smarter users SSH'ing in and what have you?
(I'm ok with that, I just was curious if there's a simple solution)
EDIT: Also, does anyone know, the precise command syntax I can do, for testing in the SSH session, before writing the file?
I do not have a user / pass (guest access) so it's a little bit unclear in the doco, hence wanting to fiddle
Display MoreHey there,
I just installed Plex via the LE docker repo. I have access to the server and it looks like its running so far.
But I can't add any share media folders from my NAS. I tried to Map the NSF Share in the settings, as you described, but when I do this I can't access Plex anymore (it just wont't start). I disabled and enabled the Addon, restarted Kodi (using Libreelec 8.2.5. with RP2), but nothing helps. If i chance the mapping back to the standard "/storage/tvshows" (for example) Plex is starting again.
The NSF share is working fine, since I am using it for my Kodi library. I also tried SMB share but with the same issue.
May I miss something!?
edit:
Some more information. When I edit the settings file to map to my shared network folder, it looks like the whole image isn't even recognized by Docker.
I tried to use the commnd "docker ps -a" to to see all images, but its completley blank. When I reset the settings to default the image show perfectly and Plex is starting.
I don't think I did anything wrong with the mapping since I am using the tree folder structure inside Kodi to point to the right direction. So I can't see why Docker can't recognize the image after I changed the settings?
<SNIP>
(My emphasis on a few lines there)
I'm having precisely this problem with mine, I've just started using LibreElec, I'm so very very impressed so far, but stuck at this point, identical issues. (I use SMB, not NFS)
My SMB pointers in my XML file, in Kodi, which are obviously working for Kodi - as soon as I configure them to be the 'redirects' for Plex in the Plex config, will stop the Plex docker executing and running.
I can confirm this by SSH in, then typing in
docker image ls
and
docker container ls
The container is pulled down, but it's not running, unless I reset those settings to default, then it's listed as running.
So what's the easy solution?
