Lytic

After a reboot of my system I can no longer boot into UnRAID without choosing "safe mode" (booting with the GUI but with plugins disabled). I assume this is caused by a plugin... but without being able to view plugins while booted into UnRAID in safe mode, how do I go about testing which plugin is at fault?

I have a custom script running at startup that disengages/unbinds Unraid's use of the graphics card. This, in turn, allows a VM to begin using it once the VM has started. As a result, Unraid doesn't require dedicated graphics once this process has occurred. Below is that code. echo 0 > /sys/class/vtconsole/vtcon0/bind echo 0 > /sys/class/vtconsole/vtcon1/bind echo efi-framebuffer.0 > /sys/bus/platform/drivers/efi-framebuffer/unbind I'm running an Asrock X470 Taichi motherboard, BIOS v.P2.00. I've heard that newer BIOS versions have caused issues with passthrough - which is why I've stayed on that version. As a side note, I have a GTX 760 in the second slot, running High Sierra VM for my wife - which is still working perfectly.

Unfortunately, this didn't work. I reinstalled the drivers from the linked page, added the emulated NVRAM, and made sure my System Parameters were identical to the ones listed above (and they were). I'm still getting a failed boot unless I include "nv_disable=1". Edit: Well, I re-installed High Sierra and now the graphics card is showing - even with "nv_disable=1", but I'm still not able to get the graphics card to boot in MacOS. Still able to get it to boot in Windows. Interestingly enough, when viewing its specs in "about this Mac" it only shows as having 256 MB of VRAM. Odd.

Up until yesterday I was running High Sierra with a Ryzen 1700x and Nvidia 1080 Ti. Unfortunately, I can't determine what ruined my setup and started from scratch. After going back through SpaceInvaderOne's tutorial I get stuck after installing the Nvidia Web Drivers. High Sierra will boot with "nv_disable=1", but not with the web drivers enabled. My 1080 Ti is installed in the first PCIe slot and has the appropriate vBios loaded in the XML (and is working with an identical setup on a Windows VM). The graphics card is not being detected by High Sierra (maybe because of the "nv_disable=1"?), but for whatever reason I am able to get video from one of the HDMI slots on the GPU. None of the other slots are functioning. Any help would be greatly appreciated. <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'> <name>High_Sierra_Lytic</name> <uuid>64310a84-7475-bd87-b9a3-bacb07c571c5</uuid> <metadata> <vmtemplate xmlns="unraid" name="Linux" icon="linux.png" os="linux"/> </metadata> <memory unit='KiB'>12582912</memory> <currentMemory unit='KiB'>12582912</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>8</vcpu> <cputune> <vcpupin vcpu='0' cpuset='8'/> <vcpupin vcpu='1' cpuset='9'/> <vcpupin vcpu='2' cpuset='10'/> <vcpupin vcpu='3' cpuset='11'/> <vcpupin vcpu='4' cpuset='12'/> <vcpupin vcpu='5' cpuset='13'/> <vcpupin vcpu='6' cpuset='14'/> <vcpupin vcpu='7' cpuset='15'/> </cputune> <os> <type arch='x86_64' machine='pc-q35-3.1'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/64310a84-7475-bd87-b9a3-bacb07c571c5_VARS-pure-efi.fd</nvram> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough' check='none'> <topology sockets='1' cores='8' threads='1'/> </cpu> <clock offset='utc'> <timer name='rtc' tickpolicy='catchup'/> <timer name='pit' tickpolicy='delay'/> <timer name='hpet' present='no'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/local/sbin/qemu</emulator> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/user/domains/High_Sierra_Lytic/vdisk3.img'/> <target dev='hdc' bus='sata'/> <boot order='1'/> <address type='drive' controller='0' bus='0' target='0' unit='2'/> </disk> <controller type='pci' index='0' model='pcie-root'/> <controller type='pci' index='1' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='1' port='0x8'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0' multifunction='on'/> </controller> <controller type='pci' index='2' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='2' port='0x9'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <controller type='pci' index='3' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='3' port='0xa'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/> </controller> <controller type='pci' index='4' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='4' port='0x13'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x3'/> </controller> <controller type='pci' index='5' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='5' port='0xb'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x3'/> </controller> <controller type='pci' index='6' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='6' port='0xc'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x4'/> </controller> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/> </controller> <controller type='sata' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/> </controller> <controller type='usb' index='0' model='ich9-ehci1'> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <master startport='0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0' multifunction='on'/> </controller> <controller type='usb' index='0' model='ich9-uhci2'> <master startport='2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/> </controller> <controller type='usb' index='0' model='ich9-uhci3'> <master startport='4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/> </controller> <interface type='bridge'> <mac address='52:54:00:10:21:d1'/> <source bridge='br0'/> <model type='vmxnet3'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </interface> <serial type='pty'> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> </serial> <console type='pty'> <target type='serial' port='0'/> </console> <channel type='unix'> <target type='virtio' name='org.qemu.guest_agent.0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='tablet' bus='usb'> <address type='usb' bus='0' port='1'/> </input> <input type='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x2e' slot='0x00' function='0x0'/> </source> <rom file='/mnt/user/domains/vbios/EVGA1080TI.rom'/> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x2e' slot='0x00' function='0x1'/> </source> <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x31' slot='0x00' function='0x3'/> </source> <address type='pci' domain='0x0000' bus='0x05' slot='0x00' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x30' slot='0x00' function='0x3'/> </source> <address type='pci' domain='0x0000' bus='0x06' slot='0x00' function='0x0'/> </hostdev> <memballoon model='none'/> </devices> <qemu:commandline> <qemu:arg value='-usb'/> <qemu:arg value='-device'/> <qemu:arg value='usb-mouse,bus=usb-bus.0'/> <qemu:arg value='-device'/> <qemu:arg value='usb-kbd,bus=usb-bus.0'/> <qemu:arg value='-device'/> <qemu:arg value='isa-applesmc,osk=xxxxxxxxxxxxxxxxxx/> <qemu:arg value='-smbios'/> <qemu:arg value='type=2'/> <qemu:arg value='-cpu'/> <qemu:arg value='Penryn,vendor=GenuineIntel,kvm=on,+invtsc,+avx,+avx2,+aes,+xsave,+xsaveopt,vmware-cpuid-freq=on,'/> </qemu:commandline> </domain>

Just wanted to give you guys an update on the SYN Flooding issue. As it so happens, that Syn Flooding was a symptom in the log of another issue: Auto Managing on Deluge. Apparently this has been an ongoing issue for at least the last four years at certain private trackers, but the "Auto Manage" feature of Deluge makes torrents unconnectable shortly after they've completed downloading. Highlighting all of my torrents, right clicking, selecting "options", then "auto managed", and then "off" fixes all of my connectability problems and Syn Flooding no longer shows up in my log. Unfortunately I have to manually turn off Auto Managing to each and every file after it begins downloading. Is there a way to permanently disable Auto Managing in Deluge?

DelugeVPN will not start if the VPN does not connect. If you would like to see the IP address, you can download a torrent ip checker. Once you add the torrent to your client, click on the torrent and look down under either your "status" or "details" tab to view the IP address the torrent recorded.

Does anyone have any ideas about my issue? I only have 10 more days on my unRAID trial and I can't commit to purchasing it if I continue having this issue. By the way, here is a section of my log file. It looks like SYN flooding may be connected to my connection problems? Nov 19 03:58:42 unRAID kernel: docker0: port 2(veth90dd007) entered disabled state Nov 19 03:58:42 unRAID kernel: device veth90dd007 left promiscuous mode Nov 19 03:58:42 unRAID kernel: docker0: port 2(veth90dd007) entered disabled state Nov 19 03:58:43 unRAID kernel: docker0: port 2(veth83ec97d) entered blocking state Nov 19 03:58:43 unRAID kernel: docker0: port 2(veth83ec97d) entered disabled state Nov 19 03:58:43 unRAID kernel: device veth83ec97d entered promiscuous mode Nov 19 03:58:43 unRAID kernel: docker0: port 2(veth83ec97d) entered blocking state Nov 19 03:58:43 unRAID kernel: docker0: port 2(veth83ec97d) entered forwarding state Nov 19 03:58:43 unRAID kernel: eth0: renamed from veth150ac6b Nov 19 04:23:05 unRAID kernel: TCP: request_sock_TCP: Possible SYN flooding on port 27515. Sending cookies. Check SNMP counters. Thanks!

Question / Problem: I have been using DelugeVPN and I seem to be having issues with port forwarding with PIA. I know that DelugeVPN automatically designates Deluge's incoming port to reflect the single open port reported by PIA. Once I see this port in Deluge's settings I hop over to my router's GUI and open the port manually through my router. At this point, all of my torrents become connectable to each tracker's server. My problem is that every day or so my torrents become unconnectable. If I go back into my settings the port has not changed and if I go back to my router the port is still open. In order to fix this problem I have to manually restart DelugeVPN every morning and go back through to open my ports. What is going wrong? And how can I become connectable without restarting the docker every single day? Thanks a ton in advance.