The /mnt/user/downloads looks like this:

root@51cdaaebf3fb:/downloads# ls -la
total 18029096
drwxrwxr-x 1 abc  abc           58 Apr 19 16:36 .
drwxr-xr-x 1 root root         230 Apr 24 23:35 ..
drwxrwxr-x 1 abc  abc           12 Apr 24 00:17 dst
drwxrwxr-x 1 abc  abc            0 Oct  3  2018 incomplete
drwxrwxr-x 1 abc  abc        42066 Apr 23 22:58 inter
drwxrwxr-x 1 abc  abc       140120 Apr 23 22:58 nzb
-rwxrwxr-x 1 abc  abc  18461792718 Apr 24 23:59 nzbget.log
drwxrwxr-x 1 abc  abc       114260 Apr 24 23:59 queue
drwxrwxr-x 1 abc  abc            0 Apr 24 23:42 tmp
drwxrwxr-x 1 abc  abc            0 Jan  7  2018 unzipped_torrents

Here are the paths inside nzbget:

5 minutes ago, aneelley said:

Seeing an issue now with nzbget fetching files.  It seems to be looking for a directory called /data but I am seeing error messages, "Could not create directory /data/inter/......then it lists the download (show, etc)"

Where are you seeing this?

1 minute ago, trurl said:

Where are you seeing this?

In the messages for nzbget.  Screenshot:

Is this an NZB you added yourself?

Note, I only have Plex and Nzbget going.  Have not installed radarr or sonarr yet.  

2 minutes ago, trurl said:

Is this an NZB you added yourself?

And you aren't using the appdata from a previous install?

7 minutes ago, trurl said:

Is this an NZB you added yourself?

As in, added to NZBGet manually and since you installed it fresh?

9 minutes ago, trurl said:

And you aren't using the appdata from a previous install?

I swear I deleted it but when I see all those downloads rolling, I am thinking I did not.

5 minutes ago, trurl said:

As in, added to NZBGet manually and since you installed it fresh?

No, it appeared once I started the container.  Not sure what to do at this point.  Really don't want do have to have Plex reload all of it's metadata.

I found out the issue.  So I had removed the appdata/plex folder.  The issue was in /mnt/user/downloads/inter directory.  It was full of intermediate download files.  Removed nzbget container and removing the inter contents and then I will re-install nzbget.

That is done and nzbget has been re-installed.  Now to configure it:

Command:root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='nzbget' --net='bridge' -e TZ="America/New_York" -e HOST_OS="Unraid" -e 'PUID'='99' -e 'PGID'='100' -p '6789:6789/tcp' -v '/mnt/user/downloads/':'/downloads':'rw' -v '/mnt/user/appdata/nzbget':'/config':'rw' 'linuxserver/nzbget' 

64f4bdc0de0c8462ba579f727dfbec2f466c7b777e14f7db2caef0138f3c581e

The command finished successfully!

Installed sonarr:

Command:root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='sonarr' --net='bridge' -e TZ="America/New_York" -e HOST_OS="Unraid" -e 'PUID'='99' -e 'PGID'='100' -p '8989:8989/tcp' -v '/dev/rtc':'/dev/rtc':'ro' -v '/mnt/user/TV Shows/':'/tv':'rw' -v '/mnt/user/downloads/':'/downloads':'rw' -v '/mnt/user/appdata/sonarr':'/config':'rw' 'linuxserver/sonarr' 

f84b490d42416c854d684a40594161adee07dfb87bd8ddb39edcb5767522977c

The command finished successfully!

So far so good.  Everything is processing correctly now.  I just have not re-installed the radarr container.  I will do that tomorrow.

Was on a roll so just went ahead and installed radarr:

Command:root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='radarr' --net='bridge' -e TZ="America/New_York" -e HOST_OS="Unraid" -e 'PUID'='99' -e 'PGID'='100' -p '7878:7878/tcp' -v '/mnt/user/downloads/':'/downloads':'rw' -v '/mnt/user/Movies/':'/movies':'rw' -v '/mnt/user/appdata/radarr':'/config':'rw' 'linuxserver/radarr' 

8d69832c37bb139f09605d32b6aa95968b82b3a8ec5b5263c63ba7c1bf4f340e

The command finished successfully!

To the moderators:  This one can be marked successful.  It is working very well now.  For some reason, the BinHex version of my nzbget was hanging on the unpack and would PPQUEUE a ton of downloads and sort of stop everything up.  The linuxserver version does not do this.  I found an old article from 2018 I think it was that said the BinHex container had that issue so not sure where it ever went with regards to fixing it.  

👍