Gary

@JorgeB Thanks so much for confirming

My problem is that settings - network settings only shows eth0 My problem is that fix common problems plugin shows the following error: eth2 is configured with a non-standard MTU of 9014, aka Jumbo Frames. It is highly recommended that you change the 'Desired MTU' back to the default of 1500. If you are confident the entire network is setup correctly you can ignore this warning.

I see that in my /boot/config/network.cfg has additional network devices. Can I just edit this file? # Generated settings: IFNAME[0]="br0" BRNAME[0]="br0" BRSTP[0]="no" BRFD[0]="0" DESCRIPTION[0]="10G" BRNICS[0]="eth0" PROTOCOL[0]="ipv4" USE_DHCP[0]="no" IPADDR[0]="192.168.X.X" NETMASK[0]="255.255.255.0" GATEWAY[0]="192.168.X.X" DNS_SERVER1="192.168.X.X" DNS_SERVER2="8.8.8.8" USE_DHCP6[0]="yes" DHCP6_KEEPRESOLV="no" IFNAME[1]="eth1" DESCRIPTION[1]="front 2" PROTOCOL[1]="ipv4" USE_DHCP[1]="yes" IFNAME[2]="eth2" DESCRIPTION[2]="10g" PROTOCOL[2]="ipv4" USE_DHCP[2]="yes" METRIC[2]="1" MTU[2]="9014" SYSNICS="3"

Hello. I have had a warning in the fix common problems plugin for a while. It says Jumbo Frames detected on eth2. I haven't had more than a single nic in this machine for a few years now. How do I go about resolving this error when eth2 doesn't show in the interface anymore.

So I have had a number of unfortunate events happen over the past few days. I had two parity drives fail within a very short time. I bought a new drive and waited a few days for it to arrive. I shut down, replaced one of the failed parity drives and then booted back up. It turns out the drive was not working. I suspected a backplane or cable issue so I replaced both. When I booted the drive back up, I found my disk 1 was Unmountable. I suspect I improperly shut it down while testing the backplane. Well now I am left with one invalid parity drive that is rebuilding and an unmountable disk.storage-diagnostics-20230830-1950.zip Am I out almost 16TB of data? Suggestions? Oh did I mention it was my Birthday?

I am having a problem after the latest update to the technitium dns server. Can anyone help me resolve this? System.UnauthorizedAccessException: Access to the path '/etc/dns/blocklists' is denied. ---> System.IO.IOException: Permission denied --- End of inner exception stack trace --- at System.IO.FileSystem.CreateDirectory(String fullPath, UnixFileMode unixCreateMode) at System.IO.Directory.CreateDirectory(String path) at DnsServerCore.DnsWebService..ctor(String configFolder, Uri updateCheckUri, Uri appStoreUri) in Z:\Technitium\Projects\DnsServer\DnsServerCore\DnsWebService.cs:line 126 at DnsServerApp.Program.Main(String[] args) in Z:\Technitium\Projects\DnsServer\DnsServerApp\Program.cs:line 54 Technitium DNS Server is stopping... Technitium DNS Server was stopped successfully.

Please ignore me. Don't let a 2 year old unplug and plug back in your computer to the wrong spot.... back to speedy transfers.

I second this. After updating, my 10G network went from 250-300MB/s to 20-40 MB/s. This is when I am copying a single 30G file from another 10G workstation to an Unraid cache drive. No errors on the cache drive. Ideas?