Jump to content

bonienl

Community Developer
  • Content Count

    7444
  • Joined

  • Last visited

  • Days Won

    42

Everything posted by bonienl

  1. This certainly has all the attention of Limetech, and if a fix is available it will be presented as soon as possible. This is not an easy problem to solve, I wish it was as simple as offering money to make a correction ...
  2. You can set specific DNS servers under network settings.
  3. I would argue that a cache pool in RAID 10 is faster than a single unassigned device (I am using a 4x SSD cache pool in RAID 10).
  4. It is recommended to use a "regular" DNS server (e.g. 8.8.8.8 or 1.1.1.1) for Unraid itself and not let Unraid use pihole. This is to avoid catch22 situations, and Unraid doesn't really need the filtering of pihole.
  5. If you have a cache device and "appdata" is set to "cache only" then it is preferred to use "/mnt/cache/appdata". When no cache device is present then use "/mnt/user/appdata" instead. "/mnt/disks" refers to "Unassigned Devices". Some users prefer to use UD to make a dedicated disk for Docker instead of the standard cache device.
  6. The route you added should not be necessary, the default route should take care of this. I expected to see br1 and not br3. Can you post the full diagnostics (see Tools -> Diagnostics).
  7. It should work without refreshing the Main page (assuming you are on Unraid 6.4 or higher).
  8. Post a screenshot of the routing table (see Settings -> Network Settings)
  9. There is a syntax error in the gateway declaration in the network.cfg file. GATEWAY[0]="192.168.1.1#213" The "#213" part must be removed. This is automatically done when upgrading via the GUI (legacy removal). Did you do a manual upgrade?
  10. Check DNS settings, if you are using pi-hole then configure Unraid to NOT use pi-hole but a 'regular' DNS server.
  11. Please post your diagnostics
  12. I have never seen it as part of "proc", but of course I am not limetech 😉
  13. Docker containers and VMs on the dashboard are loaded in the background. If something is amiss with either the Docker or libvirt service, it would hamper the dashboard.
  14. You can run the "New Permissions" tool (see Tools -> New Permissions). Select the user share you want to update and let Unraid set the default permissions (may take a while).
  15. You have a duplicate assignment, both eth0 and eth1 have the same settings. # Generated settings: IFNAME[0]="eth0" DESCRIPTION[0]="etho" PROTOCOL[0]="ipv4" USE_DHCP[0]="no" IPADDR[0]="192.168.1.103" NETMASK[0]="255.255.255.0" GATEWAY[0]="192.168.1.1" METRIC[0]="24" DNS_SERVER1="8.8.8.8" DNS_SERVER2="54.93.173.153" DNS_SERVER3="8.8.8.8" USE_DHCP6[0]="yes" DHCP6_KEEPRESOLV="no" VLANS[0]="1" IFNAME[1]="eth1" DESCRIPTION[1]="Intel" PROTOCOL[1]="ipv4" USE_DHCP[1]="no" IPADDR[1]="192.168.1.103" NETMASK[1]="255.255.255.0" GATEWAY[1]="192.168.1.1" SYSNICS="2" Open and edit the file "network.cfg" in the /config folder on your USB device. Remove all [1] entries (i.e. remove the eth1 settings) Change SYSNICS="1" Save the file and reboot your system
  16. You asked for the "obvious" 😁
  17. Enable bonding for eth0.
  18. grep -A1 '"disk4"' /var/local/emhttp/disks.ini or if you want only the device designation grep -A1 '"disk4"' /var/local/emhttp/disks.ini | grep -Po 'device="\K[^"]+'
  19. No, the management interface is fixed to eth0 (untagged)
  20. Check the current active interface cat /sys/class/net/bond0/bonding/active_slave Change the current active interface echo eth0 > /sys/class/net/bond0/bonding/active_slave
  21. Eth0 is the management interface of Unraid and must have an IP address. You can enable VLANs and assign per VLAN to use an IP address or not.
  22. You can safely do New Config and assign disks to your liking, but do NOT check "parity is valid".
  23. Try to introduce some delay (e.g. sleep 10) after execution of the ethtool command. The ethtool command is immediately followed by the command to put the system to sleep, perhaps this is too fast for the network card?