T-Beacham

I was able to resolve the issue myself. I noticed my cache drive was full, which led me to look into how to move from the cache to the array. The defaults were to keep the domain on the cache without moving to the array, which normally wouldn't be an issue but the drive I used for the cache was a 120Gb SSD I had on hand. This was keeping the VM from launching as it was overallocated. I switched the defaults for my various shares to move to the array and was able to run the mover (which wasn't running previously due to the default settings on the shares). After running mover, I had free space on the SSD and my VM was able to boot. I will look into getting a larger cache drive. I presume I will be able to move my VM domains back onto the larger cache later so I am not running them off of the slower HDD array?

Hello, I am new to UnRaid and have just setup my first server using it. I have some experience with computers but I have little to no coding knowledge and am not well versed in networking lingo. I was able to get a Windows 10 VM setup and running with all required drivers and got the GPU passthrough to work after some issues by referencing online tutorials and watching Spaceinvader One videos. Last night the VM appears to have crashed and is now freezing on boot. The VNC still launches and the recovery screen does popup after 3 failed launches but I am unable to interact with it. I believe the vdisc is corrupted due to the unexpected crash but I am not entirely certain of this. Does anyone know if this sounds right, or if they know of a separate issue that might explain this issue, and could explain how to amend this issue in such a way as a beginner such as myself can understand and follow. Basically, assume I know nothing. Let me know any screenshots or information I may need to provide to help diagnose this issue. Thank you!