ksman75
-
Posts
37 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by ksman75
-
-
Today, my parity drive went "red x" as well as one of my data drives.
Parity drive first...WD Red that I bought black Friday 2019. I can access its smart page, and run the smart self test, but unRaid flags it with a red x. I've swapped it and my second parity drive and the problem follows the drive so I don't think it's my drive bay, or cable.
Disk 2...WD Blue that I bought Christmas 2019. Just flaged with the red x. I can access its smart page, and run the smart self test, but unRaid flags it with a red x too. Reseated the drive and it's still showing bad. Now it says it's saying Unmountable: No file system.
If I format disk 2, will I loose the data that was on it, or have I already lost those files?
Should I run a parity check/rebuild?
Not sure where to go from here.
unraid-smart-20200130-1319-parity.zip unraid-diagnostics-20200130-1316.zip unraid-smart-20200130-1228-disk2.zip
-
19 minutes ago, pocketsand22 said:
Any suggested PLEX apps from the community that you would recommend?
I personally prefer the linuxserver plex container...
-
Only Windows (10) Security and I have AdBlock disabled for my domain. Also, I have the same problem when I go to the unRaid GUI on my server, and there's no ad blocker or anti virus installed on the server.
EDIT: I forgot to mention in my original post, using MC, I can access everything on my server. All shares are still in /mnt/user. I can also FTP to my server and am currently copying my most critical files to my Windows box.
-
Yesterday, I was playing with permissions with one of my shares, and though connected to all my shares, I noticed the server "Shares" tab said "There are no exportable user shares".
I have tried everything I can think of, including wiping my flash drive and installing and configuring unRaid from scratch.
Today, I created a share called "Test". It looked like it created it, but when I go back to the "Shares" tab, I get the same "There are no exportable user shares". I'm at a total loss as to what's happening, and how to get my shares back!
Help!!!!!
-
Glad to help
-
2 minutes ago, itlists said:
This is what I see when editing the plex docker:
I'm using the linuxserver.io container. You're using the Limetech container. Not a big difference. Limetech has less options to screw up, LOL. At the bottom of your screen you have the "Add another Path, Port, Variable, Label or Device" option. Click on that and you can add the path(s) you need, pointing to your actual media. It'll look like the next screenshot. The "Config Type" defaults to "Path", so leave it. "Name" can be anything you want. "Container Path" is what you'll see in Plex. Be sure to have the leading slash. "Host Path" is a drop down you can use to drill down to the path on your array path. If it helps, it's very similar to mapping a network drive in windows. You want to map your host path (/mnt/user/whatever) to a local path (/mymedia in this example) that Plex will see.
-
2
-
-
20 minutes ago, itlists said:
Hello,
New unRaid Plex user running into an issue.
I'm trying to add my libraries to the Plex server. When I go to select folders and browse to /mnt, its empty. My share is located /mnt/user/Media. However, in the Plex server gui, /mnt is empty. In fact, all root level folders are empty.
What am I doing wrong?
Any help is appreciated! Thanks
You don't want to use /mnt. When you install Plex you have the following screen...
Notice the three in red? These are the paths you want to use in Plex. You want /Movies for your movies, /TV for your TV shows, /Music for your music, etc. I add a path "/user1" that points to /mnt/user/media where all my media folders are. On my system, Plex looks like...
On my system, it looks like this...
I hope this helps
-
1
-
-
Above you show 'split level' set to 'auto split any directory' - do you think it was like that before, when you had appdata existing only on array? Also, do you know if appdata/plex directory specifically existed on multiple array disks?
Yes, that's how all my shares are configured. Yes, appdata was spread across all 14 of my array drives.
What I'd like to ask you to do is leave all config exactly the way it is, except, change the Plex appdata mapping from:
/mnt/cache/appdata/plex
to
/mnt/user/appdata/plex
Sorry
. It's not that I don't want to, but I've finally got it working, and don't want to invest any more downtime, in the event it starts failing again. I hope you can understand this from my perspective.
-
1 minute ago, limetech said:
What was it set to before?
also
Was cache also single-device or did you have multi-device pool?
Are all your other plugins/apps exactly the same? That is, if you were using a backup program, are you still using it? etc..
btw, thank you for this information!
My original configuration didn't use or have cache at all. Plex Config was set to /mnt/user/appdata/plex. Appdata (and all other shares) was configured to not use cache. After updating unRaid to 6.7.0, the database corruption started.
While trying to find a fix, I found this link: https://github.com/binhex/documentation/blob/master/docker/faq/unraid.md. Q/A 7 seemed to describe the problem...see below.
I rolled unRaid back to 6.6.7, added a single 240GB SSD cache drive, set appdata to "Cache Only", deleted the Plex folder in appdata, and reinstalled Plex. I ran this configuration for two weeks to make sure it was stable, then updated unRaid to 6.7.0 on June 13th. It has been one week today, running under 6.7.0, and I haven't has a single problem.
I'm running several of the "Community Applications" plug-ins, and several more of the "Dynamix" plug-ins. I haven't made any changes to the plug-ins. I use "CA Backup / Restore" to backup my appdata daily, and haven't made any changes to it either.
Hope this helps...
Q7. I am seeing corruption with the applications database or issues when attempting to run Lidarr/Radarr/Sonarr/Plex/PlexPass, what could be the cause?
A7. Certain applications are not compatible with FUSE, which is part of unRAID, FUSE is used to join or fuse (thus the name) multiple disks together to create a logical view of your media. The FUSE system is seen when you browse any share with /mnt/user/ in the path, such as /mnt/user/appdata. Due to this limitation certain apps need to have their configuration files defined on a non FUSE share, to do this follow the procedure below:-
- Stop the docker container that has the issues
- Left click the icon in the unRAID Web UI and select 'edit'
- Click on the toggle to switch to 'Advanced View' (top right)
- Scroll down to the path defined for /config and change it:-
from
/mnt/user/appdata/<container name>
to (if you have a cache drive):-
/mnt/cache/appdata/<container name>
or (if you do NOT have a cache drive):-
/mnt/disk<number>/appdata/<container name>
- Click on 'apply' to save the change
- Check the application is running.
Note:- If you do NOT have a cache drive and you switch to a specific disk then you may need to reconfigure the application from scratch.
-
1 minute ago, limetech said:
How is this different from the config which was failing after update to 6.7.0?
The original Plex config was /mnt/user/appdata/Plex. The new config is /mnt/cache/appdata/Plex. I also changed appdata to be cache only. I won't say this is the solution for everyone, but it is working for me. It's been a week, and I haven't had a single problem. Before making these changes, it would corrupt within hours, if not minutes.
-
1 minute ago, limetech said:
What file system are you using on your single-disk cache pool?
The default, btrfs...
-
So, it's been one full week since my last post, and everything is still running smoothly.It seems that moving appdata to cache/a single dedicated drive may be the fix for Plex corruption.
-
1 minute ago, AnyColourYouLike said:
Did you also update unraid to 6.7.0?
Your issue sounds like mine. It started working after rolling back to 6.6.x and restoring my Plex database from its own automated backup. (db."<a previous date here>")I rolled back to 6.6.7 on May 31st, and haven't had any problems since then, which should come as no surprise, since the problem seems to follow 6.7.0. I had read that spreading Plex over the array could cause the corruption problem, so I installed a 240gb ssd when I rolled back and set appdata to cache only plus I edited all my docker containers to use /mnt/cache/appdata. To get appdata on to the cache drive, I used MC (midnight commander) to move appdata from all my shares to cache.
I scoff at Triskaidekaphobia so on the 13th, I upgraded to 6.7.0 to see if forcing appdata onto the cache drive would eliminate the corruption problems. So far, I've been lucky, and haven't had any problems. I just hope it lasts, lol. I'll post an update when it crashes again, or in a couple weeks to update my success
-
1
-
-
1 hour ago, EricCharlotteNC said:
No - plex doesn't work. No other changes other than applying the license and the array starting again. Perhaps when the trial expired it corrupted the application?
Just a suggestion, and I'm no expert by any stretch of the imagination...
Assuming you're using Docker (you didn't say), and your plex folder is named 'Plex'.
- Stop plex.
- Rename or move the 'plex' folder in appdata.
- Uninstall plex.
- Reinstall plex.
- See if everything is working.
If it is then you have two choices...
- Sit back and let plex do it's thing. Yeah, I know, a PITA, but this would be my suggestion, or...
- Stop plex. Delete (no need keeping it at this point) the 'plex' folder. Rename or move your new 'plex' folder, the one you created in step 4 above, to its original name. Restart plex. You should be back to where you were in step 5 above.
Good Luck
-
11 minutes ago, jonp said:
Has anyone captured anything in their logs related to the corruption? Either the container logs, the docker logs, or the syslog itself?
On 5/25/2019 at 8:05 AM, iilied said:loading libraries stopped working completely today for unknown reasons with the messages below:
"There was an unexpected error loading the dashboard" and "There was an unexpected error loading this library"
cleaned bundle and optimize database did not solve. tried creating a new library without succeeding, and removing it seems to not work also. first time having an issue with plex in four months now. any idea how to fix this would be appreciated.
log is attached,
cheers
Plex Media Server Logs_2019-05-25_14-57-59.zip 1.54 MB · 2 downloads
iilied posted his logs from plex. Haven't seen anyone post the syslog or Docker logs. I haven't checked my syslog, but my Docker log wasn't very helpful. Plex either starts normally, or it goes into an infinite loop, something like "Starting Plex Media Server", but Plex never starts.
-
2 minutes ago, Squid said:
Downshot is after 3 days error free, then crashing, I'm bats%#t crazy, and afraid to update unRaid in fear that the next update will have the same problems. As a side note, last night, I went back to unRaid 6.6.7, but...I deleted the share, appdata, installed a SSD (cache) drive, and configured appdata to use cache only. I restored appdata from a backup, and rebuilt PLEX from scratch. Now I have the conundrum of staying with 6.6.7 or updating to 6.7.0.
-
3 hours ago, jonp said:
Can anyone using the Plex official Docker Container confirm that this issue affects them as well when using /mnt/user instead of /mnt/cache?
When this first happened to me on May 12th, I spent the following week trying to find a fix, and it happened with the plexinc, linuxserver.io and limetech containers. I didn't try the binhex container, but I would assume it has the same problem.
-
Sadly, my Plex died again.
May 30, 2019 17:09:57.041 [0x14b38a9f4700] ERROR - SQLITE3:(nil), 11, database corruption at line 65066 of [bf8c1b2b7a]
I'm at a loss as to what to do. I'm going back to unRaid 6.6.7.
-
1 hour ago, binhex said:
sadly the issue with certain applications not playing nicely with shfs/fuse is not a new incompatibility, in fact the issue (as detailed below) has been a problem for approx 2 years, possibly longer, it maybe more prevalent now perhaps, but its been a pain for a long time.
So the issue seems to affect any application that uses sqlite, im aware of database corruption caused by the sqlite database being located on /mnt/user/ for the following applications (docker containers) lidarr, radarr, sonarr, plex and plexpass, there could be others.
If a user complains of database corruption, especially if they have just setup the container then my first recommendation is to switch to /mnt/cache/appdata (assuming they have a cache drive) instead, this in most cases is the cause and immediately fixes the issue.
And I can accept incompatibility issues. I've been around too long to take issue with that. I think there are too many people like me, that don't use cache, and go with the default "/mnt/user/appdata/..." and then end up spending a lot of time trying to figure out what went wrong, when an incompatibility pops up. I lucked out and found your unRaid Docker FAQ (https://github.com/binhex/documentation/blob/master/docker/faq/unraid.md), and it set me on the right path. I just hope posting my findings and the link to your FAQ in this thread and a couple of others I've posted to will help others before the damage is done
-
12 minutes ago, iilied said:
okay, thanks to Cessquill's advice for not deleting plex's appdata, and after reinstalling and rebuilding my entire library again — which i don't mind since it's less than 300 media — i realized plex did take few backups of the previous now-corrupted library, which i believe can be restored by renaming it's extension and deleting the corrupted one. (not tested, thought.)
ksman75, this might be of help to you. you can find the backups in '/config/Library/Application Support/Plex Media Server/Plug-in Support/Databases' w/ extension of the date. you might want to give it a try and see where this takes you, since i've already rebuild mine.
Thanks! But I already knew about the backups. Be sure to not delete your newest uncorrupted database. I you restore a corrupted database, you'll be sorry!
Between my movies, music and tv episodes, I have about 10,000 media files. I use the trak.tv plugin in Plex to keep my watched movies and tv episodes in check, so my biggest problem is just the time it takes for Plex to scan my libraries, and to rebuild the metadata and preview/chapter thumbnails. If this fixes my problems, and it's been 3 days now, I'm willing to take that time and have everything back in working order. I mucked around with my database backups so many times that I don't have very much confidence on their integrity at this point.
Limetech support asked about the problem and I replied with a brief account on what I've seen. Hopefully this will all go away soon, and everyone can go back to being clueless and happy, like I was until 3 weeks ago, lol.
-
2 minutes ago, limetech said:
FUSE is a Linux subsystem which means "Filesystems in User Space". The Unraid 'shfs' (share file system) component is what implements the union and is built using FUSE.
That said, any union file system is not going to be fully POSIX compatible. It would be nice to know what is this new incompatibility, this way we can fix it.
This particular problem seems to be unique to unRaid 6.7.0. After updating from unRaid 6.6.7 to 6.7.0, a lot of people are seeing this error in Plex: "There was an unexpected error loading this library". In the Plex log there will be an entry like this: "May 25, 2019 14:57:19.398 [0x7f7fa8f2b700] ERROR - SQLITE3:(nil), 11, database corruption at line 65066 of [bf8c1b2b7a]", and Plex is pretty much dead in the water.
This happened to me within the first few minutes after updating unRaid from 6.6.7 to 6.7.0, back on May 12th. I fought with it for a full week and finally went back to 6.6.7. During the following week I did more research and was led to believe that the corruption problem occurred with the Plex database when the Plex /config path was on /mnt/user/appdata/plex. By configuring /config to be on a single drive (/mnt/disknumber/appdata/plex) rather than in the share file system (/mnt/user/appdata/plex), the problem wasn't happening.
I can't say that this is a problem with the unRaid 6.7.0 update, or something in Plex. I do know that I've been running unRaid 6.7.0 and Plex for the past 3 days and haven't seen the problem since. I made the change as I outlined above. Specifically, I configured my Plex /config fr4om /mnt/user/appdata/plex to /mnt/disk1/appdata/plex, and I haven't had any more problems.
I hope this helps, and am glad to see someone from Limetech taking interest.
-
6 hours ago, Cessquill said:
- Delete the Plex Docker
- Go to your Appdata share and delete the Plex folder - that's where all of its data is (exact name of the folder depends on how you've set it up) (although I'd just rename it for now rather than deleting it altogether, personally)
What Cessquill said.
In addition, stop Plex first, rename (preferred) or delete your old Plex folder. Uninstall Plex, reboot your server and reinstall Plex. I took the advice of Q7 at this link, https://github.com/binhex/documentation/blob/master/docker/faq/unraid.md as well.
Q7. I am seeing corruption with the applications database or issues when attempting to run Lidarr/Radarr/Sonarr/Plex/PlexPass, what could be the cause?
A7. Certain applications are not compatible with FUSE, which is part of unRAID, FUSE is used to join or fuse (thus the name) multiple disks together to create a logical view of your media. The FUSE system is seen when you browse any share with /mnt/user/ in the path, such as /mnt/user/appdata. Due to this limitation certain apps need to have their configuration files defined on a non FUSE share, to do this follow the procedure below:-
Stop the docker container that has the issues
Left click the icon in the unRAID Web UI and select 'edit'
Click on the toggle to switch to 'Advanced View' (top right)
Scroll down to the path defined for /config and change it:-
from
/mnt/user/appdata/<container name>
to (if you have a cache drive):-
/mnt/cache/appdata/<container name>
or (if you do NOT have a cache drive):-
/mnt/disk<number>/appdata/<container name>
Click on 'apply' to save the change
Check the application is running.
Note:- If you do NOT have a cache drive and you switch to a specific disk then you may need to reconfigure the application from scratch.
Step by Step:
- Go to Docker and stop Plex.
- Go to your appdata folder.
- Rename your Plex folder.
- Reboot unRaid. Not necessary, but it will insure everything has been flushed and give you a fresh install.
- Install Plex. Before you click on "APPLY" and after configuring it to your liking, click of the "Show more settings..." dropdown. This is where you set your Plex folder location.
- You will see the default setting, /mnt/user/appdata/<container name>. You want to change this to /mnt/cache/appdata/<container name> if you use a cache drive, or to /mnt/disk<number>/appdata/<container name> if you do not use cache. I don't use cache, so in my case, I changed /config from /mnt/user/appdata/PlexMediaServer to /mnt/disk1/appdata/PlexMediaServer.
- Now click on "APPLY" and you should be good.
Following the above Step by Step, I've been up for almost 22 hours with no errors, longer than it has ever run since updating to unRaid 6.7.0. I hope this helps :)
-
2
-
On 5/25/2019 at 8:05 AM, iilied said:
loading libraries stopped working completely today for unknown reasons with the messages below:
"There was an unexpected error loading the dashboard" and "There was an unexpected error loading this library"
cleaned bundle and optimize database did not solve. tried creating a new library without succeeding, and removing it seems to not work also. first time having an issue with plex in four months now. any idea how to fix this would be appreciated.
log is attached,
cheers
Plex Media Server Logs_2019-05-25_14-57-59.zip 1.54 MB · 0 downloads
Looking at your logs, your database is corrupted. Line 302 of your "Plex Media Server.log" file you will see:
May 25, 2019 14:57:19.398 [0x7f7fa8f2b700] ERROR - SQLITE3:(nil), 11, database corruption at line 65066 of [bf8c1b2b7a]
This started with my server on May 12th, after updating unRaid from 6.6.7 to 6.7.0. I fought with it for a week, and the only fix I could find was going back to unRaid 6.6.7. I have tried the limetech, plexinc and linuxserver Docker containers, and all three get the same error, anywhere from five minutes to a few hours after installing Plex.
I uninstalled Plex, deleted it's folder on appdata, rebooted my unRaid server, and reinstalled Plex several times a day, trying to isolate the problem, but nothing seemed to fix it. On May 20th, I went back to unRaid 6.6.7 and have been running for a week with no errors.
I don't know if it's unRaid or Plex causing the problem, but I have everything working for me, so I'll stick with unRaid 6.6.7 until I know for sure that this problem has been addressed and fixed.
-
1
-
-
I just had a similar problem with things not working after reboot but working manually. Check this thread out and see if it helps...
http://lime-technology.com/forum/index.php?topic=42024.new;topicseen#new
. It's not that I don't want to, but I've finally got it working, and don't want to invest any more downtime, in the event it starts failing again. I hope you can understand this from my perspective.
failed parity and data drive
in General Support
Posted
SOLVED...sorta.
I tried the "Check Filesystem" tests and everything tested good, but the two drives were still marked as bad. I went to "Tools" and chose "New Config", keeping all my settings. Both drives were being flagged with more errors than was possible. I created a "New Config" without keeping my assignments, with the same results. Errors!
I'm using a Zalman MS-800 case three 5 in 3 drive cages/backplanes (two ICY-DOCKs and one Chenbro), two LSI 9207-8i HBAs and supermicro fan-out cables. From top to bottom, left to right, I have my two parity drives followed by my data drives, and my two cache drives on the bottom. To further eliminate power/cable problems, I reversed all my drives except for the cache drives. My new configuration is from bottom to top, right to left, with the two cache drives followed by the two parity drives, then my data drives.
With a "New Config", I added/assigned one drive at a time, started the array, waited a minute or two, stopped the array, then started it again. Doing this with each drive in turn, it took a couple of hours, but every single drive came back online with no errors or loss of data. I finally added/assigned my two parity drives, and am now rebuilding parity. So far, I haven't encountered any problems or errors.
Have I solved this? Only time will tell, but it's looking good for now!