stev067

They're 4-pin, here's the model: Noctua NF-A4x10 PWM. I can't remember or see where I have them plugged in, because the wires are tucked back, but I'm pretty sure I have them running full blast 24/7.

Thanks, I was able to locate a fairly recent backup on my cache drive, and take the plugins folder from it, and added it to the mix. Back to normal now, and activated the flash backups from unraid connect.

If I restore everything but the plugins folder, I can get it to boot up and access it. Any idea what in there might be causing problems?

Something in the config folder seems to be the problem, and it's not /ssh, /ssl, or network.cfg, because I overwrote the entire /config with that of my backup, minus those I mentioned, on a fresh flash, and that makes the difference between booting or not.

Is it supposed to re-create network.cfg? It's getting to the login line, but not creating a new network.cfg, and still no access to GUI over the network. tower-diagnostics-20230826-0441.zip

It was stopping and hanging at various lines depending on which boot method I chose, and never reaching a login line. I just did replace the config folder onto a clean boot, and was able to finally pull diagnostics. I can see that it boots to the login line, but am still unable to reach the GUI from my local network. I booted the clean flash once before replacing the config folder, and was able to reach the GUI, which tells me my network is fine, and the issue is on the server side. tower-diagnostics-20230825-1112.zip

Ok I was able to get a monitor going, forgot it had to be connected to a GPU instead of the mobo. Looks like it wasn't completing boot. Also looks like I don't have a flash backup on unraid connect. I know I set up backup somewhere. I put a clean install of unraid on the flash, and now have to try and figure out how to restore the old flash.

Sorry I know this is probably trivial... Just moved to a new house, and I had successfully connected my server and windows PC. I was able to access it via the local network for a few days. Then yesterday I noticed a warning in the upper right corner but didn't address it. At some point, I was no longer able to access the server GUI. I have rebooted the server and my PC, and power cycled the network switches. I'm able to ping it from my PC, but still cannot access the GUI. I'm having trouble connecting via SSH or even getting a display out to a monitor. Where should I start? I'm using the same address that has always worked.

Intel RES2CV240. I kinda addressed this earlier, so I'll just point to that previous post.

Just over 2 years in. Zero failures across the board. Very happy with the setup, and Handbrake has been churning nearly 24/7.

Strange...even after re-binding those and rebooting, I still get those errors, and they don't show as bound in system devices. And I haven't moved the GPU at all. Edit: Scratch that, I was able to get it to stick. Had to clear it out and reboot and then remake it. Now it's sticking. Edit 2: It's working now! Thanks for your help!

Here ya go, thanks for taking a look. haven-diagnostics-20230505-1231.zip

That doesn't seem to do the trick. In fact, the 'alias name' lines don't stick. I add them, update the VM, and when I go back they're gone. I've kept the slot and function of the sound card as you and Hulk put it though, because apparently I missed that. Still getting the code 43 though.

Thanks you were right. I should've had the function for the virtual line for the sound card set to slot 0x05 and function 0x1. Unfortunately there must be something else wrong too, because I'm still getting a code 43 error.

Hey guys, Having a rough time trying to get a simple GPU passthrough working with a windows 10 (now 11) VM. The OS does recognize the GPU, but lthe resolution is painfully low, and when I look at the adapter properties in device manager, it says "a driver for this device has been disabled," so it's not liking the driver. I've tried a few different things for the driver: 1) Using SpaceInvader One's script to dump the ROM from the card. I haven't been able to get this to work. I get a message that the ROM is too small (under 70kb) and that it will try to reconnect the card. It has me push the power button on my system, and then does nothing when the system comes back from whatever hibernate state it went into. 2) Found what sounds like a matching ROM from techpowerup. This is a Geforce GT 710 1GB. I set the VM to use this as the ROM BIOS. 3) Within the VM, tried manually updating drivers, pointing to the QXL and QXLDOD folders from the VIRTIO drive. I just always get the message that the best drivers are already installed. 4) Within the VM, installed the drivers directly from Nvidia. This results in no change. The graphics and sound are in their own IOMMU group together. I'm using the latest VIRTIO driver. Is there anything I haven't thought of? Appreciate any help. <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm' id='2'> <name>Windows 11</name> <uuid>4be232f6-40d7-30e0-a6f8-99a1dcd79660</uuid> <metadata> <vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/> </metadata> <memory unit='KiB'>16777216</memory> <currentMemory unit='KiB'>16777216</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>8</vcpu> <cputune> <vcpupin vcpu='0' cpuset='12'/> <vcpupin vcpu='1' cpuset='28'/> <vcpupin vcpu='2' cpuset='13'/> <vcpupin vcpu='3' cpuset='29'/> <vcpupin vcpu='4' cpuset='14'/> <vcpupin vcpu='5' cpuset='30'/> <vcpupin vcpu='6' cpuset='15'/> <vcpupin vcpu='7' cpuset='31'/> <emulatorpin cpuset='0,6'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-i440fx-7.1'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi-tpm.fd</loader> <nvram>/etc/libvirt/qemu/nvram/4be232f6-40d7-30e0-a6f8-99a1dcd79660_VARS-pure-efi-tpm.fd</nvram> </os> <features> <acpi/> <apic/> <hyperv mode='custom'> <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='4' 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='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/user/domains/Windows 11/vdisk1.img' index='3'/> <backingStore/> <target dev='hdc' bus='virtio'/> <boot order='1'/> <alias name='virtio-disk2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/isos/Windows.iso' index='2'/> <backingStore/> <target dev='hda' bus='ide'/> <readonly/> <boot order='2'/> <alias name='ide0-0-0'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/isos/virtio-win-0.1.229-1.iso' index='1'/> <backingStore/> <target dev='hdb' bus='ide'/> <readonly/> <alias name='ide0-0-1'/> <address type='drive' controller='0' bus='0' target='0' unit='1'/> </disk> <controller type='pci' index='0' model='pci-root'> <alias name='pci.0'/> </controller> <controller type='ide' index='0'> <alias name='ide'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <controller type='virtio-serial' index='0'> <alias name='virtio-serial0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </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:5d:8f:49'/> <source bridge='br0'/> <target dev='vnet2'/> <model type='virtio-net'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </interface> <serial type='pty'> <source path='/dev/pts/1'/> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> <alias name='serial0'/> </serial> <console type='pty' tty='/dev/pts/1'> <source path='/dev/pts/1'/> <target type='serial' port='0'/> <alias name='serial0'/> </console> <channel type='unix'> <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/domain-2-Windows 11/org.qemu.guest_agent.0'/> <target type='virtio' name='org.qemu.guest_agent.0' state='connected'/> <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='3'/> </input> <input type='mouse' bus='ps2'> <alias name='input1'/> </input> <input type='keyboard' bus='ps2'> <alias name='input2'/> </input> <tpm model='tpm-tis'> <backend type='emulator' version='2.0' persistent_state='yes'/> <alias name='tpm0'/> </tpm> <audio id='1' type='none'/> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x0a' slot='0x00' function='0x0'/> </source> <alias name='hostdev0'/> <rom file='/mnt/user/isos/vbios/GT710_new.rom'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0' multifunction='on'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x0a' slot='0x00' function='0x1'/> </source> <alias name='hostdev1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x0b05'/> <product id='0x18f3'/> <address bus='3' device='2'/> </source> <alias name='hostdev2'/> <address type='usb' bus='0' port='1'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x1b1c'/> <product id='0x0c21'/> <address bus='1' device='2'/> </source> <alias name='hostdev3'/> <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>

Figured it out. I knew I had custom DNS settings before, but couldn't remember why. It was apparently required in order to disable dns rebind protection on my Nest router. https://support.google.com/googlenest/answer/9144137?hl=en

I've tried the address every way I can think of: http://ipaddress https://ipaddress http://tower https://tower The "Local Access" link from the MyServers page. The only one that gives a unique result is https://ipaddress, where it gives the 404 not found nginx message. I just wonder if there is something I need to do with a port forward, or maybe DNS settings that got undone when I factory reset my router.

Long story very short, I factory-reset my wireless router today. I took screenshots of settings that I could, but missed the port forwards. I think I had 2 or 3, and one might've been game related. I re-added the 51820 one for Wireguard. Now when I'm off my local network, and use wireguard to VPN in, I can access my Blue Iris VM stream, but I can't access my Unraid GUI. So in my mind, since I can VPN into my local network, shouldn't I be able to get the GUI? Maybe a missed forward? Any ideas?

Fractal Define 7 XL

Thank you for maintaining this docker container. I've had it churning through a media collection for almost a year now (half-way done). I don't know if you are taking feature requests, but if so, I had an idea. If there's already a way of doing this, let me know. I know you can have multiple Watch Directories, but it would be helpful to be able to assign a priority to each. For example, I want it working on my priority #1 folder when there are jobs there, and when it's empty, falling back to working on my priority #2 folder, so there isn't any down-time but I can still take care of the most important stuff first. I'm envisioning a priority attribute in the paths template, so each Watch Directory can have whatever priority the user wants. Just something I've been thinking about for a while. Thanks again!

Sounds like your needs are similar to mine. My build is the one Lolight linked earlier in the thread. I run a Plex server on mine, and I stream 4k HDR+Atmos content all the time. It's actually overkill for that job. Mostly, I have it continuously running Handbrake on 11 of the 32 cores, as well as Blue Iris surveillance software on a Windows VM running on a couple of the other cores. I've found the Ryzen 5950x to be great, and the system overall has been stable as a rock. I don't use a GPU in my system, so that is saving somewhat on PCIe lanes, but I do use a 10-gig network switch connected to a different PC. What are your specific concerns about lanes?

I'm hoping someone can help educate me on what happened to my server last night. I was using Krusader to move a couple TB of data from one disk to another, to consolidate a share. It was going to take 8 hours or something significant like that, so I let it transfer overnight. Then this morning, I see that one of the disks involved in the transfer is reporting read errors(s) and now I'm rebuilding the data on that disk. All of my disks are fairly new Ironwolf Pro, and I highly doubt there's anything wrong with this disk. In fact, I think this has happened to me before. Looking at my system logs, I found the lines below from 3am, regarding disk sdo, which is the disk with errors. Am I correct in assuming that this was caused by CA Backup/Restore trying to stop Krusader while I had a file transfer in progress? If so, is there any way I can prevent this in the future? Thanks, Steve Jan 3 03:00:01 Haven CA Backup/Restore: Stopping binhex-krusader Jan 3 03:00:01 Haven unassigned.devices: Adding partition 'sdo1'... Jan 3 03:00:01 Haven unassigned.devices: Mounting partition 'sdo1' at mountpoint '/mnt/disks/ST14000NE0008-2JK101_ZHZ7637K'... Jan 3 03:00:01 Haven unassigned.devices: Mount drive command: /sbin/mount -t 'xfs' -o rw,noatime,nodiratime '/dev/sdo1' '/mnt/disks/ST14000NE0008-2JK101_ZHZ7637K' Jan 3 03:00:01 Haven kernel: XFS (sdo1): Filesystem has duplicate UUID 87a8d7d8-43ea-4db1-bd82-4287f89568a0 - can't mount Jan 3 03:00:01 Haven unassigned.devices: Mount of 'sdo1' failed: 'mount: /mnt/disks/ST14000NE0008-2JK101_ZHZ7637K: wrong fs type, bad option, bad superblock on /dev/sdo1, missing codepage or helper program, or other error. ' Jan 3 03:00:01 Haven unassigned.devices: Partition 'ST14000NE0008-2JK101_ZHZ7637K' cannot be mounted. haven-diagnostics-20220103-0829.zip

haven-diagnostics-20211209-0729.zip

I also have been experiencing this refusal to mount, since yesterday. I didn't change anything, and I've always been able to just mount/unmount this drive whenever I wanted. I found that stopping the array was enough to get it to mount, rather than rebooting.

Dang, ok thanks. I will just try to rebuild same disk and call it a fluke. Sucks to rebuild 14TB disk though.