jlficken

@Squid Do you have a link to the virtio guest tools install or are you talking about the guest-agent directory on the ISO? (quemu-ga-x86_64.msi)?

Yeah I can't really replace the card as there's no 8-pin/6-pin supplemental power option in the Supermicro CSE-846 which is why I used the Inno3D card as it doesn't require supplemental power and no other company makes a single slot 1050 Ti. Finding another card really isn't an option right now with the global GPU shortage either. Inno3D is a huge company though and has been around since the 90's. I remember using their GPU's back when Packard Bell was still around. https://www.inno3d.com/static.php?refid=1 I have IPMI on the server so I can view the console and run that command to see what happens if I can get it to crash. ETA: I also Isolated the CPU cores that are dedicated to the VM yesterday and stopped passing through a USB DVD drive. I have ordered a PCI-E USB 3.0 card and will pass the entire card through instead when it arrives on Tuesday.

I give up as I have no idea what to try. UnRAID is just going to be my NAS from now on and I'll just keep a gaming/work PC around as having the entire server crash when simply shutting down or rebooting a VM is unacceptable.

Do I still have to pass the vBIOS to the VM? I've been having issues with GPU pass-through and a 1050 Ti where restarting/shutting down a VM will kill the entire unRAID server requiring a restart and parity rebuild. With 14TB drives that very frustrating. I want to try with this new feature to see what happens as I'd love to have a stable VM with GPU pass-through. ETA: It appears you can leave off the vBIOS if you switch to VNC, start the VM, stop the VM, and then switch to GPU w/o specifying the vBIOS ROM. I just got a black screen if I didn't start the VM in VNC mode first. Now to see if my VM issue goes away.

So I take it I'm the only one having this problem? Since disabling GPU passthrough I've restarted the VM multiple times as well as shut it down with no issues so I have no idea what the problem is. The ROM file came from my GPU using the SpaceInvaderOne script so I'm hoping that's not the problem. I've tried the TechPowerUp one for my card as well.

Can you think of any way to track down why a VM won't start after using the Hex editor process you mention to "fix" a BIOS dumped from GPU-Z? I have attached the original file dump and I removed everything above: UªxëK7400éLwÌVI ETA: I'm trying to figure out why I can use the file direct from TechPowerUp and the VM will boot but a reboot/shutdown of the VM crashes my entire server yet I can't edit the VBIOS that I've attached and have it allow my VM to function at all. I get this when I change my GPU ID to the correct one and run the script from GitHub: ........ Removing the temp vm Domain dumpvbios has been undefined Okay dumping vbios file named GeForce GTX 1050 Ti to the location /mnt/user/isos/vbios/ cat: rom: Input/output error ........ ETA: I did bind the video and audio through the interface for VFIO and have rebooted the server several times. ETA 3: I changed the forcereset setting to no and then it worked. The working ROM has been attached for anyone needing it. Now if I can just figure out why unRAID locks up when I restart /shutdown VM's with GPU Passthrough 😞 Inno3D.GTX1050Ti.4096.161227.rom

I tried using a 1050 Ti back in 6.8.3 and this happened as well. I had hoped that moving to 6.9.1 would fix it but I guess not 😞 I decided to try it again now that I'm on 6.9.1 and it did it again. Every time I have to run a Parity Check which takes 25+ hours. I've tried both machine types to no avail. It never does this when I don't have GPU passthrough enabled. Any thoughts as I'm at the end of my rope with this? fsnas1u-diagnostics-20210401-1053.zip

I just wanted to say thank you very much for making this as well as the Previous Apps option in CA. It saved my butt tonight!!!

Got the above error fixed by simply rebooting unRAID but I'm getting this now. 2021-03-25 17:47:08 information: /mnt/user/VMBackups/FSWin10PVM does not exist. creating it. mkdir: created directory '/mnt/user/VMBackups/FSWin10PVM' /tmp/vmbackup/scripts/default/user-script.sh: line 424: vdisk_types["$vdisk_path"]: bad array subscript 2021-03-25 17:47:08 information: finished attempt to backup FSWin10PVM to /mnt/user/VMBackups. 2021-03-25 17:47:08 information: cleaning out logs over 1. 2021-03-25 17:47:08 information: did not find any log files to remove. 2021-03-25 17:47:08 information: cleaning out error logs over 10. Any thoughts? The backup worked once but won't work again. ETA: I figured it out. It happened because I removed the OS Install ISO path from the VM setup. Once I put it back in the backup worked again.

I removed it and then decided to reinstall but can't. I get this error:

Having the virtio-win-0.1.185.iso assigned to the machine is absolutely vital I discovered as I was just using virtio-win-0.1.171.iso and couldn't get it to work with my Inno3D 1050 Ti. I changed over to the latest version and it started working immediately.

Is anyone else noticing that the Cache Pool size isn't showing correctly now? It shows correctly initially but then for example mine goes from 76.9GB used down to 36.7GB used My docker.img and libvirt.img have a combined size of 53.6GB and reside on the Cache Pool so I know it's wrong.

Yup. I did and changed it to only include certain shares. Sorry for the trouble!

@dlandon It appears that uninstalling the Cache Dirs plugin stopped the messages.

MTU is set to 1500 in unRAID.

Here you go: diagnostics-20210306-2101.zip

It appears that I'm getting this error on one of remote servers where I have SMB shares mapped. Any thoughts or info I can get you to help troubleshoot? I've rebooted the remote NAS as well as restarted unRAID. Mar 5 09:59:12 FSNAS1U kernel: CIFS: VFS: \\192.168.1.41 Cancelling wait for mid 43247 cmd: 5 Mar 5 09:59:12 FSNAS1U kernel: CIFS: VFS: \\192.168.1.41 Cancelling wait for mid 43248 cmd: 14 Mar 5 09:59:12 FSNAS1U kernel: CIFS: VFS: \\192.168.1.41\Sync Close unmatched open for MID:a8ef Mar 5 10:03:42 FSNAS1U kernel: CIFS: VFS: \\192.168.1.41 Cancelling wait for mid 137315 cmd: 6 Mar 5 10:03:42 FSNAS1U kernel: CIFS: VFS: \\192.168.1.41\Sync Close interrupted close

Has anyone had any luck getting it to work when on it's on a different VLAN than the UnRAID server behind the LetsEncrypt NGINX reverse proxy?

My P2000 seems to be working now...thanks! I have noticed that the feed in the interface seems to glitch out for some reason (for a few seconds and then comes back) and I haven't been able to figure that out yet.

I'm in for the solution to getting my P2000 to work! Once I get it to work I'll be moving away from Blue Iris.

Thank you for this!!!!!

I still have the problem that I mentioned earlier in this thread. Does anyone have any ideas?

I'd like Snapshots followed by Multiple Arrays. Snapshots are a must IMO for UnRAID to be adopted by small businesses. I put in a ReadyNAS at work simply due to Snapshots and the cryptolocker viruses. At home I use UnRAID as primary but have a ReadyNAS for backups just for snapshots.

Disregard....I'm an idiot.

Is there any way to send attachments with the notify script? I'd like to send the rsync log with the e-mail if possible.