File error on libraries after adding USB disks

grguthrie · October 31, 2018, 12:20am

I am running plex server on a synology NAS - and it was all working fine - I added a second USB external disk with media, and added a few new libraries to point to folders on that disk.
A few problems - on some of the new libraries when trying ot open them, I get this error:

 There was an unexpected error loading the dashboard
 Please visit our forums if you continue to experience problems

And if I try to edit the library for this entry I get:

 There was an unexpected error loading this library
 Please visit our forums if you continue to experience problems

Also if I choose “add library”, it offers the option to browse for a folder, but does not bring up any browsing selection window, just a text-box to enter a folder name.

Not sure what to do. I restarted the Plex application on the NAS - no effect.

ChuckPa · October 31, 2018, 1:02am

Please open File Station,
Navigate to the Plex share
Drill down to Library/Application Support/Plex Media Server
Right-click Logs and Compress to Logs.zip
attach that ZIP file here.

grguthrie · October 31, 2018, 3:11am

Thanks - Here.Logs.zip (2.9 MB)

ChuckPa · October 31, 2018, 3:27am

Are you running Ubitquity gear? The Cloud Key in particular?

Your LAN is screaming UPNP and driving PMS nuts.

Oct 30, 2018 19:28:52.540 [0x7f2164cb0700] DEBUG - Streaming Resource: Usage: 0kbps of WAN bandwidth, 0 streaming transcode slots, and 0 static transcode slots across 0 sessions
Oct 30, 2018 19:28:57.530 [0x7f2164f9e700] DEBUG - NAT: UPnP, not an IGD: <http://192.168.10.53:51229/>.
Oct 30, 2018 19:28:57.580 [0x7f2164f9e700] DEBUG - NAT: UPnP, found device <http://192.168.10.117:55247/dms/> with private address <192.168.10.3>
Oct 30, 2018 19:28:57.580 [0x7f2164f9e700] DEBUG - NAT: UPnP, not an IGD: <http://192.168.10.117:55247/dms/>.
Oct 30, 2018 19:28:57.583 [0x7f2164f9e700] DEBUG - NAT: UPnP, found device <http://192.168.10.84:8080/upnpd/37ec61d18a.xml> with private address <192.168.10.3>
Oct 30, 2018 19:28:57.583 [0x7f2164f9e700] DEBUG - NAT: UPnP, not an IGD: <http://192.168.10.84:8080/upnpd/37ec61d18a.xml>.
Oct 30, 2018 19:28:57.586 [0x7f2164f9e700] DEBUG - NAT: UPnP, found device <http://192.168.10.53:8888/> with private address <192.168.10.3>
Oct 30, 2018 19:28:57.586 [0x7f2164f9e700] DEBUG - NAT: UPnP, not an IGD: <http://192.168.10.53:8888/>.
Oct 30, 2018 19:28:57.588 [0x7f2164f9e700] DEBUG - NAT: UPnP, found device <http://192.168.10.150:2869/upnphost/udhisapi.dll?content=uuid:dbbb35b3-8c95-4e33-897a-ac89f1d6f227> with private address <192.168.10.3>
Oct 30, 2018 19:28:57.588 [0x7f2164f9e700] DEBUG - NAT: UPnP, not an IGD: <http://192.168.10.150:2869/upnphost/udhisapi.dll?content=uuid:dbbb35b3-8c95-4e33-897a-ac89f1d6f227>.
Oct 30, 2018 19:28:57.590 [0x7f2164f9e700] DEBUG - NAT: UPnP, found device <http://192.168.10.107:49152/wps_device.xml> with private address <192.168.10.3>
Oct 30, 2018 19:28:57.590 [0x7f2164f9e700] DEBUG - NAT: UPnP, not an IGD: <http://192.168.10.107:49152/wps_device.xml>.
Oct 30, 2018 19:28:57.607 [0x7f2164f9e700] DEBUG - NAT: UPnP, found device <http://192.168.10.201:8060/> with private address <192.168.10.3>
Oct 30, 2018 19:28:57.607 [0x7f2164f9e700] DEBUG - NAT: UPnP, not an IGD: <http://192.168.10.201:8060/>.
Oct 30, 2018 19:28:57.829 [0x7f2164f9e700] DEBUG - NAT: UPnP, found device <http://192.168.10.113:80/Canon_basic.xml> with private address <192.168.10.3>
Oct 30, 2018 19:28:57.829 [0x7f2164f9e700] DEBUG - NAT: UPnP, not an IGD: <http://192.168.10.113:80/Canon_basic.xml>.
Oct 30, 2018 19:29:24.095 [0x7f2163fff700] DEBUG - NAT: UPnP, not an IGD: <http://169.254.149.168:8060/>.
Oct 30, 2018 19:29:24.098 [0x7f2163fff700] DEBUG - NAT: UPnP, found device <http://192.168.10.100:5200/Printer.xml> with private address <192.168.10.3>
Oct 30, 2018 19:29:24.098 [0x7f2163fff700] DEBUG - NAT: UPnP, not an IGD: <http://192.168.10.100:5200/Printer.xml>.
Oct 30, 2018 19:29:24.098 [0x7f2163fff700] DEBUG - NAT: UPnP, found device <http://192.168.10.3:50001/desc/device.xml> with private address <192.168.10.3>
Oct 30, 2018 19:29:24.098 [0x7f2163fff700] DEBUG - NAT: UPnP, not an IGD: <http://192.168.10.3:50001/desc/device.xml>.
Oct 30, 2018 19:29:24.099 [0x7f2163fff700] DEBUG - NAT: UPnP, found device <http://192.168.10.3:32469/DeviceDescription.xml> with private address <192.168.10.3>
Oct 30, 2018 19:29:24.100 [0x7f2163fff700] DEBUG - NAT: UPnP, not an IGD: <http://192.168.10.3:32469/DeviceDescription.xml>.
Oct 30, 2018 19:29:24.127 [0x7f2163fff700] DEBUG - NAT: UPnP, found device <http://192.168.10.142:50001/Ircc.xml> with private address <192.168.10.3>
Oct 30, 2018 19:29:24.127 [0x7f2163fff700] DEBUG - NAT: UPnP, not an IGD: <http://192.168.10.142:50001/Ircc.xml>.
Oct 30, 2018 19:29:24.129 [0x7f2163fff700] DEBUG - NAT: UPnP, found device <http://192.168.10.84:8200/rootDesc.xml> with private address <192.168.10.3>

The logs are full of this.

grguthrie · October 31, 2018, 3:51am

No - and I don’t know what these are.
The address .192.168.10.3 is the NAS - most of the other addresses are vacant (from an IP scan). the 10.84 is another NAS (QNAP), one other (.53) is a media layer. .150 is a local windows machine. oneother is a sony-player, and .100 is a xerox printer.

NB: this was all working fine, till I added a second USB disk to the NAS today. Well, one glitch was that the NAS power came unplugged, but it seemed to restart fine, and I can browse the file system fine from the NS+AS console, and/or over the local network from windows.

Seems like it is just looking around the network - what does “not an IGD” mean?

And the “with private address….” which is the NAS server - seems odd.(?)

ChuckPa · October 31, 2018, 4:17am

I would like you to now go back to your Control Panel - Shared Folders - Select the USB disk - click EDIT then go to the Permissions tab.

Make certain user Plex has permission to read the drive. It probably got excluded.
If it’s not there, add it and save.

Next go back to Plex and “Edit” the library section where you want to use that USB drive

grguthrie · October 31, 2018, 1:03pm

Thanks; plex has Read/Write permissions for both USB drives.

ChuckPa · October 31, 2018, 3:46pm

At this point, I need to see the log files.

Verify only DEBUG logging is enabled (VERBOSE is not checked)
Scan all files again
Collect the log files when it completes (Settings - Server - Troubleshoot - Download Logs)
Attach the ZIP file

grguthrie · October 31, 2018, 5:25pm

OK; figuring some sort of corruption - I uninstalled plex app on the NAS, and deleted (renamed) the /plex folder, then reinstalled plex. All seems fine, am not just re-building all the libraries.

That is a bit tedious, as I had not yet taken the plunge to reorganize everything from my previous HTPC organization with multiple types (tv, podcast, download, movie, show, …) by topic, into the plex mandated organize by source type. But that’s another story I suppose(!).
All seems OK so far - it is still scanning things… But the dashboard comes up fine.

ChuckPa · October 31, 2018, 6:21pm

I recommend you eventually delete that renamed Plex share to recover the space.

There is one “hack” you can make to the DSM filesystem which PMS can work with.

Create a share which will be the new USB disk
Go into the shell
Rename the directory to something obvious and related to the original name
Create a symlink to /volumeUSBn from the share name created above. This makes the forward link to it using the /volume1 context.
In PMS, refer to the USB disk through its /volume1 path.

Set permissions manually in Linux. DSM won’t cope with the symlink well.

grguthrie · October 31, 2018, 6:57pm

This may be off-topic, but I did re-grouping of all files, and added to libraries in a new clean PMS install on the NAS. I have two USB disks, one with movies, and the other with podcasts, tv, etc.

I created a new “movies” library, and added the movies folder - but i the dashboard scan, it is showing a lot of other stuff - even from the other disk video folder.

Checking the “info” on some of the wrong icons, it shows a path that is wrong -
/volumeUSB2/usbshare/Media/Video/New/AMovie (2014)

This file is actually in:
\192.168.10.3\Media-1\Media\Movies\New\AMovie (2014).mp4

There is not even a video/new folder on that disk (or anywhere).

The FileStation shows everything “correctly”, same as the network browse from Windows.
Looking are the info for some of the wrong files, it says “Unavailable” - but - why is it indexing wrong? And how to fix? Note, this was a clean restart!

Is there a was to see a list of folders associated with each library?

ChuckPa · October 31, 2018, 9:23pm

let’s do a full rewind?
I need to understand how you have your Syno configured on the main Volume(s)

How many primary (internal) volumes do you have? One large SHR, RAID, or only JBOD?

grguthrie · October 31, 2018, 10:06pm

Two 4TB internals in SHR, two external USB disks (2 TB each) with the media.

I don’t point Plex to anything internal. Put media on the two USB’s.

I can see, and browse, and p lay all media properly over the network from these drives on the NAS (VLC on a HTPC Windows box). But running Plex on that (and two other) PCs is where I see the issues.

I now see how to check the folders for each library - and will review and audit that - but still, the file path(s) were wrong.

ChuckPa · October 31, 2018, 10:08pm

Thank you.

With this info, I will grab a HD, put media on it and see what happens.
From that, I can show you my results and we can compare.

grguthrie · October 31, 2018, 10:30pm

Thanks!!

Not sure what is wrong (clearly!).

I did change the library folders, one of them was wrong;
and it still shows scanning - so perhaps it will sort itself all out with time?

It does say finished processing - but then flashes some activity:

Example: The Movies Library:

But on the display:

And the info on one of the files - shows wrong path - ../video/.. instead of ../movies/…

It seems like somehow in adding USB disks to the NAS, some path names are wrong, cached somewhere? (There were some old posts (2008) about such problems with Synology NAS paths on USB disks…

It’s all kinda weird - it did find the files (has right name and info), but shows the wrong path - those files are not where it reports it found them.

Argh.. !

grguthrie · October 31, 2018, 10:46pm

Ah…! Seems like once it finished processing all the other libraries, it came back to the Movies library, and is now cleaning up.

Not sure how to rationalize the errors it had before, but looks like it is resolving them all now!

Sorry for any confusion or ruckus on this - seems like it just takes 5-6-8 hours for scanning larger collections.

It still has not resolved thumbnails for photos, even though it finished scanning that library. Any recommendations or hints? I see lots of older posts on this - so don’t want to fool with obsolete issues or fixes.

It seems that the message “finished scanning …” is just for each item, not the complete library scan(s).

ChuckPa · October 31, 2018, 10:48pm

IF the names are less than perfect, PMS takes longer.
The reason for this is it must sort through all the possibilities and find a best match.
cleaner naming gives a 90% probability hit very quickly.

If I may see some of the names / structure you have, maybe I can help prevent this in the future

grguthrie · November 1, 2018, 1:47am

Yep - Photo thumbnails seem to be (slowly…) appearing.
Time heals all. (?!)

ChuckPa · November 1, 2018, 1:59am

Any Thumbnailing takes a long time (lot of CPU processing). Not an easy thing to do on a Synology

system · January 30, 2019, 2:07am

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

Topic		Replies	Views
New Media not appearing in my Library even after refreshing & updating Library NAS & Devices server-synology	30	17376	April 23, 2019
Nuked Everything, Started Over. Still Empty Libraries NAS & Devices server-synology , library-management	26	304	January 27, 2022
Plex will not scan library Plex Media Server server-windows	47	571	March 15, 2023
Plex won't recognise all of my files General Discussions	52	7125	January 7, 2020
Plex doesn't recognizes my new medias anymore NAS & Devices server-synology	27	395	June 1, 2022

File error on libraries after adding USB disks

Related topics