SpaceInvaderOne

64 gig

sure heres my dropbox link https://www.dropbox.com/s/gymaipg6vprd508/MSI_util.zip?dl=0

Yes should be stickied! Yes dockers can be pinned aswell. click the advanced view then add to extra parameters cpuset-cpus= The cpus can be pinned if you have or havent used isolcpus. I dont pin to isolcpus cores myself just to the ones used by unraid, i just avoid pinning dockers to the first pair of threads as i have heard the linux os prefers these itself. Edit.....oops sorry squid see you just replied before me!!

Thankyou dlandon for that excellent info. I have isolcpu 8 cores for my vms and left the rest for unraid and dockers and pinned emulator tasks to 2 of those cores. Wow i get an extra 1000 score running geek bench3 on my osx vm. And i get no latency on my windows 10 vm. What a difference..... great info thanks so much for sharing

So can they be pinned to dockers or only vms after isolocpus I don't know. I've not tried. I emailed the limetech guys about this and thought i would post what they replied in case others are interested. isolcpus prevents the host OS from assigning the logical CPUs specified in the parameter to any processes (kernel or user space) at boot. Users can manually assign processes back to those CPUs using Linux's cpuset capabilities. Docker and virtual machines both support this. So you can use isolcpus to reserve a set of logical CPUs and then assign docker containers to some and VMs to others and leave the unisolated CPUs for host-based tasks, if you so desire. There may be some advantages to this, there may be some disadvantages to this. With respect to adding isolcpus capability post-boot, so that you can toggle its usage on and off, that is an interesting concept that we have been investigating, but it's not something that's built into Linux's capability set today just yet. We could manually manipulate some things in the user space for this, but it's not something we're tackling as a project right now.

i would be very interested in seeing this aswell

So can they be pinned to dockers or only vms after isolocpus

Thats interesting. I did some testing a few days ago pinning hyperthreaded pairs then pinning none hyperthreaded pairs and running passmark cpu benchmark software afterwards this is my results using a 12 core xeon @ 2.4ghz Using 8 threads or 4 cpu cores firstly 8 threads with paired hyperthreads the passmark score is 7256 next 8 threads all from non paired separate so one thread from different core passmark score is 10417 I as the threads were all on separate cores the speed was faster but i guess wouldnt have been if the other thread on each core was being used by another process. I know this is a bit off topic but thought it interesting as i never expected this result

Lol Sent from Winterfell using a raven

you can passthrough whole disk or specify the partition. eg. whole disk would be <source dev='/dev/disk/by-id/ata-ST3500312CS_9VVERKB1'/> whilst for partion 1 would be <source dev='/dev/disk/by-id/ata-ST3500312CS_9VVERKB1-part1'/> the ata-ST3500312CS_9VVERKB1 part change that to ata-yourdeviceid The problem with using sdx is that they can change on reboot

still getting error with nzbs downloaded looking at them with text edit i see <error code="100" description="Empty API Key"/> Why is this please?

still having probs. Can anyone help?

I tried passing through an unassigned usb disk to an osx vm as the primary disk. It was a clone of the startup disk of my macbook pro. I wanted to see if i could "transfer" my macbook pro and all programmes and settings to an unraid vm. Well my identification was External_USB_3.0_2012040931753. When i specified this it gave error that it wasnt valid and vm wouldnt start. I saw the disk was marked as sda. So i did it like this. (I had to change bus to sata for osx) <disk type='block' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source dev='/dev/sda'/> <target dev='hdd' bus='sata'/> </disk> The vm booted straight into my macbooks os!!

Just relating to the power consumption of both methods. i agree with a small number of drives it would be negligible. Because as well remember the data is written to the cache first, then at a later time written to the array, so it uses power twice to do its writes.

I think my watch folder not working is moviegrabber related as warnings are coming up on sab as to empty nzbs. When i look in the nzbs in the watch folder they say <error code="100" description="Empty API Key"/>

Thankyou. I am beginning to get somewhere now However of my indexers only nzb geek seems to be finding movies, yet config is exactly the same. Also could you tell me what spotweb support is please? I googled it but didnt find anything that related to it. Also another problem i have is sab isnt scanning my nzb folder, but i will post that in the correct thread. Is the best way to stop foreign language movies just to add to must not. As alot dont have language in title, but in nfo. And one last question! `For moviegrabber to check my existing movies they need to each be in their own folder, correct? My whole collection is just in one folder with metadata. Is there an easy way i could move all movies with metadata to individual folders using something like filebot?

Hi, I have been having trouble trying to get moviegrabber working for some time now but cant find what i have done wrong. When i click run now i dont get anything in history or que. Nothing comes in my watch folder. Could you look at my config and see if you can see whats wrong. Many thanks

Thanks for advise. I will keep an eye on it

Hi , How serious is having a Reallocated sector count raw value of 1. I just got this warning on the smart. Should i replace the drive asap or could i just acknowledge the error and see if it gets worse?? # Attribute Name Flag Value Worst Threshold Type Updated Failed Raw Value 1 Raw read error rate 0x000f 079 063 044 Pre-fail Always Never 84007277 3 Spin up time 0x0003 092 089 070 Pre-fail Always Never 0 4 Start stop count 0x0032 100 100 020 Old age Always Never 412 5 Reallocated sector count 0x0033 100 100 036 Pre-fail Always Never 1

Thanks yesdog for all that detailed info I now have an nvidea gpu and i am happy with it. Im running 6.2 beta aswell so running it with the hyper v enabled

I removed the option to move the apps tab down to settings because as a general rule it is a very bad idea to be modifying system files (which is what I was doing). This was always going to be a temporary fix. Starting with 6.1.7, you can go into display settings, and move the User's tab to settings which will fix those display aberrations Ah thanks thats working great now

I have just updated the community applications plugin and now i cant find how to not have the tab "apps" added to the top bar of the gui. As i use Dynamix System Buttons plugin the gui is messed up when this extra app tab is at the top of gui. How can i get this back to how it was? Thanks

Interesting, but doesn't change our recommendations. When Linus did the gaming + NAS video (not 2 gamers or 7), he had a skylake system and the ACS override didn't work for him. Luck of the draw on the hardware I guess. Certainly doesn't change anything with respect to igd pass through support. @JonP Yeah bit the he got the gpu passed through(it was only the onboard sound he couldnt pass through). I think if you say skylake isnt compatable with unraid, or not recommended for gpu passthrough, it may put alot of people off choosing to try or purchase unraid, as many people may not want to buy older hardware when building a new rig. There have been quite a few of us who have built our unraid rigs with skylake, and many people using kvm with passthough on other linux distros. Why dont you make a section with pros and cons of each main type of cpu. I realise that its hard for you to test everything and expensive, but this would help people deceide what to buy and what to expect. You guys official online manual on the wiki is for 4.7! I know it takes time updating the website (and i would far rather have you guys improving unraid and getting us our 6.2 soon!) Anyway thanks for all your hardwork you do for us.

Yes I agree. If i had only one display i would use a kvm switch, that way one keyboard can be shared by 2 vms and switched between the two. Also it would allow you to switch the display aswell.

Are you sure ACS overide not supported in Skylake CPUs, Jon? I have Skylake (hardware in sig) and ACS works for me This is my iommu groups with ACS override. Note my 2 gpus in separate groups 11 and 12 PCI Devices 00:00.0 Host bridge: Intel Corporation Sky Lake Host Bridge/DRAM Registers (rev 07) 00:01.0 PCI bridge: Intel Corporation Sky Lake PCIe Controller (x16) (rev 07) 00:01.1 PCI bridge: Intel Corporation Sky Lake PCIe Controller (x8) (rev 07) 00:02.0 VGA compatible controller: Intel Corporation Sky Lake Integrated Graphics (rev 06) 00:14.0 USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI Controller (rev 31) 00:14.2 Signal processing controller: Intel Corporation Sunrise Point-H Thermal subsystem (rev 31) 00:16.0 Communication controller: Intel Corporation Sunrise Point-H CSME HECI #1 (rev 31) 00:17.0 SATA controller: Intel Corporation Device a102 (rev 31) 00:1b.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Root Port #17 (rev f1) 00:1c.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #1 (rev f1) 00:1d.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #9 (rev f1) 00:1f.0 ISA bridge: Intel Corporation Sunrise Point-H LPC Controller (rev 31) 00:1f.2 Memory controller: Intel Corporation Sunrise Point-H PMC (rev 31) 00:1f.3 Audio device: Intel Corporation Sunrise Point-H HD Audio (rev 31) 00:1f.4 SMBus: Intel Corporation Sunrise Point-H SMBus (rev 31) 00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (2) I219-V (rev 31) 01:00.0 VGA compatible controller: NVIDIA Corporation GM206 [GeForce GTX 960] (rev a1) 01:00.1 Audio device: NVIDIA Corporation Device 0fba (rev a1) 02:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM] 02:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Caicos HDMI Audio [Radeon HD 6400 Series] 04:00.0 USB controller: ASMedia Technology Inc. Device 1242 IOMMU Groups Warning: Your system has booted with the PCIe ACS Override setting enabled. The below list doesn't not reflect the way IOMMU would naturally group devices. To see natural IOMMU groups for your hardware, go to the VM Settings page and set the PCIe ACS Override setting to No. /sys/kernel/iommu_groups/0/devices/0000:00:00.0 /sys/kernel/iommu_groups/1/devices/0000:00:01.0 /sys/kernel/iommu_groups/2/devices/0000:00:01.1 /sys/kernel/iommu_groups/3/devices/0000:00:02.0 /sys/kernel/iommu_groups/4/devices/0000:00:14.0 /sys/kernel/iommu_groups/4/devices/0000:00:14.2 /sys/kernel/iommu_groups/5/devices/0000:00:16.0 /sys/kernel/iommu_groups/6/devices/0000:00:17.0 /sys/kernel/iommu_groups/7/devices/0000:00:1b.0 /sys/kernel/iommu_groups/8/devices/0000:00:1c.0 /sys/kernel/iommu_groups/8/devices/0000:04:00.0 /sys/kernel/iommu_groups/9/devices/0000:00:1d.0 /sys/kernel/iommu_groups/10/devices/0000:00:1f.0 /sys/kernel/iommu_groups/10/devices/0000:00:1f.2 /sys/kernel/iommu_groups/10/devices/0000:00:1f.3 /sys/kernel/iommu_groups/10/devices/0000:00:1f.4 /sys/kernel/iommu_groups/10/devices/0000:00:1f.6 /sys/kernel/iommu_groups/11/devices/0000:01:00.0 /sys/kernel/iommu_groups/11/devices/0000:01:00.1 /sys/kernel/iommu_groups/12/devices/0000:02:00.0 /sys/kernel/iommu_groups/12/devices/0000:02:00.1 now this is my iommu groups wothout acs override. Note my 2 gpus now in group 1 PCI Devices 00:00.0 Host bridge: Intel Corporation Sky Lake Host Bridge/DRAM Registers (rev 07) 00:01.0 PCI bridge: Intel Corporation Sky Lake PCIe Controller (x16) (rev 07) 00:01.1 PCI bridge: Intel Corporation Sky Lake PCIe Controller (x8) (rev 07) 00:02.0 VGA compatible controller: Intel Corporation Sky Lake Integrated Graphics (rev 06) 00:14.0 USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI Controller (rev 31) 00:14.2 Signal processing controller: Intel Corporation Sunrise Point-H Thermal subsystem (rev 31) 00:16.0 Communication controller: Intel Corporation Sunrise Point-H CSME HECI #1 (rev 31) 00:17.0 SATA controller: Intel Corporation Device a102 (rev 31) 00:1b.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Root Port #17 (rev f1) 00:1c.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #1 (rev f1) 00:1d.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #9 (rev f1) 00:1f.0 ISA bridge: Intel Corporation Sunrise Point-H LPC Controller (rev 31) 00:1f.2 Memory controller: Intel Corporation Sunrise Point-H PMC (rev 31) 00:1f.3 Audio device: Intel Corporation Sunrise Point-H HD Audio (rev 31) 00:1f.4 SMBus: Intel Corporation Sunrise Point-H SMBus (rev 31) 00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (2) I219-V (rev 31) 01:00.0 VGA compatible controller: NVIDIA Corporation GM206 [GeForce GTX 960] (rev a1) 01:00.1 Audio device: NVIDIA Corporation Device 0fba (rev a1) 02:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM] 02:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Caicos HDMI Audio [Radeon HD 6400 Series] 04:00.0 USB controller: ASMedia Technology Inc. Device 1242 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:01:00.1 /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:02.0 /sys/kernel/iommu_groups/3/devices/0000:00:14.0 /sys/kernel/iommu_groups/3/devices/0000:00:14.2 /sys/kernel/iommu_groups/4/devices/0000:00:16.0 /sys/kernel/iommu_groups/5/devices/0000:00:17.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/7/devices/0000:04:00.0 /sys/kernel/iommu_groups/8/devices/0000:00:1d.0 /sys/kernel/iommu_groups/9/devices/0000:00:1f.0 /sys/kernel/iommu_groups/9/devices/0000:00:1f.2 /sys/kernel/iommu_groups/9/devices/0000:00:1f.3 /sys/kernel/iommu_groups/9/devices/0000:00:1f.4 /sys/kernel/iommu_groups/9/devices/0000:00:1f.6