Yeti Feet

If USB stick is the norm then so be it. What tool, system config or other would allow me to cleanly install 7.0.1? I've been upgrading for several years now and the accumulation of deprecated installs is clearly cluttered on my end. I would prefer to keep my data.

My unraid is unfortunately on a USB stick attached to USB 2.0. I bought an SSD and I want to reinstall UNRAID there. I do not know if I will lose all my data on my HD's or whether UNRAID will somehow check that I have data on my HD's and basically just restore the main OS (unraid) and intelligently restore my server with all data. I paid pro for the USB (Registered USB Flash GUID) but if re-install unraid then I am changing hardware and pro will be disabled. My unraid config is just cluttered with multiple configs over the years and I would like a fresh start with 7.0.1. However, I do not know if I can just tell the new install: 'here... use these 2 disks as parity and the rest as my data.. oh .. and use this NVME as cache'. any input would be appreciated.

Frankly, there is something with the VIDEO output and/or USB. Per the USB manager it found the Bluetooth but I cannot "VM attach" the Generic 4 port USB 3.0 hub. I think I will forgo using a VM at all with a dedicated GPU - not worth the trouble. I cant seem to find any sort of error or warning that something failed in the output (video/keyboard/mouse). After I rebooted the server, when I switch to HDMI port 2, I do not see anything.. blank screen. (VM works ok via VNC ok mouse/keyboard ok)

Here are all groups which shows (42) can be RESET ok: Now I did try to put my mouse and keyboard at the back of the server on group 25 but still same error (no mouse/keyboard activity). The KVM switch is a USB-to-USB block (4 USB ports at the back where one USB cable will connnect to the desired entity; the 4 front USB's is where I plug in my keyboard, mouse and camera) IOMMU group 55 c0:05.2 System peripheral [0880]: Intel Corporation Sky Lake-E RAS Configuration Registers [8086:2035] (rev 04) IOMMU group 83 e0:05.0 System peripheral [0880]: Intel Corporation Sky Lake-E VT-d [8086:2034] (rev 04) IOMMU group 17 00:04.6 System peripheral [0880]: Intel Corporation Sky Lake-E CBDMA Registers [8086:2021] (rev 04) IOMMU group 45 a0:05.4 PIC [0800]: Intel Corporation Sky Lake-E IOxAPIC Configuration Registers [8086:2036] (rev 04) IOMMU group 73 c0:0c.2 System peripheral [0880]: Intel Corporation Sky Lake-E Integrated Memory Controller [8086:2042] (rev 04) IOMMU group 35 00:1f.0 ISA bridge [0601]: Intel Corporation X299 Chipset LPC/eSPI Controller [8086:a2d2] 00:1f.2 Memory controller [0580]: Intel Corporation 200 Series/Z370 Chipset Family Power Management Controller [8086:a2a1] 00:1f.3 Audio device [0403]: Intel Corporation 200 Series PCH HD Audio [8086:a2f0] 00:1f.4 SMBus [0c05]: Intel Corporation 200 Series/Z370 Chipset Family SMBus Controller [8086:a2a3] IOMMU group 7 a0:01.0 PCI bridge [0604]: Intel Corporation Sky Lake-E PCI Express Root Port B [8086:2031] (rev 04) IOMMU group 63 c0:0a.4 System peripheral [0880]: Intel Corporation Sky Lake-E Integrated Memory Controller [8086:2044] (rev 04) IOMMU group 25 00:14.0 USB controller [0c03]: Intel Corporation 200 Series/Z370 Chipset Family USB 3.0 xHCI Controller [8086:a2af] IOMMU group 53 a0:1e.0 System peripheral [0880]: Intel Corporation Sky Lake-E PCU Registers [8086:2080] (rev 04) a0:1e.1 System peripheral [0880]: Intel Corporation Sky Lake-E PCU Registers [8086:2081] (rev 04) a0:1e.2 System peripheral [0880]: Intel Corporation Sky Lake-E PCU Registers [8086:2082] (rev 04) a0:1e.3 System peripheral [0880]: Intel Corporation Sky Lake-E PCU Registers [8086:2083] (rev 04) a0:1e.4 System peripheral [0880]: Intel Corporation Sky Lake-E PCU Registers [8086:2084] (rev 04) a0:1e.5 System peripheral [0880]: Intel Corporation Sky Lake-E PCU Registers [8086:2085] (rev 04) a0:1e.6 System peripheral [0880]: Intel Corporation Sky Lake-E PCU Registers [8086:2086] (rev 04) IOMMU group 81 c0:0d.2 System peripheral [0880]: Intel Corporation Sky Lake-E LMS Channel 2 [8086:204a] (rev 04) IOMMU group 15 00:04.4 System peripheral [0880]: Intel Corporation Sky Lake-E CBDMA Registers [8086:2021] (rev 04) IOMMU group 43 a0:05.0 System peripheral [0880]: Intel Corporation Sky Lake-E VT-d [8086:2034] (rev 04) IOMMU group 71 c0:0c.0 System peripheral [0880]: Intel Corporation Sky Lake-E Integrated Memory Controller [8086:2040] (rev 04) IOMMU group 33 [RESET] 00:1d.0 PCI bridge [0604]: Intel Corporation 200 Series PCH PCI Express Root Port #9 [8086:a298] (rev f0) IOMMU group 5 c0:00.0 PCI bridge [0604]: Intel Corporation Sky Lake-E PCI Express Root Port A [8086:2030] (rev 04) IOMMU group 61 c0:0a.2 System peripheral [0880]: Intel Corporation Sky Lake-E Integrated Memory Controller [8086:2042] (rev 04) IOMMU group 23 00:08.1 Performance counters [1101]: Intel Corporation Sky Lake-E Ubox Registers [8086:2015] (rev 04) IOMMU group 51 a0:10.0 System peripheral [0880]: Intel Corporation Sky Lake-E CHA Registers [8086:208e] (rev 04) a0:10.1 System peripheral [0880]: Intel Corporation Sky Lake-E CHA Registers [8086:208e] (rev 04) IOMMU group 13 00:04.2 System peripheral [0880]: Intel Corporation Sky Lake-E CBDMA Registers [8086:2021] (rev 04) IOMMU group 41 [RESET] 47:00.0 Non-Volatile memory controller [0108]: Phison Electronics Corporation E12 NVMe Controller [1987:5012] (rev 01) IOMMU group 31 [RESET] 00:1c.2 PCI bridge [0604]: Intel Corporation 200 Series PCH PCI Express Root Port #3 [8086:a292] (rev f0) IOMMU group 3 [RESET] e1:00.2 Ethernet controller [0200]: Intel Corporation I350 Gigabit Network Connection [8086:1521] (rev 01) IOMMU group 88 e0:15.0 System peripheral [0880]: Intel Corporation Sky Lake-E M2PCI Registers [8086:2018] (rev 04) IOMMU group 21 00:05.4 PIC [0800]: Intel Corporation Sky Lake-E IOAPIC [8086:2026] (rev 04) IOMMU group 78 c0:0c.7 System peripheral [0880]: Intel Corporation Sky Lake-E LMDP Channel 1 [8086:2047] (rev 04) IOMMU group 11 00:04.0 System peripheral [0880]: Intel Corporation Sky Lake-E CBDMA Registers [8086:2021] (rev 04) IOMMU group 68 c0:0b.1 System peripheral [0880]: Intel Corporation Sky Lake-E LM Channel 2 [8086:2049] (rev 04) IOMMU group 1 [RESET] e1:00.0 Ethernet controller [0200]: Intel Corporation I350 Gigabit Network Connection [8086:1521] (rev 01) IOMMU group 58 c0:09.0 System peripheral [0880]: Intel Corporation Sky Lake-E Integrated Memory Controller [8086:2066] (rev 04) IOMMU group 86 e0:12.0 Performance counters [1101]: Intel Corporation Sky Lake-E M3KTI Registers [8086:204c] (rev 04) IOMMU group 48 a0:0a.0 System peripheral [0880]: Intel Corporation Sky Lake-E CHA Registers [8086:208d] (rev 04) a0:0a.1 System peripheral [0880]: Intel Corporation Sky Lake-E CHA Registers [8086:208d] (rev 04) IOMMU group 76 c0:0c.5 System peripheral [0880]: Intel Corporation Sky Lake-E LM Channel 1 [8086:2045] (rev 04) IOMMU group 38 [RESET] 02:00.0 Network controller [0280]: Intel Corporation Wireless 8265 / 8275 [8086:24fd] (rev 78) IOMMU group 66 c0:0a.7 System peripheral [0880]: Intel Corporation Sky Lake-E LMDP Channel 1 [8086:2047] (rev 04) IOMMU group 28 [RESET] 00:1b.0 PCI bridge [0604]: Intel Corporation 200 Series PCH PCI Express Root Port #17 [8086:a2e7] (rev f0) IOMMU group 56 c0:05.4 PIC [0800]: Intel Corporation Sky Lake-E IOxAPIC Configuration Registers [8086:2036] (rev 04) IOMMU group 84 e0:05.2 System peripheral [0880]: Intel Corporation Sky Lake-E RAS Configuration Registers [8086:2035] (rev 04) IOMMU group 18 00:04.7 System peripheral [0880]: Intel Corporation Sky Lake-E CBDMA Registers [8086:2021] (rev 04) IOMMU group 46 a0:08.0 System peripheral [0880]: Intel Corporation Sky Lake-E CHA Registers [8086:208d] (rev 04) a0:08.1 System peripheral [0880]: Intel Corporation Sky Lake-E CHA Registers [8086:208d] (rev 04) a0:08.2 System peripheral [0880]: Intel Corporation Sky Lake-E CHA Registers [8086:208d] (rev 04) a0:08.3 System peripheral [0880]: Intel Corporation Sky Lake-E CHA Registers [8086:208d] (rev 04) a0:08.4 System peripheral [0880]: Intel Corporation Sky Lake-E CHA Registers [8086:208d] (rev 04) a0:08.5 System peripheral [0880]: Intel Corporation Sky Lake-E CHA Registers [8086:208d] (rev 04) a0:08.6 System peripheral [0880]: Intel Corporation Sky Lake-E CHA Registers [8086:208d] (rev 04) a0:08.7 System peripheral [0880]: Intel Corporation Sky Lake-E CHA Registers [8086:208d] (rev 04) IOMMU group 74 c0:0c.3 System peripheral [0880]: Intel Corporation Sky Lake-E Integrated Memory Controller [8086:2043] (rev 04) IOMMU group 36 [RESET] 00:1f.6 Ethernet controller [0200]: Intel Corporation Ethernet Connection (2) I219-V [8086:15b8] IOMMU group 8 [RESET] a1:00.0 VGA compatible controller [0300]: NVIDIA Corporation GK208B [GeForce GT 710] [10de:128b] (rev a1) IOMMU group 64 c0:0a.5 System peripheral [0880]: Intel Corporation Sky Lake-E LM Channel 1 [8086:2045] (rev 04) IOMMU group 26 00:16.0 Communication controller [0780]: Intel Corporation 200 Series PCH CSME HECI #1 [8086:a2ba] IOMMU group 54 c0:05.0 System peripheral [0880]: Intel Corporation Sky Lake-E VT-d [8086:2034] (rev 04) IOMMU group 82 c0:0d.3 System peripheral [0880]: Intel Corporation Sky Lake-E LMDP Channel 2 [8086:204b] (rev 04) IOMMU group 16 00:04.5 System peripheral [0880]: Intel Corporation Sky Lake-E CBDMA Registers [8086:2021] (rev 04) IOMMU group 44 a0:05.2 System peripheral [0880]: Intel Corporation Sky Lake-E RAS Configuration Registers [8086:2035] (rev 04) IOMMU group 72 c0:0c.1 System peripheral [0880]: Intel Corporation Sky Lake-E Integrated Memory Controller [8086:2041] (rev 04) IOMMU group 34 [RESET] 00:1d.4 PCI bridge [0604]: Intel Corporation 200 Series PCH PCI Express Root Port #13 [8086:a29c] (rev f0) IOMMU group 6 [RESET] c1:00.0 Serial Attached SCSI controller [0107]: Broadcom / LSI MegaRAID SAS-3 3108 [Invader] [1000:005d] (rev 02) IOMMU group 62 c0:0a.3 System peripheral [0880]: Intel Corporation Sky Lake-E Integrated Memory Controller [8086:2043] (rev 04) IOMMU group 90 e0:17.0 System peripheral [0880]: Intel Corporation Sky Lake-E M2PCI Registers [8086:2018] (rev 04) IOMMU group 24 00:08.2 System peripheral [0880]: Intel Corporation Sky Lake-E Ubox Registers [8086:2016] (rev 04) IOMMU group 52 a0:1d.0 System peripheral [0880]: Intel Corporation Sky Lake-E CHA Registers [8086:2054] (rev 04) a0:1d.1 System peripheral [0880]: Intel Corporation Sky Lake-E CHA Registers [8086:2055] (rev 04) a0:1d.2 System peripheral [0880]: Intel Corporation Sky Lake-E CHA Registers [8086:2056] (rev 04) a0:1d.3 System peripheral [0880]: Intel Corporation Sky Lake-E CHA Registers [8086:2057] (rev 04) IOMMU group 80 c0:0d.1 System peripheral [0880]: Intel Corporation Sky Lake-E LM Channel 2 [8086:2049] (rev 04) IOMMU group 14 00:04.3 System peripheral [0880]: Intel Corporation Sky Lake-E CBDMA Registers [8086:2021] (rev 04) IOMMU group 42 [RESET] 48:00.0 USB controller [0c03]: ASMedia Technology Inc. ASM2142/ASM3142 USB 3.1 Host Controller [1b21:2142] IOMMU group 70 c0:0b.3 System peripheral [0880]: Intel Corporation Sky Lake-E LMDP Channel 2 [8086:204b] (rev 04) IOMMU group 32 [RESET] 00:1c.4 PCI bridge [0604]: Intel Corporation 200 Series PCH PCI Express Root Port #5 [8086:a294] (rev f0) IOMMU group 4 [RESET] e1:00.3 Ethernet controller [0200]: Intel Corporation I350 Gigabit Network Connection [8086:1521] (rev 01) IOMMU group 60 c0:0a.1 System peripheral [0880]: Intel Corporation Sky Lake-E Integrated Memory Controller [8086:2041] (rev 04) IOMMU group 89 e0:16.0 System peripheral [0880]: Intel Corporation Sky Lake-E M2PCI Registers [8086:2018] (rev 04) e0:16.4 System peripheral [0880]: Intel Corporation Sky Lake-E M2PCI Registers [8086:2018] (rev 04) IOMMU group 22 00:08.0 System peripheral [0880]: Intel Corporation Sky Lake-E Ubox Registers [8086:2014] (rev 04) IOMMU group 50 a0:0f.0 System peripheral [0880]: Intel Corporation Sky Lake-E CHA Registers [8086:208e] (rev 04) a0:0f.1 System peripheral [0880]: Intel Corporation Sky Lake-E CHA Registers [8086:208e] (rev 04) a0:0f.2 System peripheral [0880]: Intel Corporation Sky Lake-E CHA Registers [8086:208e] (rev 04) a0:0f.3 System peripheral [0880]: Intel Corporation Sky Lake-E CHA Registers [8086:208e] (rev 04) a0:0f.4 System peripheral [0880]: Intel Corporation Sky Lake-E CHA Registers [8086:208e] (rev 04) a0:0f.5 System peripheral [0880]: Intel Corporation Sky Lake-E CHA Registers [8086:208e] (rev 04) a0:0f.6 System peripheral [0880]: Intel Corporation Sky Lake-E CHA Registers [8086:208e] (rev 04) a0:0f.7 System peripheral [0880]: Intel Corporation Sky Lake-E CHA Registers [8086:208e] (rev 04) IOMMU group 79 c0:0d.0 System peripheral [0880]: Intel Corporation Sky Lake-E DECS Channel 2 [8086:2048] (rev 04) IOMMU group 12 00:04.1 System peripheral [0880]: Intel Corporation Sky Lake-E CBDMA Registers [8086:2021] (rev 04) IOMMU group 40 [RESET] 04:00.0 Ethernet controller [0200]: Intel Corporation I211 Gigabit Network Connection [8086:1539] (rev 03) IOMMU group 69 c0:0b.2 System peripheral [0880]: Intel Corporation Sky Lake-E LMS Channel 2 [8086:204a] (rev 04) IOMMU group 30 [RESET] 00:1c.1 PCI bridge [0604]: Intel Corporation 200 Series PCH PCI Express Root Port #2 [8086:a291] (rev f0) IOMMU group 2 [RESET] e1:00.1 Ethernet controller [0200]: Intel Corporation I350 Gigabit Network Connection [8086:1521] (rev 01) IOMMU group 59 c0:0a.0 System peripheral [0880]: Intel Corporation Sky Lake-E Integrated Memory Controller [8086:2040] (rev 04) IOMMU group 87 e0:12.1 Performance counters [1101]: Intel Corporation Sky Lake-E M3KTI Registers [8086:204d] (rev 04) e0:12.2 System peripheral [0880]: Intel Corporation Sky Lake-E M3KTI Registers [8086:204e] (rev 04) IOMMU group 20 00:05.2 System peripheral [0880]: Intel Corporation Sky Lake-E RAS [8086:2025] (rev 04) IOMMU group 49 a0:0e.0 System peripheral [0880]: Intel Corporation Sky Lake-E CHA Registers [8086:208e] (rev 04) a0:0e.1 System peripheral [0880]: Intel Corporation Sky Lake-E CHA Registers [8086:208e] (rev 04) a0:0e.2 System peripheral [0880]: Intel Corporation Sky Lake-E CHA Registers [8086:208e] (rev 04) a0:0e.3 System peripheral [0880]: Intel Corporation Sky Lake-E CHA Registers [8086:208e] (rev 04) a0:0e.4 System peripheral [0880]: Intel Corporation Sky Lake-E CHA Registers [8086:208e] (rev 04) a0:0e.5 System peripheral [0880]: Intel Corporation Sky Lake-E CHA Registers [8086:208e] (rev 04) a0:0e.6 System peripheral [0880]: Intel Corporation Sky Lake-E CHA Registers [8086:208e] (rev 04) a0:0e.7 System peripheral [0880]: Intel Corporation Sky Lake-E CHA Registers [8086:208e] (rev 04) IOMMU group 77 c0:0c.6 System peripheral [0880]: Intel Corporation Sky Lake-E LMS Channel 1 [8086:2046] (rev 04) IOMMU group 10 00:00.0 Host bridge [0600]: Intel Corporation Sky Lake-E DMI3 Registers [8086:2020] (rev 04) IOMMU group 39 [RESET] 03:00.0 SATA controller [0106]: ASMedia Technology Inc. ASM1061/ASM1062 Serial ATA Controller [1b21:0612] (rev 02) IOMMU group 67 c0:0b.0 System peripheral [0880]: Intel Corporation Sky Lake-E DECS Channel 2 [8086:2048] (rev 04) IOMMU group 29 [RESET] 00:1c.0 PCI bridge [0604]: Intel Corporation 200 Series PCH PCI Express Root Port #1 [8086:a290] (rev f0) IOMMU group 0 e0:03.0 PCI bridge [0604]: Intel Corporation Sky Lake-E PCI Express Root Port D [8086:2033] (rev 04) IOMMU group 57 c0:08.0 System peripheral [0880]: Intel Corporation Sky Lake-E Integrated Memory Controller [8086:2066] (rev 04) IOMMU group 85 e0:05.4 PIC [0800]: Intel Corporation Sky Lake-E IOxAPIC Configuration Registers [8086:2036] (rev 04) IOMMU group 19 00:05.0 System peripheral [0880]: Intel Corporation Sky Lake-E MM/Vt-d Configuration Registers [8086:2024] (rev 04) IOMMU group 47 a0:09.0 System peripheral [0880]: Intel Corporation Sky Lake-E CHA Registers [8086:208d] (rev 04) a0:09.1 System peripheral [0880]: Intel Corporation Sky Lake-E CHA Registers [8086:208d] (rev 04) a0:09.2 System peripheral [0880]: Intel Corporation Sky Lake-E CHA Registers [8086:208d] (rev 04) a0:09.3 System peripheral [0880]: Intel Corporation Sky Lake-E CHA Registers [8086:208d] (rev 04) a0:09.4 System peripheral [0880]: Intel Corporation Sky Lake-E CHA Registers [8086:208d] (rev 04) a0:09.5 System peripheral [0880]: Intel Corporation Sky Lake-E CHA Registers [8086:208d] (rev 04) a0:09.6 System peripheral [0880]: Intel Corporation Sky Lake-E CHA Registers [8086:208d] (rev 04) a0:09.7 System peripheral [0880]: Intel Corporation Sky Lake-E CHA Registers [8086:208d] (rev 04) IOMMU group 75 c0:0c.4 System peripheral [0880]: Intel Corporation Sky Lake-E Integrated Memory Controller [8086:2044] (rev 04) IOMMU group 37 [RESET] 01:00.0 Non-Volatile memory controller [0108]: Phison Electronics Corporation E12 NVMe Controller [1987:5012] (rev 01) IOMMU group 9 a1:00.1 Audio device [0403]: NVIDIA Corporation GK208 HDMI/DP Audio Controller [10de:0e0f] (rev a1) IOMMU group 65 c0:0a.6 System peripheral [0880]: Intel Corporation Sky Lake-E LMS Channel 1 [8086:2046] (rev 04) IOMMU group 27 00:17.0 SATA controller [0106]: Intel Corporation 200 Series PCH SATA controller [AHCI mode] [8086:a282]

Not sure how to pass the USB through as a PCI device but I did bind the USB Controller (42) at boot just like the Video card: Is there a particular log we can inspect or a screenshot I can provide? Maybe syslog but I doubt the error is there. When I look at the logs of the VM it looks pretty clean: -blockdev '{"node-name":"libvirt-pflash0-format","read-only":true,"driver":"raw","file":"libvirt-pflash0-storage"}' \ -blockdev '{"driver":"file","filename":"/etc/libvirt/qemu/nvram/a161f96e-640a-2fef-630f-7c4ba10dea05_VARS-pure-efi.fd","node-name":"libvirt-pflash1-storage","read-only":false}' \ -machine pc-i440fx-9.0,usb=off,dump-guest-core=off,mem-merge=off,memory-backend=pc.ram,pflash0=libvirt-pflash0-format,pflash1=libvirt-pflash1-storage,hpet=off,acpi=on \ -accel kvm \ -cpu host,migratable=on,host-cache-info=on,l3-cache=off \ -m size=33030144k \ -object '{"qom-type":"memory-backend-ram","id":"pc.ram","size":33822867456}' \ -overcommit mem-lock=off \ -smp 6,sockets=1,dies=1,clusters=1,cores=3,threads=2 \ -uuid a161f96e-640a-2fef-630f-7c4ba10dea05 \ -display none \ -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-shutdown \ -boot strict=on \ -device '{"driver":"qemu-xhci","p2":15,"p3":15,"id":"usb","bus":"pci.0","addr":"0x7"}' \ -device '{"driver":"virtio-serial-pci","id":"virtio-serial0","bus":"pci.0","addr":"0x3"}' \ -blockdev '{"driver":"file","filename":"/mnt/user/Linux-VMs/PopOS/vdisk1.img","node-name":"libvirt-1-storage","read-only":false,"cache":{"direct":false,"no-flush":false}}' \ -device '{"driver":"virtio-blk-pci","bus":"pci.0","addr":"0x4","drive":"libvirt-1-storage","id":"virtio-disk2","bootindex":1,"write-cache":"on","serial":"vdisk1"}' \ -netdev '{"type":"tap","fd":"36","id":"hostnet0"}' \ -device '{"driver":"virtio-net","netdev":"hostnet0","id":"net0","mac":"52:54:00:d4:7f:32","bus":"pci.0","addr":"0x2"}' \ -chardev pty,id=charserial0 \ -device '{"driver":"isa-serial","chardev":"charserial0","id":"serial0","index":0}' \ -chardev socket,id=charchannel0,fd=34,server=on,wait=off \ -device '{"driver":"virtserialport","bus":"virtio-serial0.0","nr":1,"chardev":"charchannel0","id":"channel0","name":"org.qemu.guest_agent.0"}' \ -audiodev '{"id":"audio1","driver":"none"}' \ -device '{"driver":"vfio-pci","host":"0000:a1:00.0","id":"hostdev0","bus":"pci.0","addr":"0x5"}' \ -device '{"driver":"vfio-pci","host":"0000:a1:00.1","id":"hostdev1","bus":"pci.0","addr":"0x6"}' \ -device '{"driver":"vfio-pci","host":"0000:48:00.0","id":"hostdev2","bus":"pci.0","addr":"0x8"}' \ -sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny \ -msg timestamp=on 2024-09-11 06:19:49.207+0000: Domain id=1 is tainted: high-privileges char device redirected to /dev/pts/0 (label charserial0) 2024-09-11T06:19:49.272813Z qemu-system-x86_64: warning: Deprecated CPU topology (considered invalid): Unsupported clusters parameter mustn't be specified as 1 2024-09-11T06:27:14.667029Z qemu-system-x86_64: terminating on signal 15 from pid 13299 (libvirtd) 2024-09-11 06:27:17.869+0000: shutting down, reason=destroyed 2024-09-12 04:35:58.155+0000: starting up libvirt version: 10.5.0, qemu version: 9.0.1, kernel: 6.8.12-Unraid, hostname: THEPUGET LC_ALL=C \ PATH=/bin:/sbin:/usr/bin:/usr/sbin \ HOME=/var/lib/libvirt/qemu/domain-2-PopOS \ XDG_DATA_HOME=/var/lib/libvirt/qemu/domain-2-PopOS/.local/share \ XDG_CACHE_HOME=/var/lib/libvirt/qemu/domain-2-PopOS/.cache \ XDG_CONFIG_HOME=/var/lib/libvirt/qemu/domain-2-PopOS/.config \ /usr/local/sbin/qemu \ -name guest=PopOS,debug-threads=on \ -S \ -object '{"qom-type":"secret","id":"masterKey0","format":"raw","file":"/var/lib/libvirt/qemu/domain-2-PopOS/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/a161f96e-640a-2fef-630f-7c4ba10dea05_VARS-pure-efi.fd","node-name":"libvirt-pflash1-storage","read-only":false}' \ -machine pc-i440fx-9.0,usb=off,dump-guest-core=off,mem-merge=off,memory-backend=pc.ram,pflash0=libvirt-pflash0-format,pflash1=libvirt-pflash1-storage,hpet=off,acpi=on \ -accel kvm \ -cpu host,migratable=on,host-cache-info=on,l3-cache=off \ -m size=33030144k \ -object '{"qom-type":"memory-backend-ram","id":"pc.ram","size":33822867456}' \ -overcommit mem-lock=off \ -smp 6,sockets=1,dies=1,clusters=1,cores=3,threads=2 \ -uuid a161f96e-640a-2fef-630f-7c4ba10dea05 \ -display none \ -no-user-config \ -nodefaults \ -chardev socket,id=charmonitor,fd=36,server=on,wait=off \ -mon chardev=charmonitor,id=monitor,mode=control \ -rtc base=utc,driftfix=slew \ -global kvm-pit.lost_tick_policy=delay \ -no-shutdown \ -boot strict=on \ -device '{"driver":"qemu-xhci","p2":15,"p3":15,"id":"usb","bus":"pci.0","addr":"0x7"}' \ -device '{"driver":"virtio-serial-pci","id":"virtio-serial0","bus":"pci.0","addr":"0x3"}' \ -blockdev '{"driver":"file","filename":"/mnt/user/Linux-VMs/PopOS/vdisk1.img","node-name":"libvirt-1-storage","read-only":false,"cache":{"direct":false,"no-flush":false}}' \ -device '{"driver":"virtio-blk-pci","bus":"pci.0","addr":"0x4","drive":"libvirt-1-storage","id":"virtio-disk2","bootindex":1,"write-cache":"on","serial":"vdisk1"}' \ -netdev '{"type":"tap","fd":"37","id":"hostnet0"}' \ -device '{"driver":"virtio-net","netdev":"hostnet0","id":"net0","mac":"52:54:00:d4:7f:32","bus":"pci.0","addr":"0x2"}' \ -chardev pty,id=charserial0 \ -device '{"driver":"isa-serial","chardev":"charserial0","id":"serial0","index":0}' \ -chardev socket,id=charchannel0,fd=35,server=on,wait=off \ -device '{"driver":"virtserialport","bus":"virtio-serial0.0","nr":1,"chardev":"charchannel0","id":"channel0","name":"org.qemu.guest_agent.0"}' \ -audiodev '{"id":"audio1","driver":"none"}' \ -device '{"driver":"vfio-pci","host":"0000:a1:00.0","id":"hostdev0","bus":"pci.0","addr":"0x5"}' \ -device '{"driver":"vfio-pci","host":"0000:a1:00.1","id":"hostdev1","bus":"pci.0","addr":"0x6"}' \ -device '{"driver":"vfio-pci","host":"0000:48:00.0","id":"hostdev2","bus":"pci.0","addr":"0x8"}' \ -sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny \ -msg timestamp=on 2024-09-12 04:35:58.155+0000: Domain id=2 is tainted: high-privileges char device redirected to /dev/pts/0 (label charserial0) 2024-09-12T04:35:58.217287Z qemu-system-x86_64: warning: Deprecated CPU topology (considered invalid): Unsupported clusters parameter mustn't be specified as 1

Configured a VM ok for PopOS and I am able to access ok via VNC (Virtual GPU). When I select the GPU to be NVIDIA GT 700 and the sound card associated with it I see the output on my monitor (HDMI 2) The other GPU is Intel integrated being used by the motherboard with Unraid. I have a KVM switch so I can give access to my keyboard and mouse to my Unraid server. I do know that my USB Controller BUS 1 has the Sandisk USB disk that Unraid boots from (Group 25 is not usable or according to unraid: "been used by unraid") root@THEPUGET:~# for usb_ctrl in $(find /sys/bus/usb/devices/usb* -maxdepth 0 -type l); do pci_path="$(dirname "$(realpath "${usb_ctrl}")")"; echo "Bus $(cat "${usb_c trl}/busnum") --> $(basename $pci_path) (IOMMU group $(basename $(realpath $pci_pat h/iommu_group)))"; lsusb -s "$(cat "${usb_ctrl}/busnum"):"; echo; done Bus 1 --> 0000:00:14.0 (IOMMU group 25) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 0bda:5411 Realtek Semiconductor Corp. RTS5411 Hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 004: ID 05e3:0610 Genesys Logic, Inc. Hub Bus 001 Device 005: ID 0781:5571 SanDisk Corp. Cruzer Fit Bus 001 Device 006: ID 05e3:0610 Genesys Logic, Inc. Hub Bus 001 Device 007: ID 05e3:0610 Genesys Logic, Inc. Hub Bus 001 Device 008: ID 05e3:0610 Genesys Logic, Inc. Hub Bus 001 Device 009: ID 05a7:40fe Bose Corp. SoundLink Color II speaker Bus 001 Device 010: ID 05e3:0610 Genesys Logic, Inc. Hub Bus 001 Device 011: ID 1949:0281 Lab126, Inc. Fire Bus 2 --> 0000:00:14.0 (IOMMU group 25) Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 002: ID 0bda:0411 Realtek Semiconductor Corp. Hub Bus 3 --> 0000:48:00.0 (IOMMU group 42) Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 4 --> 0000:48:00.0 (IOMMU group 42) Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub I bound my GPU at boot so PopOs VM can use it. I bound IOMMU group 42 at boot so PopOS VM can use it. Result: Can see PopOS login screen on HDMI port 2 ok but I cannot use keyboard and mouse. Troubleshooting: bind/unbind USB, changed USB ports at the back of the server. Ideas?

Thanks for this. Spaceinvader gave two options to shrink the array; i chose to zero out the drives and while it took 4 days there was no issue with parity.

Recently I bought a 16TB USB 3.0 drive to offload my data. a) Plugged in my Unraid Server chassis and it is recognized in "Unassigned Devices". Format it ok to xfs. b) Created a new Device for this USB Drive. What I would like to do: 1) Access the USB drive on the network or within UNRAID to backup my data automatically. What I do not want to do: 1) Plug it in on my Linux/Mac/Windows USB 3.0 port, format it, and manually transfer all data from UNRAID to USB Drive. What is the easiest way to automate the above?

So assuming I changed NIC's, routers, switches to a 10GIG setup with CAT 6 or 7, I reckon the local network speeds will improve somewhat and to what degree? Seems like 10GIG is the solution here.

When I transfer files to/from my UNRAID server the speeds are quite slow. Not entirely sure if all my shares are actually using the cache I designated from the onset; (setting = cache: YES). As you can see from the pic, the max throughput for each HD is about 250 mb/s. I get half that if I am lucky when transferring from server to the local machine (Linux or Windows). 1) I know I have gigabit network 2) I know 3 out of 8 disks are half full so the performance will drop somewhat; I should expect about 200 MB/s or a bit more but I always hover in the 113 mb/s range. 3) Is there a setting to maximize HD transfer speed from my UNRAID server to a local endpoint (mac, linux, windows)? A gigabit managed router is managing all my connections at home (no 10 gig network).

My unraid was unfortunately built on a desktop chassis and it gets incredibly hot while my kids game on VM's and I stream large files. I need to move this unraid server to another chassis that can only accommodate 6 disks (4 for the usual data + 2 for parity) w/ plenty of airflow and faster NVME's. What is the easiest way to: 1) Delete disk 4,5,6,7 & 8 from my current array 2) Use the above to move my current array to the new chassis 3) If above is too involved - what is the cloud option you would recommend to upload all data? then wipe out current unraid and transplant disks to the new unraid chassis. Any thoughts would be appreciated.

Fantastic! deleting pinhole 443 in router and perusing WireGuard.

I work from Starbucks from time to time and I would like to know what is the most efficient, quickest way to access my 3 shares: 1) Work-Stuff 2)Wife-stuff 3)Movies How do I access my shares at home? map network with windows and smb with PopOS. I configured my unraid server to be accessed remotely (port 443 forwarded ok). I also procured a domain w/ Cloudflare. Any tidbits, help, step-by-step guides would be most appreciated. Also I am willing to pay $$ for someone to help me troubleshoot what is going on w/ Guacamole not seeing my unraid VM's over the local network - bonus if I can access that VM remotely w/ Guacamole and also ssh to my unraid server.

root@THEPUGET:~# hciconfig -a hci0: Type: Primary Bus: USB BD Address: 0C:54:15:69:86:64 ACL MTU: 1021:4 SCO MTU: 96:6 DOWN RX bytes:14992 acl:0 sco:0 events:2420 errors:0 TX bytes:595696 acl:0 sco:0 commands:2418 errors:0 Features: 0xff 0xfe 0x0f 0xfe 0xdb 0xff 0x7b 0x87 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH HOLD SNIFF Link mode: SLAVE ACCEPT Under Tools --> System Devices --> I can't seem to find this bluetooth for my guest VM device passthrough. I've inspected every IOMMU group but nothing comes close to the above. Is my motherboard bluetooth not supported in unraid 6.9.2? https://www.gigabyte.com/Motherboard/X299-DESIGNARE-EX-rev-10/sp#sp

Tutorial worked great! up and running w/ Mariadb. I noticed, like you said, it is a tad slow, but sufficient for my needs.

This worked perfect. Up and running and configuring. Thank you.

First time installing NextCloud w/ Mariadb and phphmyadmin. I am able to install all the above and I configured passwords/users ok. However, I am getting ONE persistent error. If troubleshooting is extensive on this one, I can start from scratch and wipe out everything. This is a first time install. Has anyone seen this error before and how to address it?

Localhost amended and seems to recognize the db but with the following error:

I must be missing some variable to be correctly filled out or something I missed/not-aware-of.

Excellent. I will try this sequence of steps and keep you all posted. Thanks!

@CorneliousJD this bit: "... but it is SLOW. Slow to navigate to site page, slow going between apps." Do you have other alternatives in mind? I've tried to install nextcloud with mariadb,mysql,postres and I can't install it yet because of db errors about the password or user not correct. I dabbled in the CLI creating the db name, root name, password, user pass and no dice so far. I decided to try sqlite which is the default but there is a warning about not using sqlite for production environments. I do have 2 NVME's as cache and I am hoping the slowness you mentioned would be mitigated by this available cache (2TB each) as soon as I find out how to configure nextcloud w/ postgres.