There was an unexpected error loading this library

[ConnorATX]

Server Version#: 1.15.6.1079
Player Version#: Web

All but one of my libraries show the error, There was an unexpected error loading this library.
I tried to optimize the database and then one more library started working but after a restart it’s back down to the same one library.

Dashboard says: There was an unexpected error loading the dashboard

[ConnorATX]

I’m getting this error in the console

[ConnorATX]

Bump

I manged to fix it via a backup but now it’s happened again!

[ConnorATX]

Bump.

[ConnorATX]

Bump

Fixed and it broke again! Wow, great support from the plex team. Why did I even buy this plex pass lol.

[acidiac]

My Movie library constantly gives me this error as long as the format is set to titles. if I change it to anything else such as “Date Added” it displays fine. Switch back to “By Titles” and it gives me the error. Really want to fix this somehow.

Ken

[ConnorATX]

Bump…

[dimitriz]

Well, I just got this on a new Plex Server installation.
Kind of surprised that Plex team is not looking at this error as it seems fairly persistent at this point.

[ConnorATX]

I’m very close to moving to jellyfish or emby at this point. Shame I bought the Plex pass. I don’t even use any of the features, I just wanted to support the company. Now my server is useless!

[dimitriz]

Yeah, this is ridiculous. I cannot beleive that a professional software company like Plex doesnt even give a … about users having problems with this.
I kinda got it working but had to reinstall whole Plex… so now guess what?,… lol… back to the same error.

[dkedinger]

I have been fighting this problem as well. I have tried deleting and rebuilding my library multiple times. The only thing that fixes it is restoring a backup of the database but even that doesn’t last for ever.

[ConnorATX]

Bump.
Plex Support Team? We’ve yet to hear back from you about this very persistent and damaging issue!

[mahoney621]

Well this is complete rubbish. Just bought the software for a month. Glad I only wasted $4.99 I have the same message on all my libraries. Disappointed that the tech does not seem to GAF

[pshanew]

Not sure if it’s related, but there are some database corruption issues with Unraid 6.7.0 and PMS which could be causing your issues. Here are some threads which discuss it and potential mitigations:

Plex Database keeps Corrupting

I’ve been following this here, and on the unRaid forum. Lots of people having problems with their Plex database being corrupted after updating unRaid from 6.6.7 to 6.7.0. Long story, but I’ve been trying to find a solution since May 12th. In my research, I came across a piece that said having your appdata spread across the array can cause this. The recommendation was to have appdata either on a cache drive only, or on a single dedicated drive in the array. I rolled unRaid back to 6.6.7, remove…

And:

Plex database corruption

I’ve been following this here, and on the unRaid forum. Lots of people having problems with their Plex database being corrupted after updating unRaid from 6.6.7 to 6.7.0. Long story, but I’ve been trying to find a solution since May 12th. In my research, I came across a piece that said having your appdata spread across the array can cause this. The recommendation was to have appdata either on a cache drive only, or on a single dedicated drive in the array. I rolled unRaid back to 6.6.7, remove…

And:

Database Corruption

I’m not sure who to point fingers at, but Plex and/or unRaid need to get together if necessary, and fix this. One thing I had noticed was enabling the creation of preview thumbnails, caused it to crash almost immediately, and thought that may be the problem. Not so. My latest corruption was at 16:07 this afternoon, with preview thumbnails disabled, though it had been running almost 24 hours. I removed plex from docker, deleted the plex folder from appdata, and rolled back from unRaid 6.7.0 to …

If you’re running on 6.7.0 it might be worth looking into…

[dimitriz]

Well, apparently Plex people think there is no issue or any kind of a problem here.

z-man! (dimitriz75)

[Mongo75]

I know of at least two other threads on the Plex forum and one on the unRaid forum.

Plex Database keeps Corrupting

I have 2 Plex servers runing in dockers on UNraid (one is from the Linuxserver repo and the other is from the unraid/limetech repo). One as my main and the other as an emergency backup. recently the main ones DB failed. The docker was running fine and updated (even tried Force Update). i followed the recover a corrupted DB steps (which didn’t work. Well the process change from corrupted to fine, but i still had no media). I then rolled back a couple of DB in the appdata folder, which resto…

Plex database corruption

Over the last week I’ve had to do daily restore of the plex database. It gets corrupted and no longer adds new media. Repair is never posible as it’s too damaged. Once backup is restored I can scan and it then adds the new media. Any one else having issues?

https://forums.unraid.net/topic/38974-support-limetechs-docker-repository/page/27/

In my research, I came across a piece (Check out Q/A #7 here documentation/docker/faq/unraid.md at master · binhex/documentation · GitHub), that said having your docker container config file spread across the array can cause this. The recommendation was to have the config folder on a cache drive only, or on a single dedicated drive in the array. I chose to have my appdata share set to cache only and to specify the explicit path for my docker containers.

On May 31st, I uninstalled Plex and deleted it’s folder from appdata. I installed a SSD cache Drive, moved the appdata folder from each of my 14 drives to the cache drive, then rolled unRaid back to 6.6.7. I reinstalled Plex from scratch, setting Appdata to /mnt/cache/appdata/plex.

I ran it for two weeks just to make sure it was stable. With everything running smoothly, I updated unRaid from 6.6.7 to 6.7.0 on June 13th.

I’m still running error free. It seems that having the container’s config folder set to cache or set to a single drive rather than spread across the array solved the problem. It did for me anyway.

[ConnorATX]

Thank you SO MUCH! Didn’t expect such a detailed response. This is my first time messing with unraid so this is super helpful. I’ll try it out as soon as I get home:))))

[Mongo75]

Believe me, it was no cake walk for me. From May 12th to May 19th, I had no idea what was going on. Remove Plex, Reinstall Plex, repeat. Then I found that it was somehow linked with unRaid 6.7.0. I spent the following week confirming that. Then I found the link to binhex’s Q/A, and pretty much did what it said to do. I spent another two weeks just making sure everything was stable before actually updating unRaid to 6.7.0, That was in June 13th, and it’s been smooth sailing since.

There may be other fixes and or workarounds, but I found a solution that worked for me, and I’m sticking with that

For what it’s worth, unRaid has released version 6.7.1, per the email I received this morning. I like to stay on top of updates, but after this experience, I’m somewhat reluctant to apply this update, lol.

[mikesync]

I am having the same problem. I uninstalled PMS twice already and it works for about a day and slowly it seems to get corrupted. I am on a Synology DSM 6.2.2. I first get it on the Dashboard and I go to the individual libraries and that seems to work for about a few hours then all the libraries have errors and I can’t launch any of my libraries. I’m not using Unraid so I think this problem is more wide spread.

[Mongo75]

I’m not familiar with NAS. Are you using Docker? If so, you should be able to edit the Plex container settings to have it use a single drive rather that the array…maybe…