UncleDirtNap

Members
  • Posts

    66
  • Joined

  • Last visited

About UncleDirtNap

  • Birthday 08/24/1962

Converted

  • Gender
    Male
  • Location
    Pittsburgh PA
  • AIM
    PaulInShaler
  • YIM
    psgalvanek

UncleDirtNap's Achievements

Rookie

Rookie (2/14)

0

Reputation

  1. 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??
  2. 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.
  3. 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
  4. 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
  5. 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.
  6. 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
  7. 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
  8. Only parity1, so I should be good. Thank you!
  9. 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?
  10. Alright, I'll give that a try, thank you for the assist!
  11. 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?
  12. 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?
  13. 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
  14. 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.