Jump to content

Original_Vecna

Members
  • Posts

    63
  • Joined

  • Last visited

Posts posted by Original_Vecna

  1. Yeah I have no idea. I was able to get advanced view on, and these settings still don't show up. Found another post that suggested  going to settings of the undefined device and enabling automount, passed through, and share. I've done that, going back in, automount is not staying enabled. I can access the share via windows machine, even writing to it without a login. Zoneminder still wont see it though. This is ridiculous.

  2. 8 hours ago, tjb_altf4 said:

    I just reread your first post, I think you talked about 2 seperate things.
    You stated the disk is mounted here: "/mnt/disks/212307B02", that reads like it has been mounted using UD.

    In which case if you want to use that option, the docker path being passed needs the slave option to be used.
    image.png.248d07b4c6f9a0fcff25f69b769cb397.png

    EDIT: Hoopster just beat me lol

    Where do I find this setting?

  3. Just added a 1TB SSD for recording home security video via ZoneMinder. How do I use it? I've formatted it as BTRFS, mounted it, and it's location is /mnt/disks/212307B02. I've gone into ZoneMinder to add a data source, but it doesn't read the availability of the drive.

     

    I want this drive to be on its own, not in the array or cache, and just serve as a standalone drive for event recordings.

    What am I missing? 

  4. This is from a Unraid OS Plus level  account.

    Error when trying to start the pfSense VM:

    internal error: process exited while connecting to monitor: 2021-03-15T23:57:09.593868Z qemu-system-x86_64: -device vfio-pci,host=0000:02:00.0,id=hostdev0,bus=pci.1,addr=0x0: vfio 0000:02:00.0: failed to setup container for group 16: Failed to set iommu for container: Operation not permitted

     

    I have passed the last two ports of my broadcom 4 port nic from my R710 on the Tools > System Devices screen.

    My Vfio-PCI log

    Loading config from /boot/config/vfio-pci.cfg
    BIND=0000:02:00.0|14e4:1639 0000:02:00.1|14e4:1639
    ---
    Processing 0000:02:00.0 14e4:1639
    Vendor:Device 14e4:1639 found at 0000:02:00.0
    
    IOMMU group members (sans bridges):
    /sys/bus/pci/devices/0000:02:00.0/iommu_group/devices/0000:02:00.0
    /sys/bus/pci/devices/0000:02:00.0/iommu_group/devices/0000:02:00.1
    
    Binding...
    Successfully bound the device 14e4:1639 at 0000:02:00.0 to vfio-pci
    ---
    Processing 0000:02:00.1 14e4:1639
    Vendor:Device 14e4:1639 found at 0000:02:00.1
    
    IOMMU group members (sans bridges):
    /sys/bus/pci/devices/0000:02:00.1/iommu_group/devices/0000:02:00.0
    /sys/bus/pci/devices/0000:02:00.1/iommu_group/devices/0000:02:00.1
    
    Binding...
    0000:02:00.0 already bound to vfio-pci
    0000:02:00.1 already bound to vfio-pci
    Successfully bound the device 14e4:1639 at 0000:02:00.1 to vfio-pci
    ---
    vfio-pci binding complete
    
    Devices listed in /sys/bus/pci/drivers/vfio-pci:
    lrwxrwxrwx 1 root root 0 Mar 15 18:51 0000:02:00.0 -> ../../../../devices/pci0000:00/0000:00:03.0/0000:02:00.0
    lrwxrwxrwx 1 root root 0 Mar 15 18:51 0000:02:00.1 -> ../../../../devices/pci0000:00/0000:00:03.0/0000:02:00.1
    
    ls -l /dev/vfio/
    total 0
    crw------- 1 root root 249, 0 Mar 15 18:51 16
    crw-rw-rw- 1 root root 10, 196 Mar 15 18:50 vfio

     

×
×
  • Create New...