Library isn't updating anymore

Plex Media Server Metadata & Adding Files
21

I’ve just checked on my PC and it appears that the UNC path doesn’t change if you use NFS instead of SMB. It may appear at first that the shares all have an additional backslash at the beginning of their names, but that is only a cosmetic issue in the Windows file explorer. (and actually useful to differentiate NFS file shares)

NFS file share on my NAS:

grafik
grafik767×187 10.3 KB

UNC path of one of these shares:
It doesn’t look differently from a regular SMB file share.
Windows also allows you to assign a drive letter to it.

grafik
grafik754×196 9.73 KB

I’m still a little bit skeptical, if this is a viable drop-in replacement. Since I’ve observed slightly longer reaction times at least for the first contact (i.e. when typing in the address of the NAS and pressing Enter in the address bar.)
I’d be very interested in the resulting experiences of other users.

22

Oh, thanks for testing all that out. I’ll leave mine for now and when the next PMS updates come out I’ll enable. Curious when you mentioned “ You’ll have to wait until the developers find a way to repair SMBv1 in the “boost” library.” would this maintain security with the older SMBv1?

23

No it won’t. SMB v1 is unsecure. Period. Continuing to use it carries a risk. (Even though that risk is somewhat lower, because exposure is limited to the local LAN - unless you made a mistake and let SMB traffic go outside.)

Yes, I mentioned that above.

24

Sorry, I just reread your post and saw that. I might just enable NFS now then and test it out. :slight_smile:

25

I’ve been using Suncross Network Drive Manager to map my drives, if it still works with NFS I’ll let you know if it works, it might reduce the feel of the reaction time since it connects the shares straight up.

26

Why?
All it takes is a right-click on the share in Windows file explorer.

27

I found that my mapped drives would only connect when I clicked into them. Google searches lead me to this solution. It works well.

28

Gotcha. It appears to work around certain quirks of Windows’ handling of file shares. Can be useful to Plex admins, I reckon.

1 Like
29

Not sure if anyone has mentioned that this is affecting Drivepool users too. My drivepool is in a JBOD enclosure directly attached to my (windows 11) PC.

I downgraded PMS to restore functionality.

30

it really does sound like Plex should rethink the SMBv1 changes until all the impacts are known.

31

I’m having the same issue with plex.
since windows update (2023-04 .NET 6.0.16 Security Update for x64 Client (KB5025915)) Plex is no longer detecting and ready network drives or files.
I’ve tried remapping network drives, mapping folders direct to for plex to access still doesn’t read. I’ve even tried a clean install of plex. Before the clean install of plex it was reading files already scanned and add to the libraries. But as soon as you did a rescan to add new files to the library the files disappeared. And haven’t been able to get plex to see the network drives since.
I’m running
Windows Home
Versoion 22h2
OS Build 22621.1555
update NET 6.0.16 Security Update for x64 Client (KB5025915)
Plex Version 4.100.1
Does anyone have any ideas how to fix this

32

Which type of connection is used? USB? Ethernet? SATA? Other?

It doesn’t have anything to do with Windows updates.
Look a few posts above.
See if you can teach your network file server (NAS etc.) to use SMB 2 or SMB 3. Alternatively, try and switch to NFS, if available.

33

USB connection.

34

If you’re unable to connect, you can reinstall this version until you resolve SMB issue.

https://downloads.plex.tv/plex-media-server-new/1.32.0.6918-6f393eda1/windows/PlexMediaServer-1.32.0.6918-6f393eda1-x86_64.exe

36

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