JonathanM

Did you add the port mapping for radarr to the vpn container?

Stock unraid uses apcupsd http://www.apcupsd.org/ which supports a large number of models, not just apc. If your model isn't supported by that, there is a plugin to use NUT https://networkupstools.org/ If neither of those work with it, then you are probably out of luck.

@SNReloaded, I suggest watching some of Spaceinvader One's youtube videos on the subject. He's been doing videos for several years so some of the info in the older videos may be outdated, but the core principles should help you get a grasp on what's going on.

The FAQ has answers to many more questions, it's good to browse through and see if your issue is already addressed.

Sorry I don't speak French, so you will need to translate, but I don't think you will get a response here. Your best bet is at the author's github. https://github.com/Tzahi12345/YoutubeDL-Material/issues?q=is%3Aopen+is%3Aissue

Anything that runs unsupervised should be air cooled with a large enough heatsink that air flow isn't an immediate concern. Liquid cooling only belongs in desktop rigs that run with a person sitting at the console at all times. There is just too much to go catastrophically wrong if something fails with no one to see and react within seconds.

Yep. Just be sure to follow the procedure very carefully.

Read up on CLV vs CAV.

You don't own or control duckdns.org

Add the port mapping for jackett's gui to the vpn container.

This needs to be part of the official documentation for the 6.9 release when it goes final.

Any feedback on this? "Are you sure you want to upgrade from 4.3.24.11355 to 4.3.28.11361?" From what I'm reading here https://community.ui.com/releases/UAP-Firmware-4-3-28/a02af414-6665-4c57-ac03-6e4dac8317e1 I'm very hesitant to pull the trigger, however I saw similar gripes on the thread for what I'm currently using. https://community.ui.com/releases/UAP-Firmware-4-3-24-11355/36d1d2c3-dc75-4f5d-88d9-fb8dda5169ab Anybody running the newer firmware with 0 issues?

LOL! Not what I was hoping to see, but if you are comfortable with that, it's your data!

Sounds reasonable. On first glance I thought you were expecting the data from the removed drives to magically appear on the other drives, but on a second reading I see you know to copy the data to the drives you are keeping in the array. I'm assuming you are confident in the health of all drives, and your backup strategy (not listed here) is tested to your satisfaction. If so, yes, your method will definitely save a bunch of time over doing each operation individually.

2TB older drives are probably 1/3 or less of the data speed of 12TB drives. So there is that.

What drives are currently in the array, and how many of them are making the transition to the new build? The fact that you are using ReiserFS would lead me to believe your current drives are relatively small and slow, so my answer to question 1 is to not use any of those drives in the new build and budget for a pair of large drives, depending on how much data you currently have, maybe 3 large drives. I find it difficult to imagine a system with ReiserFS built in 2012 that couldn't fit completely on a very few 12 or 14TB drives. Keep the old drives intact as backup, and copy them to new drives. PSU could probably use an upgrade, depending on the quality of the caps. No comment on AMD, I'm firmly in the intel camp for now.

https://wiki.unraid.net/The_parity_swap_procedure

Before you throw the baby out with the bath, maybe try using virt-manager?

Increase core count in small steps, benchmarking each step.

Try reducing the number of cores and memory assigned to the VM to a bare minimum and benchmark again. Something like 2 cores and 8GB RAM.

Yep. Zero errors is the only acceptable result. Try testing one stick at a time and see if you can narrow it down.

It's expected that once you passed through a video card, you will be viewing that output on a monitor connected to that card, and using the VM exactly the same as any other computer. If you wish to remote in, you will need to implement remote control software hosted in the VM, exactly like you would if you want to remote in to any other computer. If this thread were about a windows based system, RDP, teamviewer, nomachine, gotomypc, or any of that type of program would be my recommendation. Since it's mac, I'm not familiar with the best remote control options, but I'm sure they've been mentioned in the course of this thread. tldr: Any remote access software that works with mac.

Only root is allowed to log in to the webGUI. Only users OTHER than root are allowed to access the shares vs. SMB.

Those drives without the icon aren't being intercepted by UD, so those can be passed through normally without changing any settings.

At the local console type diagnostics then retrieve the zip file off of the boot USB and attach it intact to your next post in this thread.