olympia

Quick correction to my previous post: this turned out to be a false alarm on my end, qBittorrent 5.2.0 works fine. It started with Electorrent failing to connect after the upgrade (which just needed its own update to support 5.2), then I tried opening the WebUI from the Unraid Docker template and it didn't load either, which made me think the upgrade broke the WebUI. Turns out the template was pointing to the wrong port (8080) while the actual WebUI is on 8085. With the correct port the WebUI works fine, and Electorrent is also working again after its update. Sorry for the noise.

+1, I have the same issue. Container log doesn't show any error.

Thanks for the suggestion, but this command also only returns the ip address of running dockers.

Hi all, Is there a way in Unraid to get an overview/list of all IP addresses assigned to Docker containers, across my custom networks, including stopped/offline containers too? Right now the Docker tab only shows IPs for running containers, so to avoid IP conflicts when adding a new container I have to open and edit each stopped container one by one just to see what IP is assigned to it. I’m mainly looking for a GUI solution. I honestly don’t think this needs a whole new dashboard. It would be perfect if the existing Docker view could also show the assigned IP for non-running containers in the same column where running container IPs are shown. Probably with a simple toggle/setting like “show IPs for stopped containers” so users can enable/disable it. Is there any built-in way to do this already, or a plugin that adds it? Thanks!

unraid, running apcupsd as a slave, correctly and immediately sends a notification when the UPS switches to battery (main power loss). However, it never sends a “power restored” notification when the UPS goes back online, even though unraid clearly receives this status update from pfsense, which is running apcupsd as the master. I want unraid to send the power-restored notification in the same way it handles the on-battery event.

I have apcupsd configured as a slave over LAN, connected to my pfSense, which runs apcupsd as the master. Everything works fine — reporting, battery mode notifications, and clean shutdowns — but there’s no notification when power is restored and the system switches back to mains. Any clue from anyone where I should start looking to fix this?

I'm not so sure about this - I probably would have noticed it earlier. Recalling the adjustments I made from the default settings wasn't trivial. I couldn't even realize which settings had been wiped out. I had to go through backups to retrieve my disk settings and recreate all the disk shares along with their permission settings. ...and now this is the third time in a raw I'm going through this process, however, at least I now recall the settings and don't need to look at the backups. It would be fantastic if removing a disk didn't entail all of that. The first time, I couldn't even understand why my array wasn't auto-starting after a reboot or why the disks weren't spinning down, until I realized that all these settings had been reset. Not to mention the disk shares disappearing or user shares not working.

Currently, I'm in the process of upgrading to larger disks and subsequently phasing out smaller ones (replacing 2x8TB drives with a 18TB drive). The procedure I'm following is as follows: 1) Swapping one of the 8TB drives with the 18TB drive and rebuilding from parity. 2) Conducting a disk to disk transfer, copying all data from the second 8TB drive to the 18TB drive. 3) Removing the second 8TB from the array 4) Applying "New Config" tool, since there is no other way to remove disk from the array 5) Rebuilding parity I'm currently in the third cycle of this process and I'm surprised to find that I've lost all my disk shares and disk settings during the "New Config" phase, despite selecting the option to preserve assignments. While the disk assignments (positions) remain intact, all disk shares are disabled by Unraid as a result of "New Config". Moreover, all settings configured under settings/disk are lost. Strangely, I even have to reinitialize the user shares, meaning although the user shares exist, I can't write anything to them until I modify a setting within the user share, click apply, revert the change, and then reapply to restore the desired configuration. Is this behavior intentional? It's been a while since I last used "New Config," but I don't recall it wiping all settings in this manner.

Sure, I don't expect the vdisks to be restored. I have those. So if the content of /etc/libvirt/ gets restored by the plugin to /etc/libvirt/, then the restored files will be written directly into the mounted libvirt.img, so no need to take care of rebuilding this?

I see that, but how can I restore the VMs from this content? I presume, ultimately we need to recreate libvirt.img from these files.

Is there any guide somewhere how to restore libvirt.img file from the vm meta? If I do a restore of VM meta, I only get the content of /etc/libvirt restored, but what would be the way to transform this into libvirt.img?

Yes, I was talking about those Thank you for confirming and apologies if I was not clear enough with my question.

I mean I mount them under /mnt/disks and I don't use any of the other mounting points: addons, remotes and rootshare. If I understand correctly, if I mount a disk to /mnt/disks, then the other mounting points will also be created and no way to control that. Again, I am fine with this, I just wanted to check if there is any option I missed regarding those.

Definitely not a huge issue. I was just wondering if it's normal to have those by default (even if they are not being used) or there is an option to disable them. Those rare moments when I am looking at /mnt directly would have been less cluttered, but again, I am fine with this.