Jerky_san
Members
-
Joined
Everything posted by Jerky_san
-
You probably need to check to make sure your ISP isn't blocking it. If it isn't perhaps you setup a VPN on your router that took the port?
-
Asus Zenith X399
-
Just tried this but sadly my performance seems to be a lot worse only using cpu cores from the numa where my gpu and m2 device is connected. FPS in dylight dropped from 100 to barely 60 with a lot more stuttering hitching.. Very strange. My board is kind of stupid as well since it maps the CPUs differently it appears than other people's boards on this forum with a 2990wx. Should say previously I was only mapping odd cores and leaving all even cores out. For some reason it improves performance even when it crosses dies. Second die contains my M.2 Drive and 1070. Other die has the drives all attached to it for unraid.
-
Almost sound like your forwarders aren't working on your router. Have you checked to make sure the ports are open internet facing?
-
Updated to RC4 and for some reason it claims I did an unclean shutdown even though I simply rebooted via the reboot option in the GUI and it fully went down clean as far as I can tell. No changes made besides restarting with RC4 update. tower-diagnostics-20180917-1951.zip
-
@linuxserver.io Any chance you could add SSLH to this docker? I want to be able to use ssh and website on the same port and it would let me if that one package was installed. Below is the package requested https://pkgs.alpinelinux.org/package/edge/testing/x86/sslh Below is what I'm trying to do: https://www.ostechnix.com/sslh-share-port-https-ssh/ Thanks
-
I am getting a trace wrote to the sys log right after the IP comes up on my unraid system. I honestly don't know what it means as its from a file called blk-core.c. Is this bad news bears? Should I not start my array? Sep 8 17:46:08 Tower avahi-daemon[11225]: Server startup complete. Host name is Tower.local. Local service cookie is 3033537634. Sep 8 17:46:08 Tower emhttpd: shcmd (57): udevadm settle Sep 8 17:46:09 Tower emhttpd: Autostart disabled Sep 8 17:46:09 Tower kernel: mdcmd (52): stop Sep 8 17:46:09 Tower kernel: md1: stopping Sep 8 17:46:09 Tower kernel: WARNING: CPU: 44 PID: 11259 at block/blk-core.c:781 blk_cleanup_queue+0xd5/0x16c Sep 8 17:46:09 Tower kernel: Modules linked in: md_mod bonding edac_mce_amd kvm_amd kvm mpt3sas crct10dif_pclmul igb crc32_pclmul crc32c_intel ghash_clmulni_intel pcbc aesni_intel aes_x86_64 crypto_simd cryptd k10temp raid_class scsi_transport_sas i2c_piix4 i2c_algo_bit glue_helper i2c_core ahci nvme libahci wmi_bmof mxm_wmi nvme_core wmi ccp button pcc_cpufreq acpi_cpufreq Sep 8 17:46:09 Tower kernel: CPU: 44 PID: 11259 Comm: emhttpd Not tainted 4.18.6-unRAID #1 Sep 8 17:46:09 Tower kernel: Hardware name: System manufacturer System Product Name/ROG ZENITH EXTREME, BIOS 1402 08/03/2018 Sep 8 17:46:09 Tower kernel: RIP: 0010:blk_cleanup_queue+0xd5/0x16c Sep 8 17:46:09 Tower kernel: Code: 00 e8 75 5c 02 00 48 8b 83 98 01 00 00 48 8d b8 80 03 00 00 e8 5f 2a e0 ff 48 89 df e8 cb fe ff ff f6 83 04 02 00 00 02 74 02 <0f> 0b 48 83 7b 18 00 74 1c 48 89 df e8 12 56 00 00 48 8b 73 18 48 Sep 8 17:46:09 Tower kernel: RSP: 0018:ffffc90007e0bbc8 EFLAGS: 00010202 Sep 8 17:46:09 Tower kernel: RAX: ffffffff81e32c00 RBX: ffff881038988000 RCX: 0000000000000000 Sep 8 17:46:09 Tower kernel: RDX: 0000000fffffff01 RSI: 0000000000000000 RDI: ffff881038988140 Sep 8 17:46:09 Tower kernel: RBP: ffff881057e968c8 R08: 0000000000000000 R09: ffff88105df5a540 Sep 8 17:46:09 Tower kernel: R10: ffffffffff492164 R11: ffff8810595ac400 R12: ffff8810389886c8 Sep 8 17:46:09 Tower kernel: R13: ffff881057e94008 R14: ffffffffa00c626f R15: 0000000000000000 Sep 8 17:46:09 Tower kernel: FS: 000014aaab790780(0000) GS:ffff88105df00000(0000) knlGS:0000000000000000 Sep 8 17:46:09 Tower kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Sep 8 17:46:09 Tower kernel: CR2: 000000000060b348 CR3: 00000010453ae000 CR4: 00000000003406e0 Sep 8 17:46:09 Tower kernel: Call Trace: Sep 8 17:46:09 Tower kernel: do_stop+0x45/0xab [md_mod] Sep 8 17:46:09 Tower kernel: stop_array.constprop.17+0x77/0x9c [md_mod] Sep 8 17:46:09 Tower kernel: md_proc_write+0x1223/0x163d [md_mod] Sep 8 17:46:09 Tower kernel: ? walk_component+0xc2/0x249 Sep 8 17:46:09 Tower kernel: ? proc_reg_open+0xdf/0xf9 Sep 8 17:46:09 Tower kernel: ? proc_i_callback+0x13/0x13 Sep 8 17:46:09 Tower kernel: ? _cond_resched+0x1b/0x1e Sep 8 17:46:09 Tower kernel: ? dput.part.5+0x33/0xea Sep 8 17:46:09 Tower kernel: ? path_put+0xd/0x16 Sep 8 17:46:09 Tower kernel: ? path_openat+0xb2d/0xc07 Sep 8 17:46:09 Tower kernel: ? do_filp_open+0x83/0xa9 Sep 8 17:46:09 Tower kernel: ? rcu_is_watching+0x5/0x9 Sep 8 17:46:09 Tower kernel: proc_reg_write+0x41/0x5f Sep 8 17:46:09 Tower kernel: ? proc_reg_poll+0x54/0x54 Sep 8 17:46:09 Tower kernel: __vfs_write+0x2e/0x13b Sep 8 17:46:09 Tower kernel: vfs_write+0xc3/0x166 Sep 8 17:46:09 Tower kernel: ksys_write+0x58/0xa6 Sep 8 17:46:09 Tower kernel: do_syscall_64+0x57/0xe6 Sep 8 17:46:09 Tower kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9 Sep 8 17:46:09 Tower kernel: RIP: 0033:0x14aaab36fe81 Sep 8 17:46:09 Tower kernel: Code: c3 0f 1f 84 00 00 00 00 00 48 8b 05 59 91 20 00 c3 0f 1f 84 00 00 00 00 00 8b 05 6a d5 20 00 85 c0 75 16 b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 57 f3 c3 0f 1f 44 00 00 41 54 55 49 89 d4 53 Sep 8 17:46:09 Tower kernel: RSP: 002b:00007ffe001c1bb8 EFLAGS: 00000246 ORIG_RAX: 0000000000000001 Sep 8 17:46:09 Tower kernel: RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 000014aaab36fe81 Sep 8 17:46:09 Tower kernel: RDX: 0000000000000004 RSI: 00007ffe001c1bf0 RDI: 0000000000000005 Sep 8 17:46:09 Tower kernel: RBP: 00007ffe001c1d40 R08: 0000000000000000 R09: 0000000000000001 Sep 8 17:46:09 Tower kernel: R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000402c60 Sep 8 17:46:09 Tower kernel: R13: 00007ffe001c1fb0 R14: 0000000000000000 R15: 0000000000000000 Sep 8 17:46:09 Tower kernel: ---[ end trace dadb098376631c44 ]--- Sep 8 17:46:09 Tower kernel: md2: stopping Sep 8 17:46:09 Tower kernel: md3: stopping Sep 8 17:46:09 Tower kernel: md4: stopping Sep 8 17:46:09 Tower kernel: md5: stopping Sep 8 17:46:09 Tower kernel: md6: stopping Sep 8 17:46:09 Tower kernel: md7: stopping Sep 8 17:46:09 Tower kernel: md8: stopping Sep 8 17:46:09 Tower kernel: md9: stopping Sep 8 17:46:09 Tower kernel: md10: stopping Sep 8 17:46:09 Tower kernel: md11: stopping Sep 8 17:46:09 Tower kernel: md12: stopping Sep 8 17:46:09 Tower kernel: md13: stopping Sep 8 17:46:09 Tower kernel: md14: stopping Sep 8 17:46:09 Tower avahi-daemon[11225]: Service "Tower" (/services/ssh.service) successfully established. Sep 8 17:46:09 Tower avahi-daemon[11225]: Service "Tower" (/services/smb.service) successfully established. Sep 8 17:46:09 Tower avahi-daemon[11225]: Service "Tower" (/services/sftp-ssh.service) successfully established. Sep 8 17:46:17 Tower root: error: /plugins/preclear.disk/Preclear.php: wrong csrf_token Sep 8 17:46:38 Tower root: error: /plugins/preclear.disk/Preclear.php: wrong csrf_token Sep 8 17:47:49 Tower ool www[12647]: /usr/local/emhttp/plugins/dynamix/scripts/emhttpd_update Sep 8 17:47:49 Tower emhttpd: req (1): cmdStatus=apply&csrf_token=**************** Sep 8 17:47:49 Tower emhttpd: Starting services... Sep 8 17:48:12 Tower ool www[14046]: /usr/local/emhttp/plugins/dynamix/scripts/bootmode '0' tower-diagnostics-20180908-1748.zip
-
64 GB non ecc 3200 cl15-15-15-35 but its b die so can run at 14s-34. Going to buy another 64 GB when the price goes down.
-
So I have a gaming VM that runs 16 cores(pair threaded) with those cores isolated at boot. When mover or something is running in unraid I can 100% tell in game. Its like unraid is using those cores even though I have specifically said not to. A test I performed was run mover than run a "Dying Light" which usually runs at max fps at 1080p with nearly everything turned to max. When mover is running there is constant stutter. I traced this back to my first CPU core in the VM is showing around 85% utilization but unraid is saying its nearly 100%. It appears something is adding CPU usage on top of the actual usage. I then stop the mover and it shows what task manager shows in the VM. I would assume Unraid would use one of the other "64smt/32physical" cores that I have but it doesn't appear to want to. 2990wx 1070GTX 64GB 3200 CL15-15-15-35 ram Edit: Realized I didn't show the CPU isolation stuff for booting label unRAID OS menu default kernel /bzimage append isolcpus=0,1,2,3,4,5,6,7,32,33,34,35,36,37,38,39 vfio-pci.ids=1022:145f initrd=/bzroot label unRAID OS GUI Mode kernel /bzimage append isolcpus=0,1,2,3,4,5,6,7,32,33,34,35,36,37,38,39 vfio-pci.ids=1022:145f initrd=/bzroot,/bzroot-gui Pictures and diagnostics included tower-diagnostics-20180905-1100.zip
-
Most of my problems surround the editing of VMs. It appears if I edit the XML at all I am unable afterwords to save anything done in the GUI. Say I want to remove a hard drive or tick a box for CPUs or deselect some CPUs. None of it appears to work after editing the XML to add an NVME pass through. I have to fully recreate the machine each time. I also encountered an oddity where my machine wouldn't shutdown so I attempted to force it to shutdown and it errored. After that it eventually did but then it wouldn't release the image file libvirt.img and I ended up having to stop the array and start it again. I am attaching a diagnostic to reflect that part. So far past that I've not ran into any bugs. tower-diagnostics-20180902-0028.zip
-
Updated to 6.6rc1 and still won't pass through sadly. This is on my new threadripper build. Zenith x399 and 2990wx.
-
un 10 11:46:28 Tower kernel: ------------[ cut here ]------------ Jun 10 11:46:28 Tower kernel: WARNING: CPU: 2 PID: 8996 at fs/namespace.c:1169 cleanup_mnt+0x11/0x5c Jun 10 11:46:28 Tower kernel: Modules linked in: md_mod xt_CHECKSUM iptable_mangle ipt_REJECT nf_reject_ipv4 ebtable_filter ebtables ip6table_filter ip6_tables tun xt_nat veth ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 iptable_filter ip_tables nf_nat xfs bonding edac_mce_amd crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel pcbc aesni_intel aes_x86_64 crypto_simd glue_helper igb mpt3sas wmi_bmof mxm_wmi cryptd ptp i2c_piix4 pps_core i2c_algo_bit i2c_core raid_class scsi_transport_sas ccp ahci nvme libahci nvme_core wmi button acpi_cpufreq [last unloaded: kvm] Jun 10 11:46:28 Tower kernel: CPU: 2 PID: 8996 Comm: umount Tainted: G D W 4.14.41-unRAID #1 Jun 10 11:46:28 Tower kernel: Hardware name: System manufacturer System Product Name/PRIME X370-PRO, BIOS 4011 04/19/2018 Jun 10 11:46:28 Tower kernel: task: ffff880575bc8000 task.stack: ffffc9000d4d8000 Jun 10 11:46:28 Tower kernel: RIP: 0010:cleanup_mnt+0x11/0x5c Jun 10 11:46:28 Tower kernel: RSP: 0018:ffffc9000d4dbef8 EFLAGS: 00010202 Jun 10 11:46:28 Tower kernel: RAX: 0000000000000001 RBX: ffff88048325b780 RCX: 0000000000000000 Jun 10 11:46:28 Tower kernel: RDX: 0000000000000100 RSI: 0000000000000000 RDI: ffffffff81ca04c0 Jun 10 11:46:28 Tower kernel: RBP: 0000000000000000 R08: ffffffffffff0000 R09: 000000000000ffff Jun 10 11:46:28 Tower kernel: R10: 0000000000000000 R11: ffff880575bc8080 R12: ffffffff81fd8390 Jun 10 11:46:28 Tower kernel: R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000 Jun 10 11:46:28 Tower kernel: FS: 0000153bb2bc9780(0000) GS:ffff88101ec80000(0000) knlGS:0000000000000000 Jun 10 11:46:28 Tower kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Jun 10 11:46:28 Tower kernel: CR2: 000014b7b5803be0 CR3: 0000000fd409e000 CR4: 00000000003406e0 Jun 10 11:46:28 Tower kernel: Call Trace: Jun 10 11:46:28 Tower kernel: task_work_run+0x77/0x8b Jun 10 11:46:28 Tower kernel: exit_to_usermode_loop+0x46/0x75 Jun 10 11:46:28 Tower kernel: do_syscall_64+0xf7/0xfe Jun 10 11:46:28 Tower kernel: entry_SYSCALL_64_after_hwframe+0x3d/0xa2 Jun 10 11:46:28 Tower kernel: RIP: 0033:0x153bb1e3bec7 Jun 10 11:46:28 Tower kernel: RSP: 002b:00007fffc7d72988 EFLAGS: 00000246 ORIG_RAX: 00000000000000a6 Jun 10 11:46:28 Tower kernel: RAX: 0000000000000000 RBX: 00000000006072b0 RCX: 0000153bb1e3bec7 Jun 10 11:46:28 Tower kernel: RDX: 0000000000000001 RSI: 0000000000000000 RDI: 000000000060a3a0 Jun 10 11:46:28 Tower kernel: RBP: 0000000000000000 R08: 0000000000000000 R09: 0000153bb1e85a30 Jun 10 11:46:28 Tower kernel: R10: 0000000000000008 R11: 0000000000000246 R12: 000000000060a3a0 Jun 10 11:46:28 Tower kernel: R13: 0000153bb29b4ed0 R14: 0000000000607490 R15: 0000000000000000 Jun 10 11:46:28 Tower kernel: Code: c8 49 8b 14 24 48 8b 0c cd c0 83 b9 81 03 5c 0a 04 eb d9 89 d8 5b 5d 41 5c c3 53 48 89 fb 48 83 c7 48 e8 b2 ff ff ff 85 c0 74 02 <0f> 0b 48 83 bb 28 01 00 00 00 74 08 48 89 df e8 a3 d0 00 00 48 Jun 10 11:46:28 Tower kernel: ---[ end trace 97d33381545a92b2 ]--- tower-diagnostics-20180610-1153.zip
-
<hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </hostdev> Here is the XML where it lets you mount it without stubbing it via the video.
-
So I went both ways stubbed/not. The guide is for doing it without stubbing it. Both result in the same error. The VM's XML currently doesn't have it on there because it is my normal gaming machine so I'll have to re-add it. I'll get it in a little after I finish this work.
-
Any guesses?
-
Sorry I thought I had deleted the one in General Support
-
So I got my gaming machine up and running on a Ryzen system with a gpu passthrough and everything going good. Last thing I want to do is pass through an NVME drive to the machine but I keep getting this error internal error: qemu unexpectedly closed the monitor: 2018-06-04T23:48:57.302131Z qemu-system-x86_64: -device vfio-pci,host=01:00.0,id=hostdev2,bus=pci.0,addr=0x8: vfio error: 0000:01:00.0: failed to add PCI capability 0x11[0x50]@0xb0: table & pba overlap, or they don't fit in BARs, or don't align https://i.imgur.com/NDShzQT.png I used this guide Anyone have any suggestions? tower-diagnostics-20180604-1852.zip
-
woke up to plex being down this morning but log wasn't wrote. Going to try to get a lot for it this time.
-
Sadly same plex dead ;-;
-
Also I though the cache drive being enabled just ment that anything new would be wrote to cache then moved to the drives on a schedule. It appears that its trying to move everything from my storage to my cache drive and failing.
-
So I am kind of in the same boat here.. the mover is running trying to move files onto the cache filling it up and I've turned off caching on my shares but can't kill the mover and I was in the middle of adding a second parity so I can't exactly restart either.. None of the commands in this thread kill the mover.. The rsyncs just keep coming back like zombies.. Are there any other commands that can be used?
