Synaptix

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.

Guys, thanks a lot. I appreciate all the help. This community is awesome.

So one at a time won't break anything? Thanks

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.

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.

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.

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.

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.

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!

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.

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?

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!

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?

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).

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?

Noob unRAIDer here. I have a question about how I should go about setting up the downloads for Sab, especially since I'm using a cache drive. Should I set up a user share folder named "downloads" that uses the cache drive and download all my files to it? I assume this will be conflicting since I'll be using the renamer in Sonarr and Couchpotato. Or should I just set up a user share named "downloads", set it to "cache drive only", and let Sonarr and Couchpotato handle the renaming and moving the files to the array after the download completes?

Parity remains synced when any precleared disk can is added to the array. Great, thanks!

Just checked \\tower\flash\preclear_reports and the only .txt files in there are the delta preclear reports. No before and afters. I'm using the preclear plugin. Also, I just finished preclearing two drives and I'm ready to add them to the array. When I stop the array and assign the drives to new slots, can I check that the Parity is already valid since I'm inserting two zeroed drives? I'm primarily asking because if a sync is required, I might as well wait since I'll be receiving my controller and hot swap cages today. And it'll allow me to fully complete my build, and then perform the sync.

That worked. Thanks!

No kidding, is this a bug with the preclear plugin? I can just killed it by going into the tmux sessions and ctrl+C them right?

Looks like I ran into my first issue, after checking "Parity is already valid" and clicking "Start" to start the array, nothing happens. The status bar of the browser just says "Waiting for tower" and nothing else happens. I was running two preclears but they're not part of the array and I didn't think they would affect starting the array. I tried reloading the browser as well as opening the web GUI in incognito mode and nothing is bringing it up. I am able to SSH into the server though. At this point, I'm a bit afraid to reboot it. I was watching the Getting Started videos and as soon as he clicked "Start" it refreshed quickly and it gave him the "Format" button. Any suggestions?

Did you complete preclears? Do you want to post the smart reports so I can double check the drives are good? unRAID requires you assign disks to slots. Your disks are NOT identified by controller and port - they are assigned by manufacturer and serial number. So moving disks to different ports and controllers has zero impact on unRAID. Once, long ago, this was different and more complicated. I and others requested that drives be assigned by manu and serial number, and Tom agreed and made the enhancement sometime in the unRAID 3.1/3.2 days I think. What unRAID is telling you - is that once you assign a disk to an unRAID slot, with dual parity, you can't move it to another slot. Some people (me included), like to keep drives separated by content. For example, drives for TV Shows and drives for Movies. Say I have 1 drive for TV Shows (disk1), and 2 drives for Movies (2,3). And then I fill up my TV show drive, I will want to add another TV show drive. Maybe my OCD says I want that to be disk2. So I'd like to move the Movie disks to slots 3 and 4, and put the new disk in slot2. (Does it matter one bit for user shares? No. But OCD doesn't have to make sense. ) You can do that (with a little effort) with unRAID, but NOT with dual parity. You'd have to make the new disk slot4, leaving the disks in slots 1-3 alone. Unless you are willing to rebuild parity, that is. So you might say - I'd like to leave a gap for a second or even thrd TV Show disk, and therefore put my TV show disk as 1, leave 2 and 3 blank, and then have movies in 4 and 5. I do not have dual parity - so don't know if that is allowed or not. But if it is, that is an option. Preclear looks good, are you referring to the preclear report from the preclear plugin? All of them look identical with the exception of the "194-Temperature_Celsius" and "9-Power_On_Hours" values in the "S.M.A.R.T. Status default" section. All other values in that section show a 0. And above that reads "SUCCESS" for Pre-Reading, Zeroing, Writing preclear signature, verifying preclear signature, and post-read verification. If I understand correctly then, with dual parity, once I build this array with a specific drive assigned to a specific slot (for example, serial# AAAA in the "Disk 1" slot), that #AAAA hard disk can only be assigned to "Disk 1" and nothing else. If I wanted to stop the array, unassign #AAAA from Disk 1 and move #AAAA to Disk 5, I wouldn't be able to do that (unless I rebuild parity).

I am confused by this question, so let me try to explain and maybe you can reask if this doesn't hit it. Parity needs to be equal or greater than the size of your largest data drive. If your largest data drive is 4T, then you'd need one 4T drive for parity, and if you wanted dual parity, you'd need another 4T disk for that. So let's say you have 5 4T drives. 3 would be data, 2 would be parity. You need more space and you'd like to be able to move to 6T drives. So you buy a 6T drive and upsize one parity and have that 4T drive for data (4 4T drives data, 6T and 4T parity). And then you need more space, so you buy a second 6T drive and it replaces the second 4T parity, and you'd use that for data (5 4T drives data, 2 6T drives parity). Then you need more space and buy your third 6T drive. It is added as a data drive. (5 4T drives and 6T drive for data, and 2 6T drives parity). 8T is a pretty good deal right now. You can buy an 8T Seagate Archive drive for about $210. They work very well for unRAID and almost if not less than many 6T drives. $26/T is pretty good. I watched this forum a long time before I bought any, but just bought 2. Both precleared nicely and are in my array. BTW, if at any time you decide - "you know what, I don't need dual parity", you can always remove the second parity and add as a data disk. But I think every new user should have dual parity, as it may save you from a self-inflicted wound (which are the most common here). I shot myself in the foot plenty of times learning - so that's not meant to be critical, its just the way it is. Takes time to learn the ropes. After your first crisis you'll be in a better position to decide if the extra parity cost is worth it. You pretty much nailed it. So to clarify, if I'm using dual parity and decide to to upgrade my parity drives, I don't have to upgrade both at the same time. I can upgrade one parity drive, and then later on, upgrade my second parity drive if I wish? Also, I'm ready to build my first array with dual parity and when clicking start, it warns me with "Dual parity valid requires ALL disks in their original slots". Since this is my first array, technically the state of the current drives are the "original" right? Keep in mind once I receive my controller card and hot swap bays, the ports they're connected to will likely change.

I'm considering going dual parity since with all my hot swap bays, I will have space for 15 drives. I currently do not have 15 drives, but overtime, it will be slowly built to that. I think with that many drives, one parity disk is a bit too risky because the rebuild may take quite awhile (drives in array will range from 3-8TB) and a second drive failure would hurt. The problem I'm seeing though is that if I decide to upgrade my parity drives (currently 6TB), I'm going to need to double-up and upgrade both which will be costly. If I wanted to this route later, would I be able to just assign a drive later to be parity? Decisions, decisions...

Out of curiosity, what happens if I build the array with parity, stop the array, shutdown the server, remove the parity drive, then boot up again without the parity drive? Also, same scenario but instead of removing a parity drive, I remove a data drive from the array and boot the system without it?