bonienl

Community Developer
  • Posts

    9701
  • Joined

  • Last visited

  • Days Won

    67

Everything posted by bonienl

  1. network.cfg is only created when the user makes configuration changes. When this file does not exist, the system uses default network settings.
  2. When no explicit gateway address is given for the subnet, then docker will assign the first address as gateway address. This is the conflict you see. Under docker settings you need to set the specific subnet assignment for each VLAN, see example below
  3. More likely user error, can change and save DNS settings without issue.
  4. No, it can copy/move existing links but not create.
  5. Not a bug. Docker changed the IPv6 behavior and made it the same as IPv4 behavior. This means Docker itself hands out IPv4 and IPv6 addresses to containers. You still have the ability with macvlan (ipvlan) to set your own IPv4/IPv6 address.
  6. Names highlighted in red mean they exist more than once. The location column shows on which disks the same name exists. This might be a copy of the same file or a different file with the same name.
  7. Are you sure your PSU is up to the task? A parity operation involves all disks and drains a lot more power than average usage.
  8. You deleted the interface section (and perhaps more) in the XML file. I suggest you start fresh with a new VM.
  9. What does the Main page show, a green icon (active disk) or grey icon (inactive disk)? Do you have any scheduled tasks created which may access disks? The only thing I can think of is to completely move the content of the disk to another disk (i.e. make the disk completely empty). Also make sure that your general include/exclude rules (see Settings -> Global Share Settings) and per share include/exclude rules (see Shares -> <share name>) do not force to use the disk in question.
  10. My first Unraid server was with version 4.7 and 2x 2TB data drives + parity, giving a whopping 4TB storage. I thought I had endless storage
  11. The Dynamix file manager has an easy way built-in to move content from one disk to another disk (provided there is enough space on the destination disk) 1. Open the file manager from the top-right icon 2. Select the Move operation from the source disk (e.g. disk1) 3. Select the target disk to move to (e.g. disk4) 4. Select PROCEED and all content of disk1 will be moved to disk4 (existing files will not be overwritten unless explicitly selected) 5. You can follow the progress in the opened window or close it (X in top-right) and let it run in the background.
  12. webUI access to containers won't work with user defined custom networks. You can use bridge (e.g. br0) custom networks to put a container on a dedicated IP address. I run my own DNS server on my LAN network, which allows me to create names with associated IP addresses.
  13. This is expected behavior. The plugin is completely uninstalled together with the settings it retained. Consequently settings in the GUI need to be set. Perhaps, should make this clearer in the release notes!
  14. S3 sleep detects there is activity (not thinking). When read/write counters change it means something is happening. I have seen situations when a SATA controller card is used, counters are incorrectly updated, in that case you can try the other detection method which is to monitor the reported state of the disk.
  15. Successful detection is outside the scope of the plugin. Your milage may vary depending on your hardware. The Network stats plugin works fine with all Unraid versions, including latest beta release 6.11.0-rc4 It is impossible for Limetech (or anyone else) to test all possible hardware combinations out there and ensure TEMp and FANS all work. It is a deliberate decision to make this optional plugin, as success can't be guaranteed. Don't know what the concern is, but development is still in place. Though most of my time I spend on developing Unraid itself.
  16. Test with docker and vm services disabled, and see if that makes a difference.
  17. I see other distros reporting the same issue. Please retest with Unraid v6.11.0-rc4, it has newer network drivers.
  18. Please always include diagnostics. It is impossible to know what you did and what Unraid version you are using. I would advise to use the support topic first before filing a bug report. I made a quick test on version 6.11.0-rc4 (which is on my test system) and changing an array disk to btrfs results in the correct size display.
  19. There is a bug in udev which causes it to detect NICs in a bonded interface, and giving the same MAC address. This results in a wrong network rules file when interface assignments are changed while the bond interface is active. This affects Unraid 6.10 versions. Workaround is to disable the bond interface before changing interface assignments. It works correctly in latest beta release. Delete the network-rules.cfg file and retest with v6.11.0-rc4 Please always include diagnostics, which helps us to investigate the issue.
  20. Select inside the list and press the END button ...
  21. The Dynamix File Manager plugin uses jqueryUI dialogs and filetree to open a popup window with file selection. You may want to look into this combination.
  22. Just tested your time zone and it works properly for me. Try to set a different time zone and then change it back to your own time zone, see if that makes a difference.
  23. Add the .sh extension to the list defined in /config/editor.cfg located on your usb drive. Note: you can use the file manager to edit the above file
  24. The error message implies that your Unraid network interface is not fully ready yet Can you change your network settings and use a static IPv4 assignment (192.168.1.1) instead of DHCP and retest.
  25. You should make eth1 a bridge member of eth0 (br0). Change the eth0 configuration and make both eth0 and eth1 a bridge member.