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 have a decent size collection of FLAC audio files on my Unraid server and I'm starting to investigate using a RaspberryPi to do HQ audio streaming from my server. I've looked at Volumio, RoPiee and piCorePlayer but these seem to be geared to use with commercial streaming services and at first glance don't mention SMB shares or home media servers. Anyone have a recommendation for something that's particularly well suited for using a RPi to stream audio from Unraid?

Can someone answer some questions about how to proceed with replacing/upgrading my cache drive? I've been doing some spring cleaning on my UNRAID Server (ver 6.6.4), a fairly vanilla setup with 1 parity drive, 13 data drives in the array and a cache drive were my appdata and downloads for three (3) docker containers are located. The cache drive is has been in since this version of the server went up a few years ago and since it gets worked pretty hard I want to put something a bit fresher, and slightly larger in its place. Also, while going over all this I notice that the cache drive file systems is BTRFS, while everything else is XFS and not really sure why that is it's been so long since I set it up. First question is, is my assumption that the cache drive is not part of the array so if I swap out the old drive for a newer it won't rebuild correct? And even if I did it's going to rebuild with with the BTRFS file system, which unless there's some reason I'm missing I don't want to do. And if it isn't part of the array can I just pull the old drive, put in the new one and format it XFS and then copy the data over from the old one and expect everything to run after I reboot? Or is there better way to approach replacing/upgrading this drive that I'm unaware of? Any comments or suggestions would be appreciated.

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?

Wow, I must have looked at that setting half dozen times and not seen it. Thanks!

I'm having the same issue and was going to try the spinup groups next but I'm having some difficulty doing so. I have spinup groups enabled in the settings but even still I'm only seeing one drive at a time being accessed and spun up at a time. So I assume the groups have to be further defined or setup, but I can't find where to create or define groups.

Mmm, hadn't thought of that, I do already have a smaller separate APC unit that I use to keep my networking equipment running Thanks for the suggestion.

I have an unRaid server running version 6.6.4, it's been plugged into a Tripplite SMART500RT1U UPS for awhile just as a dumb unit. Lately we've been experiencing some power issues in our area and after the fourth hard shutdown in two weeks I decided to try and use the smart features to try and setup auto shutdowns. I was hoping it would be fairly straight forward, plug in the USB cable, change some settings etc but no such luck. I've fiddle with some of the settings but best I can come up with is a status message that says "lost communication." I saw mention by someone using the same UPS of running NUT, but can't find any other reference to it and don't know what it is. I've looked at the online manual and it hasn't gotten me any closer. Here are my current settings: I've tried various combinations of different UPS Cable types and UPS types to no avail. Is there a plugin I need to be running? Any other suggestions?

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.