-
Posts
3,714 -
Joined
-
Last visited
-
Days Won
6
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by Vr2Io
-
-
To be honest, this issue also happen in different Unraid build, seems some people haven't face this but I always found different user suffer the same ( ceiling at 300MB/s ) . My solution was equip the build with much much memory as cache, so it will regulate slow network transfer issue, but this not a real solution, and you need understand.
From my experience, stripe storage may got great performance then single storage ( for network file transfer ), even single storage was high end device. I never use cache pool / mover because this not the best for my use case, I use stripe pool in general.
With many memory cache + stripe storage, I can transfer file in an acceptable speed, it haven't issue even transfer in 100TB data.
-
9 hours ago, Ariloum said:
the main problem is still unresolved - unraid declines to work at 10gbe speed with that Intel X520-DA2 network adapter and barely hits 2gbps...
You may try test in parallel streams by option "-P". With two streams it reach 9.37Gbps for my X520. All my Unraid use X520 and a ConnectX-3 with Windows, so far so good.
I like OpenSpeedTest docker more then iperf3, btw both available per the need.
For Unraid network sharing not reach 10Gbps, this is other issue and you may not fix by change different type NIC.
[ 4] 6.00-7.00 sec 686 MBytes 5.75 Gbits/sec [ 4] 7.00-8.00 sec 691 MBytes 5.80 Gbits/sec [ 4] 8.00-9.00 sec 691 MBytes 5.79 Gbits/sec [ 4] 9.00-10.00 sec 689 MBytes 5.78 Gbits/sec - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bandwidth [ 4] 0.00-10.00 sec 6.71 GBytes 5.77 Gbits/sec sender [ 4] 0.00-10.00 sec 6.71 GBytes 5.76 Gbits/sec receiver[ 4] 8.00-9.00 sec 583 MBytes 4.89 Gbits/sec [ 6] 8.00-9.00 sec 538 MBytes 4.51 Gbits/sec [SUM] 8.00-9.00 sec 1.09 GBytes 9.40 Gbits/sec - - - - - - - - - - - - - - - - - - - - - - - - - [ 4] 9.00-10.00 sec 582 MBytes 4.89 Gbits/sec [ 6] 9.00-10.00 sec 534 MBytes 4.48 Gbits/sec [SUM] 9.00-10.00 sec 1.09 GBytes 9.37 Gbits/sec - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bandwidth [ 4] 0.00-10.00 sec 5.68 GBytes 4.88 Gbits/sec sender [ 4] 0.00-10.00 sec 5.68 GBytes 4.88 Gbits/sec receiver [ 6] 0.00-10.00 sec 5.24 GBytes 4.50 Gbits/sec sender [ 6] 0.00-10.00 sec 5.24 GBytes 4.50 Gbits/sec receiver [SUM] 0.00-10.00 sec 10.9 GBytes 9.38 Gbits/sec sender [SUM] 0.00-10.00 sec 10.9 GBytes 9.38 Gbits/sec receiver -
1 hour ago, birdsofprey02 said:
it just hangs at a Aorus splash screen.
In general, it won't hang on logo screen, if that, it means BIOS POST process not success and haven't go to booting process. Pls try unplug the USB and check does still hang at there.
** Just ensure fast boot always in disable **
-
30 minutes ago, MAM59 said:
Also, the now becoming common 2.5G is only "10G with pauses". It depends on flow control. Without it packets use the wrong time slot and are lost at the (non)receiving side.
Not true, flow control were some old technic to tell pause to others, it usually won't happen in nowadays network and make negative effect because it will make unnecessary pause to all other clients. For 10G with 2.5G communicate ( high speed with low speed communication ), the protocol stack will address this instead achieve by flow control.
-
You should check the iperf result at client side and not on server side, your windows show TX near 10Gbps.
-
18 hours ago, larssadbro said:
This was my attempt at getting this to work. I thought "this SHOULD work, as all I need the 710 to do is provide power and it can sit there and be stuck in "no media found" while the 430 reads the drives."
Yes, this no problem, just let 710 power it's backplane.
18 hours ago, larssadbro said:If anyone's got some expertise on why the 430 won't read the card, I appreciate it. I even tried the 710's factory card and same results. Maybe I'm missing something really simple here.
You need focus on why 430 haven't detect the add on SAS controller, your link show it is 8e card but text description said 8i (match your photo), quite confusing.
BTW, pls try plug the controller to 710 to ensure it detectable.
If two different controller can't detect on 430. Pls try different slot and double check does 430 BIOS have any PCIe setting which disable the add on SAS controller.
-
I haven't use proxy, but in longtime ago make some test with ipvlan and all work. Could you try macvlan / ipvlan have different ?
1 hour ago, heisenfig said:Additionally, other containers that are HOST or BRIDGED cannot access the containers that are set to "Custom : br0"
This could be normal, I can't ping custom ethx.y Container to HOST ( I haven't docker in bridge ) and I use macvlan ( macvtap ).
-
You haven't do anything wrong, if according official runtime chart, it should provide up to 16min backup time. Pls try disconnect Unraid server, then use another load with around 200W+ to ensure UPS work with similar loading.
Pls also ensure no any "surge protect power bar" between UPS and the server.
-
Below are the sensor config which I input to configuration.yaml. That's all.
command_line: - sensor: name: CPU Temperature command: "cat /sys/class/hwmon/hwmon0/temp1_input" # If errors occur, make sure configuration file is encoded as UTF-8 state_class: measurement device_class: temperature unit_of_measurement: °C value_template: "{{ value | multiply(0.001) | round(1) }}" - sensor: name: SATA Temperature command: "cat /sys/class/hwmon/hwmon1/temp1_input" # If errors occur, make sure configuration file is encoded as UTF-8 state_class: measurement device_class: temperature unit_of_measurement: "°C" value_template: "{{ value | multiply(0.001) | round(1) }}" - sensor: name: Nvme Temperature command: "cat /sys/class/hwmon/hwmon3/temp1_input" # If errors occur, make sure configuration file is encoded as UTF-8 state_class: measurement device_class: temperature unit_of_measurement: "°C" value_template: "{{ value | multiply(0.001) | round(1) }}"It work.
-
5 hours ago, Zippi said:
then tried leaving the USB cable unplugged so as not to have communication and see if at least that way it worked but nothing changed!
It likely your server overload the UPS, you need confirm the Watts and VA of server draw, ensure it haven't over the limit of the UPS.
There also could be battery problem, it can't provide enough power even UPS actually haven't overload.
For UPS can't communicate to Unraid, this is next issue.
-
If br2 can't got IP from DHCP, then it is UDMP / USW issue.
I haven't use UBNT network stuff.
-
8 hours ago, TrvlMike said:
I'd like to use eth2 dedicated to the VM and to use VLAN tagging. Here's what I have on Unraid. You'll see that for some reason it's getting APIPA address. I can't seem to get it to get an IP from the VLAN.
A short answer is set the switch port-9 be access port ( untag of vlan100 ), no need add vlan 100 to eth2 ( br2).
Unraid / VM no need to know it is vlan100 in such setup.
-
1 hour ago, vw-kombi said:
Further to this, mine is also 100% after swapping the cable to old USB port, but I am still seeing this in the logs over and over - filling them up :
May 30 12:04:50 Tower apcupsd[26285]: Battery disconnected.
May 30 12:04:51 Tower apcupsd[26285]: Battery reattached.
May 30 12:07:15 Tower apcupsd[26285]: Battery disconnected.
May 30 12:07:16 Tower apcupsd[26285]: Battery reattached.
May 30 12:09:28 Tower apcupsd[26285]: Battery disconnected.
May 30 12:09:29 Tower apcupsd[26285]: Battery reattached.If you confirm UPS functional normal ( putting on battery mode ) by press UPS physical button, then it should be USB port or APCUPSD / NUT issue. Pls try APCUPSD / NUT both, if still got issue, I will suggest add a USB hub ( best USB 2.0 ) between them.
-
On 5/28/2024 at 5:22 AM, n00b42 said:
I run several docker instancens and services, and I thought about turning some off for testing, however as I could not find a reliable way to trigger this issue, I do not want to keep my services disabled for weeks....
I believe some docker or add-on make your network down, other people also report similar case, I think you haven't much options, you need stop something to troubleshoot.
For me, I never got this problem with Unraid. ( several Unraid build in 5yrs+, one build were 7*24 in 1.5yrs）
May be Plex ?? I haven't that.
-
-
8 minutes ago, SeRiusMe said:
No, by now there's no interface with an empty gateway.
Then it look like no problem on docker system now.
14 minutes ago, SeRiusMe said:I change the order for the DNS at the host and put the 10.1.5.251 at the top, The container at VLAN5 resolves DNS. BUT ALSO OTHER ONE IN VLAN2. (But it takes a while, I suppose because is trying 10.1.5.251 first?
All DNS server must accessible by all subnet, client will randomly resolve on all DNS server according the setting, not 1st one then 2nd then 3rd.
-
3 minutes ago, SeRiusMe said:
RESOLUTION IN CONTAINER IN VLAN5 WORKS IF DNS OF VLAN5 IS FORCED INSTEAD OF THE DEFAULT (10.1.3.251)
Interesting, but don't know why 10.1.3.251 not work, because eth0 no gateway ?
This also the difference on my setup, my private DNS ( Pihole ) was on eth0.2, not the router or public DNS. But my private DNS endup also lookup on a public DNS.
-
After start docker service
Still no gateway at eth0 ?
Unraid routing table look nornal ?
-
19 minutes ago, SeRiusMe said:
Can you please explain me how did the other guy solved it?
In fact I am not sure OP really fix or not, but no matter how I change the network setting, I couldn't reproduce OP's docker problem.
I store docker in /tmp ( ram file system ), so each reboot will redownload all docker ( only need restore appdata ) and I never do extra docker setting, that may be help always keep docker system clean up and so no trouble at all.
-
2 minutes ago, SeRiusMe said:
Restarting docker brings this two errors, that I found online tht are related to trying to create routes and failing because they exist.
# /etc/rc.d/rc.docker restart stopping dockerd ... ... Waiting to die. starting dockerd ... RTNETLINK answers: File exists RTNETLINK answers: File existsYes, problem pointing to docker system instead network or network setting.
You may try start from scratch by remove docker image / folder to fix it.
-
Your dig result haven't answer session, anyway depends on docker itself, my HA docker have dig and nslookup. The DNS translate also 127.0.0.11
I am not sure how to diagnostic if DNS resolve not work in docker.
-
/boot/config/parity-checks.log
-
1
-
-
16 hours ago, SeRiusMe said:
I bet that the server is trying to serve all the DNS requests through the 10.1.3.xx gateway/route, and it's failing. (It must be the default route)
No, for 10.1.2.xx or 10.1.5.xx, if DNS was 10.1.3.xx it should direct route through router.
For example,
traceroute in Unraid console, 192.168.9.x subnet route through 192.168.9.9 gateway
traceroute 192.168.2.5 traceroute to 192.168.2.5 (192.168.2.5), 30 hops max, 60 byte packets 1 192.168.9.9 (192.168.9.9) 0.115 ms 0.107 ms 0.229 ms 2 * * * 3 * * *traceroute in docker console, 192.168.68.x subnet route through 192.168.68.9 gateway
traceroute 192.168.2.5 traceroute to 192.168.2.5 (192.168.2.5), 30 hops max, 46 byte packets 1 192.168.68.9 (192.168.68.9) 0.088 ms 0.099 ms 0.089 ms 2 * * * 3 * * * 4 * * * 5 * * * 6 * * * 7 * * * -
22 hours ago, SeRiusMe said:
And I can't change the empty gateway in eth0.2. And you can see that it's not creating a custom network for eth0.
This indicate problem on docker system, I have reach a case, the OP have similar problem, always can't found the custom network, finally OP mark the case resolve by remove other previous docker network. So pls check does other create network left and remove it by "docker network rm xxxxx". Also perform some check on all existing docker network.
That's also / may be why we change all network setting and problem still occur.
Sometimes, docker network like a black box, when you confirm your physical network haven't issue, but always got trouble. Then you may need further verify by VM network first.
For DNS problem, do you confirm not problem on router routing ? For me, all docker could reach private DNS and internet, also other subnet.
docker network ls NETWORK ID NAME DRIVER SCOPE 669a79230488 bridge bridge local 61f4b403738e eth0 macvlan local a5af90fcb721 eth0.2 macvlan local e4473591c365 eth0.666 macvlan local a642478c8a6d host host local 33db889adf1b none null localdocker network inspect a5af90fcb721 [ { "Name": "eth0.2", "Id": "a5af90fcb721b1133c84995351c516a77c6d3464c66a60b0a505047507bd8ef4", "Created": "2024-05-18T10:51:40.796286014+08:00", "Scope": "local", "Driver": "macvlan", "EnableIPv6": false, "IPAM": { "Driver": "default", "Options": {}, "Config": [ { "Subnet": "192.168.2.0/24", "Gateway": "192.168.2.9" } ] }, "Internal": false, "Attachable": false, "Ingress": false, "ConfigFrom": { "Network": "" }, "ConfigOnly": false, "Containers": { "1e404021ac2b09835323d92888db216c69b46dfe26a213c33a4599fce449e1a9": { "Name": "Pihole", "EndpointID": "7489add3c1bc4b7eacc43bb65541a914b39a4a63ae40ef1acfdeb08265bf0564", "MacAddress": "02:42:c0:a8:02:05", "IPv4Address": "192.168.2.5/24", "IPv6Address": "" }, "cfaa6db42d9c4023309fa94ef10458b77d3cb184d7b5eb03b4c064f8996fed66": { "Name": "NTP", "EndpointID": "7009d52484bc8ca96171d088b7f1fbe592a6c435753448952d51b560b1369c2e", "MacAddress": "02:42:c0:a8:02:06", "IPv4Address": "192.168.2.6/24", "IPv6Address": "" }, "d7ffa44f7c40585d323f540599adf7880750480881f2d1163bfb43541dbba245": { "Name": "Syslogserver2", "EndpointID": "8d800260429264b6278caf086f5a77be0cade18ab7bfd9028155ac6f9037fee0", "MacAddress": "02:42:c0:a8:02:07", "IPv4Address": "192.168.2.7/24", "IPv6Address": "" } }, "Options": { "parent": "vhost0.2" }, "Labels": {} } ]19 hours ago, SeRiusMe said:You mean that set the Id to an unused/fake vlan so traffic doesn't go anywhere?
Yes. Each interface have a PVID, so if you don't want untag traffic going to a port, then you can assign an unuse PVID to it.
Trouble migrating to new hardware (booting)
in General Support
Posted · Edited by Vr2Io
UEFI and legacy can coexist, if you remove - and make stick also legacy bootable, then actual boot mode will depends on BIOS setting.