Thanks for the explanation. Yeah, it doesn’t seem to be a Jellyfin-related issue at all, I was just wanting to include as much relevant info on my particular setup as possible. A lot of this stuff is super unfamiliar territory and I’ve never messed with Samba settings in the past. I intended to do the whole setup with NFS, but I didn’t know what I was doing and I just happened to find an easier to understand guide for configuring the fstab file using Samba and went with it. I may just remount everything and share everything with NFS. Looks like the OSMC version on my other client is using Kodi 20.5. The next one is supposed to use v 21. I just upgraded LE yesterday so they were using similar versions of Kodi at the time I was having issues.
Posts by docsuess84
-
-
I had a question with regard to how Samba is configured specifically to LibreElec as opposed to an alternate Kodi-integrated OS or Kodi installed on anything else.
I have a file transfer bottleneck issue within my LAN I’ve been trying to solve for weeks, and through process of elimination I’m pretty sure it has to do with Samba configurations between client devices and my server host machine. I have a client LibreElec Chromebox and a Vero4K running OSMC. My backend consists of a WD MyCloud network drive, WD EasyStore plugged into the My CloudC and both are available as network Samba shares. I also have a host Mac Mini running Lubuntu that hosts a Jellyfin server, but also has a separate internal HDD drive and WD MyBook drive connected via USB 3.0 drive that is used for media storage and those are also available as samba shares and on the network. The LibreElec Chromebox can play any file of any size from any location on my network with no problems whatsoever. The OSMC Vero 4K likewise has no problems with files on the dedicated NAS devices, but struggles with files served via Samba from the drives locally mounted on the Lubuntu Mac Mini. It’s pretty universal. Larger more high definition files stall and stutter faster, but even DVD rips get there eventually as well. This same problem also occurred just trying to stream files on my iOS devices with VLC as well as the native Jellyfin player app, Swiftfin. The problem went away in VLC when i went into settings and unchecked the box “Prefer Samba 1” and now everything plays flawlessly the way LibreElec does, but Swiftfin still stutters and stalls. Is there something specific about the way Samba protocols are configured as a default in LibreElec that would allow for faster transfer speeds that I should try and duplicate in the other places where the Samba protocol seems to be a transfer speed restriction? I don’t remember changing anything special on the Chromebox or there being any kind of choice to be made on the server host device when I was editing the Samba config file there either. Like I said, the only problems occurs with files on the drives locally mounted on the Lubuntu Mac Mini. The other standalone NAS devices all work great regardless of what client is used. -
It came that way out of the box, unfortunately.
-
Oh, one thing I was curious about is if there can be spaces when you’re mounting a drive. Should the share be entered as “My Book” or would it be “My_Book” ?
-
So when I mounted a dedicated network drive share from a WD MyCloud, after creating the mounting spot with sudo mkdir /media/public the command I entered was
sudo mount -t cifs -o rw,guest,vers=3.0 //deviceipaddress/Public /media/public
Would the command formats be the same only substitute the Public for My Book and the IP address as written with the :445 port on the end of the IP address? -
This is kind of a general Linux question, but the device involved is running LibreElec so I figured I’d start here. I’m setting up a Jellyfin server on a Raspberry PI and I’ve successfully mounted my dedicated network drives. The only piece left is a WD My Book USB 3.0 external hard drive. It’s plugged into a Chromebox which is running LibreElec. On a Mac or PC The Chromebox shows up as an SMB shared device and the My Book drive is just a folder. Within Kodi itself I was able to add it with ZeroConference and it displays as 192:168.0.122:445/My Book
The IP address makes sense, since that’s the address for the device, but I wasn’t sure how the 445 came into play. How does that need to be formatted if you’re trying to mount it using the sudo mount -t cifs command? -
Update:
I moved the box to my workstation temporarily to make it easier to perform the steps requested. I re-flashed the same USB drive I’ve been using with the beta version exactly the same way I have the other times. The differences in my temporary desk setup vs how I had it configured on my tv was I have it plugged into the wall directly vs to a surge protector, connected to a monitor via DisplayPort instead of HDMI and the Cat 6 connected directly to a powerline adapter instead of to a gigabit switch connected to a powerine adapter. The boot process this time was extremely fast, borderline instantaneous compared to the previous attempts where the boot screen just sat there for around 5-10 minutes before the install menu showed up. After rebooting into LibreElec I kid you not, everything is working. The network is working, the sound is working, all the sound outputs show up in the menu. I’m kind of dumbfounded. The only other thing that’s a little weird is under the audio outputs there is an ALSA: HDA Intel, HDMI #1 and #2 option even though the Chromebox only has one HDMI port. I didn’t do any logs or anything because I’m not recreating the problems I’m having. Not sure what all this means, but I’m going to try to set everything up and try to use as many of the same pieces as I can and I’ll let you all know if I continue to have any issues. Thanks for everyone’s help.
-
Then connect a USB drive and copy logs from the following locations to the USB drive using the Kodi file manager:
/storage/.cache/log/journal/*
/storage/.kodi/temp/kodi.log
I haven’t really used the file manager a ton. Is this something I can do if I plug a mouse in? Like just copy and paste that onto the USB drive?
-
-
-
For whatever reason, it won’t show up in my home network so I can’t access it from the terminal to upgrade the firmware and run the script. I imaged an Sd card to run the current version, but is there a way to force it to boot from the SD card instead of the hard drive? I can’t remember if you hold down a key or if that was only at the beginning in developer mode when it still had the stock OS on it.
-
Hey all,
I was previously running a server setup with a Chromebox I bought back in 2018. I had to disconnect the setup for some remodeling and had misplaced a few of the NAS drives so I hadn’t used Kodi in a year or two. Found the drives and connected everything and I booted it back up again, and I can’t update the version (its two versions old), and I can’t map media sources by browsing with NFS like I did before. I guess my questions are:
1) Is a six year old Chromebox still capable HTPC hardware for running the current version of LibreElec?
2) Do I just need to start fresh with a fresh install with the newest version since it seems that the update options in the LibreElec settings aren’t showing up there?3) If it’s time to put the Chromebox out to pasture any recommendations on something similar in a similar price range that’s ready to run LibreElec out of the box? I have a Pi 3 B+ at another location but I found I needed to tweak it a bit to get it to work right along with paying for the codecs and all that and I just don’t have the fiddle time I used to.
-
I'm in the process of adding an additional device to our Kodi network. I have a Dell Chromebook 11 and a FLIRC just sitting here collecting dust and I was wondering if I can repurpose it as a Kodi box for my kid's room. My Asus M004U Chromebox running LibreElec has been my favorite old-faithful performer of all my devices for several years and was just curious if Chromebooks run it in a similar way. If I can use it, will the Chromebox EZ Script still work?
-
I installed the generic Amlogic version 9.0.1 on my X96 Android box, and it seems to boot just fine, but peripherals don’t work. No keyboard, no remote dongle. Is there anyway to fix this?
-
Hi all, I have a Chromebox that was performing flawlessly until I upgraded to the latest version of LibreElec with Leia. Since then, all my DVD rips seem choppy, especially on fast motion portions of movies and shows. I have all hardware acceleration enabled. Is there any other setting I should be looking at? I haven’t changed anything in my settings other than upgrading the OS itself. Thank you. As a comparison, I went to my other setup which is a Pi3 running OSMC and DVD rips play as a they should.
-
I have an Asus Chromebox running LibreElec. I recently added a WDMyBook device locally via USB on the Chromebox itself. It worked perfectly for several weeks with no need for any modification. I was able to access it locally via the Kodi interface under the root file system under media, as well as over my network with my laptop. My daughter went to watch a movie today and it states the file couldn’t be found. The entire drive and it’s contents are gone. It won’t show up in Kodi, or via the network on my laptop. It works fine when I unplug it from the Chromebox and and plug it directly into my laptop and all the files are still there and function, so it doesn’t seem to be an issue with the drive itself. Rebooted the Chromebox, and reset the drive but nothing works. I just moved a ton of media onto this thing. Any ideas?
-
The Office episodes are VC-1 and the Firefly episodes are H264. They behave the same way.
-
Hey all,
I have the latest version of Libreelec running on a Raspberry Pi 3. Movies play flawlessly but when I try to watch ripped 1080p tv episodes it stutters and looks like it's playing in slow motion. I have a Chromebox upstairs with an identical version of Libreelec and they play fine. Any ideas on what I need to adjust in the settings? I'm stumped.