markymark

Thank you.. Helped me too

Yep i don't know why I set it to 500G originally, I must have had a brain fart. Yes, I did stop it and resize and then subsequently created it and then used CA to install them all again. I actually followed ChatGPTs instructions (as it's been pretty accurate on a lot of things like this) but it wasnt quite right and I ended up rebooting the server as a result unexpectedly and also lost my custom network but I'm not sure that would have happened anyway with a deleted docker.img It turns out last night that I had a post argument on the Matrix Synapse app that was causing it to immediately close and once I worked that out late last night I slapped my head. I was also trying to use files from the previous installation but it needed completely fresh ones which was also casuing issues so once I decided to start from scratch it worked. It must have been a coincidence that another app I chose also chose to immediately fail but it appears that the apps I actually want to install are working and I even got the stun working so happy. I think I remember now that ages ago I had a filled docker.img when it was small and had no idea what to do and so the next time just made it massive. I understand a bit better now. Host paths I just need to work out how I nuked my Nextcloud installation now and only get a 503 on the gui. Better go trawling the forum for that one.. Thanks for responding.

Hi I recently install Matrix and the admin and was trying to get the stun to work when i noticed that Matrix would no longer start. Uninstalled the app and reinstalled to no avail. Then I realizes that any new app that I installed will do the same immediate crash. I deleted the docker.img file and completely reinstalled all the apps from the templates. All the old ones before the problem arose will reinstall and work but again (except nextcloud but i'll work that one out later), but any new apps I install from now will never start. No error message popup, they just immediately close. This is really doing my head in, I cannot for the life of me work out why. Is there anyone out there much smarter than me that can take a look at the diagnostics and try and lend me a hand. Thank you tower-diagnostics-20230310-1555.zip

Hi all I would really love some help, or if anyone can help point me in the right direction. I have moved my plex server to my longstanding unraid srever but the media is still stored on another server (truenas). There are no problems accessing the media, transcoding etc but I've run into a dfs problem. I wanted to expand my media collection at the share level and keep it in a single share so set up a dfs root on the truenas server so that I now have a movies2 dfs symlink that points to a folder that is contained in another share. I know I could just add the additional share location as a mount point in the docker of plex but it annoys me that i cannot and the behavior is really weird. Using the file manager in unraid I can see the originial share (\\truenas\Media) with the dfs folder (\\truenas\Media\moves2) under it but cannot access inside it. I can even go to the actual share (\\truenas\media2) and see inside it and have full permissions when accessing the share directly from unraid. What is doing my head in is that it must be at least partially set up correctly on the truenas server as I can access the DFS share from a windows or mac machine with full access (authenticating as the same user as on unraid when creating the access to the remote share) but I cannot access it on unraid. If I try to access the folder via the unraid web gui it just shows as empty. If I ssh or terminal into unraid and navigate on the cli to the dfs share it will actually close and crash when trying to enter the dfs share. The permissions clearly indicate a possible problem that unraid has with the share but windows and mac do not. Unraid shows drwx--x--x on the dfs share. The direct share of the very same folder has drwxrwxrwx though? Does anyone have any ideas as to why unraid doesn't appear to like the dfs share (but can write into the share that the dfs symbolic link actually points to? I have given full access at the file level on the truenas sahre and file level. Cheers

Same here for over a week.

Would it be possible (unless it already is an I'm a big dufous and missed it) to be able to after searching and listing files from subdirectories using a wildcard search, then select them and do further actions with them like move, delete, copy etc. Cheers

Briliant, thanks bonienl works like a treat now I just checked..

Looks great. But is it possible to be able to move files to a share. I can only see individual disks. I would like to be able to select files from UDs and then move them to shares and then let Unraid do the splitting as per the high water settings for that share etc. Is that a possibility? Cheers

Hi people Looking for some help if possible please. If I move files in the GUI between folders, they always start immediately and not queue even those the queue button is selected in tools. I want to limit thrashing and slow transfers so want one at a time movement transfers. If I do it the manual f6-f2 way then it will queue it button I want to just drag and drop. Am I doing something wrong? Running latest binhex-krusader at the time of writing this and unraid 6.10.0-rc2 Apologies if this has been answered, I did do a search for the keyword queue in this topic. Cheers

I just realised the custom xml is overwritten every time i change something in the template so maybe I will have to go down your route.

yeah i hang ppretty much everyting off that controller and sas expander so that will be too difficult wihtout adding another hba. I'll have to tuse the serial xml instead which is enough for what I need. cheers again

actually I found a post somewhere else that references using <serial> in the xml and that has given me the opportunity to arbitrarily identify the disks with what serial I want which will definitely help me.. Cheers again for the hba isolation idea too though

hmm that's interesting. I dont have any space pci slots for another hba but I seem to recall a video where the card was stubbed out and then unstubbed after creation if my memory serves me correctly. Thanks I will investigate down this path.

Hi I have a number (8) of data prepopulated ntfs drives in Unassigned devices that I am pushing through to a VM by assigning them manually using by-id and passing through. It all works fine but for troubleshooting later I want to be able to see the serial number or other exact identifying way of which disk is which, not QM0001, 2 ,3 as the serial etc. The Disk Label is visible in the particular VM I am using which is helpful as I can see the old Drive name that it had in Windows but i'd really like to be able to see the actual disk id, especially as I wont be able to access the disk label if the drive dies. I've had a good look around but can't seem to locate the info I'm looking for. I feel like there might be something I can add to the xml in the form view of the VM that might get passed through and do what I want but don't have the knowledge or skill to work it out. Can anyone please point me in the right direction if this is at all possible. I am aware that if a disk failed I'd be able to see it in the actual unassigned devices section and work backwards but for my intentions I'd really love to ID my disks properly in the VM. Although I ran Unraid in a vm for ages in virualbox on a windows machine (to run pretty much one app) I've decided to use it properly now on baremetal and 'really' use it so I am still technically quite new to this so I apologies if I'm asking a stupid already answered question. Thank you

same issue here.

Let us know how you go.

Good point

Yeah I saw that one there but the SRAM bit scared me off of touching it I might give it a try, worst that can happen is it it won't boot I originally tried passing through the asmedia one in the last group as it appeared to be by itself but I might have done it wrong or ran into some other problem, I can't remember now. Thanks for the suggestions.

Yeah before I did the ACS overide the groups were in totally shocking massive groups. I really don't want any data errors so I think the hdmi audio extractor might be money well spent. What's a bit more $$ when i've spent this much on what I thought was going to be a great motherboard and is a iommu board from hell haha.. I know this is another topic but I've also great difficulty passing through a usb3.1 controller which this board must group all together. If I plug in a usb flash drive is it supposed to show up? I've managed to get it to add as a hard drive nut doesn't show up in disk management in Windows 10? Is this a limitation or am I just doing something wrong.

Thanks for the response Yeah that's exactly whats been happening. A reboot of the unraid server allowed the vm to start with no errors but on vm restart the errors occured as per other threads on the code 10 issue and the last two lines of the VM logs above. For some reason I thought it was the gpu audio in error state (but i think i had been looking at it too long and I was also having issues booting the vm at all if I did not have a monitor plugged into the onboard gpu (took me a while to work that one out unfortunately). I only enabled the onboard audio as I sometimes want the audio when the monitor is off and without an hdmi audio extractor the only way to do this was the onboard audio. Before I enabled the onboard audio I did not notice an errors so I have already done the limited pass through. Do you think I should pass through all the other items in that group? I wasn't sure what they all did.? I had no idea what I was getting into with this passthrough stuff when I started my unraid journey Cheers

Hi everyone I'm getting a code 10 with my Nvidia Audio (on the hdmi) on reboot of the VM. It is a GTX 1080ti Turbo. I've done a search and found a couple of similar articles with no real solution. I can't really move stuff around in the motherboard either so I'm kind of stuck with these iommu groups. I'm also very new to unraid. I've watched a LOT of videos, especially spaceinvaderone's which are awesome. I've tried isolating the devices with no luck. I'm running with q35 as I had graphcial glithes with the i440fx (white horizontal lines on the screeen and not redrawing using the i440fx). I've attach the syslinux config and the vm logs, the system devices and vm xml. Any suggestions would be awesome. Thanks in advance. System Devices IOMMU group 0: [8086:3e30] 00:00.0 Host bridge: Intel Corporation 8th Gen Core 8-core Desktop Processor Host Bridge/DRAM Registers [Coffee Lake S] (rev 0d) IOMMU group 1: [8086:1901] 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor PCIe Controller (x16) (rev 0d) IOMMU group 2: [8086:3e98] 00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 630 (Desktop 9 Series) (rev 02) IOMMU group 3: [8086:a36d] 00:14.0 USB controller: Intel Corporation Cannon Lake PCH USB 3.1 xHCI Host Controller (rev 10) [8086:a36f] 00:14.2 RAM memory: Intel Corporation Cannon Lake PCH Shared SRAM (rev 10) IOMMU group 4: [8086:a360] 00:16.0 Communication controller: Intel Corporation Cannon Lake PCH HECI Controller (rev 10) IOMMU group 5: [8086:a340] 00:1b.0 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port #17 (rev f0) IOMMU group 6: [8086:a338] 00:1c.0 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port #1 (rev f0) IOMMU group 7: [8086:a33e] 00:1c.6 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port #7 (rev f0) IOMMU group 8: [8086:a33f] 00:1c.7 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port #8 (rev f0) IOMMU group 9: [8086:a330] 00:1d.0 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port #9 (rev f0) IOMMU group 10: [8086:a305] 00:1f.0 ISA bridge: Intel Corporation Z390 Chipset LPC/eSPI Controller (rev 10) [8086:a348] 00:1f.3 Audio device: Intel Corporation Cannon Lake PCH cAVS (rev 10) [8086:a323] 00:1f.4 SMBus: Intel Corporation Cannon Lake PCH SMBus Controller (rev 10) [8086:a324] 00:1f.5 Serial bus controller [0c80]: Intel Corporation Cannon Lake PCH SPI Controller (rev 10) IOMMU group 11: [10b5:8747] 01:00.0 PCI bridge: PLX Technology, Inc. PEX 8747 48-Lane, 5-Port PCI Express Gen 3 (8.0 GT/s) Switch (rev ca) IOMMU group 12: [10b5:8747] 02:08.0 PCI bridge: PLX Technology, Inc. PEX 8747 48-Lane, 5-Port PCI Express Gen 3 (8.0 GT/s) Switch (rev ca) IOMMU group 13: [10b5:8747] 02:09.0 PCI bridge: PLX Technology, Inc. PEX 8747 48-Lane, 5-Port PCI Express Gen 3 (8.0 GT/s) Switch (rev ca) IOMMU group 14: [10b5:8747] 02:10.0 PCI bridge: PLX Technology, Inc. PEX 8747 48-Lane, 5-Port PCI Express Gen 3 (8.0 GT/s) Switch (rev ca) IOMMU group 15: [1000:0064] 05:00.0 Serial Attached SCSI controller: Broadcom / LSI SAS2116 PCI-Express Fusion-MPT SAS-2 [Meteor] (rev 02) IOMMU group 16: [1d6a:d107] 04:00.0 Ethernet controller: Aquantia Corp. AQC107 NBase-T/IEEE 802.3bz Ethernet Controller [AQtion] (rev 02) IOMMU group 17: [10de:1b06] 03:00.0 VGA compatible controller: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] (rev a1) IOMMU group 18: [10de:10ef] 03:00.1 Audio device: NVIDIA Corporation GP102 HDMI Audio Controller (rev a1) IOMMU group 19: [12d8:2304] 07:00.0 PCI bridge: Pericom Semiconductor PI7C9X2G304 EL/SL PCIe2 3-Port/4-Lane Packet Switch (rev 05) IOMMU group 20: [12d8:2304] 08:01.0 PCI bridge: Pericom Semiconductor PI7C9X2G304 EL/SL PCIe2 3-Port/4-Lane Packet Switch (rev 05) IOMMU group 21: [12d8:2304] 08:02.0 PCI bridge: Pericom Semiconductor PI7C9X2G304 EL/SL PCIe2 3-Port/4-Lane Packet Switch (rev 05) IOMMU group 22: [14f1:8880] 09:00.0 Multimedia video controller: Conexant Systems, Inc. CX23887/8 PCIe Broadcast Audio and Video Decoder with 3D Comb (rev 04) IOMMU group 23: [14f1:8880] 0a:00.0 Multimedia video controller: Conexant Systems, Inc. CX23887/8 PCIe Broadcast Audio and Video Decoder with 3D Comb (rev 04) IOMMU group 24: [1b21:1142] 0c:00.0 USB controller: ASMedia Technology Inc. ASM1042A USB 3.0 Host Controller Syslinux Configuration kernel /bzimage append pcie_acs_override=downstream,multifunction vfio-pci-ids=14f1:8880,1b21:1142,8086:a305,8086:a348,8086:a323,8086:a324,10de:1b06,10de:10ef initrd=/bzroot modprobe.blacklist=i2c_i801,i2c_smbus VM XML <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm' id='2'> <name>Home-2 v2</name> <uuid>032b0290-0434-055f-7d06-170700080009</uuid> <metadata> <vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/> </metadata> <memory unit='KiB'>45088768</memory> <currentMemory unit='KiB'>45088768</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>8</vcpu> <cputune> <vcpupin vcpu='0' cpuset='1'/> <vcpupin vcpu='1' cpuset='9'/> <vcpupin vcpu='2' cpuset='3'/> <vcpupin vcpu='3' cpuset='11'/> <vcpupin vcpu='4' cpuset='5'/> <vcpupin vcpu='5' cpuset='13'/> <vcpupin vcpu='6' cpuset='7'/> <vcpupin vcpu='7' cpuset='15'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-q35-4.1'>hvm</type> </os> <features> <acpi/> <apic/> <hyperv> <relaxed state='on'/> <vapic state='on'/> <spinlocks state='on' retries='8191'/> <vendor_id state='on' value='none'/> </hyperv> </features> <cpu mode='host-passthrough' check='none'> <topology sockets='1' cores='4' threads='2'/> </cpu> <clock offset='localtime'> <timer name='hypervclock' present='yes'/> <timer name='hpet' present='no'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/local/sbin/qemu</emulator> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/isos/virtio-win-0.1.160-1.iso'/> <backingStore/> <target dev='hdb' bus='sata'/> <readonly/> <alias name='sata0-0-1'/> <address type='drive' controller='0' bus='0' target='0' unit='1'/> </disk> <disk type='block' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source dev='/dev/disk/by-id/ata-SanDisk_SDSSDH32000G_19188F800825'/> <backingStore/> <target dev='hdc' bus='sata'/> <boot order='1'/> <alias name='sata0-0-2'/> <address type='drive' controller='0' bus='0' target='0' unit='2'/> </disk> <disk type='block' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source dev='/dev/disk/by-id/ata-ST4000DM004-2CV104_WFN1975M'/> <backingStore/> <target dev='hdd' bus='sata'/> <alias name='sata0-0-3'/> <address type='drive' controller='0' bus='0' target='0' unit='3'/> </disk> <disk type='block' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source dev='/dev/disk/by-id/ata-ST31000528AS_9VP4H0V2'/> <backingStore/> <target dev='hde' bus='sata'/> <alias name='sata0-0-4'/> <address type='drive' controller='0' bus='0' target='0' unit='4'/> </disk> <controller type='pci' index='0' model='pcie-root'> <alias name='pcie.0'/> </controller> <controller type='pci' index='1' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='1' port='0x8'/> <alias name='pci.1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0' multifunction='on'/> </controller> <controller type='pci' index='2' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='2' port='0x9'/> <alias name='pci.2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <controller type='pci' index='3' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='3' port='0xa'/> <alias name='pci.3'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/> </controller> <controller type='pci' index='4' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='4' port='0xb'/> <alias name='pci.4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x3'/> </controller> <controller type='pci' index='5' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='5' port='0xc'/> <alias name='pci.5'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x4'/> </controller> <controller type='pci' index='6' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='6' port='0xd'/> <alias name='pci.6'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x5'/> </controller> <controller type='pci' index='7' model='pcie-to-pci-bridge'> <model name='pcie-pci-bridge'/> <alias name='pci.7'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </controller> <controller type='pci' index='8' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='8' port='0xe'/> <alias name='pci.8'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x6'/> </controller> <controller type='virtio-serial' index='0'> <alias name='virtio-serial0'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/> </controller> <controller type='sata' index='0'> <alias name='ide'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/> </controller> <controller type='usb' index='0' model='qemu-xhci' ports='15'> <alias name='usb'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:8d:a4:44'/> <source bridge='br0'/> <target dev='vnet0'/> <model type='virtio'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </interface> <serial type='pty'> <source path='/dev/pts/0'/> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> <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/domain-2-Home-2 v2/org.qemu.guest_agent.0'/> <target type='virtio' name='org.qemu.guest_agent.0' state='disconnected'/> <alias name='channel0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='mouse' bus='ps2'> <alias name='input0'/> </input> <input type='keyboard' bus='ps2'> <alias name='input1'/> </input> <hostdev mode='subsystem' type='pci' managed='yes' xvga='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </source> <alias name='hostdev0'/> <rom file='/mnt/user/isos/gtx1080ti-turbo.rom'/> <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x03' slot='0x00' function='0x1'/> </source> <alias name='hostdev1'/> <address type='pci' domain='0x0000' bus='0x05' slot='0x00' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x00' slot='0x1f' function='0x3'/> </source> <alias name='hostdev2'/> <address type='pci' domain='0x0000' bus='0x07' slot='0x01' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x09' slot='0x00' function='0x0'/> </source> <alias name='hostdev3'/> <address type='pci' domain='0x0000' bus='0x06' slot='0x00' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x0a' slot='0x00' function='0x0'/> </source> <alias name='hostdev4'/> <address type='pci' domain='0x0000' bus='0x08' slot='0x00' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x046d'/> <product id='0xc246'/> <address bus='1' device='2'/> </source> <alias name='hostdev5'/> <address type='usb' bus='0' port='1'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x046d'/> <product id='0xc336'/> <address bus='1' device='3'/> </source> <alias name='hostdev6'/> <address type='usb' bus='0' port='2'/> </hostdev> <memballoon model='none'/> </devices> <seclabel type='dynamic' model='dac' relabel='yes'> <label>+0:+100</label> <imagelabel>+0:+100</imagelabel> </seclabel> </domain> VM Logs -no-shutdown \ -boot strict=on \ -device pcie-root-port,port=0x8,chassis=1,id=pci.1,bus=pcie.0,multifunction=on,addr=0x1 \ -device pcie-root-port,port=0x9,chassis=2,id=pci.2,bus=pcie.0,addr=0x1.0x1 \ -device pcie-root-port,port=0xa,chassis=3,id=pci.3,bus=pcie.0,addr=0x1.0x2 \ -device pcie-root-port,port=0xb,chassis=4,id=pci.4,bus=pcie.0,addr=0x1.0x3 \ -device pcie-root-port,port=0xc,chassis=5,id=pci.5,bus=pcie.0,addr=0x1.0x4 \ -device pcie-root-port,port=0xd,chassis=6,id=pci.6,bus=pcie.0,addr=0x1.0x5 \ -device pcie-pci-bridge,id=pci.7,bus=pci.1,addr=0x0 \ -device pcie-root-port,port=0xe,chassis=8,id=pci.8,bus=pcie.0,addr=0x1.0x6 \ -device qemu-xhci,p2=15,p3=15,id=usb,bus=pcie.0,addr=0x7 \ -device virtio-serial-pci,id=virtio-serial0,bus=pci.2,addr=0x0 \ -drive file=/mnt/user/isos/virtio-win-0.1.160-1.iso,format=raw,if=none,id=drive-sata0-0-1,readonly=on \ -device ide-cd,bus=ide.1,drive=drive-sata0-0-1,id=sata0-0-1 \ -drive file=/dev/disk/by-id/ata-SanDisk_SDSSDH32000G_19188F800825,format=raw,if=none,id=drive-sata0-0-2,cache=writeback \ -device ide-hd,bus=ide.2,drive=drive-sata0-0-2,id=sata0-0-2,bootindex=1,write-cache=on \ -drive file=/dev/disk/by-id/ata-ST4000DM004-2CV104_WFN1975M,format=raw,if=none,id=drive-sata0-0-3,cache=writeback \ -device ide-hd,bus=ide.3,drive=drive-sata0-0-3,id=sata0-0-3,write-cache=on \ -drive file=/dev/disk/by-id/ata-ST31000528AS_9VP4H0V2,format=raw,if=none,id=drive-sata0-0-4,cache=writeback \ -device ide-hd,bus=ide.4,drive=drive-sata0-0-4,id=sata0-0-4,write-cache=on \ -netdev tap,fd=36,id=hostnet0,vhost=on,vhostfd=37 \ -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:8d:a4:44,bus=pci.3,addr=0x0 \ -chardev pty,id=charserial0 \ -device isa-serial,chardev=charserial0,id=serial0 \ -chardev socket,id=charchannel0,fd=38,server,nowait \ -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 \ -device vfio-pci,host=0000:03:00.0,id=hostdev0,x-vga=on,bus=pci.4,addr=0x0,romfile=/mnt/user/isos/gtx1080ti-turbo.rom \ -device vfio-pci,host=0000:03:00.1,id=hostdev1,bus=pci.5,addr=0x0 \ -device vfio-pci,host=0000:00:1f.3,id=hostdev2,bus=pci.7,addr=0x1 \ -device vfio-pci,host=0000:09:00.0,id=hostdev3,bus=pci.6,addr=0x0 \ -device vfio-pci,host=0000:0a:00.0,id=hostdev4,bus=pci.8,addr=0x0 \ -device usb-host,hostbus=1,hostaddr=2,id=hostdev5,bus=usb.0,port=1 \ -device usb-host,hostbus=1,hostaddr=3,id=hostdev6,bus=usb.0,port=2 \ -sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny \ -msg timestamp=on 2020-01-06 07:19:26.709+0000: Domain id=2 is tainted: high-privileges 2020-01-06 07:19:26.709+0000: Domain id=2 is tainted: host-cpu char device redirected to /dev/pts/0 (label charserial0) 2020-01-06T07:19:32.285219Z qemu-system-x86_64: vfio: Cannot reset device 0000:00:1f.3, no available reset mechanism. 2020-01-06T07:19:35.408215Z qemu-system-x86_64: vfio: Cannot reset device 0000:00:1f.3, no available reset mechanism. Thanks tower-diagnostics-20200106-1547.zip

Thank you I will give it a try. Cheers again

Hi I would like to ask for support of the Edimax EN-9320TX-E 10GBe Nic in future Unraid builds. The chipset appears to be the Tehuti Networks Ltd. TN9710P 10GBase-T/NBASE-T Ethernet Adapter. I have attached a diagnostic. The card is recognised but does not enable or appear as an interface in network settings, only in System Devices. Many thanks and hopefully this is something you see fit to add Cheers alpha-diagnostics-20191209-2056.zip

ok thanks will do

Sorry, do I do that in feature requests?