Random media being marked "unavailable" - Network errors in logs (even though valid)

Server Version#: 1.25.1.5286 (Win10 21H2, firewall disabled)
Player Version#: Latest Plex Web

I’ve been randomly losing almost entire media paths and getting the “unavailable” trash can icons, but then when I go to view info for the affected item, it’s fine, and also playback works fine…I did all kinds of troubleshooting for this including restoring a previous data dir and DB. After going through scanner logs I think it might be something with my VM using rar2fs for a lot of my media paths/mounts…I’m seeing this in logs: WARN - Error scanning directory, we’ll skip and continue: boost::filesystem::directory_iterator::construct: An unexpected network error occurred:…Any ideas on what I can do next to troubleshoot? I do plan on going back to a previous VM snapshot and seeing if that makes a difference as well. I’m just tired of seeing all these trash can icons in the web view. It’s really messing with my sysadmin OCD.

I rolled back to previous Plex version 1.25.1.5286 (I was running latest 1.25.2.5319), I’ve upgraded my Windows box where I run PMS to 21H2 (was running 21H1 before) and disabled the firewall, and tried going back to a couple different VM snapshots where it was definitely scanning correctly a couple weeks ago)…this issue still persists. I have close to 4000 movies and 200 shows/10000+ episodes in my libraries. I would think if this was a permissions issue, then I would have trouble accessing these paths. But the paths work fine from Windows and they playback just fine from the Plex web player even though it’s marked as “unavailable” and plays fine from my Shield as well.

Any ideas? I might try rebuilding my rar2fs VM from scratch, but something tells me that’s not the issue.

I can provide secure logs as needed through DM etc., but I prefer not to post them here publicly.

Update: So I think I found my problem

I’ll just need some guidance on how to fix it

Pretty sure my libraries have grown so much that samba is hitting it’s file limit now

Dec 20, 2021 13:51:56.530 [11020] WARN - Error scanning directory, we'll skip and continue: boost::filesystem::directory_iterator::construct: An unexpected network error occurred: "/Path/to/files/

and then this matched timestamp entry from my syslog: Dec 20 13:51:57 plex-vm smbd[102507]: Too many open files, unable to open more! smbd's max open files = 16424

So I need to increase samba’s max open files…working on doing this now, but if anyone has any best practices for this as a guide I can follow…please share :slight_smile:

So I found another user that may have the same issue as me…and apparently this issue may have started around the PMS 1.25.x builds so it would be something recent.

Can anyone confirm that something changed with how Plex scans media that could cause this?

I upgraded my VM that uses rar2fs from debian 10 to 11 hoping that might solve the issue or at least improve it. No luck. It may have actually gotten worse. All my files are still accessible from Windows and the VM, and they still play fine in Plex web and the “get info” shows valid file/path information that is accessible. I still can’t figure out what is causing most of my media to be marked as “unavailable” and the cooresponding “too many files issue” from the rar2fs samba shares other than maybe a possible bug in a recent Plex scanner version.

Can I try downgrading to an earlier version of PMS? Like something back from Oct/Nov? Or would this have a negative impact on the database?

So I may have this figured out. It’s possible my settings for rar2fs needed to be tweaked. I’ll let it go through one more scheduled scan to make sure it’s resolved.

Update:

So I’m still having issues with this…I completely rebuilt my VM and upgraded my box hosting PMS to Win11 hoping that would resolve it, but no luck.

Does anyone else have similar issues with recent builds of PMS? I really would like to get this resolved. I’ve spent days troubleshooting this now.

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.