Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

3 Neutral

About naturalcarr

  • Rank
    Advanced Member
  • Birthday 04/06/1994


  • Gender
  • Location
    Manhattan, New York

Recent Profile Visitors

630 profile views
  1. That's what I do, I use the in-app backup, I didn't know about the .db-wal files, though, that makes totla sense, thank you. I'll make sure to delete those the next time something pops up.
  2. I've noticed a new and scary problem that happened specifically to Sonarr, for about 45 minutes, Sonarr would nearly instantly corrupt it's database on 6.7.2. I do have what I'd consider to be a decent docker load running at all times (see the image for proof). On Sunday, Sonarr, Lidarr, Radarr and Plex all corrupted their DBs during a move, Radarr was backed up that Saturday and was easy to restore, for Plex, I ran my script (i'll talk more about it below), and then came Sonarr. I had 3 backups in the Sonarr scheduled backup directory and 2 in the manual, and I have 2 months of backups of those sets mostly from the original CA Appdata Backup/Restore, with my last 3 weeks being on v2. The first 2 databases didn't fix Sonarr's malformed DB (which was weird, because I used the Manual backups that I KNEW were fine when I triggered the backup). Anyway, after trying about 1/2 of my backups none of them fixed Sonarr, and then all of a sudden one worked fine, then I tested some of the backups I'd already tried (because there was no way that ALL of my backups were corrupted for this long), and with the exception of my latest auto backup, and a rogue db from 3 weeks go, they all worked. Now, Sonarr had corrupted these DB files, I had backups upon backups so many of them were backed up redundantly, but every time Sonarr started up on one of the backups, It would corrupt, and even after Sonarr stopped doing that, the DBs were still corrupt, the overlap in backups saved me. I wish I had recorded this better as this just happened on Sunday, but I was tired, and after everything went back to normal, I just deleted all of the corrupted databases Now, as for the script I mentioned, I made this a few months ago to check and manage my plex database files, it checks them, backs up if needed, attempts a repair if needed, etc. You shouldn't run it headless, as it requires user input, although anyone who's done a basic script before can change that with two "#"s. I do apologise if this is the wrong place to post this comment, I just thought that it'd be a good place to get this out to other users who need to work on their DBs a bit during this issue.
  3. I've added this to my own mover script, but a good feature for some would be to have certain docker containers shut down before mover runs and restarted after. For example, Radarr and Sonarr both like to get currupt databases if you run mover and they weren't set to use the cache drive as their appdata directory specifically. I don't have any appdata on my cache drive, as it's only used for speeding up my downloads and file transfers.
  4. So, I've got this up and running, but now I want to put this behind a reverse proxy on nginx. (I only have a free subdomain, not a domain, so I've put all of my reverse proxied services on a subdirectory of that subdomain)
  5. From what I can gather off of forum posts, a few people have been having issues with their rotating logs either filling up the docker.img. Also, good to see you're back in the community, I loved your work (I'm still using your Filebot plugin, I just had to swap out the .jar and .sh files with updated ones, this was also a shameless contrived reason to say hello).
  6. Fixing a Malformed/Corrupted PLEX Database. Hi, all. I'm just here to update you on the "Starting Plex Media Server" issue. For me it was caused by a very malformed database file. I followed this guide which has worked perfectly. I've had a few more corruptions (brought about by failing hardware that I've replaced) but I've been able to bring my library back each time. I wrote this script to automate much of the process, and do some of the most basic backup management (creating backups if your database isn't corrupt/malformed and you agree to a prompt). PLEASE MAKE SURE YOUR TO SET THE TOP 2 VARIABLES! They're fairly self-explanatory, but here is what you set them to: appdata_directory > Your appdata directory plex_container_name > The name of your plex container (the defaults for those are "/mnt/user/appdata" and "plex" respectively) This script requires SQLite3 if you do not have it installed: 1. Go to Community Applications 2. Install the Dev Pack 3. Go to "Settings" in UNRAID 4. Open Dev Pack 5. Enable (install) SQLite3 6. Retry pmsDB.sh Also, please keep in mind that I wrote this script with this linuxserver.io image of plex in mind, it should(?) still work with other plex dockers if you edit the paths in the script, but I'm making no guarantees. Download Script: pmsDB.sh ***EDIT - 5/24/19*** I just updated the script to fix one of my checks (for sqlite3) and improved the error reporting (slightly).
  7. I'll check that out too, I haven't checked on the notification stuff since like 6.1. Also, all of the dockers are finally back up and running. No change in plex, and docker image usage is at 55%.
  8. Yeah, I actually know the values by heart, those S.M.A.R.T. errors have actually had the same values for about 2 years now, I've been checking them every month manually, but luckily they haven't budged, but those are the main reason I wanted to get a backup going. I did turn off the email notifications a while back because I'd get them everyday, twice a day due to the errors.
  9. Theres nothing like that on here. I do have a backup solution planned, but it took me a while just to get the 24ish tb of drives I have now, theres nothing super important on the server (all the media I can pull again, although it'll take a while), but that also means its all equally important to me, and I'll want to back up every bit of it when I get a robust solution sorted out. Also, I turned on the log rotation.
  10. Not on this new installation yet. My old server had it set, I was just going to let plex index everything first, then when I let my clients onto the new one, I'd swap over to the /tmp mapping. As for the docker file, I never knew that, I did have an issue where I misconfigured deluge a while back and my stuff went missing in there somewhere, but I have no idea how I'd clean that up without trashing all of my dockers. **EDIT** I do want to say that the ballooning stopped after I fixed deluge, but I'd already extended my docker image by that point.
  11. Yeah, whenever I have an unexpected shutdown I get them. I had 2 yesterday. I think it has something to do with my rig, I'm running an old SuperMicro server using a M1015 (it flashed) card for JBOD, it also gives me some issues with my cache, so I made sure my appdata (Addonfiles for me) folder isn't on there.
  12. Sure, heres everything. root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='plex' --net='bridge' -e TZ="America/New_York" -e HOST_OS="Unraid" -e 'PUID'='99' -e 'PGID'='100' -e 'VERSION'='latest' -v '/mnt/user/Files/Media/':'/media':'rw' -v '/tmp':'/transcoding_directory':'rw' -v '/mnt/user/addonfiles/dockers/plex':'/config':'rw' 'linuxserver/plex' bross-diagnostics-20190330-1259.zip
  13. Hi, all. I'm setting up a new plex server and it's was chugging along, scanning all of my media. It would become unavailable intermittently, but I thought that was because of the amount of media it was indexing and all of the calls it had to made to TVDB and Movie DB, but after doing a restart after a crash that lasted a while, all I see is "Starting Plex Media Server." in the docker logs, over and over. I've also noticed that in Plex's config folder, this "plexmediaserver.pid" file pops up and disappears intermittently,. It exists for less than a second before it disappears again.