UncleDirtNap

I looked all over disk1 and still don't see anything that I should move. So I went ahead and changed cache=yes to cache=prefer, stopped and restarted the array and no errors since. I do use /mnt/cache/appdata, should I change it to /mnt/user/appdata??

Thanks for the reply! Though I'm a bit unclear on the last part of your instructions; I've looked at all the drives in the array and I don't see any folders or files that appear to have come from or belong on the cache drive. Not sure if I'm looking for the wrong thing (files and/or folders from the containers and data folders) or looking in the wrong place.

Well it happened again. Hoping the issue was just some random corruption of the cache drive I stopped all the containers in my docker, shutdown the server and replaced the cache drive with a brand new, fresh out of the box Seagate Firecuda NVME (previous on was a new Crucial/Micron) Started the server back up, reinstalled the three docker containers (Sonarr, Radarr and Sabnzbd) using the same settings I'd copied from my old server that had been running flawlessly for several years. Server was up and running for exactly 2 days, 2 hours and 55 minutes functioning properly, multiple downloads from both Sonarr and Radarr then out of the blue the errors started again: A couple things different so far, first the messages don't seems to be related to a specific file being download last time (nothing has tried to download recently though and last successful download was 15 hours ago) and I can still write to (copy files, create folders, delete same) the appdata\downloads\complete and appdata\downloads\complete shares from a Windows machine. I'm attaching the diagnostic zip file again, this one taken just minutes after the errors started. stream-machine_new-diagnostics-20220504-1812.zip

Thanks, here it is. Also, just to clarify, it's not the entire cache drive I can't write to as the title indicates, just the appdata\downloads\complete and appdata\downloads\incomplete folders

Literally within seconds of rebooting. SABNZBD is constantly trying to write to the folder, I'm assuming to complete pending downloads and generating a continuous stream of these errors. I brought up the old server that this one was built to replace, it was up and ran fine for a very long time, to do side by side settings comparison and one thing I did notice is that on the old one the appdata\downloads folder shows up in the shares, where as on the new on it doesn't and I have no idea why. I tried to recreate it as a share to see what would happen and it looks like the folder gets created (no errors or anything unusual) but the share isn't there.

Thanks, here it is. Also, just to clarify, it's not the entire cache drive I can't write to as the title indicates, just the appdata\downloads\complete and appdata\downloads\incomplete folders stream-machine_new-diagnostics-20220430-0928.zip

I have this array running (ver 6.9.2) with a few dockers, Sonarr, Radar and Sabnzbd and it's been up and running fine for several weeks. All of a sudden tonight Sabnzbd starts showing these errors and doesn't seem to have permissions to write to the cache drive. Indeed, not just Sabnzbd, but I can't write anything to the appdata\downloads folder on the cache drive and get a permissions error when I try to create folder there from Windows machines as well. The rest of the cache drive is accessible though. Looked at the log file and it's just basically filled with the same errors. Not sure what to do, nothing was changed or updated on this machine recently ... just suddenly started doing this out of the blue. Any suggestions would be greatly appreciated

Only parity1, so I should be good. Thank you!

I think I know the answer to this already, but I don't want to mess up: I recently reduced the number of drives in my array by swapping bigger drives for some smaller ones and then removing a bunch of smaller ones using these instructions: https://wiki.unraid.net/Shrink_array Everything is working fine, but I didn't give much thought to the drive assignments at the time and the former 15 drive array now 7 drive array has drives 1, 3, 7, 9 etc listed on the main page. Just for the sake of cleaning it up visually (and my OCD is nagging me) can I just use the same instructions, change the drive assignment and this time check the Parity is Already Valid box? Or am I just looking for trouble where I shouldn't?

Alright, I'll give that a try, thank you for the assist!

Thanks, greatly appreciate the help.

One more if you don't mind, the existing drive is formatted btrfs, is there a preferred file system to format the new one with? the rest of the array is XFS, okay to make it the same?

This might be a really stupid questions, but does the mover do anything special/hidden/?? other than relocate files from the cache drive to the array and back? What would happen it I just copied all the files & folder on to say an external drive manually after stopping the dockers and disabling them, put in the new drive and formatted it then copied everything back on to the new drive?

Thanks for the reply, didn't help though. I seem to be missing something and not sure what. I tried this process before and keep getting stuck on step 5; I run the mover, it says the option is disabled while the mover is running, keeps running for a bit and then when it appears to stop nothing actually seems to have moved. My appdata folder and all the sub folders remain on the cache drive, none of it appears on any other disk in the array. Not sure what to do at this point

I posted this question about upgrading a cache drive some time ago: The answer I got didn't get me anywhere as the information was outdated, didn't correspond to what I was seeing on my server and I couldn't get anywhere with it. Decided to let it sit and hoped newer versions and updated info might be forthcoming ... then just never got back to it ... until now. Have some free time on my hands so I thought I'd try again but now the original information links are dead and I'm finding even less information on how to successfully do this. Running unRAID 6.9.2 1 Cache Drive Couple Dockers, no VMS Is there updated information on how to replace/upgrade a single cache drive that I'm just missing? Any help would be appreciated as I feel I'm running on borrowed time at this point.

I've been running binhex - Sabnzbd for a while now with no issues when suddenly the last few days I'm getting days warning messages daily on the front pages. It's a big yellowish splat followed by the message: File xxxxxxx[file/part#] "xxxxxx.par2 yEnc" is empty, skipping It seems like it's just informational about a problem par file it's trying to download but given I've never seen even one of these before and now I'm seeing them daily I thought it best to check. Is there anything to be concerned about here?

This could be completely off base but just throwing it out there ... How sure are you that it's Sonarr that is failing? I ask because last week I had a problem with my Kodi library not updating for a few days and I thought stuff wasn't downloading but after digging a bit deeper found that there was an update pending to THETVDB addon that was keeping the files that were being downloaded from appearing in my library. As soon as I updated the addon all the stuff that had previously downloaded appeared. Just a random thought

I'm unfamiliar with Deluge ... so I can't say what would take its place but if you want to use a usenet service you need three additional things .... access to an indexer (nzbplanet, nzbgeek, OZnzb etc) ... something to retrieve relevant information from the indexer (Sonarr, Couchpotato etc) which then hands it off to your download software (Sabnzbd, NZBGet etc) Also, redundancy with the usenet services and indexers isn't a bad idea but be aware that many of the usenet providers are owned and operated by the same two companies .

Indeed, I originally wrote NZBGet and Couchpotato then realizing my error edited it but just made another mistake by changing NZBGet instead of Couchpotato.

Sonarr doesn't handle the downloads, it works in conjunction with things like Sabnzbd or CouchPotato which is where you set up your usenet servers

I figured this out and thought I post in case anyone runs in to the same issue. After poking around my cache drive (where all my docker containers are on my unRAID server) I realized there were multiple locations with the sub-path \downloads\complete (and \incomplete) in them. All of which when selected as the download destination in the settings of SABnzbd appear as \config\downloads\complete. There was also a \downloads folder as well. Adding to my confusion was the fact that one of locations had an uppercase D in Downloads, which the Sonarr error message has as well indicating to me that is where it was looking … it was not. I replaced the config and .ini files for SABnzbd with those from the last working version then downloaded and successfully imported a file to make sure it worked. After doing so I opened up the two \downloads\complete folders, the \Downloads\complete and the \downloads folder and downloaded the same file again and monitored exactly which one the file was actually being downloaded to then put a null text file called This Directory in it. Put the newest config and .ini files back, went into the settings, navigated to the folder with the text file and selected it as the destination folder. I also deleted all the apparently extraneous \download\complete folders. All working now. Two things going on here it seems, the first being that when using the browse function in SABnzbd to select the download destination (and incomplete location) multiple locations all appear as the correct \config\downloads\complete AND the location that Sonarr says its looking for the downloaded file isn’t where it’s actually looking.

Import Failing After Upgrade And I Can’t Figure Out Why Sonarr version (2.0.0.5153): Mono version (5.0.0): OS: unRAID 6.4.1 So this happened to me once before and I thought I had this all figured out, but apparently not. I’m running SABnzbd and Sonar in Docker containers on and unRAID server, from the binhex repositories. After upgrading to the latest version of unRAID both Sonar and SABnzb went belly up so I deleted the containers and started again. Everything is working except that Sonar can’t seem to find the download TV shows and import them to my unRAID server. The following log message seem to indicate Sonarr is looking for them in a nonexistent location from an ancient install from another repository (I don’t know where it’s picking this up from): Import failed, path does not exist or is not accessible by Sonarr: /config/Downloads/complete/Genereic TV Show Nme.S07E04 Episode name.720p.AMZN.WEBRip.DDP5.1.x264-NTb-postbot.1/37de00f3d8f747a3acb0728d88d4ee19.mkv I’ve looked and fiddle with every setting I can find to get Sonar to pointed to the right download folder but I’m obviously missing. Anytime there is a setting field and I click on it, opens right to the correct folder with the downloaded files. I can even go into the Wanted tab on the webgui select Manual Import and the downloaded files are right there in the Recent Folder where I can manually import them. Any help or suggestions would be greatly appreciated. Here’ are my paths for Sonar and Sabnzbd:

One thing to note is that I am reasonably sure that if you use the mv command then files and folders remain on the same disks they are currently located on (I think that under the covers mv will just do a rename). This will only be an issue if you thought they might be redistributed by such an action. ???HUH??? If the share I'm copying from is restricted to disks 4, 5, 6 and 7 and the share I'm copying to is restricted to drives 10, 11, 12 and 13 that would move the files from the first set of drives to the send ... right? That is after all my objective ... to get the files off the RFS formatted drives and onto the XFS drives so I can format the former.

And a wild card is Kosher?

You don't have to do it though Windows Explorer, if you are comfortable with Linux you can move the "t" folder using mv (or another command that works) as well. Going to say this again, because it can't be said too many times. NEVER copy from /mnt/user/Share to /mnt/disk/Share or vice versa. In windows explorer this would be copying from a "Share" to "DiskX" (Where X is the disk number). This causes a file system error that will result in data loss. mnt/user0/share is a special case but I am 99% sure it suffers from the same user share to disk problem. Just to be clear, though, I should be able to move the contents of one share (ex: TV-Shows spread across 5 RFs formatted disks) to another share (ex TV Shows on 5 XFS formatted disks) with no problem right? The shares, are they just directories that I can cd into and do something like a mv * to \(destination share)