tjb_altf4

Unraid already has guest agent installed, you just need to start it

Current binex-sonarr version is 4.0.15.2941 which is the latest Maybe you locked your image to an older tag in the unraid template settings?

This guide should help you get up and running

First 11 threads are pinned topics, so will always be at the top of the sort

On the Docker page, at the bottom there is a 'Container Size' button, this will retrieve metrics for usage. Container is the application layers itself. Writeable is any volumes, or data being written in unmapped space, and is where to look for problems with individual containers. Log shouldn't be too large, if there are any outliers here you might need to ensure you have log rotation enabled in Docker settings.

Not in Unraid, but I have run a few dual GPU VMs in Proxmox, which is also KVM based like Unraid. It didn't move the primary gpu around, but I only ever SSH or VNC'd into that machine. Is it possible you changed passthrough hardware , or physical hardware multiple times? That would likely change device ordering

The mobile app will work without enabling remote management, but will only work when you are on the network or connected via VPN.

looks like there is a new firmware release with a potential fix, I'll try it next time I'm doing server maintenance.

For this issue, take a look at the Tmux plugin which will keep the terminal session running and allow you to rejoin later. https://forums.unraid.net/topic/183427-plugin-tmux-terminal-manager-ttm/

in my experience, this is usually due to an unsuccessful vpn connection. I've found PIA endpoints go down from time to time for extended periods, try switching to a different PIA endpoint.

I don't believe its hard, nor overly complex... but the mover binary is closed source, and that's where the changes really need to happen to make front end progress visualisation easy.

That firmware release has been withdrawn and no longer available publically pub

Binhex's releases are automated, looks like the source arch package still needs to be updated. Given 2.0.5.5160 is 3 days old, seems odd that not upgrading would create breaking changes... guessing the breaks are going to happen on the other *Arrs

br0.20 has an invalid dhcp pool mask, most likely should be 10.10.20.128/25 Recent releases of Unraid have become more strict around correctness of docker network settings, which is why it might have worked in the past.

Probably a misconfiguration, this would normally live in the system share, e.g. /mnt/cache/system/docker/docker.img It may still be in use, even with old modified timestamp (docker.img inside will have newer timestamp if active). You can check in Settings > Docker to see where your storage path is configured to.

Notifications can be viewed in Unraid here: Tools > Archived Notifications If you really want them in file form, the OS stores them here: /tmp/notification/archive

GitHubUnable to communicate with LidarrAPI - Lidarr API "Intern...Is there an existing issue for this? I have searched the existing open and closed issues Current Behavior Unless I miss something there might be a issue serverside. Especially since I am able to ge...For anyone that wants to keep up with progress

try this format instead: --gpus device=GPU-fd7c39b4-1d44-8d62-02c0-0d559985fa47 more info here: https://docs.nvidia.com/datacenter/cloud-native/container-toolkit/latest/docker-specialized.html

Could you elaborate?

tbh, if everything is regularly backed up, just smash it in a raid0 config unless you need the uptime. I've got a btrfs raid0 (3x hdd) config for my downloads that has been running for 4 years, but nothing irreplaceable or not backed up though!

Take a look at this thread (including the highlight post), or search for other scripts in the forum using "hdparm" as a keyword https://forums.unraid.net/topic/20449-spin-down-spare-drive/#findComment-188344

Ask yourself: Does it really matter if some disks are spinning for 15 min after an array start before the inbuilt spin down processes kick in? If not, leave it be. If it does matter, there's resources on the forum for triggering the spindown via script you could adapt for your needs, and you could use user script plugin to trigger after an array start and/or when any backup scripts finish.

not used this plugin, but I'd imagine you'd need to select the disks for them to be checked

edit the template's Repository field, change tag from :latest to :2024.3.1 (latest published image). that should get you up and running so you can migrate to another image provider, or app