Chamzamzoo

This also fixed it for me. Thanks!

Solved that problem. I was putting the USB back in what I thought was the same spot, but it wasn't. I was putting it in a slot that was being automatically passed through to the VM, which was set to auto run on array start... *facepalm* Seem to be back up and running now.! thanks for your patience

Annoyingly I have an older backup of my flash on the array, but I get the 0x8007003B error when downloading it on windows, and it just outright fails to connect on mac.

Weirdly I got nothing when I typed that, just another prompt. CDing to /boot and doing it again just gave nothing either. No error. Checked the flash drive in windows, no problems found. Now I've recreated the flash from the installer tool with my license on it, and can access the GUI, although I still have a USB error top right, which takes me to this page: Registration Error accessing your physical USB Flash boot device There is a physical problem accessing your USB Flash boot device. Please Contact Support. Flash GUID: Error code: ENOFLASH3 I was able to get my diagnostics now also! tower-diagnostics-20220125-1201.zip

didn't get very far with that! root@Tower:~# diagnostics Starting diagnostics collection... mkdir: cannot create directory ‘/boot/logs’: Input/output error done. ZIP file '/boot/logs/tower-diagnostics-20220125-0114.zip' created. No zip file to be found on the flash in logs, assume the first error prevented it.

Now I get this a Flash Device Error in the top right and all the GUI pages are blank.. but dockers and VMs that are auto ran are working. Any more ideas?

Thanks! Managed to copy over my config folder to a new USB, or parts of it anyway, a whole copy caused the crashing again.

Unraid has been working well for a long time on this machine, but the other day I started getting weird issues with temp sensors not showing up in HWINFO, so I booted to Windows from my dual boot VM Nvme. Seem to now be stuck with just windows.. The BIOS was being weird, not showing all my boot drives, refusing to boot anything except windows, unraid USB would just immediately show the boot options in the BIOS again, or boot to windows if set as the primary boot option. Updated the BIOS and set my options back as best I could (took a video of my previous BIOS pages), boot drives all reappeared and temp sensors back (in windows) but now I get stuck in the attached image when booting unraid. Any ideas? OCR'd the image usb usb usb 3 2: USB disconnect, - device number 5 3 2 . 1• USB disconnect, device number 3-3 . 2 . 2: USB disconnect, device number usb 3-3.2 •3: USB disconnect usb 3-4: device number 6 7 8 USB disconnect device number 4 xhci hod 0000: 07:00.1: USB bus 3 deregistered SQUASHES error: Failed to read block Oxbadc6c: -5 xhci_hed 0000:07:00.3: remove state 4 usb usb6 USB disconnect, device number 1 xhci hed 0000:07:00.3: USB bus 6 deregistered xhci 0000:07:00.3: remove, state "SD usb5: USB disconnect advice device number 1 usb 5-6: USB disconnect, number 2 xhci hed 0000:07:00.3: USB bus 5 deregistered SQUASHFS error : Failed to read block Oxbadc6c: -5 xhci_hcd 0000:06:00.0: remove, state 4 usb usb2 : USB disconnect. device number 1 xhci 0000:06:00.0: USB bus 2 deregistered xhci. _hod 0000:06:00.0: remove state 4 usb usbl: USB disconnect, device number 1 xhci hod 0000:06:00.0: USB bus 1 deregistered SQUASHES error: Failed to read block Oxbadc6c: -5 ufio-pci 0000: 0a: 00.0: ugaarb: changed UGA decodes : +mem: owns =io+mem

Cheers Squid. Not noticed anything untoward yet.

Hi folks, anything to worry about in my diagnostics? MCE log error from Fix common problems, but no output was recorded in the error message. tower-diagnostics-20211101-1220.zip

Any solution for MAC OS VMs? Tried the VirtIO via Virt manager thing but just one resolution still.

Any ideas how to get more resolution options for those of us not doing GPU passthrough? I've changed QXL to VirtIO and even VGA (using Virt Manager) and this changed it from one large resolution available to 1080p as the only res avaialble. I'd like to use this VM in a window, these resolutions aren't great for that.

Any thoughts as to what would be better performance for a regular use MacOSX system, the VM route or this docker?

6.9 beta 30 here with x570 Aorus Elite, 3900x and only CPU temps available, no fan speeds either. Tried loading the modprobe it87 force_id=0x8628 in boot/config/go but they fail to load on startup.

Thanks for the offer to help. Your first tip eventually sorted it for me. I've managed it with Clover after reformating windows again, now works, but only for one of my Samsung NVMes. Very odd.

That didn't work. I thought I had got to the bottom of it when I realised taht selecting my Samsung 960 NVME booted up windows from my Samsung 970 NVME, bit weird. So I wiped and clean installed Windows 10 via USB on to each drive seperatly while the other was out of the machine and tried. One ends up in the power shell interface when trying to boot as VM, one ends up with the Start PXE over IPv4 error I have above. Both boot fine baremetal. I now also have tried another mobo ( Aorus x570 Elite) and have the same issue. Driving me crackers 😆 This is all on Unraid 6.9 beta 30, as this was needed for the drivers for the 2.5gbps lan devices these boards have.

Thanks for that. Seems broadly similar to mine, from what I can make out. Going to try a different motherboard today.

Ah yes, you’re right. Unfortunately it just sits on the Clover boot loader screen and does nothing.

Not having much luck with this, the clover download file (spaces_win_clover.img) won't open, No Mountable File systems aparently (OS X 10.15.6).

Thanks for the tip, but there’s no link there! do You mean the spaceinvader one video he first made about passing through NVME?

I have a very similar problem, altough boot order 1 gave me this error: VM creation error unsupported configuration: per-device boot elements cannot be used together with os/boot elements Perhaps you could cast your eye over my thread query if you have time?

HI all, Upgraded to MSI Tomahawk x570 & 3900x (from Taichi x399 & 1900x) After the upgrade what was a prefectly working Dual boot NVME now is very unhappy. I get an error: "Start PXE over IPv4" when I try to pass through my NVME with Windows 10 on it and get no further, using i440fx.5.1 I have tried so many things, it's driving me crackers. Most upto date (1.40 beta) BIOS had only 14 IOMMU groups (with NVME's mushed in with network adaptors in group 0), so used ACS override with it. Downgraded BIOS to 1.30 to get better IOMMU groups with ACS off (30 or so, not too bad split). Using Q35-5.1 I get a shell error prompt. tried various older versions of Q35 and i440 Tried a different NVME drive with a copy of the Macrium Reflect copy of the same Windows install on it. Adding <boot order='1'/> to the hostdev section after sources for the NVME in the VM XML (gave: VM creation error unsupported configuration: per-device boot elements cannot be used together with os/boot elements) not sure what that means! Does anyone please have any suggestions? IOMMU group 0: [1022:1482] 00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge IOMMU group 1: [1022:1483] 00:01.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge IOMMU group 2: [1022:1483] 00:01.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge IOMMU group 3: [1022:1482] 00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge IOMMU group 4: [1022:1482] 00:03.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge IOMMU group 5: [1022:1483] 00:03.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge IOMMU group 6: [1022:1482] 00:04.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge IOMMU group 7: [1022:1482] 00:05.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge IOMMU group 8: [1022:1482] 00:07.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge IOMMU group 9: [1022:1484] 00:07.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B] IOMMU group 10: [1022:1482] 00:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge IOMMU group 11: [1022:1484] 00:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B] IOMMU group 12: [1022:790b] 00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 61) [1022:790e] 00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 51) IOMMU group 13: [1022:1440] 00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 0 [1022:1441] 00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 1 [1022:1442] 00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 2 [1022:1443] 00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 3 [1022:1444] 00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 4 [1022:1445] 00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 5 [1022:1446] 00:18.6 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 6 [1022:1447] 00:18.7 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 7 IOMMU group 14: [144d:a808] 01:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981/PM983 [N:0:4:1] disk Samsung SSD 970 EVO 1TB__1 /dev/nvme0n1 1.00TB IOMMU group 15: [1022:57ad] 20:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse Switch Upstream IOMMU group 16: [1022:57a3] 21:01.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge IOMMU group 17: [1022:57a3] 21:04.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge IOMMU group 18: [1022:57a3] 21:06.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge IOMMU group 19: [1022:57a4] 21:08.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge [1022:1485] 2a:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved SPP [1022:149c] 2a:00.1 USB controller: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 1ea7:1007 BTL Gaming Mouse Bus 001 Device 003: ID 8087:0029 Intel Corp. Bus 001 Device 004: ID 03f0:304a Hewlett-Packard HP Business Slim Keyboard Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub [1022:149c] 2a:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002: ID 1462:7c84 Micro Star International MYSTIC LIGHT Bus 003 Device 003: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 003 Device 004: ID 03f0:2d40 Hewlett-Packard Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub IOMMU group 20: [1022:57a4] 21:09.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge [1022:7901] 2b:00.0 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 51) [3:0:0:0] disk ATA ST32000644NS SN12 /dev/sdb 2.00TB [4:0:0:0] disk ATA Samsung SSD 850 1B6Q /dev/sdc 250GB IOMMU group 21: [1022:57a4] 21:0a.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge [1022:7901] 2c:00.0 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 51) [5:0:0:0] disk ATA WDC WD30EFRX-68E 0A80 /dev/sdd 3.00TB [6:0:0:0] disk ATA WDC WD80EZAZ-11T 0A83 /dev/sde 8.00TB [9:0:0:0] disk ATA TOSHIBA MG05ACA8 GX2A /dev/sdf 8.00TB [10:0:0:0] disk ATA WDC WD30EFRX-68E 0A80 /dev/sdg 3.00TB IOMMU group 22: [144d:a804] 23:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM961/PM961 This controller is bound to vfio, connected drives are not visible. IOMMU group 23: [10ec:8125] 26:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller (rev 04) IOMMU group 24: [8086:2723] 28:00.0 Network controller: Intel Corporation Wi-Fi 6 AX200 (rev 1a) IOMMU group 25: [10de:1b06] 2d:00.0 VGA compatible controller: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] (rev a1) [10de:10ef] 2d:00.1 Audio device: NVIDIA Corporation GP102 HDMI Audio Controller (rev a1) IOMMU group 26: [1022:148a] 2e:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Function IOMMU group 27: [1022:1485] 2f:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved SPP IOMMU group 28: [1022:1486] 2f:00.1 Encryption controller: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Cryptographic Coprocessor PSPCPP IOMMU group 29: [1022:149c] 2f:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub IOMMU group 30: [1022:1487] 2f:00.4 Audio device: Advanced Micro Devices, Inc. [AMD] Starship/Matisse HD Audio Controller <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm'> <name>Windows 10 Dual Boot</name> <uuid>64ac8a32-c948-6112-af24-2cf05d7be1ad</uuid> <metadata> <vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/> </metadata> <memory unit='KiB'>2097152</memory> <currentMemory unit='KiB'>2097152</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>16</vcpu> <cputune> <vcpupin vcpu='0' cpuset='4'/> <vcpupin vcpu='1' cpuset='16'/> <vcpupin vcpu='2' cpuset='5'/> <vcpupin vcpu='3' cpuset='17'/> <vcpupin vcpu='4' cpuset='6'/> <vcpupin vcpu='5' cpuset='18'/> <vcpupin vcpu='6' cpuset='7'/> <vcpupin vcpu='7' cpuset='19'/> <vcpupin vcpu='8' cpuset='8'/> <vcpupin vcpu='9' cpuset='20'/> <vcpupin vcpu='10' cpuset='9'/> <vcpupin vcpu='11' cpuset='21'/> <vcpupin vcpu='12' cpuset='10'/> <vcpupin vcpu='13' cpuset='22'/> <vcpupin vcpu='14' cpuset='11'/> <vcpupin vcpu='15' cpuset='23'/> </cputune> <os> <type arch='x86_64' machine='pc-i440fx-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/64ac8a32-c948-6112-af24-2cf05d7be1ad_VARS-pure-efi.fd</nvram> <boot dev='hd'/> </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='8' threads='2'/> <cache mode='passthrough'/> <feature policy='require' name='topoext'/> </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.189-1.iso'/> <target dev='hdb' bus='ide'/> <readonly/> <address type='drive' controller='0' bus='0' target='0' unit='1'/> </disk> <controller type='usb' index='0' model='ich9-ehci1'> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <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'> <master startport='2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/> </controller> <controller type='usb' index='0' model='ich9-uhci3'> <master startport='4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/> </controller> <controller type='pci' index='0' model='pci-root'/> <controller type='ide' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:22:b3:2f'/> <source bridge='br0'/> <model type='virtio-net'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </interface> <serial type='pty'> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> </serial> <console type='pty'> <target type='serial' port='0'/> </console> <channel type='unix'> <target type='virtio' name='org.qemu.guest_agent.0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x2d' slot='0x00' function='0x0'/> </source> <rom file='/mnt/user/isos/EVGA.GTX1080Ti.11264.170406_1.rom'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x2d' slot='0x00' function='0x1'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </hostdev> <memballoon model='none'/> </devices> </domain>

Same issue, also with similar hardware (samsung NVME). I previously had it working on different hardware, replaced mobo & processor, had to split up my IOMMU groups with ACS patch and now my NVME does the same as yours. Works baremetal boot from BIOS, but windows seems to think theres no install there and tries to boot from ethernet, I eventually end up on the screen you're at. Did you resolve it?

Bump... I'm having to sleep in the room with mine for the forseeable...

I see the incoming port in the Web gui for Deluge changes itself after whatever I set it to on a restart of deluge, must be that. Tried airVPN and that's banging away at 9MB/s now, guess it could be the combination of PIA and Virgin.