citizengray

Thx !

Ok never mind, somehow my array didn't stop properly. Nothing that I reboot didn't fix. Here is the new diagnosis.unraid-diagnostics-20250314-1328.zip

Sorry... I feel stupid, but I can't find a way to change the setting ? I tried disabling the array, but that setting is always grayed out

Here you go

Ohh I found the setting - my bad. But it's set a 200KB not 200GB ? So it shouldn't be that ?

Thx ! That was fast ! However I don't see this setting by clicking on any drives ? What would that setting be so high !? Does it affect the entire disk pool, or just the cache pool ?

I have been looking at this for hours, and I can't find anything My appdata is on the cache drive. - Cache drive has 198GB free. - Appdata has Minimum free space set to 0 - Docker Image is 20GB and only 2.74GiB used I can't figure out what is happening Help. unraid-diagnostics-20250314-1116.zip

Well ! A very big thank you for giving me all the details about Jumbo frame... I guess I am that old that "back in my days" we would always aim to enable jumbo frames to get the max speed out of the ethernet transfers... but since I haven't dabbled in networking stuff for a long while - this is my first run with 10Gbps - it does feel kinda useless now ! I'll leave it off then Problem solved ! Thx

I have 2 NIC, the Intel mentioned in the title and some onboard 1 Gbps NIC. The onboard was configured with 1500 MTU and the Intel with 9000 MTU. They are both connected to different networks, and for the life of me I could never figure out why I could never access unraid's admin page (or ssh for that matter) through the Intel sub-network. Until I played enough with it that I realized that when I lowered the MTU to the defaults 1500 it suddenly started working !?! So I removed all my Jumbo frames configuration on my network - I do get slightly less performance (~8k Gbps vs ~9.5 Gbps) but now I can access unraid from the right network (the other sub-network on the 1 Gbps onboard NIC was meant to be a temporary transition). I find this so weird and could not find any online content about it... anyone else noticed this ?

it should be eth0 I assume ?

SubnetL 192.168.86.0/16 Gateway: 192.168.86.1 DHCP pool: not set

What seems to me the most interesting lead so far (from reddit): This is the last 100 lines of the log (indeed it looks fishy, `subnet 172.17.0.1` !?!) root@unraid:~# tail -n 100 -f /var/log/syslog Dec 27 10:46:53 unraid nmbd[19858]: [2021/12/27 10:46:53.500183, 0] ../../lib/util/become_daemon.c:135(daemon_ready) Dec 27 10:46:53 unraid nmbd[19858]: daemon_ready: daemon 'nmbd' finished starting up and ready to serve connections Dec 27 10:46:53 unraid root: /usr/sbin/winbindd -D Dec 27 10:46:53 unraid winbindd[19868]: [2021/12/27 10:46:53.531777, 0] ../../source3/winbindd/winbindd_cache.c:3203(initialize_winbindd_cache) Dec 27 10:46:53 unraid winbindd[19868]: initialize_winbindd_cache: clearing cache and re-creating with version number 2 Dec 27 10:46:53 unraid winbindd[19868]: [2021/12/27 10:46:53.532694, 0] ../../lib/util/become_daemon.c:135(daemon_ready) Dec 27 10:46:53 unraid winbindd[19868]: daemon_ready: daemon 'winbindd' finished starting up and ready to serve connections Dec 27 10:46:53 unraid emhttpd: shcmd (317): /usr/local/sbin/mount_image '/mnt/cache/system/docker/docker.img' /var/lib/docker 20 Dec 27 10:46:54 unraid kernel: BTRFS: device fsid 84ac4ceb-da34-4f58-9fbd-0384a4bcc3e1 devid 1 transid 870852 /dev/loop2 scanned by udevd (19910) Dec 27 10:46:54 unraid kernel: BTRFS info (device loop2): using free space tree Dec 27 10:46:54 unraid kernel: BTRFS info (device loop2): has skinny extents Dec 27 10:46:54 unraid kernel: BTRFS info (device loop2): enabling ssd optimizations Dec 27 10:46:54 unraid root: Resize '/var/lib/docker' of 'max' Dec 27 10:46:54 unraid emhttpd: shcmd (319): /etc/rc.d/rc.docker start Dec 27 10:46:54 unraid root: starting dockerd ... Dec 27 10:46:54 unraid kernel: Bridge firewalling registered Dec 27 10:46:54 unraid avahi-daemon[10826]: Joining mDNS multicast group on interface docker0.IPv4 with address 172.17.0.1. Dec 27 10:46:54 unraid avahi-daemon[10826]: New relevant interface docker0.IPv4 for mDNS. Dec 27 10:46:54 unraid avahi-daemon[10826]: Registering new address record for 172.17.0.1 on docker0.IPv4. Dec 27 10:46:55 unraid rc.docker: b5c6b4129a563eb7bf3332aa3e18941c085aa843ab017ec3824ed89718f83201 Dec 27 10:46:55 unraid kernel: docker0: port 1(vethcd43b4d) entered blocking state Dec 27 10:46:55 unraid kernel: docker0: port 1(vethcd43b4d) entered disabled state Dec 27 10:46:55 unraid kernel: device vethcd43b4d entered promiscuous mode Dec 27 10:46:55 unraid kernel: docker0: port 1(vethcd43b4d) entered blocking state Dec 27 10:46:55 unraid kernel: docker0: port 1(vethcd43b4d) entered forwarding state Dec 27 10:46:55 unraid kernel: docker0: port 1(vethcd43b4d) entered disabled state Dec 27 10:46:55 unraid kernel: cgroup: cgroup: disabling cgroup2 socket matching due to net_prio or net_cls activation Dec 27 10:46:55 unraid kernel: eth0: renamed from veth0a9be5a Dec 27 10:46:55 unraid kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethcd43b4d: link becomes ready Dec 27 10:46:55 unraid kernel: docker0: port 1(vethcd43b4d) entered blocking state Dec 27 10:46:55 unraid kernel: docker0: port 1(vethcd43b4d) entered forwarding state Dec 27 10:46:55 unraid kernel: IPv6: ADDRCONF(NETDEV_CHANGE): docker0: link becomes ready Dec 27 10:46:55 unraid rc.docker: NoIp: started succesfully! Dec 27 10:46:56 unraid rc.docker: Plex-Media-Server: started succesfully! Dec 27 10:46:56 unraid kernel: docker0: port 2(vethce8951e) entered blocking state Dec 27 10:46:56 unraid kernel: docker0: port 2(vethce8951e) entered disabled state Dec 27 10:46:56 unraid kernel: device vethce8951e entered promiscuous mode Dec 27 10:46:56 unraid kernel: docker0: port 2(vethce8951e) entered blocking state Dec 27 10:46:56 unraid kernel: docker0: port 2(vethce8951e) entered forwarding state Dec 27 10:46:56 unraid kernel: docker0: port 2(vethce8951e) entered disabled state Dec 27 10:46:56 unraid kernel: eth0: renamed from veth8bed2e9 Dec 27 10:46:56 unraid kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethce8951e: link becomes ready Dec 27 10:46:56 unraid kernel: docker0: port 2(vethce8951e) entered blocking state Dec 27 10:46:56 unraid kernel: docker0: port 2(vethce8951e) entered forwarding state Dec 27 10:46:56 unraid rc.docker: radarr: started succesfully! Dec 27 10:46:56 unraid kernel: docker0: port 3(veth081108c) entered blocking state Dec 27 10:46:56 unraid kernel: docker0: port 3(veth081108c) entered disabled state Dec 27 10:46:56 unraid kernel: device veth081108c entered promiscuous mode Dec 27 10:46:56 unraid kernel: docker0: port 3(veth081108c) entered blocking state Dec 27 10:46:56 unraid kernel: docker0: port 3(veth081108c) entered forwarding state Dec 27 10:46:57 unraid kernel: eth0: renamed from veth02a7ef7 Dec 27 10:46:57 unraid kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth081108c: link becomes ready Dec 27 10:46:57 unraid rc.docker: sabnzbd: started succesfully! Dec 27 10:46:57 unraid avahi-daemon[10826]: Joining mDNS multicast group on interface docker0.IPv6 with address fe80::42:6dff:fe87:800. Dec 27 10:46:57 unraid avahi-daemon[10826]: New relevant interface docker0.IPv6 for mDNS. Dec 27 10:46:57 unraid avahi-daemon[10826]: Registering new address record for fe80::42:6dff:fe87:800 on docker0.*. Dec 27 10:46:57 unraid kernel: docker0: port 4(veth1d5370d) entered blocking state Dec 27 10:46:57 unraid kernel: docker0: port 4(veth1d5370d) entered disabled state Dec 27 10:46:57 unraid kernel: device veth1d5370d entered promiscuous mode Dec 27 10:46:57 unraid kernel: docker0: port 4(veth1d5370d) entered blocking state Dec 27 10:46:57 unraid kernel: docker0: port 4(veth1d5370d) entered forwarding state Dec 27 10:46:57 unraid kernel: eth0: renamed from vethc371dd8 Dec 27 10:46:57 unraid kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth1d5370d: link becomes ready Dec 27 10:46:57 unraid avahi-daemon[10826]: Joining mDNS multicast group on interface vethcd43b4d.IPv6 with address fe80::34d8:e2ff:fe21:f642. Dec 27 10:46:57 unraid avahi-daemon[10826]: New relevant interface vethcd43b4d.IPv6 for mDNS. Dec 27 10:46:57 unraid avahi-daemon[10826]: Registering new address record for fe80::34d8:e2ff:fe21:f642 on vethcd43b4d.*. Dec 27 10:46:57 unraid rc.docker: sonarr: started succesfully! Dec 27 10:46:58 unraid avahi-daemon[10826]: Joining mDNS multicast group on interface veth081108c.IPv6 with address fe80::4825:35ff:fef0:968. Dec 27 10:46:58 unraid avahi-daemon[10826]: New relevant interface veth081108c.IPv6 for mDNS. Dec 27 10:46:58 unraid avahi-daemon[10826]: Registering new address record for fe80::4825:35ff:fef0:968 on veth081108c.*. Dec 27 10:46:58 unraid avahi-daemon[10826]: Joining mDNS multicast group on interface veth1d5370d.IPv6 with address fe80::cc68:61ff:fef9:d3cd. Dec 27 10:46:58 unraid avahi-daemon[10826]: New relevant interface veth1d5370d.IPv6 for mDNS. Dec 27 10:46:58 unraid avahi-daemon[10826]: Registering new address record for fe80::cc68:61ff:fef9:d3cd on veth1d5370d.*. Dec 27 10:46:58 unraid avahi-daemon[10826]: Joining mDNS multicast group on interface vethce8951e.IPv6 with address fe80::e050:5fff:fee0:8df8. Dec 27 10:46:58 unraid avahi-daemon[10826]: New relevant interface vethce8951e.IPv6 for mDNS. Dec 27 10:46:58 unraid avahi-daemon[10826]: Registering new address record for fe80::e050:5fff:fee0:8df8 on vethce8951e.*. Dec 27 10:46:59 unraid kernel: process '7b37335f9343e2628ef6b509290440ad894ddac97530c6a23ecbac032c5f7bc0/usr/bin/par2' started with executable stack Dec 27 10:47:16 unraid nmbd[19858]: [2021/12/27 10:47:16.523353, 0] ../../source3/nmbd/nmbd_become_lmb.c:397(become_local_master_stage2) Dec 27 10:47:16 unraid nmbd[19858]: ***** Dec 27 10:47:16 unraid nmbd[19858]: Dec 27 10:47:16 unraid nmbd[19858]: Samba name server UNRAID is now a local master browser for workgroup WORKGROUP on subnet 192.168.86.100 Dec 27 10:47:16 unraid nmbd[19858]: Dec 27 10:47:16 unraid nmbd[19858]: ***** Dec 27 10:47:54 unraid ntpd[1918]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized Dec 27 10:47:56 unraid ntpd[1918]: frequency error 7077 PPM exceeds tolerance 500 PPM Dec 27 10:50:20 unraid avahi-dnsconfd[10836]: DNS Server 169.254.172.251 removed (interface: 8.IPv4) Dec 27 10:50:20 unraid avahi-dnsconfd[10836]: Script returned with non-zero exit code 1 Dec 27 10:50:34 unraid avahi-dnsconfd[10836]: New DNS Server 192.168.86.249 (interface: 8.IPv4) Dec 27 10:50:34 unraid avahi-dnsconfd[10836]: Script returned with non-zero exit code 1 Dec 27 10:52:35 unraid nmbd[19858]: [2021/12/27 10:52:35.751351, 0] ../../source3/nmbd/nmbd_become_lmb.c:397(become_local_master_stage2) Dec 27 10:52:35 unraid nmbd[19858]: ***** Dec 27 10:52:35 unraid nmbd[19858]: Dec 27 10:52:35 unraid nmbd[19858]: Samba name server UNRAID is now a local master browser for workgroup WORKGROUP on subnet 172.17.0.1 Dec 27 10:52:35 unraid nmbd[19858]: Dec 27 10:52:35 unraid nmbd[19858]: ***** Dec 27 10:56:04 unraid root: Fix Common Problems Version 2021.08.05 Dec 27 10:56:04 unraid root: Fix Common Problems: Error: Unable to communicate with GitHub.com Dec 27 10:56:05 unraid root: Fix Common Problems: Other Warning: Could not check for blacklisted plugins Dec 27 10:56:13 unraid root: Fix Common Problems: Other Warning: Could not perform docker application port tests Dec 27 10:57:21 unraid root: Fix Common Problems Version 2021.08.05

Opened up a thread on reddit: My router setup is completely vanilla (Google Wifi - very straight up conf). Finding so far in the reddit thread, is that it is a DNS resolution issue. Upon reboot my /etc/resolv.conf file is empty... and I have to assume that somehow it fills itself up with the proper DNS nameserver after ~24h which is why it start working again. But as I have just identified this, I cannot confirm yet. But manually entering a nameserver in there just fixes the issue right away. Feels more like a bug rather than a outside network issue to me...

Just for the test, I restarted the docker for Plex, and it took lost access to the internet...

While we are talking about SAB, I have another issue. The working folder __ADMIN__ has a different set of permission than the other files in the incomplete folder (700 vs 744) and it seems that SAB cannot delete that folder and therefore leaves a a whole bunch of folder being after failed jobs... any ideas ?