tjb_altf4

Looks like a recent change that wasn't meant to be set to required. Either those 2 variables should be set to Required=no, or removed completely.

Its usually a setting in the BIOS, Unraid itself can't control this.

out of curiosity, was the casing different? e.g. Tvshows.cfg vs TVShows.cfg (or TVshows.cfg) ?

try dropping the port from POSTGRES_HOST POSTGRES_HOST=192.168.1.163:5432 you are already specifying POSTGRES_PORT and may be causing that option to fail

Its technical debt that would require dev time to change for little gain. That said, it is likely to change when multiple arrays finally gets implemented, and at that point each array can get its own name like pools do currently.

Might need to dig through the user manual. If its not available after a reboot post being recognised, probably needs an additional configuration step. On the onboard HBA with SAS/SATA disks, you need to set usage type (RAID/Non-RAID) before it is available to OS.

Is this the U.2 expansion card? Try clicking on that plus sign on far left, should provide more info. With the Dell SAS controllers, they often need to set to be available to OS (iDrac > Physical Disks > Setup)... guessing it's the same for U.2 drives.

Radarr is normally on port 7878, try using that instead

Not that is part of Unraid, no. I believe you could do something with cgroups to deprioritise processes, but the simpler option is the one I mentioned already.

I usually reduce available available cpu to my dockers so Unraid has dedicated cores, this generally stops the server getting locked out due to compute heavy processes. With Advanced View toggled (or on cpu pinning page in settings), you can either do this in the CPU pinning section by selecting all cores except the first 2 cpu, or you can do the same by adding something like this to Extra Parameters instead: --cpuset-cpus=4-12Note adjust cpu numbers as per your available cores. This invokes the same command, but I personally find it more convenient for many dockers on high cpu count machines. If you are hitting memory limits, there are options for that also, but restricting cpu usually does the job.

You could move the key variables from the template to an envfile, and locate that file somewhere secure and encrypted (I usually go with appdata path). This way the container templates in flash drive would be always sanitised. To enable this, edit the template and adding this to your Extra Parameters field (toggle advanced view in top right): --env-file=/mnt/cache/appdata/homepage/.env edit path to where you prefer, this is an example for homepage env file path. env file itself is fairly simple, in the form VARIABLE=VALUE USERNAME=johndoe API_KEY='HelloWorld1234' DATABASE_URL="http://localhost:5432"

Its a plugin you added to your install called GUI Links, go to plugins and select remove for that plugin

Answered over on Discord, notification is from Dell's idrac (out of band management), unrelated to Unraid. OP mentioned they had sold their Dell server long ago and wasn't reset to default, most likely left email creds in notifications and new owner started setting up alerts.

Your setup is similar to mine, a few things to try: setting the numa flag for cpu explicitly disabling memory ballooning (which won't normally work with pci passthrough anyway) Possibly you also could try falling back to the default display implementation with noVNC. You may also like to enable the guest agent on the Unraid vm for better controls and some info like IP in proxmox

It seems you've already isolated the problem to virtualisation, as you said bare metal runs at expected speeds so I would be more interested in your proxmox vm config than the Unraid config. A screenshot of your proxmox vm's Hardware tab would probably be the most useful

Is your CPU type set to "host" in Proxmox?

Docker natively lets you set limits per container, but not easily for a group. I think for a group you'd need to lean on standard linux tooling like cgroups and manage the cgroup's resources. You can assign a container to a cgroup as explained here: https://docs.docker.com/reference/cli/docker/container/run/#cgroup-parent You'd also have to create and configure the cgroup in this scenario

idrac should log any hardware issues, I would start there.

Tips and Tweaks plugin has cron scheduling for power settings, although it raises a good point and it probably should be part of the built in power management settings.

This is all you need to do, but you need to restart... or possibly force update (rebuild) the container for the envs to stick. note: I've explicitly stated /mnt/cache, but /mnt/user is fine.

From earlier logs: Mar 7 14:22:12 VMs apcupsd[54659]: /sbin/apcupsd: Bogus configuration value (*invalid-cable*) Mar 7 14:22:12 VMs apcupsd[54659]: apcupsd FATAL ERROR in apcconfig.c at line 672#012Terminating due to configuration file errors. Looks like you've not configured ups settings correctly on the native ups service (apcupsd). Share a screen shot of your ups settings page if you are interested in fixing the inbuilt ups configuration

3551 is standard apcupsd communication port, so default port is used even if not specified. I've setup my slave apcupsd service on my windows desktop in a similar way.

Sounds like nzget is being a resource hog and starving the system, try restricting cpu through pinning resources (avoid first 2 cores if possible). example: note: advanced view must be toggled to see this option in docker template

Bump https://docs.docker.com/docker-hub/usage/