heilage

Here are the benchmarks for the system drive, which is a vdisk on the cache, and the mounted share where the steam library is, which is a cache-only share, mounted through SMB. Doesn't seem bad at all, so I guess AS SSD was the issue for me.

I benched it with AS SSD, but I'll give it a go with Crystal Disk Mark and report back with the results some time during the weekend.

How did you mount outside of the array? Are we talking like it's a raw drive formatted for Windows? My cache drive is a Samsung 840 250GB, and I run the vdisks off it. Maybe the SSD itself is dying...

I haven't had time to look into this, unfortunately. Some notes: - I only use local accounts - Currently, unRAID shares are invisible to my Windows VM. Should they not be browseable? They must manually be added by using hostname or IP - I know that any application running as administrator (or requiring UAC, like running first time setup) does not see my mounted share. Why? Is it only mounted on user level? - It does appear that running a game off a network share, except in jonp's case, even on SSD, has a high performance penalty? So far vdisks seem to be the best way to do this, which is less than optimal as a practical solution I guess. I attached the XML for my VM, maybe someone can spot something. Have I perhaps set up the network in a bad way? In the meantime I'll keep tinkering, and I'm going to try to bench the cache-only share to see what kind of reads and writes I'm getting. <domain type='kvm' id='11' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'> <name>Prometheus</name> <uuid>32e936ec-5987-9089-029f-574bd8c1cbb2</uuid> <description>Spillmaskina</description> <metadata> <vmtemplate name="Custom" icon="windows.png" os="windows"/> </metadata> <memory unit='KiB'>12582912</memory> <currentMemory unit='KiB'>12582912</currentMemory> <memoryBacking> <nosharepages/> <locked/> </memoryBacking> <vcpu placement='static'>4</vcpu> <cputune> <vcpupin vcpu='0' cpuset='0'/> <vcpupin vcpu='1' cpuset='1'/> <vcpupin vcpu='2' cpuset='2'/> <vcpupin vcpu='3' cpuset='3'/> </cputune> <resource> <partition>/machine</partition> </resource> <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='4' 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/cache/VMer/Prometheus/vdisk1.img'/> <backingStore/> <target dev='hda' bus='virtio'/> <boot order='1'/> <alias name='virtio-disk0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </disk> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/cache/VMer/Prometheus/vdisk2.img'/> <backingStore/> <target dev='hdb' bus='virtio'/> <alias name='virtio-disk1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </disk> <controller type='usb' index='0'> <alias name='usb'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/> </controller> <controller type='pci' index='0' model='pci-root'> <alias name='pci.0'/> </controller> <controller type='virtio-serial' index='0'> <alias name='virtio-serial0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:4d:8f:4b'/> <source bridge='br0'/> <target dev='vnet0'/> <model type='virtio'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </interface> <serial type='pty'> <source path='/dev/pts/0'/> <target port='0'/> <alias name='serial0'/> </serial> <console type='pty' tty='/dev/pts/0'> <source path='/dev/pts/0'/> <target type='serial' port='0'/> <alias name='serial0'/> </console> <channel type='unix'> <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/Prometheus.org.qemu.guest_agent.0'/> <target type='virtio' name='org.qemu.guest_agent.0' state='connected'/> <alias name='channel0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <hostdev mode='subsystem' type='usb' managed='yes'> <source> <vendor id='0x046d'/> <product id='0xc52b'/> <address bus='1' device='6'/> </source> <alias name='hostdev0'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='yes'> <source> <vendor id='0x046d'/> <product id='0xc318'/> <address bus='1' device='5'/> </source> <alias name='hostdev1'/> </hostdev> <memballoon model='virtio'> <alias name='balloon0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' 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=00:1b.0,bus=root.1,addr=01.0'/> </qemu:commandline> </domain> EDIT: Holy crap, I benched the C: drive (vdisk1) with AS SSD, and got 0,5MB/s 4K Write. What the hell? This can't be normal? A lot in this setup seems to be off. EDIT2: I messed around a bit more and painted myself into a corner. It turns out, you can do a soft link in the main steam folder to the SMB share, which appears to work well and Steam assumes all games are locally. The backside of this however, is that the space calculations are done on the C drive, which means that if your free space is less than the size of the game, it will not install, even though you're not actually installing it to C. Not sure how to get around this, but I might just create a new VM and reinstall...

Well, i guess we're gonna have to get to work then. I want to figure this out. If I have time tomorrow, I will return with a bunch of data describing setups and settings, and we can have a look at how it differs from a working setup.

I noticed he was using a newer beta, I'm currently on the last official release. Any word on release date for 6.2?

I too have a fairly extensive Steam library, and I would love to have it accessible by any OS, and install them all, but that doesn't appear feasible at the moment. I do wonder how jonp did this in his video. Perhaps this is a problem exclusive to Windows 10?

Interestingly, it worked fine if I moved it to the vdisk and then tried to run it. I'm going to try moving it back to the share and see if it still runs. I suspect it will, but perhaps with issues. I saw that Linus video earlier today, and he seemed to go with running games from vdisks, and I'm partial to agreeing. This is causing a lot of hassle that's not necessarily warranted, they are just games and I store nothing important on my Windows VM anyway (all my code is accessed through the Linux VM, and is stored on parity-proteced shares and synced with my offsite VPS). I'm thinking of just adding a big 500GB SSD and add it to the cache pool, and put a big vdisk on it to store my games. Also, I noticed when copying the game, that the file transfer speeds dropped way down to 20MB/s on certain files. The 4K read issue could be playing a role there, but I'm not sure how the vdisks and unRAID file system structures its partitioned sectors.

No go, but I believe I have found what is causing the problem. I checked out the Steam logs, and found several instances of: ERROR: /installscript failed on: <location>\runasadmin.vdf I tried running Steam as an Aministrator, but then Steam cannot see the mounted share, thus the game does not exist. The video about Steam libraries had no mention of any issues like this... This is causing me to be forced to install everything on a vdisk, which sucks and probaby hurts performance.

That's a great tip, this isn't the first time Windows has been difficult with SMB shares on my network. I tried it now, and when I tried to launch the newly installed AC: Unity on that share, the "verify file integrity" function failed with 20GB missing, and Steam failed in almost the exact same way, so I suspect that something with the mounting of the SMB share is a bit off. In my current logon session, it automatically mounted the share after giving it the same access as my username/pw in Windows 10. So now I just have to wait an hour for the broken 20GB to download... Will return with new reports later.

Yes, they are mapped (otherwise, how would I install them?) and should attach on login. It fails across boot sessions as well, so rebooting has yet to make a difference. Are there any logs in Steam one could check out? I'm going to look into how the process actually fails, if I can.

Hey there. New unRAID here, so far I've been pretty satisfied wth it all. However, I've been trying to get the gaming portion up and running, and I'm having some troubles with Steam. According to a video posted here (from YouTube), one should set up a share (cache only) for games in Steam, but so far I've had little success making this work. Games install just fine, I can add the share as a library folder in Steam, but whenever I try to actually start a game, the "first time run" process starts and immidiately quits on Step 1, and nothing else happens. No error message or anything of the sort. To eliminate drivers or Windows setup, I made a new vdisk and mounted it with my VM, installed Just Cause 3 on it (one of the games that didn't run), and now it runs pretty much like normal. Has anyone experieced something like this?