harleywastaken

is the github repo for the docker image not public? i have this up and running, but i'm not seeing logs or configs on my cache drive, just db stuff. everything seems to be working ok but some of my wyze RTSP cameras seem to freeze in the ui; i'd rather look at the log files directly rather than through the unraid web ui...

i'm not using windows, however i'm also seeing drives spin up when i would not expect them to. in your case i'd guess Explorer is trying to read some file metadata (thumbnails for picture files, etc) which cache_dirs cannot help with. in my case i _suspect_ it's sonarr/radarr running in Docker containers doing the same thing as the spin-ups appear to coincide with either app starting a library scan, as well as the Settings > Media Management > File Management > Analyze Video Files option being enabled... hopefully i'll have time to debug further soon. edit: duplicate episodes/movies were my issue - on each scan the duplicate was found and it was scanned for metadata during the process to compare it with the existing episode/movie to see if it should be replaced. once the dupes were removed there was no comparison to be made and the disks do not spin up.

got it, thanks.

sorry, not sure i'm following - the Docker container is using the default of PUID 99 & PGID 100; sonarr itself is set to chown user nobody & group users. if i add a new show sonarr creates a directory for it owned by 65534:users rather than the nobody:users i'd expect. taking a closer look, on unraid nobody maps to uid 99, while inside the container nobody maps to uid 65534 - most likely the mismatch is here, though i would have expected someone else to run into this issue as well. anyone else have a similar setup that's working, or should i just disable permissions in sonarr/radarr and make sure the downloaders are setting them correctly?

i have sonarr set to chown to nobody:users, but it ends up using 65534:users. anyone else have/had this issue?

unfortunately Host Mode didn't help, still seeing "Error getting response stream (ReadDone2): ReceiveFailure" after a while when sonarr tries to talk to nzbget after an undetermined amount of time. anyone else seen a similar issue? edit: looks like this was a resource issue; i set nzbget to pause while checking/verifying/unarchiving yesterday and so far no problems. seems like sonarr has issues seeing that nzbget is up after it thinks its down since it's (probably) not replying if things slow down while unarchiving and still downloading.

i had been running nzbget/sonarr/couchpotato all in bridge mode without issue for years. recently sonarr has had issues communicating with nzbget; it would work for a few hours, then sonarr would throw an error trying to talk to nzbget. the weirdest thing was, if i changed the nzbget host in sonarr from my unraid's hostname to its IP, it would work again for a while, then fail. at that point switching back to the hostname would get it to work for a few more hours, then fail again. after some searching someone said they solved it by linking the docker containers, but this didn't help in my situation. i tried asking in #sonarr, but they threw up their hands as soon as i said docker. at this point i'm leaning towards it being a sonarr issue, but i haven't had the time to break out tcpdump and try to narrow it down to sonarr vs docker. i just switched over to Host mode to test, so far so good.

there are a few different ways to go about it; figured i'd just open an issue - for now you can just kill one of the processes after bringing it up so it doesn't continually try to start.

hmm, must have missed that - was trying to stay up for the end of the preclear cycle, but once i woke up in the living room at 4am on the couch i just went to bed. i'll keep an eye out for the final preclear reports when i preclear the next 3 drives that are currently en-route. thanks!

hi guys, everything looks ok from what i gather, but since this is my first unRAID build a second opinion would put me more at ease - if any more info is needed, please let me know. edit: removed smart reports