mackid1993

How much memory do you have in total? You may be running out of memory, which will cause a lock up.

Backblaze doesn't work with mapped drives.

I'm not sure where you saw that, the only links in my post are to the source documentation: https://github.com/virtio-win/kvm-guest-drivers-windows/wiki/Virtiofs:-Shared-file-system#multiple-virtiofs-instances and the WinFSP website: https://winfsp.dev/rel/. I'm not sure where the confusion came from but hopefully you can get this set up now. Just to set expectations some have had issues on AMD systems, although there hasn't been a lot of testing done in the community that has been reported. Performance will saturate the Unraid array but nvme to nvme transfers are faster over SMB. In certain situations SMB would perform better. I would suggest creating a shortcut that points to \\yourserver\ to easily access your shares over SMB and pin that to quick access. Also you cannot run executables off of a Virtofs share. it is fantastic for Backblaze Computer backup though... that is an excellent use case.

Configuration script: Another link to my instructions that I already shared: https://forums.unraid.net/topic/129352-virtiofs-support-page/page/5/#comment-1301832

Could something be causing you to run out of memory? Most of the times Unraid has locked up on me was when something was causing the server to completely run of of memory. Misconfigured rclone did this to me once, I didn't set a cache location so it cached to RAM.

I literally shared the guide with you, please take the time to read it lol.

If you follow my guide Virtiofs won't mount with Z. You'd be disabling the Virtiofs service and mounting through WinFSP which will allow you to mount each share as its own drive letter instead of /mnt/user as Z: which is more natural for Windows. It's really just running a batch file with Task Scheduler after the initial setup.

I tried to make it as straightforward as possible.

On Windows:

I have never seen this. Maybe check the file permissions on the server.

FYI anyone having issues getting their VM's to start in 7.0.0.-beta3 see here: TL;DR run: sed -i 's/$options\[\] = "--fd=".$argoptions\['"'"'fd'"'"'\];/if (isset($argoptions\['"'"'fd'"'"'\])) {\n $options[] = "--fd=".$argoptions\['"'"'fd'"'"'\];\n}/' /usr/local/emhttp/plugins/dynamix.vm.manager/scripts/virtiofsd.php and insert into /boot/config/go to make persistent. (ie, nano /boot/config/go and paste this line in) just remove it prior to the next release.

Maybe test in another VM to see if it's Windows or Unraid. Also perhaps maybe something got messed up in your XML. I've seen Virtofs shares refuse to mount because something in the xml got messed up. You can try recreating the VM template.

That sounds like it mounted. When you are using this script the service is not supposed to start so those events make sense. Information: "launcher-x64: terminated virtiofs\viofsZ" looks like something is killing the process. This looks like something within the VM to me. Maybe try the newer virtio drivers.

What prints out to the console when you run the mount script?

Well those paths aren't supported by Windows but are fine in Linux so that could explain the crash.

It's possible you have some file names/paths that are over 255 characters long. Windows doesn't support this and it will cause VirtioFS to crash. Something like this may help: https://github.com/deadlydog/PathLengthChecker ViritoFS is totally stable, I've been using it for months and months with zero crashes and have 10 TB backed up to Backblaze. It's something else causing your issues.

.248 Virtio drivers. WinFSP 2.0.23075. Maybe go into device manager and make sure the Virtiofs device is not using an older driver sitting in the driver store. I've seen that before.

I have mine set up with individual drive letters for each share, and Backblaze has been stable for several months now. I have 10 TB backed up

I've been running 7 since it was the 6.13 closed beta and have had only minor issues. Not even a crash. I suggest trying Unraid 7 and see if it helps. If not roll back.

Just a suggestion. Buy an nvme drive, bind it to VFIO and pass it through over PCIe to your VM. Use a disk cloning tool such as Macrium Reflect to clone your vidsk to the nvme drive. Then boot baremetal into the nvme drive and play Roblox. Plug a monitor, mouse and keyboard into your server.

Yeah it probably doesn't have error handling for that. Windows doesn't like it so virtiofs.exe just dies.

What does this mean for the end user?

I wonder if we could emulate a newer CPU. Emulating Skylake may cause issues with Windows 11.

255 characters is the path limit for Windows but it doesn't matter so much for Linux. Perhaps you were over that limit hence the crash.