boxtor

I'm following the steps of the guide and I'm getting an extra line added when I save the VM. I enter <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x00' slot='0x1f' function='0x6'/> </source> </hostdev> and it saves as <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x00' slot='0x1f' function='0x6'/> </source> <address type='pci' domain='0x0000' bus='0x07' slot='0x01' function='0x0'/> </hostdev> I'm trying to pass a i-219 onboard NIC to my VM. 00:00.0 Host bridge: Intel Corporation 10th Gen Core Processor Host Bridge/DRAM Registers (rev 03) 00:01.0 PCI bridge: Intel Corporation 6th-10th Gen Core Processor PCIe Controller (x16) (rev 03) 00:02.0 VGA compatible controller: Intel Corporation CometLake-S GT2 [UHD Graphics 630] (rev 03) 00:14.0 USB controller: Intel Corporation Tiger Lake-H USB 3.2 Gen 2x1 xHCI Host Controller (rev 11) 00:14.2 RAM memory: Intel Corporation Tiger Lake-H Shared SRAM (rev 11) 00:16.0 Communication controller: Intel Corporation Tiger Lake-H Management Engine Interface (rev 11) 00:17.0 SATA controller: Intel Corporation Device 43d2 (rev 11) 00:1c.0 PCI bridge: Intel Corporation Tiger Lake-H PCI Express Root Port #5 (rev 11) 00:1f.0 ISA bridge: Intel Corporation Device 4388 (rev 11) 00:1f.3 Audio device: Intel Corporation Device f0c8 (rev 11) 00:1f.4 SMBus: Intel Corporation Tiger Lake-H SMBus Controller (rev 11) 00:1f.5 Serial bus controller: Intel Corporation Tiger Lake-H SPI Controller (rev 11) 00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (14) I219-V (rev 11) 01:00.0 Ethernet controller: Mellanox Technologies MT27500 Family [ConnectX-3] 02:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM961/PM961/SM963 00:1f.6 0200: 8086:15fa (rev 11) It's being claimed by the stub when I boot up. Sep 17 15:26:41 Tower kernel: pci-stub: add 8086:15FA sub=FFFFFFFF:FFFFFFFF cls=00000000/00000000 Sep 17 15:26:41 Tower kernel: pci-stub 0000:00:1f.6: claimed by stub When I start the VM, it terminates due to group 7 not being viable. -blockdev '{"driver":"file","filename":"/mnt/user/domains/haos_ova-9.0.qcow2","node-name":"libvirt-1-storage","cache":{"direct":false,"no-flush":false},"auto-read-only":true,"discard":"unmap"}' \ -blockdev '{"node-name":"libvirt-1-format","read-only":false,"cache":{"direct":false,"no-flush":false},"driver":"qcow2","file":"libvirt-1-storage","backing":null}' \ -device virtio-blk-pci,bus=pci.3,addr=0x0,drive=libvirt-1-format,id=virtio-disk2,bootindex=1,write-cache=on \ -chardev pty,id=charserial0 \ -device isa-serial,chardev=charserial0,id=serial0,index=0 \ -chardev socket,id=charchannel0,fd=34,server=on,wait=off \ -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 \ -device usb-tablet,id=input0,bus=usb.0,port=1 \ -audiodev '{"id":"audio1","driver":"none"}' \ -vnc 0.0.0.0:0,websocket=5700,audiodev=audio1 \ -k en-us \ -device qxl-vga,id=video0,max_outputs=1,ram_size=67108864,vram_size=67108864,vram64_size_mb=0,vgamem_mb=16,bus=pcie.0,addr=0x1 \ -device usb-host,hostdevice=/dev/bus/usb/001/005,id=hostdev0,bus=usb.0,port=2 \ -device usb-host,hostdevice=/dev/bus/usb/001/004,id=hostdev1,bus=usb.0,port=3 \ -device vfio-pci,host=0000:00:1f.6,id=hostdev2,bus=pci.7,addr=0x1 \ -device virtio-balloon-pci,id=balloon0,bus=pci.4,addr=0x0 \ -sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny \ -msg timestamp=on char device redirected to /dev/pts/2 (label charserial0) qxl_send_events: spice-server bug: guest stopped, ignoring 2022-09-17T22:28:48.754730Z qemu-system-x86_64: -device vfio-pci,host=0000:00:1f.6,id=hostdev2,bus=pci.7,addr=0x1: vfio 0000:00:1f.6: group 7 is not viable Please ensure all devices within the iommu_group are bound to their vfio bus driver. 2022-09-17 22:28:49.243+0000: shutting down, reason=failed 2022-09-17 22:41:17.152+0000: starting up libvirt version: 8.2.0, qemu version: 6.2.0, kernel: 5.15.46-Unraid, hostname: Tower LC_ALL=C \ PATH=/bin:/sbin:/usr/bin:/usr/sbin \ HOME='/var/lib/libvirt/qemu/domain-3-Home Assistant' \ XDG_DATA_HOME='/var/lib/libvirt/qemu/domain-3-Home Assistant/.local/share' \ XDG_CACHE_HOME='/var/lib/libvirt/qemu/domain-3-Home Assistant/.cache' \ XDG_CONFIG_HOME='/var/lib/libvirt/qemu/domain-3-Home Assistant/.config' \ /usr/local/sbin/qemu \ -name 'guest=Home Assistant,debug-threads=on' \ -S \ -object '{"qom-type":"secret","id":"masterKey0","format":"raw","file":"/var/lib/libvirt/qemu/domain-3-Home Assistant/master-key.aes"}' \ -blockdev '{"driver":"file","filename":"/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd","node-name":"libvirt-pflash0-storage","auto-read-only":true,"discard":"unmap"}' \ -blockdev '{"node-name":"libvirt-pflash0-format","read-only":true,"driver":"raw","file":"libvirt-pflash0-storage"}' \ -blockdev '{"driver":"file","filename":"/etc/libvirt/qemu/nvram/daec4048-aab8-9201-ae0f-316786352df7_VARS-pure-efi.fd","node-name":"libvirt-pflash1-storage","auto-read-only":true,"discard":"unmap"}' \ -blockdev '{"node-name":"libvirt-pflash1-format","read-only":false,"driver":"raw","file":"libvirt-pflash1-storage"}' \ -machine pc-q35-6.2,usb=off,dump-guest-core=off,mem-merge=off,pflash0=libvirt-pflash0-format,pflash1=libvirt-pflash1-format,memory-backend=pc.ram \ -accel kvm \ -cpu host,migratable=on,host-cache-info=on,l3-cache=off \ -m 3072 \ -object '{"qom-type":"memory-backend-ram","id":"pc.ram","size":3221225472}' \ -overcommit mem-lock=off \ -smp 1,sockets=1,dies=1,cores=1,threads=1 \ -uuid daec4048-aab8-9201-ae0f-316786352df7 \ -no-user-config \ -nodefaults \ -chardev socket,id=charmonitor,fd=35,server=on,wait=off \ -mon chardev=charmonitor,id=monitor,mode=control \ -rtc base=utc,driftfix=slew \ -global kvm-pit.lost_tick_policy=delay \ -no-hpet \ -no-shutdown \ -boot strict=on \ -device pcie-root-port,port=16,chassis=1,id=pci.1,bus=pcie.0,multifunction=on,addr=0x2 \ -device pcie-root-port,port=17,chassis=2,id=pci.2,bus=pcie.0,addr=0x2.0x1 \ -device pcie-root-port,port=18,chassis=3,id=pci.3,bus=pcie.0,addr=0x2.0x2 \ -device pcie-root-port,port=19,chassis=4,id=pci.4,bus=pcie.0,addr=0x2.0x3 \ -device pcie-root-port,port=20,chassis=5,id=pci.5,bus=pcie.0,addr=0x2.0x4 \ -device pcie-root-port,port=21,chassis=6,id=pci.6,bus=pcie.0,addr=0x2.0x5 \ -device pcie-pci-bridge,id=pci.7,bus=pci.1,addr=0x0 \ -device ich9-usb-ehci1,id=usb,bus=pcie.0,addr=0x7.0x7 \ -device ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pcie.0,multifunction=on,addr=0x7 \ -device ich9-usb-uhci2,masterbus=usb.0,firstport=2,bus=pcie.0,addr=0x7.0x1 \ -device ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pcie.0,addr=0x7.0x2 \ -device virtio-serial-pci,id=virtio-serial0,bus=pci.2,addr=0x0 \ -blockdev '{"driver":"file","filename":"/mnt/user/domains/haos_ova-9.0.qcow2","node-name":"libvirt-1-storage","cache":{"direct":false,"no-flush":false},"auto-read-only":true,"discard":"unmap"}' \ -blockdev '{"node-name":"libvirt-1-format","read-only":false,"cache":{"direct":false,"no-flush":false},"driver":"qcow2","file":"libvirt-1-storage","backing":null}' \ -device virtio-blk-pci,bus=pci.3,addr=0x0,drive=libvirt-1-format,id=virtio-disk2,bootindex=1,write-cache=on \ -chardev pty,id=charserial0 \ -device isa-serial,chardev=charserial0,id=serial0,index=0 \ -chardev socket,id=charchannel0,fd=34,server=on,wait=off \ -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 \ -device usb-tablet,id=input0,bus=usb.0,port=1 \ -audiodev '{"id":"audio1","driver":"none"}' \ -vnc 0.0.0.0:0,websocket=5700,audiodev=audio1 \ -k en-us \ -device qxl-vga,id=video0,max_outputs=1,ram_size=67108864,vram_size=67108864,vram64_size_mb=0,vgamem_mb=16,bus=pcie.0,addr=0x1 \ -device usb-host,hostdevice=/dev/bus/usb/001/005,id=hostdev0,bus=usb.0,port=2 \ -device usb-host,hostdevice=/dev/bus/usb/001/004,id=hostdev1,bus=usb.0,port=3 \ -device vfio-pci,host=0000:00:1f.6,id=hostdev2,bus=pci.7,addr=0x1 \ -device virtio-balloon-pci,id=balloon0,bus=pci.4,addr=0x0 \ -sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny \ -msg timestamp=on char device redirected to /dev/pts/4 (label charserial0) qxl_send_events: spice-server bug: guest stopped, ignoring 2022-09-17T22:41:17.220002Z qemu-system-x86_64: -device vfio-pci,host=0000:00:1f.6,id=hostdev2,bus=pci.7,addr=0x1: vfio 0000:00:1f.6: group 7 is not viable Please ensure all devices within the iommu_group are bound to their vfio bus driver. 2022-09-17 22:41:17.709+0000: shutting down, reason=failed Group 7 has other devices within it. Sep 17 15:26:41 Tower kernel: pci 0000:00:1f.0: Adding to iommu group 7 Sep 17 15:26:41 Tower kernel: pci 0000:00:1f.3: Adding to iommu group 7 Sep 17 15:26:41 Tower kernel: pci 0000:00:1f.4: Adding to iommu group 7 Sep 17 15:26:41 Tower kernel: pci 0000:00:1f.5: Adding to iommu group 7 Sep 17 15:26:41 Tower kernel: pci 0000:00:1f.6: Adding to iommu group 7 Is there something else I need to do in this case? I would like to pass my onboard NIC to the VM so it can be on a separate VLAN and not have that VLAN access any exposed shares.

Bad RAM

I was preclearing a HDD at 95% of the zero'ing, when the UI became partially responsive. The dashboard wasn't updating properly and the Unassigned Devices widget on the main screen failed to refresh. I noticed the following in my logs and I'm wondering if I have a non-HDD component failing. I haven't tried any version before 6.10.3, since it's the first version I have installed recently. Eventually the UI started responding correctly. Sep 14 15:17:58 Tower kernel: BUG: Bad page map in process preclear_disk.s pte:8000000161454065 pmd:20a5c5067 Sep 14 15:17:58 Tower kernel: page:000000001e13fb34 refcount:1 mapcount:-1 mapping:00000000d4efed99 index:0xb pfn:0x161454 Sep 14 15:17:58 Tower kernel: memcg:ffff88810018a000 Sep 14 15:17:58 Tower kernel: aops:shmem_aops ino:76f dentry name:"libpam.so.0.85.1" Sep 14 15:17:58 Tower kernel: flags: 0x2ffff000008003e(referenced|uptodate|dirty|lru|active|swapbacked|node=0|zone=2|lastcpupid=0xffff) Sep 14 15:17:58 Tower kernel: raw: 02ffff000008003e ffffea0005851548 ffffea00058513c8 ffff88810720c1e8 Sep 14 15:17:58 Tower kernel: raw: 000000000000000b 0000000000000000 00000001fffffffe ffff88810018a000 Sep 14 15:17:58 Tower kernel: page dumped because: bad pte Sep 14 15:17:58 Tower kernel: addr:00000000007b7000 vm_flags:00100073 anon_vma:ffff8881c29084d0 mapping:0000000000000000 index:7b7 Sep 14 15:17:58 Tower kernel: file:(null) fault:0x0 mmap:0x0 readpage:0x0 Sep 14 15:17:58 Tower kernel: CPU: 2 PID: 11894 Comm: preclear_disk.s Tainted: G U 5.15.46-Unraid #1 Sep 14 15:17:58 Tower kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./H510M-ITX/ac, BIOS P1.60 04/15/2021 Sep 14 15:17:58 Tower kernel: Call Trace: Sep 14 15:17:58 Tower kernel: <TASK> Sep 14 15:17:58 Tower kernel: dump_stack_lvl+0x46/0x5a Sep 14 15:17:58 Tower kernel: print_bad_pte+0x1c2/0x1dc Sep 14 15:17:58 Tower kernel: unmap_page_range+0x45d/0x711 Sep 14 15:17:58 Tower kernel: unmap_vmas+0x6f/0x9d Sep 14 15:17:58 Tower kernel: exit_mmap+0xd6/0x145 Sep 14 15:17:58 Tower kernel: __mmput+0x43/0xd7 Sep 14 15:17:58 Tower kernel: do_exit+0x385/0x915 Sep 14 15:17:58 Tower kernel: do_group_exit+0x93/0x93 Sep 14 15:17:58 Tower kernel: get_signal+0x5d6/0x5fc Sep 14 15:17:58 Tower kernel: arch_do_signal_or_restart+0x39/0x6d0 Sep 14 15:17:58 Tower kernel: ? __do_sys_kill+0x4e/0x14a Sep 14 15:17:58 Tower kernel: exit_to_user_mode_prepare+0x79/0x131 Sep 14 15:17:58 Tower kernel: syscall_exit_to_user_mode+0x18/0x23 Sep 14 15:17:58 Tower kernel: do_syscall_64+0x9f/0xa5 Sep 14 15:17:58 Tower kernel: entry_SYSCALL_64_after_hwframe+0x44/0xae Sep 14 15:17:58 Tower kernel: RIP: 0033:0x14c43b13dae7 Sep 14 15:17:58 Tower kernel: Code: Unable to access opcode bytes at RIP 0x14c43b13dabd. Sep 14 15:17:58 Tower kernel: RSP: 002b:00007ffec529e928 EFLAGS: 00000202 ORIG_RAX: 000000000000003e Sep 14 15:17:58 Tower kernel: RAX: 0000000000000000 RBX: 000000000052a5e4 RCX: 000014c43b13dae7 Sep 14 15:17:58 Tower kernel: RDX: 00007ffec529e720 RSI: 000000000000000b RDI: 0000000000002e76 Sep 14 15:17:58 Tower kernel: RBP: 000000000000000b R08: 00007ffec529e870 R09: 0000000000000000 Sep 14 15:17:58 Tower kernel: R10: 0000000000000008 R11: 0000000000000202 R12: 00000000ffffffff Sep 14 15:17:58 Tower kernel: R13: 00000000ffffffff R14: 2520726f66206769 R15: 0000000000000000 Sep 14 15:17:58 Tower kernel: </TASK> Sep 14 15:17:58 Tower kernel: Disabling lock debugging due to kernel taint Sep 14 15:17:58 Tower kernel: BUG: Bad rss-counter state mm:00000000fd98fbe6 type:MM_ANONPAGES val:1 Sep 14 15:17:58 Tower kernel: BUG: Bad rss-counter state mm:00000000fd98fbe6 type:MM_SHMEMPAGES val:-1 Later, I keep getting the following spammed every 3 minutes. Sep 14 21:33:31 Tower kernel: rcu: INFO: rcu_sched self-detected stall on CPU Sep 14 21:33:31 Tower kernel: rcu: 7-....: (960014 ticks this GP) idle=765/1/0x4000000000000000 softirq=8501379/8501379 fqs=239808 Sep 14 21:33:31 Tower kernel: (t=960015 jiffies g=34023325 q=4927800) Sep 14 21:33:31 Tower kernel: NMI backtrace for cpu 7 Sep 14 21:33:31 Tower kernel: CPU: 7 PID: 24553 Comm: atd Tainted: G BU 5.15.46-Unraid #1 Sep 14 21:33:31 Tower kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./H510M-ITX/ac, BIOS P1.60 04/15/2021 Sep 14 21:33:31 Tower kernel: Call Trace: Sep 14 21:33:31 Tower kernel: <IRQ> Sep 14 21:33:31 Tower kernel: dump_stack_lvl+0x46/0x5a Sep 14 21:33:31 Tower kernel: nmi_cpu_backtrace+0xae/0xd2 Sep 14 21:33:31 Tower kernel: ? lapic_can_unplug_cpu+0x93/0x93 Sep 14 21:33:31 Tower kernel: nmi_trigger_cpumask_backtrace+0x56/0xd3 Sep 14 21:33:31 Tower kernel: rcu_dump_cpu_stacks+0xc3/0xea Sep 14 21:33:31 Tower kernel: rcu_sched_clock_irq+0x22d/0x631 Sep 14 21:33:31 Tower kernel: ? _raw_spin_unlock_irqrestore+0xe/0x1b Sep 14 21:33:31 Tower kernel: ? tick_sched_do_timer+0x3e/0x3e Sep 14 21:33:31 Tower kernel: update_process_times+0x8c/0xab Sep 14 21:33:31 Tower kernel: tick_sched_timer+0x38/0x65 Sep 14 21:33:31 Tower kernel: __hrtimer_run_queues+0xf8/0x18a Sep 14 21:33:31 Tower kernel: hrtimer_interrupt+0x92/0x160 Sep 14 21:33:31 Tower kernel: __sysvec_apic_timer_interrupt+0x96/0xdb Sep 14 21:33:31 Tower kernel: sysvec_apic_timer_interrupt+0x61/0x7d Sep 14 21:33:31 Tower kernel: </IRQ> Sep 14 21:33:31 Tower kernel: <TASK> Sep 14 21:33:31 Tower kernel: asm_sysvec_apic_timer_interrupt+0x12/0x20 Sep 14 21:33:31 Tower kernel: RIP: 0010:xa_is_node+0x17/0x1a Sep 14 21:33:31 Tower kernel: Code: 05 e8 ef c1 3d 00 48 83 c4 10 c3 c6 07 00 0f 1f 40 00 c3 48 89 f8 83 e0 03 48 83 f8 02 0f 94 c0 48 81 ff 00 10 00 00 0f 97 c2 <21> d0 c3 48 89 f8 83 e0 03 48 83 f8 02 0f 94 c0 48 81 ff fd 00 00 Sep 14 21:33:31 Tower kernel: RSP: 0018:ffffc90006defa08 EFLAGS: 00000286 Sep 14 21:33:31 Tower kernel: RAX: 0000000000000001 RBX: 0000000000000182 RCX: 0000000000000000 Sep 14 21:33:31 Tower kernel: RDX: 0000000000000001 RSI: ffffc90006defa20 RDI: ffff888101b74b6a Sep 14 21:33:31 Tower kernel: RBP: ffffea0005851500 R08: ffff888101b74b6a R09: 0000000000000001 Sep 14 21:33:31 Tower kernel: R10: ffffc90006defa20 R11: fefefefefefefeff R12: 0000000000000000 Sep 14 21:33:31 Tower kernel: R13: ffff88810720c1e8 R14: 000000000000000b R15: ffff88810720c1f0 Sep 14 21:33:31 Tower kernel: ? xas_start+0x6f/0xa7 Sep 14 21:33:31 Tower kernel: xas_load+0x13/0x39 Sep 14 21:33:31 Tower kernel: pagecache_get_page+0x72/0x1ff Sep 14 21:33:31 Tower kernel: shmem_getpage_gfp.constprop.0+0xd7/0x50f Sep 14 21:33:31 Tower kernel: shmem_fault+0x190/0x1ca Sep 14 21:33:31 Tower kernel: __do_fault+0x4b/0x69 Sep 14 21:33:31 Tower kernel: __handle_mm_fault+0x98a/0xc5c Sep 14 21:33:31 Tower kernel: handle_mm_fault+0x11c/0x1e2 Sep 14 21:33:31 Tower kernel: do_user_addr_fault+0x342/0x50b Sep 14 21:33:31 Tower kernel: exc_page_fault+0xe2/0x101 Sep 14 21:33:31 Tower kernel: asm_exc_page_fault+0x1e/0x30 Sep 14 21:33:31 Tower kernel: RIP: 0010:strncpy_from_user+0x87/0x10c Sep 14 21:33:31 Tower kernel: Code: 00 00 55 53 0f 01 cb 0f ae e8 48 bd ff fe fe fe fe fe fe fe 49 89 cb 48 b8 80 80 80 80 80 80 80 80 49 83 e3 f8 49 39 d3 74 52 <4c> 8b 14 17 49 8d 34 2a 4c 89 d3 48 f7 d3 48 21 de 49 8d 1c 11 48 Sep 14 21:33:31 Tower kernel: RSP: 0018:ffffc90006defdc8 EFLAGS: 00050202 Sep 14 21:33:31 Tower kernel: RAX: 8080808080808080 RBX: ffffc90006defe98 RCX: 0000000000000fe0 Sep 14 21:33:31 Tower kernel: RDX: 0000000000000000 RSI: 00007ffffffff000 RDI: 000014e8e450a8df Sep 14 21:33:31 Tower kernel: RBP: fefefefefefefeff R08: 0000000000000fe0 R09: ffff8881070bc020 Sep 14 21:33:31 Tower kernel: R10: 000014e8e450b8bf R11: 0000000000000fe0 R12: 0000000000000001 Sep 14 21:33:31 Tower kernel: R13: 000014e8e450a8df R14: 0000000000000000 R15: 0000000000000001 Sep 14 21:33:31 Tower kernel: getname_flags+0x49/0x150 Sep 14 21:33:31 Tower kernel: user_path_at_empty+0x23/0x50 Sep 14 21:33:31 Tower kernel: vfs_statx+0x75/0x108 Sep 14 21:33:31 Tower kernel: __do_sys_newfstatat+0x26/0x58 Sep 14 21:33:31 Tower kernel: ? handle_mm_fault+0x11c/0x1e2 Sep 14 21:33:31 Tower kernel: ? do_user_addr_fault+0x35c/0x50b Sep 14 21:33:31 Tower kernel: ? syscall_enter_from_user_mode+0x10/0x36 Sep 14 21:33:31 Tower kernel: do_syscall_64+0x80/0xa5 Sep 14 21:33:31 Tower kernel: entry_SYSCALL_64_after_hwframe+0x44/0xae Sep 14 21:33:31 Tower kernel: RIP: 0033:0x14e8e441ba2a Sep 14 21:33:31 Tower kernel: Code: 48 89 f2 b9 00 01 00 00 48 89 fe bf 9c ff ff ff e9 0b 00 00 00 66 2e 0f 1f 84 00 00 00 00 00 90 41 89 ca b8 06 01 00 00 0f 05 <3d> 00 f0 ff ff 77 07 31 c0 c3 0f 1f 40 00 48 8b 15 09 84 0d 00 f7 Sep 14 21:33:31 Tower kernel: RSP: 002b:00007ffc21babc88 EFLAGS: 00000246 ORIG_RAX: 0000000000000106 Sep 14 21:33:31 Tower kernel: RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 000014e8e441ba2a Sep 14 21:33:31 Tower kernel: RDX: 00007ffc21babcb0 RSI: 000014e8e450a8df RDI: 00000000ffffff9c Sep 14 21:33:31 Tower kernel: RBP: 0000000000409810 R08: 00000000004089e0 R09: 0000000000413f10 Sep 14 21:33:31 Tower kernel: R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 Sep 14 21:33:31 Tower kernel: R13: 00007ffc21babcb0 R14: 0000000000000000 R15: 0000000000409993 Sep 14 21:33:31 Tower kernel: </TASK>

Is there a specific model of Mellanox ConnectX-2 cards that is preferable for unRAID for 10 Gbe? I've seen multiple versions listed and I want to get the correct type. I intend to do a direct connect between 2 cards. Is there a specific model for of the 2 port version of the card that works well in case I decide to do this with 2 client PCs?

Bridge mode solved it. TYVM.

I think I'm missing something. While following the instructions, I set the port to an unused port and changed the directories. I also had to edit the WebUI string since it was still pointed at 8096. I attached a screen shot of the settings. The instance always fails at start up since it's still trying to use {"EnableUPnP":true,"PublicPort":8096,"PublicHttpsPort":8920,"HttpServerPortNumber":8096,"HttpsPortNumber":8920, And 8096 is already in use. The only way I've successfully used the new instance is to shutdown the original and leave the port at 8096. I was able to get to the set up wizard.

How do I create a separate instance of an Emby docker running with a different /config directory and network port? I tried using Community Applications to add another instance, but it updated the pre-existing instance. I had the revert the changes in the pre-existing instance in order to connect to it again. Why would I do this? It's Emby's recommendation to do this if you have content you don't want everyone to see.

I ran into the same behavior today with 6.1.9. I started a parity rebuild a removing a drive. When the main page reloaded, the icons for parity (orange triangle) and circles for the data disks were not displayed. When I attempted to refresh the page, it wouldn't load. However, I also could not connect using SSH. I was able to log in using a keyboard and the rebuild was still in process and the array was mounted fine (/mnt/user was populated). After a few minutes, both the GUI and SSH became responsive.

Is there a way to prevent the mover from moving files to a specific drive? In my case, I have shares that use a SMR drive. Since the files could of be questionable quality (and therefore replaced with a better quality version in the future) I would rather mover did not write to that (or multiple drives) and instead write the files to my PMR drives. I'll manually move files to the appropriate disk when I deem the files worthy.

There is the Norco RPM-4308 rackmount case with 8 hot swap trays. It's short depth.

http://sqlitebrowser.org/ I use the Windows version for updating the Plex database as needed. It would be nice to have a Docker version on the server.

I have a question related to removing a drive I'm not going to replace. My Seagate 8TB NAS drive is too loud for my taste with its constant high pitched humming. The desktop version doesn't have this problem. The drive is blank. All I've done is format the disk and run the SMART tests. I am running version 6.1.8. I've looked at the wiki and I would like to know if these are the steps I should follow. After stopping the array, powering down, removing the drive, and powering back on, 1) Perform a new config. At this point do I click Apply or Done? 2) Assign the parity 3) Assign the data drives 4) Start the array

I have a disk that developed a SMART error (198 Offline uncorrectable raw value=1). It will be empty by the time I replace it this week (I'm moving the files from /mnt/disk2 to my other data disks). I will be replacing it with a different brand disk (replacing 4TB WD with a 4TB Seagate). When looking at the Official Documentation on the Wiki, it has a section for replacing a failed disk. Is this the instructions to follow even though my disk was not red balled? Or should I be using New Configuration? If so, is there any documentation on this? The Wiki doesn't appear to cover it except to say to use it. The drive I'm replacing should be empty by that time, so there won't be any contents. I'm using version 6.1.8.

Another one that works with non-ECC memory is http://www.asrockrack.com/general/productdetail.asp?Model=E3C226D2I#Memory

I use http://www.asrockrack.com/general/productdetail.asp?Model=E3C224D4I-14S#Specifications You can choose which ever CPU meets your criteria.

I am interested in this too.

I use the E3C224D4I-14S, works great.

If you do decide to flash the IPMI and LSI, be sure to understand the instructions thoroughly. IIRC, there was some outdated information with updating the IPMI.

I'd like a docker for a anti-virus package to scan files for Windows threats. I think ClamAV or the free license of BitDefender for Linux would work.

In Tools, there is a Processes option. I look for a line such as root 25982 1611 0 23:27 ? 00:00:00 sshd: root@pts/0 to determine if there is a terminal open. I've also had an array fail to shutdown when Docker wouldn't shutdown properly. I forget what I was doing to cause that.

You need to exit your SSH/telnet when stopping the array.

I've searched the wiki and forum, but I have a couple questions related to changing my cache drive. 1) Do I need to preclear an SSD? 2) On /mnt/cache/AppData, there are a docker image, config.json, and a directory related to plex. The only thing I need to copy off the drive is the plex directory since both the docker image and the config file (it looks like it has stock values) should be recreated on the new SSD?

You can swap the fans out. I replaced them with Noctua fans. There is also an optional fan wall to use 3x 120 mm fans instead of 4x smaller fans. http://www.ipcdirect.net/120mm-fan-wall-bracket-for-rpc-4224-rpc-4220-rpc-4216-rpc-4116-rpc-4020-rpc-4164/

Thanks for the help. The transition went relatively smooth.

I'm creating a second unRAID server, but I intend to use the drives in the old server. This will be using a new cache drive and USB stick (I bought the cheap 2nd license). To use the existing drives with existing data on the new server, all I would need to do is create the initial config where the parity drive is mapped to the existing parity drive and all the data drives are included? Note: I'm backing up the data before moving to the new server.