ross232

Members
  • Posts

    31
  • Joined

  • Last visited

Posts posted by ross232

  1. I don't think ZFS is displacing any of the existing file system options. It's just another option you can optionally choose to use. In my case I'm using individual ZFS formatted drives in a normal parity protected array.

     

    The advantage here is that you can use snapshots, compression etc. But I retain the advantage of being able to use disks of different size and I can mount them individually. I also use ZFS on my cache drives because I don't love the way BTRFS reports free-space and have had issues with this in the past.

     

    I can see why there are use cases for people wanting a full ZFS array too. If speed is a priority then this will always win out over a parity + cache combo. People doing media creation (e.g. YouTubers etc) may want to start with a parity array, then migrate to a full ZFS backed one later. Add in the paid support options UNRAID now has and you have something you can rely on as your needs grow/change.

    • Upvote 1
  2. Hello,

     

    Does anyone know which file unassigned devices writes it's passthrough configuration to?

     

    I am having trouble with a VM. In the libvirt log I can see that it can't resolve a disk previously passed through as I have physically removed it.

     

    I can no longer change that configuration via the UI.

     

    Thanks,

    Ross

  3. 7 minutes ago, aidenpryde said:

    I'm having nothing but problems getting this to work on Linux (I haven't tried Windows yet because of all the other requirements).  When I try these commands I get a "mount point does not exist in terminal."


    I can get it mounted in linux and write permissions seem to work as well. I just wish it would work for Steam/Proton games - I think flock or symlink functionality might not be working.

     

    Here's my config.

    I have this in my VM XML (memoryBacking also has hugepages but I've removed it from here):

      <memoryBacking>
        <source type='memfd'/>
        <access mode='shared'/>
      </memoryBacking>

        <filesystem type='mount' accessmode='passthrough'>
          <driver type='virtiofs' queue='1024'/>
          <binary path='/usr/libexec/virtiofsd' xattr='on'>
            <cache mode='always'/>
            <sandbox mode='chroot'/>
            <lock posix='on' flock='on'/>
          </binary>
          <source dir='/mnt/user/'/>
          <target dir='shares'/>
          <alias name='fs0'/>
          <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/>
        </filesystem>

     

    And the following in my /etc/fstab in my VM:

    shares /mnt/unraid virtiofs 0 0

     

    NB: You must create /mnt/unraid first in the VM.

  4. 5 minutes ago, ich777 said:

    As soon as you build the images with the gnif patch you can't install any plugins with drivers included.

     

    Just a little note, when 6.10.0 drops you don't have to build a custom Kernel and you can install everything with plugins, even the gnif vendor reset. ;)


    Oh that is awesome news ^_^

     

    Thanks for the reply too, much appreciated!

    • Like 1
  5. @ich777 Thanks again for this. I used the tool to create a custom kernel with the GNIF patch and also coral and DVB drivers. I did want to ask - are plugins compatible with this?

     

    Initially I just had the GNIF patch on and then installed the DVB and Coral driver plugins from the app section. But as soon as the coral driver was modprobe'd I got a kernel panic. So I rebuilt with GNIF and coral drivers built in. But then I would get a kernel panic when my DVB hardware was initialised from the plugin as well.

     

    So ultimately I built the kernel with all three and that works fine.

    • Like 1
  6. @thor2002ro Thanks for this - I've just installed 5.13rc7 O3 :)

     

    What do I need to do to enable DVB on this kernel? I see the following in dmesg at the moment:

     

    [   19.006411] dvb-usb: did not find the firmware file 'dvb-usb-dib0700-1.20.fw' (status -2). You can use <kernel_dir>/scripts/get_dvb_firmware to get the firmware

     

    The standard DVB plugin doesn't work with this kernel from what I can tell.
     

  7. Upgraded from 6.9.0 rc-2. Disks won't spin down for me now.

     

    It's weird because one of the disks has nothing on it but I'm periodically seeing reads/writes to it.

     

    EDIT: Disabling the TurboWrite plugin prevents this problem. I'm not sure why it worked ok in RC2 but now now.

  8. On 1/13/2021 at 12:31 AM, cloudz said:

    Thank you so much for the clarification! No wonder I can always see the 3rd GPU available there, now I feel much better to use it without fear.

     

    You can also put the following in as a user script that runs on first array start:

     

    #!/bin/bash
    echo 0 > /sys/class/vtconsole/vtcon0/bind
    echo 0 > /sys/class/vtconsole/vtcon1/bind
    echo efi-framebuffer.0 > /sys/bus/platform/drivers/efi-framebuffer/unbind 

     

    This will allow you to see unRAID booting via your GPU and then unhook it for use as passthrough into VMs.

  9. I'm running an RX 480 on a Ryzen 5 2600 processor.

     

    I don't need a vBIOS at all with mine - are you sure you need one? I do use - rcu_nocbs and at the moment have disabled C States (although this may not be necessary).

     

    ACS isn't necessary for me (using a Tomahawk B350 BIOS). Have you made sure your BIOS is up to date? Check to see if your video card already has it's own IOMMU group in the unRAID diagnostics prior to enabling this.

     

    Also I need to use the Q35 machine type with OVMF for things to work.

  10. Hello,

     

    The '2020-01-12T11:04:22.026175Z qemu-system-x86_64: vfio_region_write(0000:02:00.0:region1+0x12cc60, 0x0,8) failed: Device or resource busy' lines indicate something else has hold of the GPU.

     

    Maybe unRAID itself?


    Try running the following in a terminal prior to booting the VM:

     

    echo 0 > /sys/class/vtconsole/vtcon0/bind
    echo 0 > /sys/class/vtconsole/vtcon1/bind
    echo efi-framebuffer.0 > /sys/bus/platform/drivers/efi-framebuffer/unbind

     

    Ensure you have your vBIOS set correctly as per the reply above. You will likely lose display after running the above commands - you might need to use your phone or a tablet on the same network to start the VM and test this.

     

    Cheers,

    Ross.

  11. I'm loving the all in one capability unRAID gives me - it's my gaming VM, my NAS and it runs all of the docker contains I need for local servers!

     

    I would love it if there is a way of being able to VNC into a GPU pass through enabled VM. This would be really handy when something goes wrong with pass through and you want to check without needing to boot the VM up specifically in VNC mode.

  12. Hello,

     

    I have GPU pass through working on an RX480 / Ryzen machine. I'm having an issue when no monitors are connected at the time I boot in the unRAID server. If I do this I am still able to start the Windows VM but I get an error code 43 and it reverts to the Microsoft Basic Display Adapter.

     

    If I connect a display and boot the unRAID server, the VM starts but this time the RX480 driver loads normally (at whatever resolution the HDMI input reports). I have ordered a dummy HDMI adapter in the interim.

     

    I am using the following workaround from this thread as I couldn't get GPU pass-through working without it:

    echo 0 > /sys/class/vtconsole/vtcon0/bind
    echo 0 > /sys/class/vtconsole/vtcon1/bind
    echo efi-framebuffer.0 > /sys/bus/platform/drivers/efi-framebuffer/unbind

     

    I will try disabling this tonight incase it isn't needed when no display is present.

     

    Does anyone have any thoughts?

     

    Thanks!

     

    Ross.

  13. Hello,

     

    I'm a new unRAID user. When setting things up I added 1x 4TB HDD drive to parity and 2x 4TB HDD drive(s) to the array. I also added a 250GB SSD drive to the array which I intended on using exclusively for domain (VM) storage (I have set the domains share to only include this disk). Other shares are set to exclude it.

     

    I didn't realise that SSDs weren't supported. I'm now not sure if this will be problematic later due to TRIM issues (as I understand it, TRIM should be disabled and I'd guess that write operations shouldn't be huge apart from OS updates).

     

    Should I remove the SSD from the array as this could cause parity problems? If I want to do this, what's the best course of action here?

     

    Thanks in advance :)


    Kind Regards,

     

    Ross.