JonathanM

I think the reality of it is that the user to user based support on the forum is so thorough that the actual paid staff really don't poke around much unless summoned. If you need to talk to somebody other than all us volunteers, then either email support, or page one of the Administrators like @SpencerJ or @jonp. I get that you shouldn't have to do that in an ideal world, and one of the paid staff would read every post and respond if one of us volunteers doesn't have a good answer, but so far the volunteers cover things rather well so the paid staff don't react very quickly unless specifically asked. The fact that you are a more advanced user means that your questions are typically NOT going to be easy answers that are common knowledge, so your support experience isn't typical of the newbie questions that we see day in and day out.

Some new AMD boards can have on board SATA issues, it's tough to nail down.

But that's implied by the number. Stating it would be redundant.

Pretty much. Worse, you would lose everything in the emulated disk3 at the same time. You can replace disk3 with an 8TB normally, or a larger drive using https://wiki.unraid.net/The_parity_swap_procedure

You can mount network shares so they show up in unraid, so the primary server would have a remote share mapped. Unassigned devices is one way to mount remote shares.

Yes, but not automatically, and not without possible glitches.

I suggest you two need to work together to get VM USB configuration all in one GUI.

Bridge mode uses Unraid's IP, yes.

Ahh, I've had good luck taping the stick firmly to the case, that way it has a large heat sink area instead of sitting in stale air.

Are you using a full size USB 2.0 stick like the kingston se9?

If you are running the container in bridge mode, change the host port.

https://wiki.unraid.net/The_parity_swap_procedure

As a quick proof of concept, I just added the 7879-7878 mapping to delugevpn, added --net=container:binhex-delugevpn to the extra parameters and changed bridge to none on binhex-radarr, and it works fine using tower:7879 I'm lost as to why it's not working for you. Maybe set up delugevpn as a test? It's not like a ton of work, copy a couple vpn files and type in some settings. 5 minutes tops.

Possibly, but I can't see how. I'm using delugevpn and youtube-dl-material, so no, I'm not comparing apples to apples, but I can't see how using qb and radarr should be any different.

Should be fine. I'll requote the most important bit just to emphasize it. If the drive to be removed has data you want to stay in the array, you must move it yourself to the other data drives.

Best practice is to mount the USB stick inside the case, that way it can't easily get removed or damaged. IDC to USB adapters are cheap.

Very strange. I'm doing something very similar, except I remap the exposed port in the vpn container so I don't have to remove the port allocation when I'm running bridge. Try changing the vpn port map to 7879 host 7878 container, that way you don't have to remove the mapping to test, and can simply use 7879 when radarr is running through the vpn.

What IP is your unraid server? If you temporarily change ONLY radarr net to bridge and remove the --net=container line, does it connect properly?

At some point you will still have to manually move the data from disk 1 to another drive, or rebuild it while at least 1 of the current parity drives is still valid, meaning no other drive changes have been made yet.

How do you think this situation should be handled?

Try with a different browser, or incognito mode.

Not possible, the USB unique guid is what the unraid license is validated against, so an image file can't be licensed.

Multiple ways of scripting this, with varying degrees of difficulty and security. Bottom line, you can start any VM with a console command, how you trigger that command is the interesting part. virsh start <vmname> You could write a user script that checks for the presence of a specific file on a specific share, and when it finds the file, starts the VM and deletes the file. That way you could use an SMB client on the phone to push a small file which would trigger the VM start. You could also directly send the ssh command from the phone, but that would be more complicated on the phone end and less secure. ControlR may have implemented limited users at some point, I don't know.

Post the docker run commands for both containers, redacting passwords if applicable.