[DNS resolution stopping on 6.12.0-rc5 and rc6]

9 hours ago, bonienl said:

When DHCP is used then the server obtains the DNS information from your router.

Using a link-local address as DNS server is wrong and your router should be configured with a global DNS server address instead.

 

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.

[[6.12.2] SMB Share size not including ZFS formatted drives]

Retested with 6.12.3 with a full zfs share and btrfs cache pool.

Changed Status to Solved

[[6.12.2] SMB Share size not including ZFS formatted drives]

5 hours ago, JorgeB said:

that share also exists on your btrfs downloads pool, so it's still the same bug.

 

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

[[6.12.2] SMB Share size not including ZFS formatted drives]

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

[[6.12.2] SMB Share size not including ZFS formatted drives]

2 hours ago, JorgeB said:

Please post the diagnostics.

Completely missed to create and attach the diagnostic. Sorry for that.

boxofcare-diagnostics-20230703-1309.zip

[DNS resolution stopping on 6.12.0-rc5 and rc6]

10 hours ago, nblom said:

Are you using Plex with NVIDIA drivers?

 

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

[DNS resolution stopping on 6.12.0-rc5 and rc6]

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

[[6.9.1] Setting warning/critical temperature in SMART settings not possible]

10 hours ago, limetech said:

Changed Status to Retest

 

It works for me expect for one drive (UnRAID v6.9.2).  

I suspect it has to do with the identifier in the webUI having a dot that is substituted with a underscore in the smart-one.cfg.  

WebUI: Samsung_SSD_850_EVO_M.2_250GB_S33CNX0H506075N  
Conf : Samsung_SSD_850_EVO_M_2_250GB_S33CNX0H506075N

It's the dot in "M.2" that seems to cause the problem as changing the underscore to a dot in the config makes the values appear in the WebUI too.

[[6.9.1] Docker Update Check not reliable for external container]

While I understand that this isn't the intended way to use container on UnRAID and am transitioning over my stacks from docker-compose at some point, I still think that something as basic as checking if a running container has an update available or not should work. 

Ideally the UnRAID UI would support compose files somewhere in an advanced view directly and then deal with those separately from the rest.

[[6.9.1] Docker Update Check not reliable for external container]

Still an issue with 6.9.1 Stable.