First time unraid user, wanted to replace a home NAS and get a new gaming system, so decided to kill two birds with one stone.  The videos and documentation are great, I watched them all before starting then again as I completed the build.  Unfortunately I have spent a few days trying to get some things working and have run out of ideas.  3rd one is my biggest concern, but here goes....

 

1) Tower does not show in Network Neighborhood - I see it on my W7 and Mac systems so this seems to be a W10 issue.  I can map drives by IP and if I run \\tower it opens and the populates the neighborhood. Seen a lot of W10 posts similar, but cant seem to find a fix.

 

 

2) Using shares as recommended, but noticing that all data seems to be put only on fist disk. Is this expected behavior or do I possibly have an issue in my setup?

 

 

 

3) Memory Utilization at ~90% at start and no processes seem to be using it. I have done poolman, etc, there is nothing using it that I can find and this is from a fresh boot.  Created a second VM clean using documented steps and get the same result.

 

 

 

 

System details:

 

Unraid Plus / Windows 10 home

 

Gigabyte Z170X Gaming 7

Intel Core I7-6700K

G.Skill TridentZ Series 32GB

Asus GeForce GTX 970 4GB STRIX

2 x Samsung 850 EVO 500g SSD (Cache)

1 x 3tb parity disk

3 x 2tb data disks

 

System Info:

 

VM Template:

 

VM XML:

<domain type='kvm' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'>
  <name>RL-W10</name>
  <uuid>b29c08be-092d-e8c9-db2b-6a0783c8259b</uuid>
  <metadata>
    <vmtemplate name="Custom" icon="windows.png" os="windows"/>
  </metadata>
  <memory unit='KiB'>16777216</memory>
  <currentMemory unit='KiB'>2097152</currentMemory>
  <memoryBacking>
    <nosharepages/>
    <locked/>
  </memoryBacking>
  <vcpu placement='static'>6</vcpu>
  <cputune>
    <vcpupin vcpu='0' cpuset='2'/>
    <vcpupin vcpu='1' cpuset='3'/>
    <vcpupin vcpu='2' cpuset='4'/>
    <vcpupin vcpu='3' cpuset='5'/>
    <vcpupin vcpu='4' cpuset='6'/>
    <vcpupin vcpu='5' cpuset='7'/>
  </cputune>
  <os>
    <type arch='x86_64' machine='pc-i440fx-2.3'>hvm</type>
  </os>
  <features>
    <acpi/>
    <apic/>
  </features>
  <cpu mode='host-passthrough'>
    <topology sockets='1' cores='6' threads='1'/>
  </cpu>
  <clock offset='localtime'>
    <timer name='rtc' tickpolicy='catchup'/>
    <timer name='pit' tickpolicy='delay'/>
    <timer name='hpet' present='no'/>
  </clock>
  <on_poweroff>destroy</on_poweroff>
  <on_reboot>restart</on_reboot>
  <on_crash>restart</on_crash>
  <devices>
    <emulator>/usr/bin/qemu-system-x86_64</emulator>
    <disk type='file' device='disk'>
      <driver name='qemu' type='raw' cache='writeback'/>
      <source file='/mnt/user/vdisks/RL-W10/vdisk1.img'/>
      <target dev='hdc' bus='virtio'/>
      <boot order='1'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/>
    </disk>
    <disk type='file' device='cdrom'>
      <driver name='qemu' type='raw'/>
      <source file='/mnt/user/ISOs/Windows-10.iso'/>
      <target dev='hda' bus='ide'/>
      <readonly/>
      <boot order='2'/>
      <address type='drive' controller='0' bus='0' target='0' unit='0'/>
    </disk>
    <disk type='file' device='cdrom'>
      <driver name='qemu' type='raw'/>
      <source file='/mnt/user/ISOs/virtio-win-0.1.102.iso'/>
      <target dev='hdb' bus='ide'/>
      <readonly/>
      <address type='drive' controller='0' bus='0' target='0' unit='1'/>
    </disk>
    <controller type='usb' index='0'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/>
    </controller>
    <controller type='pci' index='0' model='pci-root'/>
    <controller type='ide' index='0'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/>
    </controller>
    <controller type='virtio-serial' index='0'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/>
    </controller>
    <interface type='bridge'>
      <mac address='52:54:00:4e:cf:6f'/>
      <source bridge='br0'/>
      <model type='virtio'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/>
    </interface>
    <serial type='pty'>
      <target port='0'/>
    </serial>
    <console type='pty'>
      <target type='serial' port='0'/>
    </console>
    <channel type='unix'>
      <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/RL-W10.org.qemu.guest_agent.0'/>
      <target type='virtio' name='org.qemu.guest_agent.0'/>
      <address type='virtio-serial' controller='0' bus='0' port='1'/>
    </channel>
    <hostdev mode='subsystem' type='usb' managed='yes'>
      <source>
        <vendor id='0x1532'/>
        <product id='0x0043'/>
      </source>
    </hostdev>
    <hostdev mode='subsystem' type='usb' managed='yes'>
      <source>
        <vendor id='0x1532'/>
        <product id='0x011a'/>
      </source>
    </hostdev>
    <hostdev mode='subsystem' type='usb' managed='yes'>
      <source>
        <vendor id='0x1b1c'/>
        <product id='0x0c04'/>
      </source>
    </hostdev>
    <memballoon model='virtio'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/>
    </memballoon>
  </devices>
  <qemu:commandline>
    <qemu:arg value='-device'/>
    <qemu:arg value='ioh3420,bus=pci.0,addr=1c.0,multifunction=on,port=2,chassis=1,id=root.1'/>
    <qemu:arg value='-device'/>
    <qemu:arg value='vfio-pci,host=01:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on'/>
    <qemu:arg value='-device'/>
    <qemu:arg value='vfio-pci,host=01:00.1,bus=root.1,addr=00.1'/>-
  </qemu:commandline>
</domain>

 

Thanks in advance for any suggestions.

Set initial and max memory to the same value.

 

I think that might have something to do with it, but I'm pretty new to unRAID as well.

 

Damn that Linus made it look so easy.

As for Question #2 if you're set using High water on your shares it will fill one disk to

 

High-Water

In this method, the system will pick the disk which currently has the least free space that is still above a certain minimum (called the "high water" mark). Suppose in our example above, we have this situation:

disk         size         free

disk1 80GB 75GB

disk2 120GB 110GB

disk3 80GB 70GB

 

The initial high water mark is set to the 1/2 the size of the largest disk; in this case, it will be set to 60GB. In this state, disk1 has 15GB of free space above the "high water" mark; disk2 has 50GB, and disk3 has 10GB.

As new objects are created, the system will choose disk3 until the amount of free space on disk3 falls under 60GB. Subsequently, the system will start allocating from disk1 until it's free space falls under 60GB. Then it will allocate from disk2 until it's free space also falls under 60GB. Once the amount of free space on all disks is below 60GB, a new high water mark is established by dividing the old high water mark by 2.

The advantage of High-water method is that when writing a series of files, most of the time only one data disk will need to be spun up.

Set initial and max memory to the same value.

 

I think that might have something to do with it, but I'm pretty new to unRAID as well.

 

Damn that Linus made it look so easy.

 

Wow, I would have never guessed that as a fix.  Set it 16/16 and I am now at 8%.  Thanks.

As for Question #2 if you're set using High water on your shares it will fill one disk to

 

 

Ah, that makes sense.  So is is reasonable to set my shares as most-free to make sure I get a good spread?  And if I do is there any way to 'level' the data out without moving it around?

Once you start filling up your shares it will spread.

 

I'd leave as is- here's what my spread currently looks like...

 

Once you start filling up your shares it will spread.

 

 

So I am moving off a synology running raid 10 and using crap NAS drives, so was hoping to gain some performance by spreading the data across the same drives vs. all my data going to one.  I guess the term unraid just clicked for me.

 

Might be overthinking it, but I think I will try most-free to get them all participating.  For now I dont have much more than 1tb so I like the idea of it being more 1/3 each than all on one.

 

Thanks

Did you have any problems with HDMI Audio on your Nvidia card?

 

That's my next hurtle.

 

I tried the reg fix, but it didn't help.

I still need to get another monitor with HDMI, but tested it on an ASUS VG248QE and it worked.  So I would make sure you have only the HDMI cable connected for starters and the device set in the VM setup (its in my pic above).  In my case the MSISupported was there under the PCI device already and I just had to set it to 1 from 0.

 

http://lime-technology.com/wiki/index.php/UnRAID_6/VM_Guest_Support#Enable_MSI_for_Interrupts_to_Fix_HDMI_Audio_Support

 

 

Yeah I had to do the reg hacks.. I think I may have just gotten it to work but won't be able to test till I get home later today.

 

I had originally set it for just the Graphics card, but I think I needed to set it for the HD Audio as well which was separate.