goinsnoopin

Yes, I have a root password set. Memtest has been running for 17.5 hours and no errors.

Rob, I did not stop the array. I opened chrome on the VM and while typing the Google search, the VM screen went blank. I went to tower on my phone and the array was stopped. I then restarted the array. Never did I stop the array....as a matter of fact I didn't even have the webgui loaded. I also have a diagnostic that I left in the 6.2.3 release thread where on the reboot from installing 6.2.3 that this happened and I repeated this process of starting the array 2 or 3 times. I did recently increase the ram in my unraid box from 16 to 32gb. This is the reason I indicated that I am running memtest. It is still running...8 hours in and no errors.

Marking this as solved....chrome browser was refreshing open tab causing array stop/vm shutdown. My VMs are crashing at random since upgrading to 6.2.3, and I am getting this randomly in my VM logs (pid varies): qemu-system-x86_64: terminating on signal 15 from pid 11336 Does anyone know what this means? Full diagnostics are attached. I am going to run memtest to see what that turns up. Here is the syslog from around that time (12:31 on 11/6/2016): Nov 6 11:28:38 Tower kernel: mdcmd (43): spindown 6 Nov 6 11:28:54 Tower kernel: mdcmd (44): spindown 4 Nov 6 11:29:49 Tower kernel: mdcmd (45): spindown 1 Nov 6 11:30:08 Tower kernel: mdcmd (46): spindown 3 Nov 6 11:52:12 Tower kernel: mdcmd (47): spindown 0 Nov 6 12:31:08 Tower emhttp: Spinning up all drives... Nov 6 12:31:08 Tower kernel: mdcmd (48): nocheck Nov 6 12:31:08 Tower kernel: md: nocheck_array: check not active Nov 6 12:31:08 Tower kernel: mdcmd (49): spinup 0 Nov 6 12:31:08 Tower emhttp: shcmd (1281): /usr/sbin/hdparm -S0 /dev/sdf &> /dev/null Nov 6 12:31:08 Tower kernel: mdcmd (50): spinup 1 Nov 6 12:31:08 Tower kernel: mdcmd (51): spinup 2 Nov 6 12:31:08 Tower kernel: mdcmd (52): spinup 3 Nov 6 12:31:08 Tower kernel: mdcmd (53): spinup 4 Nov 6 12:31:08 Tower kernel: mdcmd (54): spinup 5 Nov 6 12:31:08 Tower kernel: mdcmd (55): spinup 6 Nov 6 12:31:17 Tower emhttp: Stopping services... Nov 6 12:31:17 Tower cache_dirs: Stopping cache_dirs process 5219 Nov 6 12:31:17 Tower unassigned.devices: Unmounting Devices... Nov 6 12:31:17 Tower emhttp: Nov 6 12:31:17 Tower emhttp: Nov 6 12:31:18 Tower emhttp: shcmd (1283): /etc/rc.d/rc.libvirt stop |& logger Nov 6 12:31:21 Tower root: Domain d13cb820-b946-f513-afc6-960d2061f381 is being shutdown Nov 6 12:31:21 Tower root: Nov 6 12:31:27 Tower kernel: usb 3-9.1.4.7: reset low-speed USB device number 7 using xhci_hcd Nov 6 12:31:27 Tower kernel: usb 3-9.1.4.7: ep 0x81 - rounding interval to 64 microframes, ep desc says 80 microframes Nov 6 12:31:27 Tower kernel: usb 3-9.1.4.5: reset low-speed USB device number 6 using xhci_hcd Nov 6 12:31:28 Tower kernel: usb 3-9.1.4.5: ep 0x81 - rounding interval to 64 microframes, ep desc says 80 microframes Nov 6 12:31:28 Tower kernel: usb 3-9.1.4.5: ep 0x82 - rounding interval to 1024 microframes, ep desc says 2040 microframes Nov 6 12:31:28 Tower kernel: br0: port 2(vnet0) entered disabled state Nov 6 12:31:28 Tower kernel: device vnet0 left promiscuous mode Nov 6 12:31:28 Tower kernel: br0: port 2(vnet0) entered disabled state Nov 6 12:31:28 Tower kernel: input: Logitech USB Keyboard as /devices/pci0000:00/0000:00:14.0/usb3/3-9/3-9.1/3-9.1.4/3-9.1.4.5/3-9.1.4.5:1.0/0003:046D:C31C.0007/input/input13 Nov 6 12:31:28 Tower kernel: hid-generic 0003:046D:C31C.0007: input,hidraw0: USB HID v1.10 Keyboard [Logitech USB Keyboard] on usb-0000:00:14.0-9.1.4.5/input0 Nov 6 12:31:28 Tower kernel: input: Logitech USB Keyboard as /devices/pci0000:00/0000:00:14.0/usb3/3-9/3-9.1/3-9.1.4/3-9.1.4.5/3-9.1.4.5:1.1/0003:046D:C31C.0008/input/input14 Nov 6 12:31:28 Tower kernel: hid-generic 0003:046D:C31C.0008: input,hidraw1: USB HID v1.10 Device [Logitech USB Keyboard] on usb-0000:00:14.0-9.1.4.5/input1 Nov 6 12:31:28 Tower kernel: input: Logitech USB-PS/2 Optical Mouse as /devices/pci0000:00/0000:00:14.0/usb3/3-9/3-9.1/3-9.1.4/3-9.1.4.7/3-9.1.4.7:1.0/0003:046D:C01D.0009/input/input15 Nov 6 12:31:28 Tower kernel: hid-generic 0003:046D:C01D.0009: input,hidraw2: USB HID v1.10 Mouse [Logitech USB-PS/2 Optical Mouse] on usb-0000:00:14.0-9.1.4.7/input0 Nov 6 12:31:29 Tower kernel: vgaarb: device changed decodes: PCI:0000:09:00.0,olddecodes=io+mem,decodes=io+mem:owns=none Nov 6 12:31:32 Tower root: Domain 50b73fd1-eaa0-77c8-2f16-5cad767f79d4 is being shutdown Nov 6 12:31:32 Tower root: Nov 6 12:31:34 Tower kernel: br0: port 3(vnet1) entered disabled state Nov 6 12:31:34 Tower kernel: device vnet1 left promiscuous mode Nov 6 12:31:34 Tower kernel: br0: port 3(vnet1) entered disabled state Nov 6 12:31:36 Tower kernel: vgaarb: device changed decodes: PCI:0000:01:00.0,olddecodes=io+mem,decodes=io+mem:owns=none Nov 6 12:31:36 Tower root: Waiting on VMs to shutdown.. Nov 6 12:31:36 Tower root: Stopping libvirtd... Nov 6 12:31:36 Tower dnsmasq[11771]: exiting on receipt of SIGTERM Nov 6 12:31:36 Tower kernel: device virbr0-nic left promiscuous mode Nov 6 12:31:36 Tower kernel: virbr0: port 1(virbr0-nic) entered disabled state Nov 6 12:31:36 Tower avahi-daemon[3766]: Interface virbr0.IPv4 no longer relevant for mDNS. Nov 6 12:31:36 Tower avahi-daemon[3766]: Leaving mDNS multicast group on interface virbr0.IPv4 with address 192.168.122.1. Nov 6 12:31:36 Tower avahi-daemon[3766]: Withdrawing address record for 192.168.122.1 on virbr0. Nov 6 12:31:36 Tower root: Network a4007147-6d28-4b27-8a73-0b1a1672c02b destroyed Nov 6 12:31:36 Tower root: Nov 6 12:31:39 Tower emhttp: shcmd (1284): umount /etc/libvirt Nov 6 12:31:39 Tower emhttp: shcmd (1286): /etc/rc.d/rc.docker stop |& logger Nov 6 12:31:39 Tower root: stopping docker ... Nov 6 12:31:43 Tower root: 18576e020f2e Nov 6 12:31:45 Tower ntpd[1674]: Deleting interface #6 as0t0, 172.27.224.1#123, interface stats: received=0, sent=0, dropped=0, active_time=5677 secs Nov 6 12:31:47 Tower root: 2d71f23078a7 Nov 6 12:31:50 Tower kernel: veth2603fef: renamed from eth0 Nov 6 12:31:50 Tower kernel: docker0: port 6(veth202afd5) entered disabled state Nov 6 12:31:50 Tower kernel: docker0: port 6(veth202afd5) entered disabled state Nov 6 12:31:50 Tower kernel: device veth202afd5 left promiscuous mode Nov 6 12:31:50 Tower kernel: docker0: port 6(veth202afd5) entered disabled state Nov 6 12:31:50 Tower root: 730d327aad7a Nov 6 12:31:54 Tower kernel: veth5dc01ce: renamed from eth0 Nov 6 12:31:54 Tower kernel: docker0: port 5(veth41c2e41) entered disabled state Nov 6 12:31:54 Tower kernel: docker0: port 5(veth41c2e41) entered disabled state Nov 6 12:31:54 Tower kernel: device veth41c2e41 left promiscuous mode Nov 6 12:31:54 Tower kernel: docker0: port 5(veth41c2e41) entered disabled state Nov 6 12:31:54 Tower root: 07831e4d28b4 Nov 6 12:31:54 Tower kernel: vetha2c9752: renamed from eth0 Nov 6 12:31:54 Tower kernel: docker0: port 7(veth797030a) entered disabled state Nov 6 12:31:54 Tower kernel: docker0: port 7(veth797030a) entered disabled state Nov 6 12:31:54 Tower kernel: device veth797030a left promiscuous mode Nov 6 12:31:54 Tower kernel: docker0: port 7(veth797030a) entered disabled state Nov 6 12:31:54 Tower root: 8d7fba88a276 Nov 6 12:31:55 Tower kernel: veth813e985: renamed from eth0 Nov 6 12:31:55 Tower kernel: docker0: port 2(vethd4d9246) entered disabled state Nov 6 12:31:55 Tower kernel: docker0: port 2(vethd4d9246) entered disabled state Nov 6 12:31:55 Tower kernel: device vethd4d9246 left promiscuous mode Nov 6 12:31:55 Tower kernel: docker0: port 2(vethd4d9246) entered disabled state Nov 6 12:31:55 Tower root: 2018e5eb6489 Nov 6 12:31:59 Tower root: 1e752c6d3bbe Nov 6 12:32:00 Tower kernel: vethc37c7d6: renamed from eth0 Nov 6 12:32:00 Tower kernel: docker0: port 1(vethde42fb8) entered disabled state Nov 6 12:32:00 Tower kernel: docker0: port 1(vethde42fb8) entered disabled state Nov 6 12:32:00 Tower kernel: device vethde42fb8 left promiscuous mode Nov 6 12:32:00 Tower kernel: docker0: port 1(vethde42fb8) entered disabled state Nov 6 12:32:00 Tower root: 4d1379a89045 Nov 6 12:32:01 Tower root: fb9e962fa926 Nov 6 12:32:01 Tower kernel: vethe222581: renamed from eth0 Nov 6 12:32:01 Tower kernel: docker0: port 4(veth7103e15) entered disabled state Nov 6 12:32:01 Tower kernel: docker0: port 4(veth7103e15) entered disabled state Nov 6 12:32:01 Tower kernel: device veth7103e15 left promiscuous mode Nov 6 12:32:01 Tower kernel: docker0: port 4(veth7103e15) entered disabled state Nov 6 12:32:01 Tower root: 2c736fef2ae9 Nov 6 12:32:01 Tower kernel: vethfea3cbb: renamed from eth0 Nov 6 12:32:01 Tower kernel: docker0: port 3(veth7b9d444) entered disabled state Nov 6 12:32:01 Tower kernel: docker0: port 3(veth7b9d444) entered disabled state Nov 6 12:32:01 Tower kernel: device veth7b9d444 left promiscuous mode Nov 6 12:32:01 Tower kernel: docker0: port 3(veth7b9d444) entered disabled state Nov 6 12:32:01 Tower root: df582c070cea Nov 6 12:32:02 Tower avahi-daemon[3766]: Interface docker0.IPv4 no longer relevant for mDNS. Nov 6 12:32:02 Tower avahi-daemon[3766]: Leaving mDNS multicast group on interface docker0.IPv4 with address 172.17.0.1. Nov 6 12:32:02 Tower avahi-daemon[3766]: Withdrawing address record for 172.17.0.1 on docker0. Nov 6 12:32:02 Tower emhttp: shcmd (1287): umount /var/lib/docker |& logger Nov 6 12:32:02 Tower emhttp: shcmd (1288): /etc/rc.d/rc.samba stop |& logger Nov 6 12:32:02 Tower emhttp: shcmd (1289): rm -f /etc/avahi/services/smb.service Nov 6 12:32:02 Tower avahi-daemon[3766]: Files changed, reloading. Nov 6 12:32:02 Tower avahi-daemon[3766]: Service group file /services/smb.service vanished, removing services. Nov 6 12:32:02 Tower emhttp: shcmd (1292): /etc/rc.d/rc.avahidaemon stop |& logger Nov 6 12:32:02 Tower root: Stopping Avahi mDNS/DNS-SD Daemon: stopped Nov 6 12:32:02 Tower avahi-daemon[3766]: Got SIGTERM, quitting. Nov 6 12:32:02 Tower avahi-dnsconfd[3775]: read(): EOF Nov 6 12:32:02 Tower avahi-daemon[3766]: Leaving mDNS multicast group on interface br0.IPv4 with address 192.168.0.50. Nov 6 12:32:02 Tower avahi-daemon[3766]: avahi-daemon 0.6.32 exiting. Nov 6 12:32:02 Tower emhttp: shcmd (1293): /etc/rc.d/rc.avahidnsconfd stop |& logger Nov 6 12:32:02 Tower root: Stopping Avahi mDNS/DNS-SD DNS Server Configuration Daemon: stopped Nov 6 12:32:02 Tower emhttp: Sync filesystems... Nov 6 12:32:02 Tower emhttp: shcmd (1294): sync Nov 6 12:32:04 Tower ntpd[1674]: Deleting interface #5 docker0, 172.17.0.1#123, interface stats: received=0, sent=0, dropped=0, active_time=5707 secs Nov 6 12:32:05 Tower emhttp: shcmd (1295): set -o pipefail ; umount /mnt/user |& logger Nov 6 12:32:05 Tower emhttp: shcmd (1296): rmdir /mnt/user |& logger Nov 6 12:32:05 Tower emhttp: shcmd (1297): set -o pipefail ; umount /mnt/user0 |& logger Nov 6 12:32:05 Tower emhttp: shcmd (1298): rmdir /mnt/user0 |& logger Nov 6 12:32:05 Tower emhttp: shcmd (1299): rm -f /boot/config/plugins/dynamix/mover.cron Nov 6 12:32:05 Tower emhttp: shcmd (1300): /usr/local/sbin/update_cron &> /dev/null Nov 6 12:32:05 Tower emhttp: Unmounting disks... Nov 6 12:32:05 Tower emhttp: shcmd (1301): umount /mnt/disk1 |& logger Nov 6 12:32:05 Tower kernel: XFS (md1): Unmounting Filesystem Nov 6 12:32:05 Tower emhttp: shcmd (1302): rmdir /mnt/disk1 |& logger Nov 6 12:32:05 Tower emhttp: shcmd (1303): umount /mnt/disk2 |& logger Nov 6 12:32:06 Tower kernel: XFS (md2): Unmounting Filesystem Nov 6 12:32:06 Tower emhttp: shcmd (1304): rmdir /mnt/disk2 |& logger Nov 6 12:32:06 Tower emhttp: shcmd (1305): umount /mnt/disk3 |& logger Nov 6 12:32:06 Tower kernel: XFS (md3): Unmounting Filesystem Nov 6 12:32:06 Tower emhttp: shcmd (1306): rmdir /mnt/disk3 |& logger Nov 6 12:32:06 Tower emhttp: shcmd (1307): umount /mnt/disk4 |& logger Nov 6 12:32:06 Tower kernel: XFS (md4): Unmounting Filesystem Nov 6 12:32:07 Tower emhttp: shcmd (1308): rmdir /mnt/disk4 |& logger Nov 6 12:32:07 Tower emhttp: shcmd (1309): umount /mnt/disk5 |& logger Nov 6 12:32:07 Tower kernel: XFS (md5): Unmounting Filesystem Nov 6 12:32:07 Tower emhttp: shcmd (1310): rmdir /mnt/disk5 |& logger Nov 6 12:32:07 Tower emhttp: shcmd (1311): umount /mnt/disk6 |& logger Nov 6 12:32:07 Tower kernel: XFS (md6): Unmounting Filesystem Nov 6 12:32:07 Tower emhttp: shcmd (1312): rmdir /mnt/disk6 |& logger Nov 6 12:32:07 Tower emhttp: shcmd (1313): umount /mnt/cache |& logger Nov 6 12:32:08 Tower emhttp: shcmd (1314): rmdir /mnt/cache |& logger Nov 6 12:32:08 Tower kernel: mdcmd (56): stop Nov 6 12:32:08 Tower kernel: md1: stopping Nov 6 12:32:08 Tower kernel: md2: stopping Nov 6 12:32:08 Tower kernel: md3: stopping Nov 6 12:32:08 Tower kernel: md4: stopping Nov 6 12:32:08 Tower kernel: md5: stopping Nov 6 12:32:08 Tower kernel: md6: stopping Nov 6 12:32:09 Tower emhttp: shcmd (1315): rmmod md-mod |& logger Nov 6 12:32:09 Tower kernel: md: unRAID driver removed Nov 6 12:32:09 Tower emhttp: shcmd (1316): modprobe md-mod super=/boot/config/super.dat |& logger Nov 6 12:32:09 Tower kernel: md: unRAID driver 2.6.8 installed Nov 6 12:32:09 Tower emhttp: Pro key detected, GUID: 05DC-A701-0802-054128260907 FILE: /boot/config/Pro1.key Nov 6 12:32:09 Tower emhttp: Device inventory: Nov 6 12:32:09 Tower emhttp: shcmd (1317): udevadm settle Nov 6 12:32:09 Tower emhttp: LEXAR_JD_FIREFLY_67CC0802054128260907-0:0 (sda) 1966048 Nov 6 12:32:09 Tower emhttp: WDC_WD30EFRX-68EUZN0_WD-WCC4NEUA5L20 (sdb) 2930266532 Nov 6 12:32:09 Tower emhttp: WDC_WD1003FZEX-00MK2A0_WD-WCC3F2VKVHYE (sdc) 976762552 Nov 6 12:32:09 Tower emhttp: WDC_WD20EFRX-68EUZN0_WD-WMC4M1062491 (sdd) 1953514552 Nov 6 12:32:09 Tower emhttp: WDC_WD30EFRX-68EUZN0_WD-WMC4N0M6V0HC (sde) 2930266532 Nov 6 12:32:09 Tower emhttp: Samsung_SSD_850_EVO_500GB_S2RANX0H543209Z (sdf) 488386552 Nov 6 12:32:09 Tower emhttp: WDC_WD1001FALS-00J7B0_WD-WMATV0360335 (sdg) 976762552 Nov 6 12:32:09 Tower emhttp: WDC_WD20EARX-008FB0_WD-WCAZAF142676 (sdh) 1953514552 Nov 6 12:32:09 Tower emhttp: ST3000VN000-1HJ166_W6A0WEG0 (sdi) 2930266532 Nov 6 12:32:09 Tower emhttp: WDC_WD10EARX-00N0YB0_WD-WMC0T1042974 (sdj) 976762552 tower-diagnostics-20161106-1238.zip

I had a small hiccup with my 6.2.3 upgrade from 6.2.2. After installing the upgrade via the plugin I rebooted the server. I have my unraid Tower setup to automatically start the array and then start several dockers and then two VMs. At first everything looked fine..unraid booted and both VMs started...just after the VM was up I opened chrome and started to browse and the VM went blank. I browsed to the unraid webgui and the array was stopped. I restarted the array and the samething happened. I tried on more time and on this array start, I immediately went to one of the VMs and stopped it. The other VM spun up and has been running for a day. I also then spun the second VM up and it has been running along side the first one for awhile now. Here is the entry in the VM log that concerns me: 2016-11-03T18:10:58.258022Z qemu-system-x86_64: terminating on signal 15 from pid 14432 For each of the VM crashes there is one of these entries and each VM failed with the same signal 15, but on three different pids. I have attached diagnostics. Mods - feel free to move if you think this belongs in the KVM forum. Any thoughts? Dan tower-diagnostics-20161103-1421.zip

Since the docker upgrade, I have not been able to get the webgui or proxy up and running. Like the other poster if I disable the VPN the webgui runs. I am using PIA and my local lan is 192.168.0.0/24. I turned debugging on and attached is my log with passwords and username blanked out. Any suggestions? delugevpnlog.txt

I have a Texas Instruments USB 3 PCIe card that I successfully passed through to a windows 7 VM. I just converted that VM to windows 10 (clean install...not an upgrade) and I am unable to get this card to function properly. I have attached a .png of what device manager is telling me, as well as, my unraid diagnostics. Currently unraid is at stable 6.2.1. Quick question in case it is related...with 6.2.1 do you still need to use a pci-stub in the syslinux.cfg file? Here is my stub language below for reference (2 PCI USB cards) vfio-pci.ids=104c:8241,1b73:1100 Thanks, Dan tower-diagnostics-20161011-2212.zip

I upgraded from 6.2 RC5 to 6.2 Stable yesterday. Shortly after the upgrade I started getting notifications/warnings that I had reallocated sectors on my Samsung 850 EVO 500GB cache drive (formated BTRFS). Shortly there after I started getting uncorrectable error count warnings...it got up to 41 of these errors and I have not gotten any more over the past 18 hours or so. I have attached my smart report for this disk as well as my diagnostics. I believe this is just a coincidence and that the drive just failed...but would like opinions for more experienced users. I assume since the error report does not pass that I should purchase a new drive to keep my system up and running since Samsung does not offer an advanced RMA option to cross ship the drives. If you have any other thoughts, I would love to hear them. Thanks, Dan tower-diagnostics-20160915-2312.zip Samsung_SSD_850_EVO_500GB_S2RANXAH111068J-20160916-1812.txt

Good point I can try this. Should have mentioned in original post that USB cable is only 6 feet long. So I take it you have devices plugged into a hub??? I just wasn't sure if devices needed to be present when unraid booted and by losing power the only way to reconnect them was through a reboot.

So I have a question about unraid and USB Hubs. Does unraid play nice with USB hubs? The reason I ask is that I have my unraid tower in the basement and I ran a single usb cable to my first floor where I have a 7 port hub. This hub has my unraid keyboard and mouse plugged into it. If I pull the usb keyboard or mouse out...they stop working and plugging them in does nothing and I have to reboot my unraid server. This also happens on a power outage...unraid Tower is on a UPS but the usb hub is not...see the attached diagnostics in the syslog at 06:35am on 8/7/2016 you will see an entry about a power outage followed by the usb not being able to reset. Here is a snippet from the syslog...this repeats until I reboot the server: Aug 7 06:35:42 Tower apcupsd[24366]: Power failure. Aug 7 06:35:43 Tower kernel: usb 3-9.1.4-port2: cannot reset (err = -71) Aug 7 06:35:43 Tower kernel: usb 3-9.1.4-port2: cannot reset (err = -71) Aug 7 06:35:43 Tower kernel: usb 3-9.1.4-port2: cannot reset (err = -71) Aug 7 06:35:43 Tower kernel: usb 3-9.1.4-port2: cannot reset (err = -71) Aug 7 06:35:43 Tower kernel: usb 3-9.1.4-port2: cannot reset (err = -71) Aug 7 06:35:43 Tower kernel: usb 3-9.1.4-port2: Cannot enable. Maybe the USB cable is bad? Is this normal behavior and maybe I should eliminate the USB hub...or could it be that I should try a new USB hub? Let me know any thoughts you may have. Thanks, Dan modified to add code snippet to make it easier for people to see what is going on in syslog. tower-diagnostics-20160807-0723.zip

Is there any way to do the equivalent of hitting F8 or shift F8 to force my Windows 10 VM to enter safe mode? I installed Avira using the ninite installer and something went wrong and my VM boots to windows 10 and the VM is locked up. I would love to remove Avira from startup. Running unraid 6.2 RC3, Win10 vm is OVMF. Thanks, Dan

I want to convert my license from windows 7 to windows 10 before tomorrow's deadline. My plan is to type in the product key from my current windows 7 vm into a brand new clean install of windows 10. So I know you have 30 days to revert...but my question is what will happen to my existing windows 7 VM. Will I be able to boot it up? The reason I am asking is that it makes a difference in how I go about backing up anything critical in this windows 7 VM. Thanks, Dan

What about the chip set emulation? I assume this could cause issues with Microsoft activation. I know i440fx is more mature and Q35 is a more modern design. I also recall limetech's recommendation was i440fx for Windows VMs What are most people using? Since I have 6 licenses of win7 and only need 3 VMs should I do 3 of each when upgrading to Windows 10 in an attempt to future proof?

I am getting ready to redo a few windows VMs this week and am looking to get some suggestions or best practice recommendations. I am currently having an issue where I keep having to grow the size of my primary disk . I know windows does have a tendency to do this. I was thinking that when I rebuild the VM that I would keep just the windows install on the primary disk and then assign a second disk for all my programs. Is this what most of you do? Also curious how large you make the windows primary disk. Any other tips or suggestions not listed in limetech's VM guides would be greatly appreciated! Thanks, Dan

Do you need to install win 7 first? I was under the impression that the current win 10 ISO allowed you to enter a win 7 product key. Here is a reference link from Microsoft:. https://support.microsoft.com/en-us/help/12440/windows-10-activation Thanks for all the info so far!

I am glad this topic came up. With the windows 10 free upgrade looming I am not sure what to do. I am new to using VMs and currently have two running Win7 Pro and an unauthorized Win10 VM (test driving it) both of these VMs were created in 6.1.9 and use the default seabios and i440x that was recommended in 6.1.9. I just upgraded to Unraid 6.2 RC2 and everything went smooth. The driver for the upgrade of unraid was to get to a position where I have VMs that have been created in 6.2 with OVMF as that is going to be the default going forward and to be able to leverage the free upgrade to windows 10 as it seems to work better for the kids PC games. From reading the forums it is my understanding that making a change from seabios to ovmf or i440x to q35 is going to trigger MS authentication issues. My kids are just getting into PC gaming and at this point I don't have a feel for the best configuration...I get the feeling Win10 is better for gaming and I also get the impression that I better lock down my VM configuration...i.e. number of CPUS, memory etc as that can also create MS authentication issues. I currently have seven (6) Win7 Pro 64 licenses. The maximum number of windows VMs that I anticipate running is 3. Any recommendations on how many I should upgrade to Win10 or CPU/memory assignments to give me the most flexibility? Any thoughts would be greatly appreciated! Dan

f3dora, Thank you for your post. I did as you suggested and installed Origin on my mapped network share (on my cache drive) and it works perfectly. Nice simple solution! Thanks again to everyone for their input. Dan

I worked on this some more. Samba is locking the file. I telnet into unraid console and stopped samba then started samba and I was able to mount the VHD. So now I need to Google for a solution/setting to keep samba from locking these files on a VM reboot. Dan

Saarg and f3dora, Thanks for the information. I am having an issue still with attaching the vhd. If I reboot the VM and try and attach it manually through disk management I get an error that says the file cannot be accessed because it is in use by another process. Again I used process explorer and it doesn't show anything using this file. If I try with the simple VHD manager 1.2 I get a different message: "The file cannot be attached! The file is corrupt or not supported by the system." However if I wait long enough I am able to attach the VHD. Not sure if it is related...I am unable to attach a VHD through the simple VHD manager gui...however since I enabled the right click context menu options and I am able to attach the VHD by right clicking and selecting mount or by double clicking the VHD. I really need to figure out this inability to attach a drive after a reboot of the VM. Thanks, Dan

Rix, I have tried your suggestion of using VHDs and it works great. I have a question for you....Do you have a way of auto mounting these VHDs on a reboot of the VM? I find that if I reboot the VM, I get a message that the file is in use by another process. I have used process explorer and it does not show the file in use by anything, however if I wait or retry to attach them later (haven't measured time) they then are able to attach. Do you unmount them before a reboot? I am using a Steam Link to playback games on a TV in the kids room and from time to time something crashes and we need to reboot the VM from the unraid VM manager and I am looking for a simple way to make sure these VHDs can attach right away on a reboot. Any suggestions would be greatly appreciated. Dan

I am hoping that we get to final before the end of July. I have a license of win7 pro that I want to upgrade to win10 for free. I have been holding off as unraid 6.2 switched to ovmf and my current win7 VM is seabios. I usually don't install betas.... but as the free upgrade date gets closer....maybe I'll change my mind. Just trying to avoid activation issues with Microsoft.

So I have a windows 10 VM that has functioned flawless for the past several months. Today when I go to start the VM I can see the windows logo, then I get the blue screen and the bottom is says NTFS_File_system error and then it says it is going to reboot to fix it and it ends up in an endless loop. Every once and a while the message changes to some other error...but I didnt catch it. This VM is not critical...so I can just start a new one..but am curious is there anything else I can do to attempt to repair this? Thanks, Dan P.S. I did get to a troubleshooting screen and selected the option to fix windows...but it returned a message that is was unsucessful...I then picked an option to reinstall and it said the drive that contained my install files was locked.

notSteve, Updated xml looks good. I may have found one issue, lines 21 you have a // between Media and videos, I believe is only supposed to be a single / Samething in line 47. What do you think about also installing the client? For me I don't need it for playback of video, but would love to be able to edit preferences, add shows to record, etc. Dan

notSteve and Squid, Thanks for your help. I have this docker running. I got it to work before notSteve updated his xml, so I have not tested that yet. notSteve - what are you using as a client, I see stuckless over at the sagetv forums also has an opensource client available. I wonder if this can also be installed. Not understanding dockers completely, I know some docker authors have leveraged guacamole to create a remote desktop connection to clients....Squid do you know if my recollection is correct? Any suggestions of a posting or thread that would detail how to do this? Thanks, Dan

Squid, Thanks for the compliant xml. I edited your sample to match my user share names and then copied the xml file to my flash drive. I then went to dockerman and created a new container and selected the my-SageTV template and the settings with my correct mappings showed up. I then hit create and the process complete and the docker is there with the red stop sign and it will not start. When I edit the container it looks like the <Host>/sagetv</Host> portion is missing. Also after the creation when I look at the my-SageTV.xml several entries are then missing. Here is the xml after docker creation: <?xml version="1.0" encoding="utf-8"?> <Container> <Name>SageTv</Name> <Description></Description> <Registry></Registry> <Repository>notsteve/sagetv-unraid</Repository> <BindTime>true</BindTime> <Privileged>false</Privileged> <Environment/> <Networking> <Mode>host</Mode> <Publish/> </Networking> <Data> <Volume> <HostDir>/mnt/user/Offline/</HostDir> <ContainerDir>/var/media/videos</ContainerDir> <Mode>rw</Mode> </Volume> <Volume> <HostDir>/mnt/user/Music/</HostDir> <ContainerDir>/var/media/music</ContainerDir> <Mode>rw</Mode> </Volume> <Volume> <HostDir>/mnt/user/Photos/</HostDir> <ContainerDir>/var/media/pictures</ContainerDir> <Mode>rw</Mode> </Volume> <Volume> <HostDir>/mnt/user/SageTV/</HostDir> <ContainerDir>/var/recordings</ContainerDir> <Mode>rw</Mode> </Volume> </Data> <Version></Version> <WebUI></WebUI> <Banner></Banner> <Icon>http://forums.sagetv.com/forums/images/misc/SagetvLogo170.jpg</Icon> <ExtraParams></ExtraParams> </Container> Does this make sense? Any suggestions would be greatly appreciated! I attached my edited version of your xml (renamed as .txt for attachment purposes), and two screenshots of the docker template settings for reference. Thanks, Dan my-SageTV.txt

As the person who originally requested this, I am thrilled. However, I am running Unraid 6.1.9 so this template does not work for me. I have never created my own template, so this is new to me. In generating the template most of the items are self explanatory. However, I am having trouble with notSteve's line for the installation of Sagetv...not sure what you mean by persistant storage??? Here is the line I am having trouble with....how would this be entered into the template? <Config Name="SageTv Data" Target="/sagetv" Default="" Mode="rw" Description="Container Path: /opt/sagetv" Type="Path" Display="always" Required="yes" Mask="false"></Config> Thanks! Dan