jrc1883

Does anyone have any ideas, I have tries all I can think of. I have attached the full log file. unjoe-diagnostics-20161027-1812.zip

[EDIT] For some reason the wrong URL was being retrieved. I went into /tmp/plugins and found the appropriate .plg file and edited it so that it pulled from the right URL and I am back up and running with the latest version! I am trying to update unRAID Server OS from 6.2.0-rc3 to 6.2.0-stable and I am getting this message: plugin: updating: unRAIDServer.plg plugin: downloading: https://s3.amazonaws.com/dnld.lime-technology.com/stable/unRAIDServer-6.2-x86_64.zip ... failed (Invalid URL / Server error response) plugin: wget: https://s3.amazonaws.com/dnld.lime-technology.com/stable/unRAIDServer-6.2-x86_64.zip download failure (Invalid URL / Server error response) Also for Dynamix webGui from 2016.07.27 to 2016.09.15: plugin: updating: dynamix.plg plugin: downloading: "https://github.com/limetech/dynamix/archive/2016.09.15.tar.gz" ... failed (Invalid URL / Server error response) plugin: wget: "https://github.com/limetech/dynamix/archive/2016.09.15.tar.gz" download failure (Invalid URL / Server error response) all other plugins updated fine. From syslog: Oct 26 19:56:14 Unjoe emhttp: cmd: /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin update unRAIDServer.plg Oct 26 19:56:14 Unjoe root: plugin: creating: /tmp/unRAIDServer.sh - from INLINE content Oct 26 19:56:14 Unjoe root: plugin: running: /tmp/unRAIDServer.sh Oct 26 19:56:14 Unjoe root: plugin: creating: /tmp/unRAIDServer.zip - downloading from URL https://s3.amazonaws.com/dnld.lime-technology.com/stable/unRAIDServer-6.2-x86_64.zip Oct 26 19:57:18 Unjoe emhttp: cmd: /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin update dynamix.plg Oct 26 19:57:18 Unjoe root: plugin: creating: /boot/config/plugins/dynamix/dynamix-2016.09.15.tar.gz - downloading from URL https://github.com/limetech/dynamix/archive/2016.09.15.tar.gz If I try to manually enter a URL, for example with the URL: https://s3.amazonaws.com/dnld.lime-technology.com/stable/unRAIDServer-6.2.2-x86_64.zip I get another error: plugin: installing: https://s3.amazonaws.com/dnld.lime-technology.com/stable/unRAIDServer-6.2.2-x86_64.zip plugin: downloading https://s3.amazonaws.com/dnld.lime-technology.com/stable/unRAIDServer-6.2.2-x86_64.zip plugin: downloading: https://s3.amazonaws.com/dnld.lime-technology.com/stable/unRAIDServer-6.2.2-x86_64.zip ... done Warning: simplexml_load_file(): /tmp/plugins/unRAIDServer-6.2.2-x86_64.zip:1: parser error : Start tag expected, '<' not found in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 214 Warning: simplexml_load_file(): PK in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 214 Warning: simplexml_load_file(): ^ in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 214 Warning: simplexml_load_file(): /tmp/plugins/unRAIDServer-6.2.2-x86_64.zip:1: parser error : Start tag expected, '<' not found in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 214 Warning: simplexml_load_file(): PK in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 214 Warning: simplexml_load_file(): ^ in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 214 Warning: simplexml_load_file(): /tmp/plugins/unRAIDServer-6.2.2-x86_64.zip:1: parser error : Start tag expected, '<' not found in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 214 Warning: simplexml_load_file(): PK in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 214 Warning: simplexml_load_file(): ^ in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 214 plugin: xml parse error Any help would be awesome!

OK, I have had a WIN 10 VM running for about a month stable. I went on vacation so I shut my VM down. When I came back from vacation and started my VM it went into a perpetual BSOD boot loop with a SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (NETIO.SYS) error. I have tried a few configuration things with no luck. What is needed by me for this awesome community to help me troubleshoot this?

UPDATE: I gave a fixed amount of memory (16gb) instead of a min and max and have been running solid for about a week now. Thanks a lot!! Hello all! I currently have a Windows 10 VM setup that will randomly log out (~30 min-90 min). This has happened while I was actively typing away on my VM. I'll give the basic details but please let me know what logs & additional info is needed. I am new to unraid but not to the *nix general environment. -Unraid 5 beta 21 (I know, I know, its beta thanks ahead of time for Capt. Obvious) -No dockers currently enabled Hardware: -Intel i7 - 6700k -32 gb of viper memory (2x16gb) -(2) nvidia 960's in sli for VM. -Intel cpu for unraid graphics I have went through all the windows 10 vm customization/tweaks as discussed in the documentation. I have min of 2gb ram assigned, max of 16gb. xml file: <domain type='kvm' id='1'> <name>Windows 10</name> <uuid>57a97c8c-d7ae-31be-5110-44ee34587c28</uuid> <metadata> <vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/> </metadata> <memory unit='KiB'>2097152</memory> <currentMemory unit='KiB'>2097152</currentMemory> <memoryBacking> <nosharepages/> <locked/> </memoryBacking> <vcpu placement='static'>4</vcpu> <cputune> <vcpupin vcpu='0' cpuset='4'/> <vcpupin vcpu='1' cpuset='5'/> <vcpupin vcpu='2' cpuset='6'/> <vcpupin vcpu='3' cpuset='7'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-q35-2.5'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/57a97c8c-d7ae-31be-5110-44ee34587c28_VARS-pure-efi.fd</nvram> </os> <features> <acpi/> <apic/> <hyperv> <relaxed state='on'/> <vapic state='on'/> <spinlocks state='on' retries='8191'/> <vendor id='none'/> </hyperv> </features> <cpu mode='host-passthrough'> <topology sockets='1' cores='2' threads='2'/> </cpu> <clock offset='localtime'> <timer name='hypervclock' present='yes'/> <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/vms/Windows 10/vdisk1.img'/> <backingStore/> <target dev='hdc' bus='virtio'/> <boot order='1'/> <alias name='virtio-disk2'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x03' function='0x0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/vms/ISOs/virtio-win-0.1.112-1.iso'/> <backingStore/> <target dev='hdb' bus='sata'/> <readonly/> <alias name='sata0-0-1'/> <address type='drive' controller='0' bus='0' target='0' unit='1'/> </disk> <controller type='usb' index='0' model='nec-xhci'> <alias name='usb'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/> </controller> <controller type='sata' index='0'> <alias name='ide'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/> </controller> <controller type='pci' index='0' model='pcie-root'> <alias name='pcie.0'/> </controller> <controller type='pci' index='1' model='dmi-to-pci-bridge'> <model name='i82801b11-bridge'/> <alias name='pci.1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x1e' function='0x0'/> </controller> <controller type='pci' index='2' model='pci-bridge'> <model name='pci-bridge'/> <target chassisNr='2'/> <alias name='pci.2'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x01' function='0x0'/> </controller> <controller type='virtio-serial' index='0'> <alias name='virtio-serial0'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x02' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:cb:c3:ba'/> <source bridge='br0'/> <target dev='vnet0'/> <model type='virtio'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x01' function='0x0'/> </interface> <serial type='pty'> <source path='/dev/pts/0'/> <target port='0'/> <alias name='serial0'/> </serial> <console type='pty' tty='/dev/pts/0'> <source path='/dev/pts/0'/> <target type='serial' port='0'/> <alias name='serial0'/> </console> <channel type='unix'> <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/domain-Windows 10/org.qemu.guest_agent.0'/> <target type='virtio' name='org.qemu.guest_agent.0' state='connected'/> <alias name='channel0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </source> <alias name='hostdev0'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x04' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x02' slot='0x00' function='0x0'/> </source> <alias name='hostdev1'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x05' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x01' slot='0x00' function='0x1'/> </source> <alias name='hostdev2'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x06' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x02' slot='0x00' function='0x1'/> </source> <alias name='hostdev3'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x07' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x046d'/> <product id='0xc52b'/> <address bus='1' device='3'/> </source> <alias name='hostdev4'/> </hostdev> <memballoon model='virtio'> <alias name='balloon0'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x08' function='0x0'/> </memballoon> </devices> </domain> VM log file: 2016-04-09 15:30:01.423+0000: starting up libvirt version: 1.3.1, qemu version: 2.5.1, hostname: Unjoe LC_ALL=C PATH=/bin:/sbin:/usr/bin:/usr/sbin HOME=/ QEMU_AUDIO_DRV=none /usr/local/sbin/qemu -name 'Windows 10' -S -machine pc-q35-2.5,accel=kvm,usb=off,mem-merge=off -cpu host,hv_time,hv_relaxed,hv_vapic,hv_spinlocks=0x1fff,hv_vendor_id=none -drive file=/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd,if=pflash,format=raw,unit=0,readonly=on -drive file=/etc/libvirt/qemu/nvram/57a97c8c-d7ae-31be-5110-44ee34587c28_VARS-pure-efi.fd,if=pflash,format=raw,unit=1 -m 2048 -realtime mlock=on -smp 4,sockets=1,cores=2,threads=2 -uuid 57a97c8c-d7ae-31be-5110-44ee34587c28 -nographic -no-user-config -nodefaults -chardev 'socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-Windows 10/monitor.sock,server,nowait' -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime -no-hpet -no-shutdown -boot strict=on -device i82801b11-bridge,id=pci.1,bus=pcie.0,addr=0x1e -device pci-bridge,chassis_nr=2,id=pci.2,bus=pci.1,addr=0x1 -device nec-usb-xhci,id=usb,bus=pcie.0,addr=0x7 -device:00.1,id=hostdev2,bus=pci.2,addr=0x6 -device vfio-pci,host=02:00.1,id=hostdev3,bus=pci.2,addr=0x7 -device usb-host,hostbus=1,hostaddr=3,id=hostdev4 -device virtio-balloon-pci,id=balloon0,bus=pci.2,addr=0x8 -msg timestamp=on Domain id=1 is tainted: high-privileges Domain id=1 is tainted: host-cpu char device redirected to /dev/pts/0 (label charserial0) System log (2 log outs occurred during this time: Apr 10 18:45:24 Unjoe kernel: usb 1-13: reset full-speed USB device number 3 using xhci_hcd Apr 10 18:45:24 Unjoe kernel: usb 1-13: reset full-speed USB device number 3 using xhci_hcd Apr 10 18:45:25 Unjoe kernel: usb 1-13: reset full-speed USB device number 3 using xhci_hcd Apr 10 18:45:27 Unjoe dhcpcd[1856]: br0: xid 0x3f6ece53 is for hwaddr 52:54:00:cb:c3:ba:00:00:00:00:00:00:00:00:00:00 Apr 10 18:47:30 Unjoe dhcpcd[1856]: br0: xid 0x23792124 is for hwaddr dc:85:de:8a:1e:c8:00:00:00:00:00:00:00:00:00:00 Apr 10 18:47:52 Unjoe dhcpcd[1856]: br0: xid 0xa0d551e3 is for hwaddr dc:85:de:8a:1e:c8:00:00:00:00:00:00:00:00:00:00 Apr 10 18:53:04 Unjoe dhcpcd[1856]: br0: xid 0xa949652 is for hwaddr dc:85:de:8a:1e:c8:00:00:00:00:00:00:00:00:00:00 Apr 10 19:00:34 Unjoe dhcpcd[1856]: br0: xid 0xf8cb4c2a is for hwaddr dc:85:de:8a:1e:c8:00:00:00:00:00:00:00:00:00:00 Apr 10 19:13:34 Unjoe kernel: usb 1-13: reset full-speed USB device number 3 using xhci_hcd Apr 10 19:13:35 Unjoe kernel: usb 1-13: reset full-speed USB device number 3 using xhci_hcd Apr 10 19:13:40 Unjoe kernel: usb 1-13: reset full-speed USB device number 3 using xhci_hcd Apr 10 19:13:40 Unjoe kernel: usb 1-13: reset full-speed USB device number 3 using xhci_hcd Apr 10 19:13:41 Unjoe kernel: usb 1-13: reset full-speed USB device number 3 using xhci_hcd Apr 10 19:13:43 Unjoe dhcpcd[1856]: br0: xid 0xb78d6b8b is for hwaddr 52:54:00:cb:c3:ba:00:00:00:00:00:00:00:00:00:00 Apr 10 19:15:46 Unjoe dhcpcd[1856]: br0: xid 0xbcce7b20 is for hwaddr dc:85:de:8a:1e:c8:00:00:00:00:00:00:00:00:00:00 Apr 10 19:21:20 Unjoe dhcpcd[1856]: br0: xid 0xd53ed25e is for hwaddr dc:85:de:8a:1e:c8:00:00:00:00:00:00:00:00:00:00 Apr 10 19:36:51 Unjoe dhcpcd[1856]: br0: xid 0xb7fed898 is for hwaddr dc:85:de:8a:1e:c8:00:00:00:00:00:00:00:00:00:00 Apr 10 19:51:20 Unjoe dhcpcd[1856]: br0: xid 0x44b03bc9 is for hwaddr dc:85:de:8a:1e:c8:00:00:00:00:00:00:00:00:00:00 Apr 10 20:01:17 Unjoe dhcpcd[1856]: br0: xid 0xc588e367 is for hwaddr dc:85:de:8a:1e:c8:00:00:00:00:00:00:00:00:00:00 Apr 10 20:21:20 Unjoe dhcpcd[1856]: br0: xid 0xd90798a7 is for hwaddr dc:85:de:8a:1e:c8:00:00:00:00:00:00:00:00:00:00 Apr 10 20:23:16 Unjoe dhcpcd[1856]: br0: xid 0x1aa8cd34 is for hwaddr dc:85:de:8a:1e:c8:00:00:00:00:00:00:00:00:00:00 Apr 10 20:36:21 Unjoe dhcpcd[1856]: br0: xid 0x46a67711 is for hwaddr dc:85:de:8a:1e:c8:00:00:00:00:00:00:00:00:00:00 Apr 10 20:36:51 Unjoe dhcpcd[1856]: br0: xid 0x85b6763 is for hwaddr dc:85:de:8a:1e:c8:00:00:00:00:00:00:00:00:00:00 Apr 10 20:38:47 Unjoe dhcpcd[1856]: br0: xid 0x3f635b60 is for hwaddr dc:85:de:8a:1e:c8:00:00:00:00:00:00:00:00:00:00 Apr 10 20:41:44 Unjoe kernel: usb 1-13: reset full-speed USB device number 3 using xhci_hcd Apr 10 20:41:44 Unjoe kernel: usb 1-13: reset full-speed USB device number 3 using xhci_hcd Apr 10 20:41:50 Unjoe kernel: usb 1-13: reset full-speed USB device number 3 using xhci_hcd Apr 10 20:41:50 Unjoe kernel: usb 1-13: reset full-speed USB device number 3 using xhci_hcd Apr 10 20:41:50 Unjoe kernel: usb 1-13: reset full-speed USB device number 3 using xhci_hcd Apr 10 20:41:52 Unjoe dhcpcd[1856]: br0: xid 0x6c657af2 is for hwaddr 52:54:00:cb:c3:ba:00:00:00:00:00:00:00:00:00:00 Apr 10 20:43:55 Unjoe dhcpcd[1856]: br0: xid 0xa96816e5 is for hwaddr dc:85:de:8a:1e:c8:00:00:00:00:00:00:00:00:00:00 Apr 10 20:44:26 Unjoe dhcpcd[1856]: br0: xid 0x8153d52 is for hwaddr dc:85:de:8a:1e:c8:00:00:00:00:00:00:00:00:00:00 Apr 10 20:49:29 Unjoe dhcpcd[1856]: br0: xid 0x129a9b49 is for hwaddr dc:85:de:8a:1e:c8:00:00:00:00:00:00:00:00:00:00 Apr 10 20:51:27 Unjoe dhcpcd[1856]: br0: xid 0x6e097e67 is for hwaddr dc:85:de:8a:1e:c8:00:00:00:00:00:00:00:00:00:00 Apr 10 21:04:29 Unjoe dhcpcd[1856]: br0: xid 0xc8b19f76 is for hwaddr dc:85:de:8a:1e:c8:00:00:00:00:00:00:00:00:00:00 Apr 10 21:06:27 Unjoe dhcpcd[1856]: br0: xid 0x83bac7bc is for hwaddr dc:85:de:8a:1e:c8:00:00:00:00:00:00:00:00:00:00 Apr 10 21:11:59 Unjoe dhcpcd[1856]: br0: xid 0xd9e4de7b is for hwaddr dc:85:de:8a:1e:c8:00:00:00:00:00:00:00:00:00:00 Apr 10 21:13:57 Unjoe dhcpcd[1856]: br0: xid 0xa4af5e34 is for hwaddr dc:85:de:8a:1e:c8:00:00:00:00:00:00:00:00:00:00 I have scoured the interwebs, any help is greatly appreciated. I will be using this VM for photoshop and lightroom primarily.