lionelhutz

Fair enough, I've just found that entry level boards can have poor IOMMU groupings which make it range from more difficult to impossible when trying to assign things like USB cards to a VM.

TV with 3 lets seasons split? I've never tried to sort by type with Radarr. If you add movies manually you could add and pick the paths for each one.

I'm curious what you're using that container for if you don't have it pointing to a valid MQTT broker and you don't use Home Assistant?

I would expect Z690 motherboards would be more likely to have good IOMMU groupings for assigning cards to VM's.

I don't believe radarr can do that. I don't see that level of sorting options. What structure were you trying to store? With those settings directories below the Media share won't split. Honestly, I wouldn't recommend the Media share in most cases. Do a share for each type of media.

I'm trying to use a HUSBZB-1 stick and I can't get it to work. I've passed the /dev/ttyUSB0 or USB1 devices to containers but no luck. It's well documented that the USB0 is the zwave and the USB1 is the zigbee. In Home Assistant, the zigbee is recognized and HA suggests installing the ZHA integration. Doing that give the serial number of the stick but it just won't open the radio and ultimately fails. In zwavejs2MQTT it's the same thing, I can't get the zwave radio to work. I tried this container - https://github.com/walthowd/husbzb-firmware by passing the /dev/ttyUSB1 device and I was able to update the radio just fine. Yet, passing the same /dev/ttyUSB1 device to HA fails to work. I tried searching for the HA error in HA but there were only a couple of unresolved threads. Searching for using this stick just says passing the USB0 and USB1 devices works fine. I know those devices can change, but no point changing to a more permanent device mapping until it works. Right now I'm thinking the stick is simply bad, but I wanted to check here in case I'm missing something.

Hmm, my install must have keep an earlier messed up template once I installed it.... I haven't had any other containers act like this one, I guess the original assignments in them must have been fine with how I wanted to use them. When did Media become a default user share that is created by a new unRAID install?

There are these 2 lines in the template <Config Mask="false" Required="true" Display="always" Type="Path" Description="Container Path: /media/frigate" Mode="rw" Default="/mnt/user/Media/frigate" Target="/media/frigate/" Name="Clips path">/mnt/user/Frigate/</Config> ... <Config Mask="false" Required="true" Display="always" Type="Path" Description="Container Path: /media/frigate" Mode="rw" Default="/mnt/user/Media/frigate" Target="/media/frigate" Name="Media path">/mnt/user/Media/frigate</Config> Both are required (forced) and both map to the same container path so it makes absolutely no sense to have it twice. Every time I update the container this screws up my container settings. Every time I have to delete the second one that gets re-added and I also have to delete the media user share that gets created by the mapping because the container re-started after the update. The name and default system paths also don't match in the first one where I underlined them. I don't use a media share so that isn't right for my system. Lots of people don't. I would suggest using the typical /mnt/user/Frigate type path like all the other templates I've used are doing. I would remove the fist one and also remove the Media from the path in the second one. Also, the paths to the GPU and CPU mapping should not be required(forced). I was testing it without a TPU and no GPU acceleration so I deleted those device mappings but updating the container messed that up for me too by adding them back in so I had to delete them again.

The mapping is /data on the container side and /mnt/user/Downloads/ on the unRAID side. So, when working inside the container, ie SAB settings, you use /data. When working in unRAID you use /mnt/user/Downloads/ or the Downloads share over the network. In SAB, you'd use something like /data/complete and /data/incomplete for the completed and temporary download folders. Then, in categories you can simply use a name like tv or movies with no slashes required. If you're using Sonarr, you MUST put the exact same container path and host path in the container settings for it. Some containers have /data for the container path and others have /download which will not work together when the programs exchange information over an API like SAB and Sonarr do.

Sonaar uses the SAB API to to control SAB. SAB tells Sonaar what the directory is where the file was downloaded. This means the mapping in Sonaar for the download location must be exactly the same as SAB on both sides. For example, SAB has this mapped - /downloads On the docker container side to /mnt/user/Downloads/ On the host (unRAID) side. You must map both in the Sonaar docker the exact same. Using /data would be useless so you'd edit or delete it to create your own using /downloads instead.

ryanth - your docker container mappings are fine except I would dump the mapping to incomplete-downloads. It just isn't necessary and makes it more confusing. The container already has access to /mnt/cache/Downloads via the /downloads mapping, so there is no reason to map another directory below that. Most people put the complete and incomplete downloads all into a Downloads share so I have no idea why that SAB container has that extra /incomplete-downloads mapping point. It might be a Folders setting in SAB. In SAB, do you have the temporary download folder set to /downloads/incomplete and the complete downloads folder set to /downloads/complete? You can change the incomplete and complete names if you want, but don't deviate from the /downloads/ part because it must be there to use the mapped Downloads share. Otherwise, the downloads can end up in /config which is /mnt/cache/appdata/sabnzbd on the unRAID side. Once SAB does a download, check that the file is in the complete directory in the Downloads share. If you use categories then it will be in the category directory. If it's not there, then you still have the folder settings in SAB set wrong. mikedputt4120 - if you want to know why I do it, it is so I can share the Downloads as public for reading and writing over the network but NOT share the appdata share at all so it can't get messed up. It is also simpler to get to the downloads when the downloads are in their own share. Besides, It's not outside the box for these Docker containers, but rather quite a normal setup.

Can you mount the remote location so it appears as a local file system? That'd make it easy to access from the Sonar container. If not then login to the Sonar container and see if you can reach the remote server from it.

Yup, I posted /downloads --> /mnt/user/Downloads/ but it can be anything on either side as long the "/downloads" side matches in the different applications and the "/mnt/user/Downloads" side matches in the different applications. Of course, I'm only talking about the applications that talk to each other through an API like Radarr to SABnzbd. I deleted the incomplete mapping in LSIO. I certainly don't need it and I really have no idea why they would even put it in the template. Only reason I can think of is maybe they did it for a setup where SAB can does the post processing itself?????

^^^^^^^^^^^^^^ Don't use that because it will not work. It must be like below. BOTH the container and unRAID sides have to be exactly the same for it to work. FOR ALL /downloads --> /mnt/user/Downloads/ Point completed downloads in SAB to /downloads/complete and incomplete downloads to /downloads/incomplete. When incomplete downloads are in the Downloads share you can just delete this because it's pointless to have it in the container.

You have the containers mapped with /media pointing to your media share but the error says Sonarr tried to put the file into /tv. You either have to change the containers and replace /media with /tv and make sure the server side direction does point to the TV location on the server. Otherwise, set Sonarr to put the file into /media. In Sonarr, go to the Series page and then click the wrench icon for the Last Week Tonight series to see the path. If all series have the wrong path it'd be easier to just change the mapping. You should not need the media share mapped at all in NZBget.

I'm sure there was a reason but it wasn't obvious and after seeing the issue I'm just saying to be careful about using BTRFS with older hardware. Test it and make sure it's stable before jumping in with both feet. I'm not the only one that has had BRTFS corruption occur for no apparent reason. I'm using it fine now on newer hardware since I've done some upgrades in the last year.

You'd think so, but the hardware was perfectly stable using XFS.

My guess would be a Sonarr setup issue. You have /media entered to be used somewhere, likely as the location for the completed files.

I had really bad luck trying BRTFS on my cache drive with a little older hardware like say 6-8 year old parts. The data would start to corrupt after a few weeks. I would recommend you test the stability by setting up a single disk and doing a few days of fairly intense reading and writing to it.

Just to make sure it's clear. A single BTRFS disk file system can detect data errors but it can't correct them. I've seen it confused that the BTRFS check summing will provide error correction, but it's only for the metadata on a single disk.

http://permissions-calculator.org/ The directories from files I wrote to the server via the user shares are drwxrwxrwx which is 0777 and the files are -rw-rw-rw- which is 0666.

It will fix new files. You have to fix the old stuff manually or using the new permissions script. I believe unRAID uses 0666 for files and 0777 for folders as the default.

It's not useful just with certain controllers. It's also useful if you use a single PC to access multiple things on the server at the same time. A PC using SMB makes a single connection to the server. So, the whole network connection hangs while the PC waits for a drive to spin up, even if the hard drive controllers in unRAID can keep responding. If you're playing a video on one monitor and try to access any other file using the second monitor you could get a pause. Of course, this means the spin-up group could include all disks if you truly had a need to fix this SMB issue. The original intent was for the master/slave IDE channels. But, it was found that even with controllers that didn't pause a PC would have hang-up issues if it was multitasking. In my testing, I could access spun-down drives all I wanted from another PC, but if I did it from my media PC while it was playing a video file, the video file would pause unless I used a player that could be set to use a big buffer. I have no idea if NFS also has the issue, but I suspect not. If your PC is using SMB and WMC requests a file that is on a disk which takes time to respond then all network traffic pauses until the disk is spun up and the file is made available. This being an issue or not is something you'd have to test, unless you don't use SMB as the connection.

My bays have power buttons and I don't see any reason to be concerned about swapping disks if they are not mounted.

I have added, pre-cleared and assigned drives without rebooting the server. I just had to stop the array when I assigned each drive then start it again. Preclear and the unassigned devices plugin will work without stopping the array. When upgrading a drive, I would first hot-plug the new drive into a spare slot to preclear it. Then, I would stop the array, pull the drives involved and put the new drive into the slot for the old drive before starting the array again. If I was selling the old drive, after a week or two I'd plug it into a spare slot again to clear it before selling it. I've also upgraded the cache with VM's and Dockers turned off and then plugged the old cache into a spare slot to copy the application data to the new cache before turning the VM's and Dockers back on. I then unmounted the old cache drive and pulled it without stopping the array. You can't actually hot-swap existing array drives with the array started, but having bays and hot-plugging drives is handy.