-
Posts
10233 -
Joined
-
Last visited
-
Days Won
65
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by bonienl
-
-
I made several fixes and improvements for the next release.
Perhaps you can try it when it becomes available (soon)
-
8 minutes ago, michaelmurfy said:
I'm not fully confident this is the sole reason for the issues given the host is getting an IP
IPv6 works a bit different and doesn't like loops (it is doing multicast).
As I said, change the bonding mode for testing purposes, it will give you a better view what to look for.
-
9 minutes ago, HDRW said:
I wonder what happened?
We wonder too
- 1
-
9 minutes ago, michaelmurfy said:
Yep - switch (Mikrotik) sure does and is working as expected.
As a test you can change the bonding mode to "Active-Standby" as see if the NFS service is able to bind to the interface (this is new in 6.12.0)
The error message you receive is because both sides of the bond are initially in different states and the bond acts as a layer 2 connection with one or more loops.
It could be a timing issue (perhaps configurable), but I am not familiar with Mikrotik.
-
How do you access the GUI, by name or by IP address?
Try IP address and see if that makes a difference.
I see in your configuration that you use IPv6 link local addresses for the DNS servers.
I don't know if that works, the usual approach is to take the regular IPv6 address of your router (or alternatively one of the public IPv6 DNS servers from google or cloudflare)
-
17 minutes ago, michaelmurfy said:
I see some things I'd much rather not out in the public even in the anonymous zip)
Please let us know what should be removed or altered. Always willing to adjust diagnostics and remove private stuff.
- 1
-
You have set up bonding with LACP, but it returns an error.
Does your switch support LACP and is it properly configured?
Jun 18 01:49:15 Pikachu kernel: br0: received packet on bond0 with own address as source address (addr:5c:ba:2c:25:c4:48, vlan:0)
The network error is the reason for not accepting the IPv6 address.
-
If you only complain but don't provide more detailed information (diagnostics), we can't do much.
6.12.0 is a lot strickter and unfortunately people start to discover now incorrect settings from the past.
NFS and IPv6 should work. Here is an extract from my log
Jun 17 16:50:06 vesta root: Starting NFS server daemons: Jun 17 16:50:06 vesta root: /usr/sbin/exportfs -r Jun 17 16:50:06 vesta root: /usr/sbin/rpc.nfsd -u -s -H 10.0.101.11 -H 2a02:a448:32d5:101:xxxx:xxxx:xxxx:xxxx -H 10.253.0.1 -H 127.0.0.1 -H ::1 8 Jun 17 16:50:07 vesta root: /usr/sbin/rpc.mountd Jun 17 16:50:07 vesta kernel: NFSD: Using UMH upcall client tracking operations. Jun 17 16:50:07 vesta kernel: NFSD: starting 90-second grace period (net f0000000)
-
You have a routing loop.
In your network configuration make sure the gateway for br0 has a LOWER metric value then the gateway for br1.
-
Please start a new support ticket. This is a completely different problem you have.
Your USB device is corrupted.
-
When you close all tiles in a column, then the column isn't visible and the GUI reduces the number of columns displayed.
Use the "Reset" function under Management Tools (wrench icon) to restore original.
- 1
-
-
Not every month has 31 days, those months are skipped.
Change "31" to "Last day" and it will do a montly check.
-
- 1
-
Please also include the result of
# cat /etc/nginx/conf.d/servers.conf
-
32 minutes ago, Pete0 said:
I don't see my underscores.
A bug of firefox browser, using other browsers like Chrome, Edge, Safari or Brave it displays correctly.
- 1
-
The number of support tickets is already quite high, making S3 part of Unraid will see that number going through the roof.
Limetech simply doesn’t have the resources to handle that.
- 1
-
Not really an answer to your question, but the built-in wireguard functionality of Unraid is there to prevent these kind of “accidents”.
It allows the user to start/stop docker or even array while communication persists.
- 1
-
2 hours ago, craigr said:
Not a big deal, just wondering if it might be fixed?
The capacity is as reported by your BIOS, only a fix in the BIOS of your motherboard can resolve it.
- 1
-
-
The original go file does not call emhttpd directly, but refers to emhttp.
This was done to maintain compatability with older Unraid versions.
-
Can you try Unraid version 6.12.0-rc7.
It has some networking improvements
-
Try the following.
Edit the file /config/share.cfg on your USB device and change to
shareAvahiEnabled="no"
Save the update and reboot your system.
-
On 5/29/2023 at 11:28 AM, Revan335 said:
I can't move to unlimited Directory Level.
For example /mnt/disk3/Backup_folder/Daten/user/Client move /mnt/disk1/Backup_folder/Daten/ ended there. I can't selected underlying directory level /user/ or /user/Client
Thanks, made a fix.
- 2
6.12 - Why only 2 collums on Dashboard on 1080p Screen?!
in Feature Requests
Posted
The browser uses the following to determine the number of columns in black/white themes:
div.grid{display:grid;grid-template-columns:repeat(auto-fit,minmax(610px,1fr));column-gap:30px}
This means 3 columns = 3 x 610 + 2 x 30 = 1890px