Cael817

Thank you @JorgeB, just a note, i got the message upgrading from 6.12.4 so that got me a bit confused. Thanks again.

Hi, I went to upgrade and got this message during the tests "Checking for tg3 driver and IOMMU enabled Issue Found: It appears that you have an ethernet adapter using the tg3 driver and IOMMU enabled. This combination has been found to potentially cause serious data corruption issues. Disable IOMMU in the BIOS" I found this thread With the same issue and i also cannot find a way to disable IOMMU in the bios of the R720xd server I'm using. Is this still an issue or is it solved in 6.10.3 as that thread indicates? For now i only use the Broadcom card that seems to use that driver as a backup and i don't have any VMs passed to a physical NIC. If necessary, will it help if i remove the NIC as backup? Thanks

Crap, genuinely sorry. I completely forgot about this when i got some cool suff for my 3D printer build. Anyway, i don't remember doing anything special, heres a screen with eth1 removed from the bond And here's when re adding it Now, i have to admit that i have not tested if the backup is working but im going to pull the 10GB in a few minutes and see what happens 😃 Few minutes later, failover worked

I hope this is of some help, it was about a year ago i fiddled with this, these are my settings (starting to think that having a 1GBe as backup may hurt my performance but im not sure, system is up so my settings don't seem to show the same screen as yours but i can stop my VMs tomorrow if you need better screens). This is the cables i bought from fs.com Im not sure i explained my connections thoroughly and im not sure this will help but.. Wan is connected to a pfSense box with 1GBe fiber, pfSense box has one one the Mellanox cards and a 1GBe SFP in the Wan port, The second (LAN) port has one of the DAC cables connecting to my switch (Cisco, that's why i bought a Cisco coded cable, i think you can disable the check but price was low and id didn't want to screw around with that, fortunately the Mellanox card didn't complain (and shouldn't to my understanding)), Then from the switch i have the other DAC cable connected to my Unraid and eth0 using the other Mellanox card (second SFP port on this Mellanox card is unused).

Good news, changing the PCIe port worked. This is a Dell R720xd and i had the Mellanox card in riser 2, slot 5 which indicates that its connected to CPU 1. Moved it around to riser 1, slot 3 and that slot says CPU 2. Show right up after starting the server, set it to 'eth0' and did a restart and viola, everything works. Thanks @JorgeB.

Hi all, Recently bought a couple of Mellanox MCX312B-XCCT CX312B, these are dual ports and one is used for connecting a pfsense box between WAN and LAN (1G SFP on the WAN side and a 10G SFP+ DAC cable on the LAN side). The other i put in my Unraid box (One port unused and one connected to LAN with a 10G SFP+ DAC) but it won't show up in the list of NICs in the "/Settings/NetworkSettings -> Interface Rules and the drop down lists. Checking the logs gives me these warnings and "0000:04:00.0" being my Mellanox card indicates that everything is not all right. Jan 22 19:39:48 Tower kernel: ACPI: Early table checksum verification disabled Jan 22 19:39:48 Tower kernel: pci 0000:04:00.0: BAR 9: failed to assign [mem size 0x04000000 64bit pref] Jan 22 19:39:48 Tower kernel: floppy0: no floppy controllers found Jan 22 19:39:48 Tower kernel: ACPI Error: No handler for Region [SYSI] (000000001bc0de87) [IPMI] (20220331/evregion-130) Jan 22 19:39:48 Tower kernel: ACPI Error: Region IPMI (ID=7) has no handler (20220331/exfldio-261) Jan 22 19:39:48 Tower kernel: ACPI Error: Aborting method \_SB.PMI0._GHL due to previous error (AE_NOT_EXIST) (20220331/psparse-529) Jan 22 19:39:48 Tower kernel: ACPI Error: Aborting method \_SB.PMI0._PMC due to previous error (AE_NOT_EXIST) (20220331/psparse-529) Jan 22 19:39:48 Tower kernel: ACPI: \_SB_.PMI0: _PMC evaluation failed: AE_NOT_EXIST Jan 22 19:39:48 Tower kernel: mlx4_core 0000:04:00.0: Failed to initialize queue pair table, aborting Jan 22 19:39:48 Tower kernel: mlx4_core: probe of 0000:04:00.0 failed with error -5 Jan 22 19:52:02 Tower root: Fix Common Problems: Warning: Deprecated plugin ca.backup2.plg Jan 22 19:52:08 Tower root: Fix Common Problems: Other Warning: dynamix.file.manager Support Updated I have updated the FW to the latest i could find "2.42.5000" but i have the error/issue. I have also deleted network-rules.cfg and network.cfg and rebooted but no dice. The two cards i have have been swapped around between the pfsense box and the unraid one where both worked as intended in pfsense. Last idea i have right now is to swap in the card in another PCIe port but wanted to ask here first. Bit of googeling on "mlx4_core 0000:04:00.0: Failed to initialize queue pair table, aborting" but that doesn't seem like something 'i' can configure? https://support.mellanox.com/s/article/MLNX2-117-2389kn Someone have any good ideas? tower-diagnostics-20230122-2125.zip

Wrote a long thank you and i pressed "Mark as solution" to your post and all my text vanished =). Anyway. Thank you again, Funny thing is that after i made the change to cqow2 i got the same result and landed in UEFI Interactive Shell and "No mapping found". On a hunch i also changed bus form SCSI to VirtIO which led to a boot into 'Windows recovery" something something, and an inaccessible boot device. I shut it down and changed it back to SCSI and thought why not try another start and behold, it booted normally I've done 5-6 restart and everything seems to work fine with no abnormal errors so far. Thanks, you probably saved me a lot of time recreating this machine, don't know why the shift between SCSI and VirtIO did anything, i was probably just impatient.

Thank you @ghost82, Looks like qcow2... root@Tower:~# fdisk -l /mnt/user/domains/ws_2019_1/vdisk1.img Disk /mnt/user/domains/ws_2019_1/vdisk1.img: 21.04 GiB, 22596419584 bytes, 44133632 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes root@Tower:~# qemu-img info /mnt/user/domains/ws_2019_1/vdisk1.img image: /mnt/user/domains/ws_2019_1/vdisk1.img file format: qcow2 virtual size: 30 GiB (32212254720 bytes) disk size: 21 GiB cluster_size: 65536 Format specific information: compat: 1.1 compression type: zlib lazy refcounts: false refcount bits: 16 corrupt: false root@Tower:~#

Hi, I just got an issue where one of my VMs wont start after it got an update. I applied the update from within the VM (ws_2019_1) and it prompted a restart, afterwards it just lands in UEFI shell and it looks to me like the drive isn't registered, at all. Prior to the restart(months before) i did a cleanup of folders and files and the windows installation ISO and the VirtIO ISO was mapped to a place that doesn't exist anymore (was "/mnt/user/isos/template/iso/" and is now "/mnt/user/isos/") and i did get some error pop up regarding something like that, being an idiot i didn't take note so i cannot tell what the error said before i clicked away. I removed the paths to the mentioned ISOs (i also did this for another VM (ws_2019-_2) which seems fine but the config is a bit different). I see the 'old' path to the windows installation ISO in the qemu diagnostic file for this VM /qemu/ws_2019_1.txt Also, i may have screwed around with the disk settings for the vdisk1.img trying to resolve this myself. Is this recoverable? Thanks for any ideas 😃 <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm' id='5'> <name>ws_2019_1</name> <uuid>20524a83-cbbe-b4d2-cf94-55d1a7a58267</uuid> <description>ws-dc-p</description> <metadata> <vmtemplate xmlns="unraid" name="Windows Server 2016" icon="windows.png" os="windows2016"/> </metadata> <memory unit='KiB'>8388608</memory> <currentMemory unit='KiB'>8388608</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>4</vcpu> <cputune> <vcpupin vcpu='0' cpuset='1'/> <vcpupin vcpu='1' cpuset='21'/> <vcpupin vcpu='2' cpuset='2'/> <vcpupin vcpu='3' cpuset='22'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-q35-5.1'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/20524a83-cbbe-b4d2-cf94-55d1a7a58267_VARS-pure-efi.fd</nvram> </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' migratable='on'> <topology sockets='1' dies='1' cores='2' threads='2'/> <cache mode='passthrough'/> </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='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/user/domains/ws_2019_1/vdisk1.img' index='1'/> <backingStore/> <target dev='hdc' bus='scsi'/> <boot order='1'/> <alias name='scsi0-0-0-2'/> <address type='drive' controller='0' bus='0' target='0' unit='2'/> </disk> <controller type='scsi' index='0' model='virtio-scsi'> <alias name='scsi0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x2'/> </controller> <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='0x10'/> <alias name='pci.1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0' multifunction='on'/> </controller> <controller type='pci' index='2' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='2' port='0x11'/> <alias name='pci.2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x1'/> </controller> <controller type='pci' index='3' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='3' port='0x12'/> <alias name='pci.3'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x2'/> </controller> <controller type='pci' index='4' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='4' port='0x1b'/> <alias name='pci.4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x3'/> </controller> <controller type='pci' index='5' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='5' port='0x14'/> <alias name='pci.5'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x4'/> </controller> <controller type='virtio-serial' index='0'> <alias name='virtio-serial0'/> <address type='pci' domain='0x0000' bus='0x03' 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='ich9-ehci1'> <alias name='usb'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <alias name='usb'/> <master startport='0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0' multifunction='on'/> </controller> <controller type='usb' index='0' model='ich9-uhci2'> <alias name='usb'/> <master startport='2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/> </controller> <controller type='usb' index='0' model='ich9-uhci3'> <alias name='usb'/> <master startport='4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/> </controller> <interface type='bridge'> <mac address='52:54:00:47:7a:b5'/> <source bridge='br0'/> <target dev='vnet2'/> <model type='virtio-net'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </interface> <serial type='pty'> <source path='/dev/pts/2'/> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> <alias name='serial0'/> </serial> <console type='pty' tty='/dev/pts/2'> <source path='/dev/pts/2'/> <target type='serial' port='0'/> <alias name='serial0'/> </console> <channel type='unix'> <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/domain-5-ws_2019_1/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='tablet' bus='usb'> <alias name='input0'/> <address type='usb' bus='0' port='1'/> </input> <input type='mouse' bus='ps2'> <alias name='input1'/> </input> <input type='keyboard' bus='ps2'> <alias name='input2'/> </input> <graphics type='vnc' port='5902' autoport='yes' websocket='5702' listen='0.0.0.0' keymap='sv'> <listen type='address' address='0.0.0.0'/> </graphics> <video> <model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1' primary='yes'/> <alias name='video0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0'/> </video> <memballoon model='virtio'> <alias name='balloon0'/> <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0'/> </memballoon> </devices> <seclabel type='dynamic' model='dac' relabel='yes'> <label>+0:+100</label> <imagelabel>+0:+100</imagelabel> </seclabel> </domain> tower-diagnostics-20220501-1800.zip