Jump to content

isrdude

Members
  • Content Count

    52
  • Joined

  • Last visited

Community Reputation

2 Neutral

About isrdude

  • Rank
    Advanced Member

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I just had a brain malfunction and haven't recovered....where am I going to get 6.7.3-rc3???
  2. I tried having the appdata on disk1 using 6.7.2....when that corrupted, I rebuilt by having appdata on cache drive while still running 6.7.2 and binhex-plexpass. Rebuilt again on cache and rolled back to 6.6.7 about 4 weeks or so ago and still using binhex-plexpass. Not a problems since with any corruption issues. Afraid to try 6.7.3-rc2 since everything is going so well with 6.6.7. I have a backup tower that is running 6.7.2 that I could run 6.7.2-rc3 and then load plex to see what happens. Won't matter on the backup if DB corrupts. I'll consider and let you know if I do and the outcome!
  3. I had to rollback yesterday because of the broken update...all was fine until a few hours ago. My movie library shows up as "There are no items in this library" when I launch Plex from the docker image on unraid. The files are there as the desktop app shows them, but not via the gui. I updated to the just released fixed docker app. Didn't fix the problem. Anyone see this in the past and have a clue how to fix? Thanks
  4. Where I noticed the performance gain was in the metadata matching! I switched to mounting dockers in cache drive first, before I rolled back. It took almost a full day for my movie collection to fetch all the metadata. After another crash, I kept dockers on the cache drive, rolled back to UNRAID 6.6.7. When I started rebuilding the libraries, my metadata downloading was a lot faster. I had same config as always in PLEX but I was then able to tag my movies, music, and tv shows all in under 12 hours. NEVER had this happen before. We're talking a 16TB library here. I know the cache drive helped quite a bit, but until the rollback, never saw rebuilds that were this fast.
  5. I did, I copy pasted it over to your new thread
  6. I too have experienced the corruption issue with my Plex DBs. Sooooo, I took the first suggestion and changed my appdata location to /mnt/disk1....rebuilt everything....lasted for not even 28 hours before I was back to corrupted DBs. I deleted everything related to Plex Docker, started over using binhex-PlexPass, set appdata location to /mnt/disk1....corrupted again, but lasted for 2 days this time. Back to the drawing board, same set up with binhex-PlexPass and location, BUT, returned my UNRAID to 6.6.7. Everything is running stable so far now for 3 days. Here's what I found when I went to the logs to see what was causing the issue First, everything was relatively stable until I started added media content to my library After a few loads, I would see that the media was being updated into Plex even though it was on the drive and in proper Plex format Next, when I went to my TV Shows, it would show zero seasons, but if you clicked on the thumbnail, to go to the individual season folders, they'd be there, go back to home and then try to get back, you couldn't! It would show library as empty. If I went to movie folder and clicked on it, I would see the movies I had without the ones I just loaded. When I went back to home, all the sudden my movie library showed as zero. In both cases, TV Shows and Movies, once they showed zero, then all the library folders showed zero content and I would get the gray screen of death. Looked at log files, and sure enough, in every corruption case, it shows Sqlite errors, Seems with what I'm seeing now, defining the appdata location to cache or diskX, and going back to unraid 6.6.7 is the way to go. I just hope this gets fixed on the Sqlite side as I'm nervouse that this could only be a band-aid if Plex alters some of their coding. I hope this provides some more data to help fix the issue. 
  7. I too have experienced the corruption issue with my Plex DBs. Sooooo, I took the first suggestion and changed my appdata location to /mnt/disk1....rebuilt everything....lasted for not even 28 hours, I was uploading data, and then, I was back to corrupted DBs. I deleted everything related to Plex Docker, started over using binhex-PlexPass, set appdata location to /mnt/disk1....corrupted again, but lasted for 2 days this time. Once again, I was uploading data when issue occured. Back to the drawing board, same set up with binhex-PlexPass and location, BUT, returned my UNRAID to 6.6.7. Everything is running stable so far now for 3 days. Here's what I found when I went to the logs to see what was causing the issue First, everything was relatively stable until I started adding media content to my library After a few loads, I would see that the media was not being updated into Plex even though it was on the drive and in proper Plex format Next, when I went to my TV Shows, it would show zero seasons, but if you clicked on the thumbnail, to go to the individual season folders, they'd be there, go back to home and then try to get back, you couldn't! It would show library as empty. If I went to movie folder and clicked on it, I would see the movies I had without the ones I just loaded. When I went back to home, all the sudden my movie library showed as zero. In both cases, TV Shows and Movies, once they showed zero, then all the library folders showed zero content and I would get the gray screen of death. Looked at log files, and sure enough, in every corruption case, it shows Sqlite errors. I'm wondering if media uploading, metadata uploading, etc., is causing the Sqlite issues leading to the corrupt databases? Seems with what I'm seeing now, defining the appdata location to cache or diskX, and going back to unraid 6.6.7 is the way to go. I just hope this gets fixed on the Sqlite side as I'm nervouse that this could only be a band-aid if Plex alters some of their coding. I've been doing extensive uploading of movies and TV shows and so far, databases holding up and Plex functioning normally! I hope this provides some more data to help fix the issue.
  8. No idea. Was searching for that myself both here and on Plex. Supposedly, it can be done but it appears to me, it wouldn't delete your files or alter them, but you'd have to go through the entire process of loading the docker image and creating paths, containers, etc....which means all your data will need to back through Metadata search and tagging.
  9. Has anyone notice with latest plex build (Version 1.15.4.993) that Plex will stop when uploading files or adding new library? Never seen it do that before. Simple fix, just go to dashboard and restart but........
  10. JohnathanM.....great news! I shut down, pulled the plug, went to off on the psu, pulled the LSI card, turned back on rebooted. Got errors, many in fact, as I expected. Powered down, pulled plug and turned off psu again, replaced LSI card, hooked power back in, powered up, and Voila! Now have all good disk showing and unit went straight to parity sync! Best of all, the disk that was nothing but read errors is running without error!! I'm thinking I'm buying some new cables!
  11. Sigh, while I was waiting, I did that. Went to new config, check the box that I wanted to do that....selected it...went back to array and nothing. Still the same issue. Tried a reboot, and still the same. Nothing is working and I'm about ready to see how far an unraid array can fly
  12. I'm sorta thinking best move would be to power completely down, to include pulling the plug, pull out and reseat the LSI controller, then reattach the cables. Just not sure if that will make matters worse or do nothing.
  13. Nope! Like I said, complete new install. Haven't gotten to the data loading stage yet....thankfully.
  14. Here goes.....I recently had 2 major drive failures. That's OK as I had new ones to put in and besides that, some of the drives were old and I wanted to replace them any way. Sooooo, I started from a completely new, clean install. Everything went great was able to preclear drives, format, etc. Got to parity sync and all started well except for one drive when read was coming back with nothing but constant errors. I stopped the parity sync as I decided, since this is a fresh install, why start with error indicators. I checked the sata cable and found that the tip was bad and probably wasn't making good connection. I had 3 start cables from my LSI Logic LSI00344 9300-8i SGL SAS 8Port 12Gb/s PCIE3.0 HBA Controller, so I swapped, rebooted...Now I get nothing but a missing disk indication, I can't clear it, I won't let me put in another drive, I can't start array. I have all new cables for the controller coming but I can't believe I have multiple cable errors as other drives connected to the controller are being read just fine. Anyone have any thoughts? I hope....
  15. I also see after the scan that the count is zero