Hey Guys,

I am still fairly new. Been playing with the system for about 1.5 Months.

 

At this time I am currently looking for help getting my 1050TI and or 580GTX to work with VM. I think I have everything setup correctly at this point, but when I go to start the VM, it starts up and if I try to use my keyboard or wait long enough it crashes the whole system and I have to hard reset.

 

I am using the BIOS I dumped using Spaceinvader video (How to passthrough an nvidia gpu as primary gpu in unRAID - YouTube) .

 

From here I changed the Graphics ROM BIOS to : /mnt/user/system/asus1050ti.dump which is where I put it. - I am using my monitor and directly plugged into the Graphic card to view the OS. If I use VNC, everything is fine.

 

System Info:

M/B: Gigabyte Technology Co., Ltd. - Z97X-Gaming 5

CPU: Intel® Core™ i7-4790 CPU @ 3.60GHz

HVM: Enabled

IOMMU: Enabled

Cache: 256 kB, 1024 kB, 8192 kB

Memory: 24 GB (max. installable capacity 32 GB)

Array:

P-4TB

D1-4TB

D2-3TB

D3-2TB

D4-4TB

 

 

Some SysLogs

Apr 13 18:56:10 Tower kernel: BTRFS info (device loop2): disk space caching is enabled
Apr 13 18:56:10 Tower kernel: BTRFS info (device loop2): has skinny extents
Apr 13 18:56:10 Tower root: Resize '/var/lib/docker' of 'max'
Apr 13 18:56:10 Tower kernel: BTRFS info (device loop2): new size for /dev/loop2 is 21474836480
Apr 13 18:56:10 Tower emhttpd: shcmd (99): /etc/rc.d/rc.docker start
Apr 13 18:56:10 Tower root: starting dockerd ...
Apr 13 18:56:13 Tower kernel: ip_tables: (C) 2000-2006 Netfilter Core Team
Apr 13 18:56:13 Tower avahi-daemon[7371]: Joining mDNS multicast group on interface docker0.IPv4 with address 172.17.0.1.
Apr 13 18:56:13 Tower avahi-daemon[7371]: New relevant interface docker0.IPv4 for mDNS.
Apr 13 18:56:13 Tower avahi-daemon[7371]: Registering new address record for 172.17.0.1 on docker0.IPv4.
Apr 13 18:56:13 Tower kernel: IPv6: ADDRCONF(NETDEV_UP): docker0: link is not ready
Apr 13 18:56:15 Tower root: error: /plugins/preclear.disk/Preclear.php: wrong csrf_token
Apr 13 18:56:16 Tower emhttpd: shcmd (113): /usr/local/sbin/mount_image '/mnt/user/system/libvirt/libvirt.img' /etc/libvirt 1
Apr 13 18:56:16 Tower kernel: BTRFS info (device loop3): disk space caching is enabled
Apr 13 18:56:16 Tower kernel: BTRFS info (device loop3): has skinny extents
Apr 13 18:56:16 Tower root: Resize '/etc/libvirt' of 'max'
Apr 13 18:56:16 Tower kernel: BTRFS info (device loop3): new size for /dev/loop3 is 1073741824
Apr 13 18:56:16 Tower emhttpd: shcmd (115): /etc/rc.d/rc.libvirt start
Apr 13 18:56:16 Tower root: Starting virtlockd...
Apr 13 18:56:16 Tower root: Starting virtlogd...
Apr 13 18:56:16 Tower root: Starting libvirtd...
Apr 13 18:56:16 Tower kernel: tun: Universal TUN/TAP device driver, 1.6
Apr 13 18:56:16 Tower kernel: mdcmd (52): check correct
Apr 13 18:56:16 Tower kernel: md: recovery thread: check Q ...
Apr 13 18:56:16 Tower kernel: md: using 1536k window, over a total of 3907018532 blocks.
Apr 13 18:56:16 Tower kernel: ip6_tables: (C) 2000-2006 Netfilter Core Team
Apr 13 18:56:16 Tower root: error: /plugins/preclear.disk/Preclear.php: wrong csrf_token
Apr 13 18:56:16 Tower kernel: Ebtables v2.0 registered
Apr 13 18:56:16 Tower kernel: virbr0: port 1(virbr0-nic) entered blocking state
Apr 13 18:56:16 Tower kernel: virbr0: port 1(virbr0-nic) entered disabled state
Apr 13 18:56:16 Tower kernel: device virbr0-nic entered promiscuous mode
Apr 13 18:56:16 Tower avahi-daemon[7371]: Joining mDNS multicast group on interface virbr0.IPv4 with address 192.168.122.1.
Apr 13 18:56:16 Tower avahi-daemon[7371]: New relevant interface virbr0.IPv4 for mDNS.
Apr 13 18:56:16 Tower avahi-daemon[7371]: Registering new address record for 192.168.122.1 on virbr0.IPv4.
Apr 13 18:56:16 Tower kernel: virbr0: port 1(virbr0-nic) entered blocking state
Apr 13 18:56:16 Tower kernel: virbr0: port 1(virbr0-nic) entered listening state
Apr 13 18:56:17 Tower dnsmasq[9059]: started, version 2.78 cachesize 150
Apr 13 18:56:17 Tower dnsmasq[9059]: compile time options: IPv6 GNU-getopt no-DBus i18n IDN2 DHCP DHCPv6 no-Lua TFTP no-conntrack ipset auth no-DNSSEC loop-detect inotify
Apr 13 18:56:17 Tower dnsmasq-dhcp[9059]: DHCP, IP range 192.168.122.2 -- 192.168.122.254, lease time 1h
Apr 13 18:56:17 Tower dnsmasq-dhcp[9059]: DHCP, sockets bound exclusively to interface virbr0
Apr 13 18:56:17 Tower dnsmasq[9059]: reading /etc/resolv.conf
Apr 13 18:56:17 Tower dnsmasq[9059]: using nameserver 64.59.184.13#53
Apr 13 18:56:17 Tower dnsmasq[9059]: using nameserver 64.59.190.242#53
Apr 13 18:56:17 Tower dnsmasq[9059]: using nameserver 8.8.8.8#53
Apr 13 18:56:17 Tower dnsmasq[9059]: read /etc/hosts - 2 addresses
Apr 13 18:56:17 Tower dnsmasq[9059]: read /var/lib/libvirt/dnsmasq/default.addnhosts - 0 addresses
Apr 13 18:56:17 Tower dnsmasq-dhcp[9059]: read /var/lib/libvirt/dnsmasq/default.hostsfile
Apr 13 18:56:17 Tower kernel: virbr0: port 1(virbr0-nic) entered disabled state
Apr 13 18:56:29 Tower kernel: docker0: port 1(veth7772088) entered blocking state
Apr 13 18:56:29 Tower kernel: docker0: port 1(veth7772088) entered disabled state
Apr 13 18:56:29 Tower kernel: device veth7772088 entered promiscuous mode
Apr 13 18:56:29 Tower kernel: IPv6: ADDRCONF(NETDEV_UP): veth7772088: link is not ready
Apr 13 18:56:29 Tower kernel: docker0: port 1(veth7772088) entered blocking state
Apr 13 18:56:29 Tower kernel: docker0: port 1(veth7772088) entered forwarding state
Apr 13 18:56:29 Tower kernel: docker0: port 1(veth7772088) entered disabled state
Apr 13 18:56:32 Tower kernel: docker0: port 2(veth7d3244e) entered blocking state
Apr 13 18:56:32 Tower kernel: docker0: port 2(veth7d3244e) entered disabled state
Apr 13 18:56:32 Tower kernel: device veth7d3244e entered promiscuous mode
Apr 13 18:56:32 Tower kernel: IPv6: ADDRCONF(NETDEV_UP): veth7d3244e: link is not ready
Apr 13 18:56:32 Tower kernel: docker0: port 2(veth7d3244e) entered blocking state
Apr 13 18:56:32 Tower kernel: docker0: port 2(veth7d3244e) entered forwarding state
Apr 13 18:56:32 Tower kernel: docker0: port 2(veth7d3244e) entered disabled state
Apr 13 18:56:40 Tower kernel: eth0: renamed from veth294e914
Apr 13 18:56:40 Tower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth7772088: link becomes ready
Apr 13 18:56:40 Tower kernel: docker0: port 1(veth7772088) entered blocking state
Apr 13 18:56:40 Tower kernel: docker0: port 1(veth7772088) entered forwarding state
Apr 13 18:56:40 Tower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): docker0: link becomes ready
Apr 13 18:56:42 Tower avahi-daemon[7371]: Joining mDNS multicast group on interface docker0.IPv6 with address fe80::42:58ff:fe9d:8470.
Apr 13 18:56:42 Tower avahi-daemon[7371]: New relevant interface docker0.IPv6 for mDNS.
Apr 13 18:56:42 Tower avahi-daemon[7371]: Registering new address record for fe80::42:58ff:fe9d:8470 on docker0.*.
Apr 13 18:56:42 Tower avahi-daemon[7371]: Joining mDNS multicast group on interface veth7772088.IPv6 with address fe80::1404:dff:fef9:534f.
Apr 13 18:56:42 Tower avahi-daemon[7371]: New relevant interface veth7772088.IPv6 for mDNS.
Apr 13 18:56:42 Tower avahi-daemon[7371]: Registering new address record for fe80::1404:dff:fef9:534f on veth7772088.*.
Apr 13 18:56:45 Tower kernel: eth0: renamed from veth1ae39be
Apr 13 18:56:45 Tower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth7d3244e: link becomes ready
Apr 13 18:56:45 Tower kernel: docker0: port 2(veth7d3244e) entered blocking state
Apr 13 18:56:45 Tower kernel: docker0: port 2(veth7d3244e) entered forwarding state
Apr 13 18:56:45 Tower root: error: /plugins/preclear.disk/Preclear.php: wrong csrf_token
Apr 13 18:56:47 Tower avahi-daemon[7371]: Joining mDNS multicast group on interface veth7d3244e.IPv6 with address fe80::5cab:c4ff:feba:206e.
Apr 13 18:56:47 Tower avahi-daemon[7371]: New relevant interface veth7d3244e.IPv6 for mDNS.
Apr 13 18:56:47 Tower avahi-daemon[7371]: Registering new address record for fe80::5cab:c4ff:feba:206e on veth7d3244e.*.
Apr 13 19:11:04 Tower emhttpd: req (2): csrf_token=****************&title=System+Log&cmd=%2FwebGui%2Fscripts%2Ftail_log&arg1=syslog
Apr 13 19:11:04 Tower emhttpd: cmd: /usr/local/emhttp/plugins/dynamix/scripts/tail_log syslog

 

I would suggest that you post up your entire Diagnostics file       Tools   >>>  Diagnostics         with your next post.  That will give the Gurus a bit more meat to chew on.  

Attached Diagnotic

tower-diagnostics-20180414-1014.zip