GHunter

What about using Symlinks or Hard Links? Would that work for your use case?

SQL server connections outside the local pc are disabled by default. You have to enable them using the SQL server configuration manager. See here for details: https://social.technet.microsoft.com/wiki/contents/articles/2102.how-to-troubleshoot-connecting-to-the-sql-server-database-engine.aspx

Updated from 6.4. No problems to report. All VM's working great and system is stable. Love the addition of the Graphics column in the VM tab! Thanks!

Hmm, ok. I was thinking that this worked under previous stable releases but I guess I'm wrong. Thanks for the reply.

I upgraded to 6.4.0 from 6.4.0-rc21b yesterday. Flawless upgrade. My Windows VM's start, stop, restart perfectly through the webGUI. Great job to all on the tremendous work that went into 6.4.0!! One minor thing I noticed (probably a WebGUI problem @bonienl) is that when I stop a VM, the page does not automatically refresh to reflect the VM's current status. Issuing a start or force stop command through the WebGUI does automatically refresh the page to show the VM's new status. Attaching diagnostics in case they are of any use. filesvr-diagnostics-20180118-0639.zip

It is the CPU family that you have to worry about not the MB. Your CPU is a Broadwell CPU if the specs in your signature are current. So you're fine.

I read about this issue yesterday here: http://techreport.com/news/32152/hyper-threading-erratum-rears-its-head-in-skylake-and-kaby-lake I'm still running a Haswell CPU so I'm not affected by it but it was an interesting read.

In your Windows 7 VM, check your network type and make sure you're not on a public network. Should be home or private network. RDP won't work over a public network. Gary

This is the file I think. Haven't used it in a long time. Gary tftp2.tar

You could simply bookmark http://tower/Dashboard I'd love this as well. The Dashboard page seems more appropriate as the Home page in my opinion. I've been using the bookmark suggested above now for ages.

At the rate it's filling the syslog, it's clearly going to be trouble, probably causing you to have to reboot every other day. That number corresponds to -8, but I have no idea what table to check for an error return of 8. I do notice that you are very tight on memory, about as tight as I've ever seen, so it's possible that's an indirect indication of something not being able to allocate the memory it requested. It first occurred at 10:05pm, with no other clues associated. It's associated with the onboard Intel USB controller. Perhaps consider decreasing by 1GB the RAM assigned to one VM? One other thing I noticed, you may want to raise the tunable md_sync_thresh to at least 320, but 600 or 610 may be even better, for better parity check performance. Thanks for the help and advice Rob. I'll definitely make some changes as you suggested. Gary

Is this a new issue vs. 6.2.4? This issue might be caused by an attached USB device auto-suspending or auto-poweroff. A plugin or container or vm might be trying to do this Please post output of these commands and we might be able to figure out which device it is: lsusb for i in /sys/bus/usb/devices/*/power/autosuspend; do echo -n "$i "; cat $i; done for i in /sys/bus/usb/devices/*/power/level; do echo -n "$i "; cat $i; done (Click [select] above, then Ctrl-C to copy to clipboard. Then in telnet/ssh window open to server, "paste" those commands - with putty you can use right-mouse click or hit Shift-Insert.) I've had this issue prior to v6.3.0 so it isn't specific to this version of unRaid. Here is my output to the commands you requested: root@FileSvr:~# lsusb Bus 002 Device 002: ID 8087:8001 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 005 Device 002: ID 0764:0501 Cyber Power System, Inc. CP1500 AVR UPS Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:8009 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 002: ID 13fe:5200 Kingston Technology Company Inc. Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 004: ID 0471:0815 Philips (or NXP) eHome Infrared Receiver Bus 003 Device 007: ID 147a:e042 Formosa Industrial Computing, Inc. Bus 003 Device 002: ID 04d9:a015 Holtek Semiconductor, Inc. Bus 003 Device 006: ID 046d:c31c Logitech, Inc. Keyboard K120 Bus 003 Device 005: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub root@FileSvr:~# for i in /sys/bus/usb/devices/*/power/autosuspend; do echo -n "$i "; cat $i; done /sys/bus/usb/devices/1-1/power/autosuspend 0 /sys/bus/usb/devices/2-1/power/autosuspend 0 /sys/bus/usb/devices/3-10/power/autosuspend 2 /sys/bus/usb/devices/3-13/power/autosuspend 2 /sys/bus/usb/devices/3-3/power/autosuspend 2 /sys/bus/usb/devices/3-6/power/autosuspend 2 /sys/bus/usb/devices/3-9/power/autosuspend 2 /sys/bus/usb/devices/4-3/power/autosuspend 2 /sys/bus/usb/devices/5-1/power/autosuspend 2 /sys/bus/usb/devices/usb1/power/autosuspend 0 /sys/bus/usb/devices/usb2/power/autosuspend 0 /sys/bus/usb/devices/usb3/power/autosuspend 0 /sys/bus/usb/devices/usb4/power/autosuspend 0 /sys/bus/usb/devices/usb5/power/autosuspend 0 /sys/bus/usb/devices/usb6/power/autosuspend 0 root@FileSvr:~# for i in /sys/bus/usb/devices/*/power/level; do echo -n "$i "; cat $i; done /sys/bus/usb/devices/1-1/power/level auto /sys/bus/usb/devices/2-1/power/level auto /sys/bus/usb/devices/3-10/power/level on /sys/bus/usb/devices/3-13/power/level on /sys/bus/usb/devices/3-3/power/level on /sys/bus/usb/devices/3-6/power/level on /sys/bus/usb/devices/3-9/power/level on /sys/bus/usb/devices/4-3/power/level on /sys/bus/usb/devices/5-1/power/level on /sys/bus/usb/devices/usb1/power/level auto /sys/bus/usb/devices/usb2/power/level auto /sys/bus/usb/devices/usb3/power/level auto /sys/bus/usb/devices/usb4/power/level auto /sys/bus/usb/devices/usb5/power/level auto /sys/bus/usb/devices/usb6/power/level auto root@FileSvr:~# One other thought that might help if you think this is a USB problem. I have 2 USB devices being passed through to 2 Win 10 VM's. Bus 003 Device 004: ID 0471:0815 Philips (or NXP) eHome Infrared Receiver is passed through to a VM via an Ethernet to USB adapter. And the other one is Bus 003 Device 007: ID 147a:e042 Formosa Industrial Computing, Inc. is passed through to a different VM via an Ethernet to USB adapter. I've tried passing these devices through in both USB 2.0 EHCI mode and USB 3.0 XHCI mode and both modes still cause problems. I've disabled all power saving features inside the VM's and ran through the BIOS to check for any possible problems there. I've also tried switch Ethernet cables too. None of which helped. Of course I could go through and troubleshoot again now that I'm on unRaid v6.3.0. If you could point me in the right direction, that would be great. I just don't know if this is an unRaid problem or something on my end. Thanks again, Gary

My upgrade from v6.2.4 seems to be working fine. I do have tons of this line in my syslog occurring every 1 or 2 seconds and I don't know what it is or if I should be worried about it, other then filling up the syslog. Feb 5 09:01:08 FileSvr kernel: xhci_hcd 0000:00:14.0: URB transfer length is wrong, xHC issue? req. len = 0, act. len = 4294967288 Diagnostics attached. Gary filesvr-diagnostics-20170205-0908.zip

Strange upgraded from 6.2.4 to 6.3.0 and I have the exact same disk type ST300DM001-9YN166 also die on reboot to new version. I have 11 of those drives in my unRaid server spread across 3 controllers. Most likely not an unRaid problem but a SATA or power related problem. Could be a driver issue too depending on the HBA you are using. I'm not suggesting anything other than helping to rule out a possible problem with unRaid itself. Post diagnostics so that someone with more experience can lend a hand Gary

I installed the update coming from v6.2.4. One of my VM's would not start due to an "Invalid Machine Type" error. I knew what the error was right away. Changed the machine type in the XML from: <type arch='x86_64' machine='pc-q35-2.3'>hvm</type> to: <type arch='x86_64' machine='pc-q35-2.7'>hvm</type> and then it started up just fine. Yeah, it was and old VM created ages ago! Just thought I'd mention it in case anyone else runs into this problem. Thanks for the great release as always! Gary

My guess would be that the network type changed from private to public which would not allow your RDP connection. This can happen with a Windows or driver update. If you can get into it somehow either local or VNC, check your network type.

A black and a lime green pin stripe around the collar and around the bottom edge of each sleeve would look cool too and a bit classy I think.

Ok, my log files are filling up again. Syslog Sep 10 16:13:48 FileSvr kernel: xhci_hcd 0000:00:14.0: URB transfer length is wrong, xHC issue? req. len = 0, act. len = 4294967288 Living Room - Emby Theater.log libusb: error [op_clear_halt] clear_halt failed error -1 errno 71 filesvr-diagnostics-20160911-0819.zip

Upgraded to RC5 from RC4 and everything seems to be working well so far. I mentioned a possible problem quoted below which seems to have been resolved with the RC5 release. Thanks! Gary

Here is my VM log as mentioned above. I had to trim it cause even zipped, it was still bigger than 320k. Gary Living_Room_-_Emby_Theater.log.txt

Upgraded to RC4 from RC3. Everything appears to work fine. Also added a 2nd parity drive Noticed something in my log files that are filling them up and not sure if there is something I can do on my end. My syslog has a ton of entries like this: Aug 23 00:41:55 FileSvr kernel: xhci_hcd 0000:00:14.0: URB transfer length is wrong, xHC issue? req. len = 0, act. len = 4294967288 And my VM log has a ton of these entries: libusb: error [op_clear_halt] clear_halt failed error -1 errno 71 Attaching my diagnostics here minus the vm log. I'll post the vm log in a separate post. Gary filesvr-diagnostics-20160823-0455.zip

Works for me. Maybe clear your browser cache or try another browser? BTW, the work you guys have done on the VM creation and management is pure awesomeness! Everything I have tried and played with has worked perfectly. I must have created a dozen VM's yesterday trying different options with and without hardware pass through and it works flawlessly. Thanks! Gary

Just updated from 6.1.9. I have several VM's and followed the directions form the beta 18 thread to make sure my VM's would work on 6.2 RC1. Everything went smooth and no issues to report. Gary

I think it was mentioned in one of the Linus Tech videos. Maybe the 7 VM's in 1 PC. Gary

Think they meant RDP, which is Microsoft's Remote Desktop Protocol. You use the protocol to connect to your remote PC (VM in this case) and the all the screen data is transferred and viewed on the local PC. More info here: http://windows.microsoft.com/en-us/windows/connect-using-remote-desktop-connection#connect-using-remote-desktop-connection=windows-7 Gary