SOLVED: tv library not scanning

[n4tur3502]

Ok, so when I try md5sum on a video file (tv or movie) it just kinda sits there and does nothing. When I tried it in a file in the root directory it gave a long string. So I am guessing this user doesn't have write permissions. I really thought I had it.

I dont know if this helps, but I have a plex server on another computer that appears to be updating the libraries just fine. Do you think that has anything to do with jellyfin not updating?

Also I dont think i mentioned the nfs is pulling from a mergefs pool.

[TheDreadPirate]

md5sums have to read the entire file before calculating the checksum. I'm not sure how long you waited, but it could be several minutes for multi-gigabyte movies.

[n4tur3502]

Ah ok, I am trying it again now. I did notice that when I restart the jellyfin service it does appear to update the libraries.

Edit: It did appear to give a checksum from the file in the videos directory. Just took a few minutes like you said.

[n4tur3502]

I've run the checksum command on a few video files in my media folder and they all give checksums.

[TheDreadPirate]

Just for clarification. What do you mean when you say that your TV library isn't scanning? Is the home page not updating the "Latest TV Shows"? Or are these shows not showing up AT ALL, even if you go into your TV Show library?

[n4tur3502]

All the existing videos (movies, tv shows) I already had showed up fine when I installed jellyfin. Now when anything new is added it doesnt show up at all. not on the front page or even when going to that library directly. Sorry for not clarifying that sooner.

[TheDreadPirate]

Go to a folder for a show or movie that works and run "ls -l" and copy the output here. Also "ls -ld ." so we can see the directory permissions. Again, copy that output here.

The only thing that makes sense here is a permissions issue. I'm running out of ideas.

[n4tur3502]

I ended up getting super frustrated and just turned on guest access for my network share. suddenly everything works. I am gonna count that as a win and just move on. I really appreciate your help.

[bitmap]

Been a hot minute since I used OMV, so I don't recall exactly where things needed to be set in the GUI. I typed this up and...I'm wondering a big question...did you install the NFS client package on your Ubuntu machine? I think the package is nfs-common? If not...that may be the source of your issue.

Code:

sudo apt install nfs-common

Start there, then read on if you've already installed that package. Mounting this as NFS requires you to have that package installed for anything to work properly.

In OMV, you need to make sure that the NFS is set to be exported to either explicitly your IP for your server or to your entire internal network. Know your risks -- every decision you make has a risk. Exporting to the whole network makes the drives available to every machine that connects to your network. If you squash (as I'm suggesting), you can't trace file modifications or restrict access using FACL or other methods. These are too complex for my setup where I have two machines that do the business and sharing with other machines happens outside the confines of NFS.

So if you have your shares setup properly in OMV to export to the right subnet or explicit IP(s), the next step is setting options. Here is an example of one of my exports, straight from /etc/exports, which is the same format that OMV uses (ignore the mount and the export -- the options are what you're interested in):

Code:

/mnt/media/4K  192.168.1.31(rw,sync,no_subtree_check,anonuid=1000,anongid=995)

These are simple options that work for me. Read/write, sync, no subtree check, and I squash all access down to appear as though it comes from my service user that owns the files to ensure I don't have access issues with my NFS shares. On the other end, where you're mounting the NFS shares (which would be in Ubuntu, in /etc/fstab as you've gathered), it would look like this:

Code:

192.168.1.31:/mnt/media/core    /mnt/media/core nfs    defaults        0      0

Abstracting:

Code:

host:/remote/path    /local/mount/path    type    defaults    0    0

The type is the type of file system (NFS), defaults means no special options (those are set in the exports by the host), and the other two numbers relate to special options that I've looked up and read over before but do not understand enough to relay. There's plenty of documentation and I'd rather you read from there than get confused by me. Hopefully this helps? Good luck.