1812
-
Content Count
2395 -
Joined
-
Last visited
-
Days Won
12
5 Followers
Recent Profile Visitors
11185 profile views
.thumb.jpg.0c644260dacbdbc011d7ad8ba9a1c10a.jpg)
-
push it higher. I had to go to 100 threads to hit 9.x Gbps but at the same time, on 10 I hit 7.xGbps so you do have some other issue... how long are your cat6 runs? are they just cat6 or 6a? bend in any cables?
-
You may need to increase the number of threads to truly saturate the 10gbit link. See the below link and scroll down to my iperf testing with 10gbit:
-
updated from 6.8.0 rc2(?) to rc7. aside from it swiping my primary network adapter for the secondary (which wasn't plugged in) and failing to switch to an operational one, after that time I installed a windows 10 vm. following errors pop up: first is a network error with call trace. this occurs when the vm is using the bridge. Inside the vm I disabled the virtio bridge and used the solar flare 10g I have in it and these errors stopped. Dec 3 08:31:33 Backup kernel: e1000e 0000:00:19.0 eth0: Detected Hardware Unit Hang: Dec 3 08:31:33 Backup kernel: TDH <27> Dec 3 08:31:33 Backup kernel: TDT <7d> Dec 3 08:31:33 Backup kernel: next_to_use <7d> Dec 3 08:31:33 Backup kernel: next_to_clean <26> Dec 3 08:31:33 Backup kernel: buffer_info[next_to_clean]: Dec 3 08:31:33 Backup kernel: time_stamp <1000a35c2> Dec 3 08:31:33 Backup kernel: next_to_watch <27> Dec 3 08:31:33 Backup kernel: jiffies <1000a3d40> Dec 3 08:31:33 Backup kernel: next_to_watch.status <0> Dec 3 08:31:33 Backup kernel: MAC Status <80083> Dec 3 08:31:33 Backup kernel: PHY Status <796d> Dec 3 08:31:33 Backup kernel: PHY 1000BASE-T Status <3c00> Dec 3 08:31:33 Backup kernel: PHY Extended Status <3000> Dec 3 08:31:33 Backup kernel: PCI Status <10> Dec 3 08:31:35 Backup kernel: e1000e 0000:00:19.0 eth0: Detected Hardware Unit Hang: Dec 3 08:31:35 Backup kernel: TDH <27> Dec 3 08:31:35 Backup kernel: TDT <7d> Dec 3 08:31:35 Backup kernel: next_to_use <7d> Dec 3 08:31:35 Backup kernel: next_to_clean <26> Dec 3 08:31:35 Backup kernel: buffer_info[next_to_clean]: Dec 3 08:31:35 Backup kernel: time_stamp <1000a35c2> Dec 3 08:31:35 Backup kernel: next_to_watch <27> Dec 3 08:31:35 Backup kernel: jiffies <1000a4540> Dec 3 08:31:35 Backup kernel: next_to_watch.status <0> Dec 3 08:31:35 Backup kernel: MAC Status <80083> Dec 3 08:31:35 Backup kernel: PHY Status <796d> Dec 3 08:31:35 Backup kernel: PHY 1000BASE-T Status <3c00> Dec 3 08:31:35 Backup kernel: PHY Extended Status <3000> Dec 3 08:31:35 Backup kernel: PCI Status <10> Dec 3 08:31:38 Backup kernel: e1000e 0000:00:19.0 eth0: Detected Hardware Unit Hang: Dec 3 08:31:38 Backup kernel: TDH <27> Dec 3 08:31:38 Backup kernel: TDT <7d> Dec 3 08:31:38 Backup kernel: next_to_use <7d> Dec 3 08:31:38 Backup kernel: next_to_clean <26> Dec 3 08:31:38 Backup kernel: buffer_info[next_to_clean]: Dec 3 08:31:38 Backup kernel: time_stamp <1000a35c2> Dec 3 08:31:38 Backup kernel: next_to_watch <27> Dec 3 08:31:38 Backup kernel: jiffies <1000a4d40> Dec 3 08:31:38 Backup kernel: next_to_watch.status <0> Dec 3 08:31:38 Backup kernel: MAC Status <80083> Dec 3 08:31:38 Backup kernel: PHY Status <796d> Dec 3 08:31:38 Backup kernel: PHY 1000BASE-T Status <3c00> Dec 3 08:31:38 Backup kernel: PHY Extended Status <3000> Dec 3 08:31:38 Backup kernel: PCI Status <10> Dec 3 08:31:40 Backup kernel: e1000e 0000:00:19.0 eth0: Detected Hardware Unit Hang: Dec 3 08:31:40 Backup kernel: TDH <27> Dec 3 08:31:40 Backup kernel: TDT <7d> Dec 3 08:31:40 Backup kernel: next_to_use <7d> Dec 3 08:31:40 Backup kernel: next_to_clean <26> Dec 3 08:31:40 Backup kernel: buffer_info[next_to_clean]: Dec 3 08:31:40 Backup kernel: time_stamp <1000a35c2> Dec 3 08:31:40 Backup kernel: next_to_watch <27> Dec 3 08:31:40 Backup kernel: jiffies <1000a5540> Dec 3 08:31:40 Backup kernel: next_to_watch.status <0> Dec 3 08:31:40 Backup kernel: MAC Status <80083> Dec 3 08:31:40 Backup kernel: PHY Status <796d> Dec 3 08:31:40 Backup kernel: PHY 1000BASE-T Status <3c00> Dec 3 08:31:40 Backup kernel: PHY Extended Status <3000> Dec 3 08:31:40 Backup kernel: PCI Status <10> Dec 3 08:31:42 Backup kernel: e1000e 0000:00:19.0 eth0: Detected Hardware Unit Hang: Dec 3 08:31:42 Backup kernel: TDH <27> Dec 3 08:31:42 Backup kernel: TDT <7d> Dec 3 08:31:42 Backup kernel: next_to_use <7d> Dec 3 08:31:42 Backup kernel: next_to_clean <26> Dec 3 08:31:42 Backup kernel: buffer_info[next_to_clean]: Dec 3 08:31:42 Backup kernel: time_stamp <1000a35c2> Dec 3 08:31:42 Backup kernel: next_to_watch <27> Dec 3 08:31:42 Backup kernel: jiffies <1000a5d40> Dec 3 08:31:42 Backup kernel: next_to_watch.status <0> Dec 3 08:31:42 Backup kernel: MAC Status <80083> Dec 3 08:31:42 Backup kernel: PHY Status <796d> Dec 3 08:31:42 Backup kernel: PHY 1000BASE-T Status <3c00> Dec 3 08:31:42 Backup kernel: PHY Extended Status <3000> Dec 3 08:31:42 Backup kernel: PCI Status <10> Dec 3 08:31:43 Backup kernel: ------------[ cut here ]------------ Dec 3 08:31:43 Backup kernel: NETDEV WATCHDOG: eth0 (e1000e): transmit queue 0 timed out Dec 3 08:31:43 Backup kernel: WARNING: CPU: 1 PID: 0 at net/sched/sch_generic.c:447 dev_watchdog+0x161/0x1bb Dec 3 08:31:43 Backup kernel: Modules linked in: xt_CHECKSUM ipt_REJECT ip6table_mangle ip6table_nat iptable_mangle ip6table_filter ip6_tables vhost_net tun vhost tap xt_MASQUERADE iptable_filter iptable_nat nf_nat ip_tables xfs md_mod bonding e1000e sfc mdio wmi_bmof sb_edac x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel aesni_intel aes_x86_64 crypto_simd cryptd glue_helper intel_cstate intel_uncore intel_rapl_perf i2c_i801 i2c_core ahci libahci mpt3sas isci libsas raid_class scsi_transport_sas wmi button [last unloaded: e1000e] Dec 3 08:31:43 Backup kernel: CPU: 1 PID: 0 Comm: swapper/1 Not tainted 5.3.12-Unraid #1 Dec 3 08:31:43 Backup kernel: Hardware name: Hewlett-Packard HP Z420 Workstation/1589, BIOS J61 v03.94 07/10/2018 Dec 3 08:31:43 Backup kernel: RIP: 0010:dev_watchdog+0x161/0x1bb Dec 3 08:31:43 Backup kernel: Code: 98 b1 00 00 75 39 48 89 ef c6 05 b5 98 b1 00 01 e8 f6 d5 fc ff 44 89 e9 48 89 ee 48 c7 c7 bb 06 db 81 48 89 c2 e8 0a c1 ac ff <0f> 0b eb 11 41 ff c5 48 81 c2 40 01 00 00 41 39 cd 75 95 eb 13 48 Dec 3 08:31:43 Backup kernel: RSP: 0018:ffffc900000fcea0 EFLAGS: 00010286 Dec 3 08:31:43 Backup kernel: RAX: 0000000000000000 RBX: ffff888bd2a54438 RCX: 0000000000000524 Dec 3 08:31:43 Backup kernel: RDX: 0000000000000001 RSI: 0000000000000002 RDI: 0000000000000247 Dec 3 08:31:43 Backup kernel: RBP: ffff888bd2a54000 R08: 0000000000000003 R09: 000000000001cd00 Dec 3 08:31:43 Backup kernel: R10: 0000000000000000 R11: 000000000000005c R12: ffff888bd2a5441c Dec 3 08:31:43 Backup kernel: R13: 0000000000000000 R14: ffff888bd8622080 R15: 0000000000000001 Dec 3 08:31:43 Backup kernel: FS: 0000000000000000(0000) GS:ffff888c0f640000(0000) knlGS:0000000000000000 Dec 3 08:31:43 Backup kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Dec 3 08:31:43 Backup kernel: CR2: 00001480adc18b10 CR3: 000000000200a005 CR4: 00000000001626e0 Dec 3 08:31:43 Backup kernel: Call Trace: Dec 3 08:31:43 Backup kernel: <IRQ> Dec 3 08:31:43 Backup kernel: call_timer_fn.isra.0+0x12/0x6f Dec 3 08:31:43 Backup kernel: ? qdisc_put_unlocked+0x28/0x28 Dec 3 08:31:43 Backup kernel: expire_timers+0x7e/0x8d Dec 3 08:31:43 Backup kernel: run_timer_softirq+0x72/0x120 Dec 3 08:31:43 Backup kernel: ? __hrtimer_run_queues+0xc3/0x10b Dec 3 08:31:43 Backup kernel: ? ktime_get+0x44/0x95 Dec 3 08:31:43 Backup kernel: __do_softirq+0xc9/0x1d3 Dec 3 08:31:43 Backup kernel: irq_exit+0x47/0x86 Dec 3 08:31:43 Backup kernel: smp_apic_timer_interrupt+0x80/0x8b Dec 3 08:31:43 Backup kernel: apic_timer_interrupt+0xf/0x20 Dec 3 08:31:43 Backup kernel: </IRQ> Dec 3 08:31:43 Backup kernel: RIP: 0010:cpuidle_enter_state+0xe8/0x1f0 Dec 3 08:31:43 Backup kernel: Code: ff 45 84 ff 74 1d 9c 58 0f 1f 44 00 00 0f ba e0 09 73 09 0f 0b fa 66 0f 1f 44 00 00 31 ff e8 e1 43 ba ff fb 66 0f 1f 44 00 00 <45> 85 e4 0f 88 ea 00 00 00 49 63 cc be ff ff ff 7f 48 ba ff ff ff Dec 3 08:31:43 Backup kernel: RSP: 0018:ffffc90000087e90 EFLAGS: 00000246 ORIG_RAX: ffffffffffffff13 Dec 3 08:31:43 Backup kernel: RAX: ffff888c0f660ac0 RBX: ffffe8ffff27bf00 RCX: 000000000000001f Dec 3 08:31:43 Backup kernel: RDX: 0000000000000000 RSI: 000000002ac4fcf0 RDI: 0000000000000000 Dec 3 08:31:43 Backup kernel: RBP: ffffffff820584e0 R08: 000000e47c6036a7 R09: 000000e47a5e3354 Dec 3 08:31:43 Backup kernel: R10: 071c71c71c71c71c R11: 0000000000000020 R12: 0000000000000004 Dec 3 08:31:43 Backup kernel: R13: 000000e47c3003af R14: 000000e47c6036a7 R15: 0000000000000000 Dec 3 08:31:43 Backup kernel: cpuidle_enter+0x25/0x31 Dec 3 08:31:43 Backup kernel: do_idle+0x17e/0x1fc Dec 3 08:31:43 Backup kernel: cpu_startup_entry+0x18/0x1a Dec 3 08:31:43 Backup kernel: start_secondary+0x154/0x16f Dec 3 08:31:43 Backup kernel: secondary_startup_64+0xa4/0xb0 Dec 3 08:31:43 Backup kernel: ---[ end trace ffdb4b11edd93456 ]--- second is when the windows 10 vm sees high load/gaming on the cores Dec 3 11:11:56 Backup kernel: kvm_set_msr_common: 155 callbacks suppressed Dec 3 11:11:56 Backup kernel: kvm [3974]: vcpu2, guest rIP: 0xfffff802755b5b92 kvm_set_msr_common: MSR_IA32_DEBUGCTLMSR 0x1, nop Dec 3 11:11:56 Backup kernel: kvm [3974]: vcpu2, guest rIP: 0xfffff802755b5b92 kvm_set_msr_common: MSR_IA32_DEBUGCTLMSR 0x1, nop Dec 3 11:11:56 Backup kernel: kvm [3974]: vcpu2, guest rIP: 0xfffff802755b5b92 kvm_set_msr_common: MSR_IA32_DEBUGCTLMSR 0x1, nop Dec 3 11:11:56 Backup kernel: kvm [3974]: vcpu2, guest rIP: 0xfffff802755b5b92 kvm_set_msr_common: MSR_IA32_DEBUGCTLMSR 0x1, nop Dec 3 11:11:56 Backup kernel: kvm [3974]: vcpu2, guest rIP: 0xfffff802755b5b92 kvm_set_msr_common: MSR_IA32_DEBUGCTLMSR 0x1, nop Dec 3 11:11:56 Backup kernel: kvm [3974]: vcpu2, guest rIP: 0xfffff802755b5b92 kvm_set_msr_common: MSR_IA32_DEBUGCTLMSR 0x1, nop Dec 3 11:11:56 Backup kernel: kvm [3974]: vcpu2, guest rIP: 0xfffff802755b5b92 kvm_set_msr_common: MSR_IA32_DEBUGCTLMSR 0x1, nop Dec 3 11:11:56 Backup kernel: kvm [3974]: vcpu2, guest rIP: 0xfffff802755b5b92 kvm_set_msr_common: MSR_IA32_DEBUGCTLMSR 0x1, nop Dec 3 11:11:56 Backup kernel: kvm [3974]: vcpu2, guest rIP: 0xfffff802755b5b92 kvm_set_msr_common: MSR_IA32_DEBUGCTLMSR 0x1, nop Dec 3 11:11:56 Backup kernel: kvm [3974]: vcpu2, guest rIP: 0xfffff802755b5b92 kvm_set_msr_common: MSR_IA32_DEBUGCTLMSR 0x1, nop Dec 3 11:12:03 Backup kernel: kvm_set_msr_common: 5673 callbacks suppressed Dec 3 11:12:03 Backup kernel: kvm [3974]: vcpu2, guest rIP: 0xfffff802755b5b92 kvm_set_msr_common: MSR_IA32_DEBUGCTLMSR 0x1, nop Dec 3 11:12:03 Backup kernel: kvm [3974]: vcpu2, guest rIP: 0xfffff802755b5b92 kvm_set_msr_common: MSR_IA32_DEBUGCTLMSR 0x1, nop Dec 3 11:12:03 Backup kernel: kvm [3974]: vcpu2, guest rIP: 0xfffff802755b5b92 kvm_set_msr_common: MSR_IA32_DEBUGCTLMSR 0x1, nop Dec 3 11:12:03 Backup kernel: kvm [3974]: vcpu2, guest rIP: 0xfffff802755b5b92 kvm_set_msr_common: MSR_IA32_DEBUGCTLMSR 0x1, nop Dec 3 11:12:03 Backup kernel: kvm [3974]: vcpu2, guest rIP: 0xfffff802755b5b92 kvm_set_msr_common: MSR_IA32_DEBUGCTLMSR 0x1, nop Dec 3 11:12:03 Backup kernel: kvm [3974]: vcpu2, guest rIP: 0xfffff802755b5b92 kvm_set_msr_common: MSR_IA32_DEBUGCTLMSR 0x1, nop Dec 3 11:12:03 Backup kernel: kvm [3974]: vcpu2, guest rIP: 0xfffff802755b5b92 kvm_set_msr_common: MSR_IA32_DEBUGCTLMSR 0x1, nop Dec 3 11:12:03 Backup kernel: kvm [3974]: vcpu2, guest rIP: 0xfffff802755b5b92 kvm_set_msr_common: MSR_IA32_DEBUGCTLMSR 0x1, nop Dec 3 11:12:03 Backup kernel: kvm [3974]: vcpu2, guest rIP: 0xfffff802755b5b92 kvm_set_msr_common: MSR_IA32_DEBUGCTLMSR 0x1, nop Dec 3 11:12:03 Backup kernel: kvm [3974]: vcpu2, guest rIP: 0xfffff802755b5b92 kvm_set_msr_common: MSR_IA32_DEBUGCTLMSR 0x1, nop Dec 3 11:12:08 Backup kernel: kvm_set_msr_common: 77 callbacks suppressed Dec 3 11:12:08 Backup kernel: kvm [3974]: vcpu4, guest rIP: 0xfffff802755b5b92 kvm_set_msr_common: MSR_IA32_DEBUGCTLMSR 0x1, nop Dec 3 11:12:08 Backup kernel: kvm [3974]: vcpu4, guest rIP: 0xfffff802755b5b92 kvm_set_msr_common: MSR_IA32_DEBUGCTLMSR 0x1, nop Dec 3 11:12:08 Backup kernel: kvm [3974]: vcpu4, guest rIP: 0xfffff802755b5b92 kvm_set_msr_common: MSR_IA32_DEBUGCTLMSR 0x1, nop Dec 3 11:12:08 Backup kernel: kvm [3974]: vcpu4, guest rIP: 0xfffff802755b5b92 kvm_set_msr_common: MSR_IA32_DEBUGCTLMSR 0x1, nop Dec 3 11:12:08 Backup kernel: kvm [3974]: vcpu4, guest rIP: 0xfffff802755b5b92 kvm_set_msr_common: MSR_IA32_DEBUGCTLMSR 0x1, nop Dec 3 11:12:08 Backup kernel: kvm [3974]: vcpu4, guest rIP: 0xfffff802755b5b92 kvm_set_msr_common: MSR_IA32_DEBUGCTLMSR 0x1, nop Dec 3 11:12:08 Backup kernel: kvm [3974]: vcpu4, guest rIP: 0xfffff802755b5b92 kvm_set_msr_common: MSR_IA32_DEBUGCTLMSR 0x1, nop Dec 3 11:12:08 Backup kernel: kvm [3974]: vcpu4, guest rIP: 0xfffff802755b5b92 kvm_set_msr_common: MSR_IA32_DEBUGCTLMSR 0x1, nop Dec 3 11:12:08 Backup kernel: kvm [3974]: vcpu4, guest rIP: 0xfffff802755b5b92 kvm_set_msr_common: MSR_IA32_DEBUGCTLMSR 0x1, nop Dec 3 11:12:08 Backup kernel: kvm [3974]: vcpu4, guest rIP: 0xfffff802755b5b92 kvm_set_msr_common: MSR_IA32_DEBUGCTLMSR 0x1, nop Now, I did not have a windows 10 vm on this computer before upgrading. the rIP problem has never occurred on the macOS video editing vm. I don't use the network bridge either for the macOS vm (10g card) so I can't be 100% sure the issues wouldn't have occurred before the update. But the server consistently throws the errors under the conditions listed above. Thanks! backup-diagnostics-20191203-1711.zip
-
Hey!.... I can wait. You all are awesome to the max.
-
We’ve had a few issues in regards to it not compiling starting 2 RC,s ago including but not limited to not having time to work on why it’s not compiling due to being away from home, and wandering into technical areas beyond the scope of our collective knowledge. This combined with the problems the nvidia is currently having building caused the RMRR patch to fall on the back burner for the moment as they may (or may not) be similar issues and/or be a new second issue that will need to be resolved. with that said, I’m hoping to spend a little more time on this starting next week when I return from traveling. But we are definitely interested in assistance in getting it compiled so it can be available again!
-
Predictable retort is predictable.
-
Obvious post is obvious.
-
HP Proliant / Workstation & unRaid Information Thread
1812 replied to 1812's topic in General Support
remove the space after the coma for the last device id and reboot. you would have to check your scheduler and the logs to see what is happening at that time.... could be trim, could be anything. -
Transfers from a work station to ssd cache, bigger pipe out of the server to serve data to multiple clients from a single simpler connection, reads from the array that would normally saturate gigabit lan.... to name a few reasons why I have it. There are probably more.
-
shop eBay, they are half or less and many include cables
-
Perhaps instead of “Remark”’the text should say “Reminder” because I thought I was doing it wrong and forwarding wasn’t working because it kept showing up....partly due to the explanation in the first post about auto UDP... (and maybe I didn’t read all the explanation very closely and it is clear?)
-
I played around with this today and got it going. Pretty cool! Faster than the built in VPN in sophos as too! Leaving the following info as I use sophos UTM 9 and it might help anyone else using this firewall and this service: Setup NAT forwarding for port forward to your server as demonstrated here and automatically create a firewall rule: Setup WireGuard per the instructions at the top of this thread. For basic server and Lan access, you are done. If you want VPN access to the internet from a peer/client: Use the VPN address/pool provide by the wireguard setup for clients to use starting at xxx.xx.xx.0 and add a masquerading rule to allow that pool to access External (WAN). That's it. A note though, the plugin still complains about this: Remark: configure your router with port forwarding of port 51820/UDP to 86.75.30.9 But everything still works. Don't know if its a bug or if it's sophos being sophos. Either way, thanks for the great feature!
-
I've found that when this happens, click and hold, then drag the mouse cursor to where you want to be, then click again. It's a pain, but "works"
-
I'm planning on running it again to build a new vm image this afternoon on another server. Maybe something went wonky for me during install, even though it "worked" first time through! Again, many thanks for this, it's pretty awesome!
-
I have a gigabit connection but it looked like it was only downloading about 40mbps (per unRaid dashboard). Additionally a quick speedtest from fast.com after the vm was created, I was only showing 30-60mbps download, so possibly an issue with using vmxnet3 as the starting virtual Nic. As a test, I tried switching that for e1000-82545em in the vm but kept getting spinning beach balls, the vm wouldn't appear on the network for apple screen sharing, and I couldn't even load network settings in the vm (had to force shutdown.) There is a thread on here about the e1000-82545em causing issues with the apple store. The suggested fix is to use e1000e but when I booted with that, it didn't find it in the network control panel. Booting with 2 virtual nics, first as vmxnet and the other the e1000-82545em resulted in network control panel showing a cable unplugged for the e1000-82545em but network utilities refused to open. Safari also refused to launch and the vm hung while shutting down. Returning this to a single vmxnet 3 resolved the issues, but slow speed tests still continued. For disk type I used qcow2 and apfs.
