tomjrob

Will do. Thank You.

JorgeB, Thank you for the quick response. However, I am confused, as I do not see device sdl1 on my system. Below are the System Devices listed with the Unassigned devices noted. Am I missing something? SCSI Devices [0:0:0:0]disk SanDisk Cruzer Fit 1.00 /dev/sda 16.0GB [2:0:0:0]disk ATA HITACHI HUS72404 NS04 /dev/sdg 4.00TB [2:0:1:0]disk ATA PNY CS900 1TB SS 06B5 /dev/sdh 1.00TB [2:0:2:0]disk ATA HITACHI HUS72404 NS04 /dev/sdi 4.00TB [2:0:3:0]disk ATA ST8000DM004-2U91 0001 /dev/sdj 8.00TB [2:0:4:0]disk ATA HITACHI HUS72404 NS04 /dev/sdk 4.00TB [3:0:0:0]disk ATA Samsung SSD 860 3B6Q /dev/sdc 500GB Unassigned (Boot device for a Windows 11 VM) [7:0:0:0]disk ATA OOS8000G OOS1 /dev/sdd 8.00TB [10:0:0:0]disk ATA WL4000GSA6472E 01 /dev/sde 4.00TB [11:0:0:0]disk ATA Samsung SSD 870 0A0 /dev/sdf 1.00TB [14:0:0:0]disk Hitachi HUA722020ALA330 /dev/sdm 2.00TB Unassigned (Not in use) [14:0:0:1]disk Hitachi HUA723020ALA640 /dev/sdn 2.00TB Unassigned (Not in use) [14:0:0:2]disk Hitachi HUS724040ALE640 /dev/sdo 4.00TB Unassigned (Not in use) [14:0:0:3]disk WDC WD50 00AAKX-75U6AA0 /dev/sdp 500GB Unassigned (Not in use) Also, Someone suggested to run the command below. Here is the output. root@Tower:~# du -h -d 1 /var/log 0 /var/log/pwfail 0 /var/log/preclear 4.0K /var/log/unraid-api 4.0K /var/log/swtpm 16K /var/log/samba 0 /var/log/plugins 32K /var/log/pkgtools 4.0K /var/log/nginx 0 /var/log/nfsd 12K /var/log/libvirt 128M /var/log root@Tower:~#

I have recently seen this error happening in "Fix Common Problems" on my Unraid server. I have checked the scheduler to insure that Mover Logging is disabled. I am hoping someone in the community can shed some light on this with a possible resolution. I am attaching Diagnostics below. Thanks in advance for any assistance. tower-diagnostics-20250721-0811.zip

Issue Resolved. FlamongOle, I was able to resolve this issue, by changing the smart controller type in Smart Settings of each device from "Use default" to "JMicron ATA pass-through" All devices are now recognized in Disk Location plugin. To get there: main/unassigned devices/device/smart controller type Hopefully this will help someone else that may use external drive bays. thank you for your help.

Thank you for the response. Current version running is 2025.06.03. I am not sure which version worked in the past. I have found some additional information though. When i check the attributes of the devices connected to the external drive bay in unassigned devices plugin, they all say Unsupported USB bridge [0x152d The interesting thing is that all of the devices that do not show up in the Disk Location plugin are visible on the network and are working fine. I am next going to research the message above and see if there are options to resolve that, as well as checking the posts you mentioned. I am kinda new at this, so I appreciate the help.

Not sure what is different with the latest version of this plugin, but I have a mobile stor device which houses 4 external drives that used to be detected by the Disk Location plugin. Now those devices do not show up. They are connected via a USB cable and show up fine in the unassigned devices plugin. I can (and do) pass on some as boot devices for VM's, and it would be nice to again see where they are located in the frame. Always worked before latest update. Is there any chance that this functionality can be restored? Thanks in advance.

Is there anyone out there who can shed some light on this? Any help is greatly appreciated.

I am wondering if you ever received any help on this or have you been able to resolve it? I am having the same problem with a Nvidia GE Force GT-520 GPU. Thanks in advance

I have created a working Windows 10 KVM in Unraid to virtualize a physical PC. The VM boots from a disk fine with no errors. I have an ASUS branded GE Force GT-520 GPU that I have passed through to the VM, along with the imbedded sound card. The GPU is recognized in Device Manager, reports as Nvidia GE Force GT 520, but has the following error. This device cannot find enough free resources that it can use. (Code 12) If you want to use this device, you will have to disable one of the other devices on this system. Things I have tried to resolve this. Verified that the GT-520 card and it's multi-function sound card are in their own IOMMU Group by themselves. Checked the box to bind them to VFIO at boot, and rebooted the system. Tried multiple drivers for the GT-520 Enabled PCIe ACS Override in VM Manager and rebooted. (Did not affect the Iommu Group fpr the GT-520 card) Have since Disabled PCIe Override and rebooted again since it didn't resolve the problem. Have tried disabling the GPU in device manager and then scanned for hardware changes to rediscover the card. Card was rediscovered but still has same error. I am including the XML of the VM below and attaching diagnostics. VM XML <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm'> <name>TOM-PC-VM</name> <uuid>5cf260fc-40b7-f93e-4fdd-ba41c5f5d083</uuid> <metadata> <vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10" webui="" storage="default"/> </metadata> <memory unit='KiB'>8388608</memory> <currentMemory unit='KiB'>8388608</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>4</vcpu> <cputune> <vcpupin vcpu='0' cpuset='2'/> <vcpupin vcpu='1' cpuset='3'/> <vcpupin vcpu='2' cpuset='4'/> <vcpupin vcpu='3' cpuset='5'/> </cputune> <os> <type arch='x86_64' machine='pc-i440fx-9.1'>hvm</type> </os> <features> <acpi/> <apic/> <hyperv mode='custom'> <relaxed state='on'/> <vapic state='on'/> <spinlocks state='on' retries='8191'/> <vpindex state='on'/> <synic state='on'/> <stimer state='on'/> <vendor_id state='on' value='none'/> </hyperv> </features> <cpu mode='host-passthrough' check='none' migratable='on'> <topology sockets='1' dies='1' clusters='1' cores='2' threads='2'/> <cache mode='passthrough'/> <feature policy='require' name='topoext'/> </cpu> <clock offset='localtime'> <timer name='hpet' present='no'/> <timer name='hypervclock' present='yes'/> </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/KVM ISO Library/virtio-win-0.1.204-1.iso'/> <target dev='hdb' bus='ide'/> <readonly/> <address type='drive' controller='0' bus='0' target='0' unit='1'/> </disk> <disk type='block' device='disk'> <driver name='qemu' type='raw' cache='writeback' discard='unmap'/> <source dev='/dev/sde'/> <target dev='hdc' bus='ide' rotation_rate='1'/> <serial>vdisk1</serial> <boot order='1'/> <address type='drive' controller='0' bus='1' target='0' unit='0'/> </disk> <controller type='pci' index='0' model='pci-root'/> <controller type='pci' index='1' model='pci-bridge'> <model name='pci-bridge'/> <target chassisNr='1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </controller> <controller type='pci' index='2' model='pci-bridge'> <model name='pci-bridge'/> <target chassisNr='2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </controller> <controller type='pci' index='3' model='pci-bridge'> <model name='pci-bridge'/> <target chassisNr='3'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </controller> <controller type='pci' index='4' model='pci-bridge'> <model name='pci-bridge'/> <target chassisNr='4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </controller> <controller type='pci' index='5' model='pci-bridge'> <model name='pci-bridge'/> <target chassisNr='5'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/> </controller> <controller type='pci' index='6' model='pci-bridge'> <model name='pci-bridge'/> <target chassisNr='6'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x09' function='0x0'/> </controller> <controller type='pci' index='7' model='pci-bridge'> <model name='pci-bridge'/> <target chassisNr='7'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x0a' function='0x0'/> </controller> <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> <controller type='usb' index='0' model='qemu-xhci' ports='15'> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:11:e4:4d'/> <source bridge='virbr0'/> <model type='virtio-net'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x0b' 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='tablet' bus='usb'> <address type='usb' bus='0' port='1'/> </input> <input type='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <graphics type='vnc' port='-1' autoport='yes' websocket='-1' listen='0.0.0.0' sharePolicy='ignore'> <listen type='address' address='0.0.0.0'/> </graphics> <audio id='1' type='none'/> <video> <model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1' primary='yes'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x1e' function='0x0'/> </video> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </source> <rom file='/mnt/user/Files/Asus.GT520.1024.110322.rom'/> <address type='pci' domain='0x0000' bus='0x07' slot='0x01' function='0x0' multifunction='on'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x01' slot='0x00' function='0x1'/> </source> <address type='pci' domain='0x0000' bus='0x07' slot='0x01' function='0x1'/> </hostdev> <memballoon model='none'/> </devices> </domain> tower-diagnostics-20250608-1510.zip

I have also attempted to use the xml of a new working Windows 10 VM and just point it to the failing vdisk.qcow2 file and it fails with the same "no bootable disk" error.

I do not understand what "this has not changed to raw" means. Can you elaborate? Since last week, I have been able to create new Windows 10 KVM's and they start without issue. I have also done qemu-img check on the vdisk.qcow2 file that will not boot and it returns no errors. I have looked through the xml of the failing VM and compared it to the new Windows 10 VM's and nothing appears different so I am lost. This VM is important and the only remaining issue from the motherboard upgrade, so any and all help is greatly appreciated.

SimonF, I removed the hostdev section, and it corrected the execution error. Thank you for the assistance. Unfortunately, even though the Kvm starts, it now fails with a message of No bootable disk. This is the same vdisk file that worked with the last motherboard so I am going to close this thread and investigate the new error.

SimonF, Thanks for the suggestion. I believe it was a sound card. I will try and remove the hostdev section and retry the KVM.

After upgrading my Unraid motherboard to an ASUS ROG Strix X570-E motherboard, I am getting the following execution error trying to start a Windows 10 KVM. All other VM's (Various Linux based) and Dockers are working fine after the upgrade. Execution error Device 0000:00:14.2 not found: could not access /sys/bus/pci/devices/0000:00:14.2/config: No such file or directory ! Not valid! I understand that this error relates to a line in the xml which was working fine with the old mobo, but do not know how to fix the issue. I am attaching diagnostics and the xml and asking if anyone can assist in resolving the issue. Thank you in advance. tower-diagnostics-20240725-0829.zip Sharon-PC xml version.docx

After upgrading my Unraid motherboard to an ASUS ROG Strix X570-E motherboard, I am getting the following execution error trying to start a Windows 10 KVM. All other VM's (Various Linux based) and Dockers are working fine after the upgrade. Execution error Device 0000:00:14.2 not found: could not access /sys/bus/pci/devices/0000:00:14.2/config: No such file or directory ! Not valid! I understand that this error relates to a line in the xml which was working fine with the old mobo, but do not know how to fix the issue. I am attaching diagnostics and the xml and Sharon-PC xml version.docxSharon-PC xml version.docxasking if anyone can assist in resolving the issue. Thank you in advance. tower-diagnostics-20240725-0829.zip

Virt Manager Functionality built in to Unraid. Managing multiple KVM,s with a GUI interface, including snapshot management and the ability to make changes to the config without hosing the xml file would be a great addition to the product. The older Docker versions were fine, but no longer supported.

I decided to leave the array at the new ipaddress so all is complete here. I am still not sure why my flash backup did not contain all of the files, including the go file, but after restoring from a prior backup, I was able to update after the array booted, and all is well. Only app lost was web-virt-manager. Looks like that is no longer an option. I hope Limeteck has plans to provide that functionality somehow going forward. Thanks to all for the help.

So I did copy the Config folder from the backup and then I was able to boot and access the array over the network. So progress here, but somehow the disk configuration got confused and and decided Disk1 of the array was the wrong disk (it wasn't). However I just started the array anyway and the disk is being rebuilt. I would still like to change the ipaddress of the array back to what s was before the upgrade but I will wait on that because at least the upgrade is completed and the array is working. Is there anybody who knows the proper way to change the ipaddress correctly without losing network access, I would be grateful for the info. this would save me the effort of adding port forwards, etc. to the router for the new address and also save me from having to change all of the Wireguard settings for VPN access. In any case, thank you JorgeB for your assistance here.

Those diagnostics were posted before I restored the flash drive from a backup. I used the Unraid creator tool to do the restore and now I realize that the tool does not copy everything from the backup over . One of the things that is not moved over is the go file, amongst others. There is no cat directory, but I was able to look into /bot/config/ and there is no go file. Can I just copy all files from the backup over to the flash drive with another tool and then boot? I have been an unraid user for 10 years and have never been this deep into the weeds. All from trying to change the ipaddress using the network settings. Not sure where to go from here. the server is unuseable if I cannot access the interface.

JorgeB, Thanks for the help, but I do not appear to have a go file. I searched the net for the location of the go file in unraid, and was told it is a file on the flash drive. I checked the flash drive on windows and no go file. I have also just restored the flash drive from a backup I made prior to upgrading the hardware. It boots up fine but the console says that the ipaddress is now 169.254.32.119. However, if I type ifconfig in the console, it says that the br0: interface ipaddress is 10.0.0.158. also, I have no other devices connected to the router with an ipaddress beginning with 169. I also noted that after the server boots, the "Tower" shows up on the windows network, but when I try to access it, windows is saying that the server refused connection. It appears that the network setting are hosed but I am unable to correct. to repeat, everything worked fine after the upgrade until I attempted to change the IPaddress in the Network Settings to the servers former ipaddress. At that point all web connectivity stopped and have been unable to get it back. Thank you again for the help.

Yes, I have tried both http://10.0.0.158 and also https://10.0.0.158 There is a change in the symptoms from yesterday though. Yesterday, the tower never showed as being connected to the router. Today, when I checked the router, it shows the "Tower" connected on ipaddress 10.0.0.158. Bur I still cannot connect via the web interface

Adding Diagnostics File tower-diagnostics-20240701-1656.zip

I would appreciate any insight into my issue. Upgraded my unraid server today with new mobo, ram, and processor. Upgrade was completed in a few hours and I was able to boot into unraid, but noticed on the console that the IPaddress for the server had changed with the upgrade. I was able to access the server over the network with the new ipaddress and all seemed well. All dockers, VM's etc. working, and hardware was working at that point. As I do have port forwards on the router for remote access, I decided to try and change the server ipaddress back to the original one. I went into the Network settings and changed it there per suggestions on the forum. At that point, I lost access to the server over the network immediately and haven't been able to get it back. Things I have done. - changed network config file on the flash back to original post upgrade ipaddress. No help. - rebooted the router multiple times after any change. No help. - renamed network config file on the flash, rebooted unraid, new file created with newyet another ipaddress at boot. Still no access from the network to the new ipaddress. Unraid boots sucessfully every time, shows the ipaddress as last entry on the console, but no access able over the network. Also noticed that when I check the router, the unraid server never shows up as a connected device. I am trying to find out how to produce diagnostics from the command line to add to this note and will do that once i get the correct commands, if possible. Thanks in advance. any help would be greatly appreciated.

The Tower is primarily used as a media server and file storage. The emby docker is used daily. Have streamed movies, TV Shows, etc. since the upgrade. In addition I have used a number of other dockers including Sonaar, Crashplan Pro backup (daily), Diskspeed, and others with no issues or errors in the logs. Have also booted and upgraded a Windows 10 VM. As I was away for Christmas, I also was able to access the Tower (all shares) and via VPM Manager (Wireguard) with no issues. Hope this helps. PS I did backup the flash drive and create a diagnostics report prior to the upgrade as this is a best practice, Didn't need them thankfully.

Upgraded from 6.12.4 to 6.12.6 with no issues. Tower has been running for 10 days with no problems.