-
[Plugin] FolderView Plus
Yes exactly. Just checked after updating to v2026.04.06.19 and now it works :)
-
[Plugin] FolderView Plus
Sorry, it doesn't seem to work for me. Tried setting the order to manuel and picked the order below but it seems still to be locked in the old format. I cleared cache, tried inkognito mode in an other browser just to be sure. FolderView Plus Support Bundle-2026-04-06T19-07-26+00-00.json
-
[Plugin] FolderView Plus
FolderView Plus Support Bundle-2026-04-06T12-57-11+00-00.json
-
[Plugin] FolderView Plus
I've tried clearing the cache but it didn't help, i dont seem to be able to change the order of the folders. I've tried both A-Z and Manual. In the settings i set the following order. But refuse to change, even when setting it manually.
-
Unraid 7.1.4 docker and vm view becomes unresponsive after a couple of days.
Hi I've gotten a new issue that i've never had before and it's driving me nuts. After about 5-6 days after a fresh reboot my vm / docker manager stopps working, i'm unable to see the vms or dockers it just loads forever. The docker and VMs still work without a problem so that's fine. I just can't view them. If i try to go into the plugin settings the whole gui crashes and i'm unable to reach the web gui for about 5 minutes and then it comes back. If i reboot the unraid server everything works just fine for a couple of more days. I have a backup running at 3 am so thats why the dockers restart at this time. I've included the logfiles. The problem came after upgrading to 7.1.4 graphql-api.txt libvirt.txt syslog.txt syslog-previous.txt vfio-pci.txt
-
Passthrough and new disk to VM doesn't work after drive failure. I'm at a loss.
I've now tried everything to add a new drive just to get that to work but i'm unable to, so it feels like it's bugged? No errors in the logs and not even the passthrough work? Could it be a driver issue? I've tried different versions but still nothing.. :( EDIT1: I tried creating a new VM, and on that vm i have no issue adding a new drive. Then i do the exact same on the old VM and it just doesn't work.. EDIT2: Kind of solved it, tried cloning the VM. And in the new clone the passthrough and adding of a new disk works. compared the .xml files of both and the only difference i can see is in the pci configuration.
-
Passthrough and new disk to VM doesn't work after drive failure. I'm at a loss.
Hi I'm desperate, i don't know why this happend, i lost one of my NVME drives in my unraid server. The good thing is that the only thing it was hosting was the iso share and a vm .img drive that only stores temporary files. So nothing lost. So i just swapped out the NVMe for a new one. Redownloaded the correct Virto driver ISO so it's the same version as before. Created a new hdd. on this drive and now comes the issue. I can't see it inside the OS, and the 2 other NVMe drives that i was using passthrough with stopped showing aswell.. I'm lost. I've tried reinstalling the driver pack but it doesn't help. Nothing should have changed, have no clue why the 2 passthrough drives stopps showing just because the D: drive shit the bed. 1. New drive mounted. 2. Can see that the .img is created. 3. Can see that the drive is stored on the correct drive. The size is 200GB. 4. Same driver version pack as worked this morning, can see the correct path to the new .img drive. In the bottom you can see that it sees the 2 nvme drives i've passthroughed. Looks just like it did when it worked before. 5. In windows it's missing the drives. A & B was the NVMe drives that was passthroughed and D: was the .img drive that crashed. 2025-07-25 20:08:16.905+0000: starting up libvirt version: 11.2.0, qemu version: 9.2.3, kernel: 6.12.24-Unraid, hostname: UNR-FS01 LC_ALL=C \ PATH=/bin:/sbin:/usr/bin:/usr/sbin \ HOME=/var/lib/libvirt/qemu/domain-6-qbit-w10 \ XDG_DATA_HOME=/var/lib/libvirt/qemu/domain-6-qbit-w10/.local/share \ XDG_CACHE_HOME=/var/lib/libvirt/qemu/domain-6-qbit-w10/.cache \ XDG_CONFIG_HOME=/var/lib/libvirt/qemu/domain-6-qbit-w10/.config \ /usr/local/sbin/qemu \ -name guest=qbit-w10,debug-threads=on \ -S \ -object '{"qom-type":"secret","id":"masterKey0","format":"raw","file":"/var/lib/libvirt/qemu/domain-6-qbit-w10/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/117a1a67-f8e4-632d-917f-eacf58cd4e15_VARS-pure-efi.fd","node-name":"libvirt-pflash1-storage","read-only":false}' \ -machine pc-q35-7.2,usb=off,dump-guest-core=off,memory-backend=pc.ram,pflash0=libvirt-pflash0-format,pflash1=libvirt-pflash1-storage,hpet=off,acpi=on \ -accel kvm \ -cpu host,migratable=on,hv-time=on,hv-relaxed=on,hv-vapic=on,hv-spinlocks=0x1fff,hv-vpindex=on,hv-synic=on,hv-stimer=on,hv-vendor-id=none,host-cache-info=on,l3-cache=off \ -m size=8388608k \ -object '{"qom-type":"memory-backend-memfd","id":"pc.ram","share":true,"x-use-canonical-path-for-ramblock-id":false,"size":8589934592}' \ -overcommit mem-lock=off \ -smp 8,sockets=1,dies=1,clusters=1,cores=4,threads=2 \ -uuid ***censored*** \ -no-user-config \ -nodefaults \ -chardev socket,id=charmonitor,fd=38,server=on,wait=off \ -mon chardev=charmonitor,id=monitor,mode=control \ -rtc base=localtime \ -no-shutdown \ -boot strict=on \ -device '{"driver":"pcie-root-port","port":8,"chassis":1,"id":"pci.1","bus":"pcie.0","multifunction":true,"addr":"0x1"}' \ -device '{"driver":"pcie-root-port","port":9,"chassis":2,"id":"pci.2","bus":"pcie.0","addr":"0x1.0x1"}' \ -device '{"driver":"pcie-root-port","port":10,"chassis":3,"id":"pci.3","bus":"pcie.0","addr":"0x1.0x2"}' \ -device '{"driver":"pcie-root-port","port":19,"chassis":4,"id":"pci.4","bus":"pcie.0","addr":"0x2.0x3"}' \ -device '{"driver":"pcie-root-port","port":20,"chassis":5,"id":"pci.5","bus":"pcie.0","addr":"0x2.0x4"}' \ -device '{"driver":"pcie-root-port","port":21,"chassis":6,"id":"pci.6","bus":"pcie.0","addr":"0x2.0x5"}' \ -device '{"driver":"pcie-root-port","port":22,"chassis":7,"id":"pci.7","bus":"pcie.0","addr":"0x2.0x6"}' \ -device '{"driver":"ich9-usb-ehci1","id":"usb","bus":"pcie.0","addr":"0x7.0x7"}' \ -device '{"driver":"ich9-usb-uhci1","masterbus":"usb.0","firstport":0,"bus":"pcie.0","multifunction":true,"addr":"0x7"}' \ -device '{"driver":"ich9-usb-uhci2","masterbus":"usb.0","firstport":2,"bus":"pcie.0","addr":"0x7.0x1"}' \ -device '{"driver":"ich9-usb-uhci3","masterbus":"usb.0","firstport":4,"bus":"pcie.0","addr":"0x7.0x2"}' \ -device '{"driver":"virtio-serial-pci","id":"virtio-serial0","bus":"pci.2","addr":"0x0"}' \ -blockdev '{"driver":"file","filename":"/mnt/user/domains/qbit-w10/vdisk1.img","node-name":"libvirt-3-storage","read-only":false,"discard":"ignore","cache":{"direct":false,"no-flush":false}}' \ -device '{"driver":"virtio-blk-pci","bus":"pci.3","addr":"0x0","drive":"libvirt-3-storage","id":"virtio-disk2","bootindex":1,"write-cache":"on"}' \ -blockdev '{"driver":"file","filename":"/mnt/slask/qbit-w10/vdisk2.img","node-name":"libvirt-2-storage","read-only":false,"discard":"unmap","cache":{"direct":false,"no-flush":false}}' \ -device '{"driver":"virtio-blk-pci","bus":"pci.4","addr":"0x0","drive":"libvirt-2-storage","id":"virtio-disk3","bootindex":2,"write-cache":"on","serial":"vdisk2"}' \ -blockdev '{"driver":"file","filename":"/mnt/user/isos/virtio-win-0.1.225-2.iso","node-name":"libvirt-1-storage","read-only":true}' \ -device '{"driver":"ide-cd","bus":"ide.1","drive":"libvirt-1-storage","id":"sata0-0-1"}' \ -netdev '{"type":"tap","fd":"39","vhost":true,"vhostfd":"41","id":"hostnet0"}' \ -device '{"driver":"virtio-net-pci","netdev":"hostnet0","id":"net0","mac":"52:54:00:e6:4d:6a","bus":"pci.1","addr":"0x0"}' \ -chardev pty,id=charserial0 \ -device '{"driver":"isa-serial","chardev":"charserial0","id":"serial0","index":0}' \ -chardev socket,id=charchannel0,fd=37,server=on,wait=off \ -device '{"driver":"virtserialport","bus":"virtio-serial0.0","nr":1,"chardev":"charchannel0","id":"channel0","name":"org.qemu.guest_agent.0"}' \ -device '{"driver":"usb-tablet","id":"input0","bus":"usb.0","port":"1"}' \ -audiodev '{"id":"audio1","driver":"none"}' \ -vnc 0.0.0.0:0,websocket=5700,share=ignore,audiodev=audio1 \ -k en-us \ -device '{"driver":"qxl-vga","id":"video0","max_outputs":1,"ram_size":67108864,"vram_size":67108864,"vram64_size_mb":63,"vgamem_mb":64,"bus":"pcie.0","addr":"0x1e"}' \ -global ICH9-LPC.noreboot=off \ -watchdog-action reset \ -device '{"driver":"vfio-pci","host":"0000:04:00.0","id":"hostdev0","bootindex":3,"bus":"pci.5","addr":"0x0"}' \ -device '{"driver":"vfio-pci","host":"0000:05:00.0","id":"hostdev1","bootindex":4,"bus":"pci.6","addr":"0x0"}' \ -sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny \ -msg timestamp=on 2025-07-25 20:08:16.905+0000: Domain id=6 is tainted: high-privileges char device redirected to /dev/pts/0 (label charserial0) 2025-07-25T20:20:27.555934Z qemu-system-x86_64: warning: no scancode found for keysym 246
-
System and Domain missing after upgrade to 7.0.0
Yea i should have. I downgraded back to 6.12.4 and now everything works again.
-
System and Domain missing after upgrade to 7.0.0
Hi Just upgraded to 7.0.0 and after the upgrade it seems that the share domain and system is missing. They were located on it's own SSD. But something is just off after the upgrade. I'm unable to recreate the share. System, iso and domains are missing. The vm service is unable to start because of the missing shares. The VM Manager is still says the path is missing. When i try to recreate the system share. I also see now that one of my nvme drives is not working, because i have a share missing. It also has a wierd SCSI Device name:
-
[Plugin] Appdata.Backup
You can just add a post backup script that zip the files.
-
Hide the EDIT button when not in "dashboard editing mode"
Hi As the title refers to. Would like to request that the "EDIT" button is hidden when you're not actively editing the dashboard.(Locked/unlocked Dashboard)
-
[Plugin] Appdata.Backup
I only see the option to get a notification when an error / warning has occurred, not when the backup finished successfully.
-
[Plugin] Appdata.Backup
Would it be possible in the future to make the applicaton to use unraids notifications system? Im using pushover and would love to get notifications when backups have run or if they failed.
-
[Plugin] Appdata.Backup
Didn't know you could click on each docker to see the mounts. Change the source to \mnt\"drivename"\appdata Now everything gets backuped like it should. Thank you!
-
[Plugin] Appdata.Backup
Hi I just updated to the new app. I have a problem where it only backs up 2 out of my 7 dockers. For the 5 that doesn't work i get this message. Debug Code: fe870bc2-9d17-4c2b-88e3-6b0882f98a4f [09.09.2023 09:32:38][ℹ️][homeassistant] Stopping homeassistant... done! (took 5 seconds) [09.09.2023 09:32:43][ℹ️][homeassistant] Should NOT backup external volumes, sanitizing them... [09.09.2023 09:32:43][ℹ️][homeassistant] homeassistant does not have any volume to back up! Skipping [09.09.2023 09:32:43][ℹ️][homeassistant] Starting homeassistant... (try #1) done! The source path is \mnt\user\appdata and if i browse to the path i see data in all 7 docker folders so i have no clue why only some of the works.
Luke_Starkiller
Members
-
Joined
-
Last visited