SuperW2

This seemed to fix the issue at least with just 1 reboot. Rebooted the server, opened Console with Firefox (vs. Chrome), Cache Drive was again Unassigned. Stopped array, assigned cache drive, restarted array. Stopped and rebooted and reopened console with Chrome and cache drive assigned an all good... Odd, but seems to be OK now, so thanks! -SW2

I can give that a try on next reboot... I'm a 100% Chrome user (but have others installed obviously, just don't use them).

Only Plugins I have installed currently are "Preclear Disks" and "Community Applications".

So just noticed a new odd issue, happened at least with 6.1.5 and 6.1.6, but possibly earlier (I hadn't rebooted for a couple month previously to some drive upgrades over the past few weeks). On every reboot of my Server, the Cache Drive comes back unassigned. I can't be 100% sure on the timing, but it's possible that I started notice after I did a "New Config" to Shrink my array (removed a couple smaller/empty drives). No issue if I just re-assign the cache drive back and everything seems to be OK. Attached is Syslog from last reboot this morning (when the Cache Drive was again unassigned and I had to assign it). media-syslog-20151203-0707.zip

I'm glad it's a Seagate, it's all I buy and use! You are more lucky my friend... The only drives that have only lasted 2yrs or less have been Seagates....my hitschi and WD have been going strong for 4+ And I'm talking about around 5-6 failed Seagates in the past 3 yrs vs 1 WD and 1 Hitachi in my servers I have 20 of them in my current array, several 5 + years.... I've had a failure or two, but % wise WAY less than any other brand I've used. Specifically for the Seagate NAS Drives (now up to 5 or 6 of them in my array)... zero issues with any of them.

I'm glad it's a Seagate, it's all I buy and use!

Did you get a Newegg packing slip? If so, does it say anything different from a regular Newegg order? Packing List has "Jet" at the Top, but there is a "NewEgg SO#" and "NewEgg Item Number" (22-178-748) in the body of the List...

I'd never heard of Jet.Com before....my Drive showed up today in a NewEgg Box... I guess for the price, I don't really care!

"Sorry, we've SOLD OUT of this item at the Surprise Sale price. Please watch for more Surprise Sales in the future." Back up to $332.98

OK, I found a Radeon HD5570 (which is probably a little older than the 560ti still), but re-created the VM with the new GPU, then seeing the video passthrough to the connected monitor. I still had to click next for all of the default settings with the USB Keyboard on the server before the Kore would connect, but once I did, Kore on my Android tablet then saw the server and connected as I expected it too and am now browsing and adding my shares. Sorry for blowing up your Template support thread! Thanks for your help and patience!

Most certainly sure, yes... have no issues connecting to my Plex Docker on my Media server from the same Android device(s) and my unRAID console via the browser, etc, I just removed the entire new VM, re-setup everything and no change, doesn't even appear to be getting an IP Address now from my Router, so I think time to call it a night and look at it again in the morning. -W I bet it's your default network bridge. Goto settings -> network settings and see if the network bridge is enabled. If not, stop the array and enable it. Once enabled, go to Settings -> VM Manager and make sure that the default bridge is set to br0 and not virbr0. Remove the existing OpenELEC from the VMs tab, then add a new OpenELEC VM and it will have this new bridge enabled by default. This will ensure you VM gets an IP on the network and is accessible by the Kore app. I'm been using a "br1" (which is what I changed the bridge name too in my network settings) bridge that I setup previously when playing with Win10 VM, not using virbr0. It's getting a 192.168.1.xx IP address from my router that I can ping and see on my primary network just fine. This might be a dumb question, but If I physically plug a monitor into the GPU should I be seeing "something" on that monitor when the VM is running? I'm getting absolutely nothing... Yes you should. If you have nothing on the display, that means your not successfully assigning the GPU yet. There are steps in the wiki relating to GPU pass through that you can try. I know we have had issues with the GTX 550 in the past, so the 560 may share a similar fate. It is a rather older GPU. Some things you can try are in the wiki though. If you have another GPU laying around, I'd give that a shot. I think this was the least old of the old GPU's that I had in my "surplus" box but I will try one of the others.

Most certainly sure, yes... have no issues connecting to my Plex Docker on my Media server from the same Android device(s) and my unRAID console via the browser, etc, I just removed the entire new VM, re-setup everything and no change, doesn't even appear to be getting an IP Address now from my Router, so I think time to call it a night and look at it again in the morning. -W I bet it's your default network bridge. Goto settings -> network settings and see if the network bridge is enabled. If not, stop the array and enable it. Once enabled, go to Settings -> VM Manager and make sure that the default bridge is set to br0 and not virbr0. Remove the existing OpenELEC from the VMs tab, then add a new OpenELEC VM and it will have this new bridge enabled by default. This will ensure you VM gets an IP on the network and is accessible by the Kore app. I've been using a "br1" (which is what I changed the br0 bridge name too in my network settings) bridge that I setup previously when playing with Win10 VM, not using virbr0. It's getting a 192.168.1.xx IP address from my router that I can ping and see on my primary network just fine. This might be a dumb question, but If I physically plug a monitor into the GPU should I be seeing "something" on that monitor when the VM is running? I'm getting absolutely nothing... I've passed through a USB KB and Mouse and nada.

Most certainly sure, yes... have no issues connecting to my Plex Docker on my Media server from the same Android device(s) and my unRAID console via the browser, etc, I just removed the entire new VM, re-setup everything and no change, so I think time to call it a night and look at it again in the morning. -W

No USB devices, and I tried using Kore App on my Android device and it's not finding any media center on my network even though the VM is running and I can see the "OpenELEC" has been assigned an IP address on my router. Attempted a manual config to that IP but no clue on Username/PW and it didn't connect either, so I'm likely missing something obvious. I tried to SSH from into that IP with no luck... Maybe I just need to wait... I didn't get the whole Docker and VM's thing for a while either, now more or less "get those", so maybe this will eventually "hit me" also. -W

Thanks for you help getting the OpenElec VM started... I guess I still don't get the Kodi part... I can't seem to remote or access the OpenElec VM in any way to make any configuration changes, add my video shares, etc. I guess I need to keep reading, but it seems uber complex with not very good docs on setting up, or doing something with the VM or the app, but maybe I'm just "slow"... -W

OK, well I did both of those things...(before I saw this 2nd reply), I moved one of the SAS Cards up one PCI-E slot and also enabled the ACS Override... The VM Appears to now have been successfully created (now I need to find the writeup on what to do with it now and how to setup Kodi ).... Should I disable the ACS Override Setting?

Appears to be one of my SAS Controllers 01:00.0 RAID bus controller: Marvell Technology Group Ltd. 88SE9485 SAS/SATA 6Gb/s controller (rev c3) I'll enable the PCI ACS Override, reboot and report back.

IOMMU Groups /sys/kernel/iommu_groups/0/devices/0000:00:00.0 /sys/kernel/iommu_groups/1/devices/0000:00:01.0 /sys/kernel/iommu_groups/1/devices/0000:00:01.1 /sys/kernel/iommu_groups/1/devices/0000:01:00.0 /sys/kernel/iommu_groups/1/devices/0000:02:00.0 /sys/kernel/iommu_groups/1/devices/0000:02:00.1 /sys/kernel/iommu_groups/2/devices/0000:00:14.0 /sys/kernel/iommu_groups/3/devices/0000:00:16.0 /sys/kernel/iommu_groups/3/devices/0000:00:16.3 /sys/kernel/iommu_groups/4/devices/0000:00:19.0 /sys/kernel/iommu_groups/5/devices/0000:00:1a.0 /sys/kernel/iommu_groups/6/devices/0000:00:1b.0 /sys/kernel/iommu_groups/7/devices/0000:00:1c.0 /sys/kernel/iommu_groups/8/devices/0000:00:1c.1 /sys/kernel/iommu_groups/9/devices/0000:00:1c.3 /sys/kernel/iommu_groups/10/devices/0000:00:1c.5 /sys/kernel/iommu_groups/11/devices/0000:00:1c.6 /sys/kernel/iommu_groups/12/devices/0000:00:1c.7 /sys/kernel/iommu_groups/13/devices/0000:00:1d.0 /sys/kernel/iommu_groups/14/devices/0000:00:1f.0 /sys/kernel/iommu_groups/14/devices/0000:00:1f.2 /sys/kernel/iommu_groups/14/devices/0000:00:1f.3 /sys/kernel/iommu_groups/14/devices/0000:00:1f.6 /sys/kernel/iommu_groups/15/devices/0000:04:00.0 /sys/kernel/iommu_groups/16/devices/0000:05:00.0 /sys/kernel/iommu_groups/17/devices/0000:06:00.0 /sys/kernel/iommu_groups/17/devices/0000:07:03.0 /sys/kernel/iommu_groups/18/devices/0000:08:00.0 /sys/kernel/iommu_groups/19/devices/0000:09:00.0

Unsure if proper place to add this, but unable to start the newly created OpenElec VM. Attempting to start using a NVIDIA GeForce GTX 560TI and get the following "VM Creation Error" when I click Create. internal error: early end of file from monitor: possible problem: 2015-09-01T02:11:03.171941Z qemu-system-x86_64: -device vfio-pci,host=02:00.0,bus=pcie.0,multifunction=on,x-vga=on: vfio: error, group 1 is not viable, please ensure all devices within the iommu_group are bound to their vfio bus driver. 2015-09-01T02:11:03.171963Z qemu-system-x86_64: -device vfio-pci,host=02:00.0,bus=pcie.0,multifunction=on,x-vga=on: vfio: failed to get group 1 2015-09-01T02:11:03.171970Z qemu-system-x86_64: -device vfio-pci,host=02:00.0,bus=pcie.0,multifunction=on,x-vga=on: Device initialization failed 2015-09-01T02:11:03.171977Z qemu-system-x86_64: -device vfio-pci,host=02:00.0,bus=pcie.0,multifunction=on,x-vga=on: Device 'vfio-pci' could not be initialized

I have a fairly modestly sized 49.5TB - 20 disk array (18 Data + Parity + Cache) and was just looking through my disks to see which might be the next to get upgraded (not that I'm out of space yet, but I like to be proactive). I still have (5) 1.5TB Seagate Drives as the smallest drives in the array, so mostly likely the next to get upgraded. I was looking at the SMART reports for these drives and for at least 3 of them the "Power On Hours" seems pretty high... I don't really remember when I built my first unRAID, or if these drives were re-purposed, but the age seems pretty high (the other 2 are in the 2-3.5year range, and could possibly be warranty replacements, but don't remember for sure) I guess I'm just wondering if these metrics are real and/or accurate, and if so, I guess I should count myself lucky that the drives have lived this long. 9 Power On Hours 0x0032 018 018 000 Old age Always - 72548 (8y, 102d, 20h) 9 Power On Hours 0x0032 023 023 000 Old age Always - 67989 (7y, 277d, 21h) 9 Power On Hours 0x0032 013 013 000 Old age Always - 76809 (8y, 280d, 9h)

Solved.... seems that if you login with a PIN (as recommended by Win10), it won't connect to the unRAID server or shares...if I use a Password it does fine... go figure.

Same here (failing to AutoUpdate since 10130)...and it seems they have stopped posting the ISO's from 162 and up, and per the Windows Blog at least for now and trying to force everyone on Tech Previews to AutoUpdate instead of ISO update. On a Supermicro - X10SAE Motherboard with Xeon® E3-1230...

Kind of a newbie, so apologize if this is something "simple", or a Windows 10 thing instead of a unRAID/KVM thing... I am using Bridged networking in my VM config, Windows 10 Pro (10166) with Private Network setup on Windows. From the VM, I am able to Ping the IP/Hostname of my unRAID server and able to access via WebAdmin. Win10 VM is on same "Workgroup" as what's setup in SMB Settings in unRAID settings. No issues accessing the unRAID shares anywhere else on my network (other Physical PC's, including others running Win10), and on the VM I see other Windows PC's on my Network and am able map to shares I have on them... my unRAID Server doesn't even show up when browsing, and unable to map a network drive by name or IP. Any ideas? Thanks SW2

Thanks for the updates.... both SAB and SB are back working now after forced update! -SW2

Same.... Sickbeard from Binhex also failing with similar error. 2015-06-29 21:06:10,535 DEBG fd 8 closed, stopped monitoring (stderr)> 2015-06-29 21:06:10,535 DEBG fd 6 closed, stopped monitoring (stdout)> 2015-06-29 21:06:10,535 INFO exited: sickbeard (exit status 2; not expected) 2015-06-29 21:06:10,535 DEBG received SIGCLD indicating a child quit 2015-06-29 21:06:13,539 INFO spawned: 'sickbeard' with pid 10 2015-06-29 21:06:13,547 DEBG 'sickbeard' stderr output: /usr/sbin/python2: can't open file '/opt/sickbeard/SickBeard.py': [Errno 2] No such file or directory