Thx And Bye

This is the default behavior for many routers (e.g. OpenWRT) if IPv6 is enabled and the router handles DNS forward. By default they then advertise their own local IPv4 and link-local/ULA IPv6 as DNS servers via DHCP. Usually to support DNS resolutions for your local devices. You wouldn't want to advertise a global DNS server via DHCP in this case.

Retested with 6.12.3 with a full zfs share and btrfs cache pool. Changed Status to Solved

Yes that is correct. I'll keep that pool btrfs then and will report back when this is fixed in a stable release.

I've completed the transfer to all zfs drives now and only have zfs drives in my array. Now the reported space in Windows makes absolutely no sense at all anymore. Installed capacity is 2x16TB and 2x4TB and Windows reports 104TB total space. (currently verifying parity after the removal of the two remaining xfs drives) boxofcare-diagnostics-20230708-1743.zip

Completely missed to create and attach the diagnostic. Sorry for that. boxofcare-diagnostics-20230703-1309.zip

Yes I have Nvidia Driver version 535.54.03 and the latest plexinc/pms-docker installed.

I have this issue on the stable release 6.12.0, I never had this issue prior with any 6.11.x release. Adding a valid nameserver to /etc/resolv.conf instantly fixes the issue. Diagnostics are attached. This issue should be at least be treated as Minor and not just as Annoyance imo. boxofcare-diagnostics-20230623-2255.zip

The output from docker ps -a.txtlooks rather normal to me. Here is the docker inspect 2eda680bcc88.txt but I can't see anything special about it either? Here is the log of the containers starting:container startup logs.txt

Yes I have CA Auto Update Applications installed. The error occurs on manual backups too though and the backup and auto update run at different times anyways. It's always the same container that has this problem (it starts just fine when doing so manually via the webUI). The container is part of a stack deployed via docker-compose (Compose Manager Plugin) and not touched by the auto update. I've also replaced my gzip with pigz for (much) faster compression, but it's likely unrelated as the creation and validation of the archives works just fine.

I'm always getting a failed backup but none of the archives failes to validate. One container failes to start because the image can't be deleted (?) though. But a container not starting correctly shouldn't fail the backup, right? backup.log

Would it be feasible to get a checkbox to run nvidia-persistenced after the driver install on system startup to keep the driver loaded? More information: https://docs.nvidia.com/deploy/driver-persistence/index.html

Yes, two of them have. plexinc/pms-docker has it build in and I've created my own that checks that my VPN container is properly connected.

For now I'm running a user script on a daily schedule as a workaround: #!/bin/bash /usr/local/bin/unraid-api/unraid-api restart

I'm on version 2021.10.12.1921 currently, so it should be the most recent one. But this issue is present at least for a few versions now.