Jump to content

Synaptix

Members
  • Content Count

    45
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Synaptix

  • 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 recently changed my dual parity drives from 6 TB to 8 TB. After adding the old 6 TB drives back into the array as data drives, I noticed that they're both taking 6.60 GB of space each even though they're empty. What would be causing them to take a total of 13.2 GB of space away from my array? I attached a screenshot for reference.
  2. Guys, thanks a lot. I appreciate all the help. This community is awesome.
  3. So one at a time won't break anything? Thanks
  4. I have two 6 TB parity drives in my setup and looking to upgrade to two 8 TB drives down the road. Might be a dumb question, but do I need to upgrade both drives simultaneously? Or can I upgrade one to 8TB, and the other later? My assumption is that both will need to be stopped and replaced at the same time. And the instructions would be to just follow the parity drive replacement guide, but do it for both parity drives (stopping, unassigning, etc.) as opposed to one parity drive in the instructions.
  5. The download user share is set to cache only so there's no additional drive to spin up. In addition, the appdata folder is also set to cache only and all docker contains run off the cache. I would think that an SSD would have no problems with disk I/O, which is why this is strange to me.
  6. Is anybody experiencing their server completely unresponsive whenever Sabnzbd is unpacking? Honestly, I'm not sure if this is a problem with Sabnzbd or Radarr. Whenever a movie is finished downloading and unpacking, it completely freezes my server, where docker containers' WebGUI are unresponsive and Plex stops streaming a movie. Once it is unpacked, everything starts up again.
  7. Setup reverse proxy It takes a few minutes for Ombi to check if the content requested is available. You can change the min intervals under Settings - Scheduled Jobs under Plex Availability Checker. It has nothing to do with the docker itself. If you're still having issues feel free to PM me. Thanks for the help. I tried changing the checker interval and even manually ran it by clicking the refresh icon next to the availability checker and the status hasn't changed.
  8. I'm not sure if this is an Ombi issue or a docker issue, but whenever a specific episode is requested, it downloads and adds it to Plex, but the "Request Status" in the "Requests" section never changes. It just keeps showing "Processing Status" even though the episode is available.
  9. I noticed that the auto-updater is already disabled in Radarr and Sonarr from linuxserver.io. I'll just update the container as they come along then. Thanks!
  10. Sorry for the bump. But how are you guys updating Radarr since it default installs the "develop" build? And https://github.com/Radarr/Radarr/wiki/Docker---Why-not-to-use-Develop-or-Nightly says not to update the docker container.
  11. I'm still new to unRAID and have installed several dockers. My dashboard shows that there is an update for Radarr, however, according to this: https://github.com/Radarr/Radarr/wiki/Docker---Why-not-to-use-Develop-or-Nightly, I'm not supposed to update the container. I am currently on the "develop" Branch, which is what the linuxserver.io repository installed by default. How do I ago about updating this?
  12. I don't see why you think that it would conflict...(since the two options you've stated are the same) But you do generally set up a downloads share, setup Sab, Sonarr, and CP with the exact same mappings for it, and CP/Sonarr will properly find the downloads when sab is finished and then move them wherever you specify Do I set the "download" user shares to cache only since the renamer on Sonarr and CP will be doing the moving, and not the mover script? Myself, I set it to "prefer" so that in case of an absolutely huge file that may not fit on the cache drive the overflow will go to the array. CP/Sonarr will probably be moving it to a Movies share or a TV share which you will set to be either use cache yes or no depending upon your preference. Wait, so I have to set the movie and TV shares to use cache as well? I thought they could be set to not use cache since the files will be moving from the "download" user share (stored on cache) to the array (where TV and movie user shares are). Any share can be set to use the cache or not (or only use it as in the case of downloads) If say your movie share is set to use cache, the CP will move it from the downloads share (cache only/prefer) to the movie share, and the file will stay on the cache drive until mover comes along and moves it to the array. Even with the file sitting on the cache drive (in the movie share), it is still part of the movie share and you can watch it from there... That's where I'm kinda confused. Let's say for example a cache is set to be used on a TV share at /tv, and I download a TV show to /download/completed (a cache only share), Sonarr will rename and move it from /download/completed to /tv. So you're saying that because cache is set to be used on /tv, Sonarr is really creating a /tv on the cache drive, and moving the file to there because cache is set on /tv? It just looks like it's moving it to the array but it's not? Correct and your playback devices can't tell the difference either you set a share to use the cache if you want faster writes to the share and if you're not worried about losing the file in the event you have a cache drive failure before the mover kicks in at 4am to actually move it to the parity protected array Sent from my SM-T560NU using Tapatalk That's pretty damn cool. Thanks for the help!
  13. I don't see why you think that it would conflict...(since the two options you've stated are the same) But you do generally set up a downloads share, setup Sab, Sonarr, and CP with the exact same mappings for it, and CP/Sonarr will properly find the downloads when sab is finished and then move them wherever you specify Do I set the "download" user shares to cache only since the renamer on Sonarr and CP will be doing the moving, and not the mover script? Myself, I set it to "prefer" so that in case of an absolutely huge file that may not fit on the cache drive the overflow will go to the array. CP/Sonarr will probably be moving it to a Movies share or a TV share which you will set to be either use cache yes or no depending upon your preference. Wait, so I have to set the movie and TV shares to use cache as well? I thought they could be set to not use cache since the files will be moving from the "download" user share (stored on cache) to the array (where TV and movie user shares are). Any share can be set to use the cache or not (or only use it as in the case of downloads) If say your movie share is set to use cache, the CP will move it from the downloads share (cache only/prefer) to the movie share, and the file will stay on the cache drive until mover comes along and moves it to the array. Even with the file sitting on the cache drive (in the movie share), it is still part of the movie share and you can watch it from there... That's where I'm kinda confused. Let's say for example a cache is set to be used on a TV share at /tv, and I download a TV show to /download/completed (a cache only share), Sonarr will rename and move it from /download/completed to /tv. So you're saying that because cache is set to be used on /tv, Sonarr is really creating a /tv on the cache drive, and moving the file to there because cache is set on /tv? It just looks like it's moving it to the array but it's not?
  14. I don't see why you think that it would conflict...(since the two options you've stated are the same) But you do generally set up a downloads share, setup Sab, Sonarr, and CP with the exact same mappings for it, and CP/Sonarr will properly find the downloads when sab is finished and then move them wherever you specify Do I set the "download" user shares to cache only since the renamer on Sonarr and CP will be doing the moving, and not the mover script? Myself, I set it to "prefer" so that in case of an absolutely huge file that may not fit on the cache drive the overflow will go to the array. CP/Sonarr will probably be moving it to a Movies share or a TV share which you will set to be either use cache yes or no depending upon your preference. Wait, so I have to set the movie and TV shares to use cache as well? I thought they could be set to not use cache since the files will be moving from the "download" user share (stored on cache) to the array (where TV and movie user shares are).
  15. I don't see why you think that it would conflict...(since the two options you've stated are the same) But you do generally set up a downloads share, setup Sab, Sonarr, and CP with the exact same mappings for it, and CP/Sonarr will properly find the downloads when sab is finished and then move them wherever you specify Do I set the "download" user shares to cache only since the renamer on Sonarr and CP will be doing the moving, and not the mover script?