Jump to content

mackid1993

Members
  • Posts

    263
  • Joined

  • Last visited

Everything posted by mackid1993

  1. What prints out to the console when you run the mount script?
  2. Well those paths aren't supported by Windows but are fine in Linux so that could explain the crash.
  3. 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.
  4. .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.
  5. 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
  6. 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.
  7. 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.
  8. Yeah it probably doesn't have error handling for that. Windows doesn't like it so virtiofs.exe just dies.
  9. What does this mean for the end user?
  10. I wonder if we could emulate a newer CPU. Emulating Skylake may cause issues with Windows 11.
  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.
  12. That's strange, I personally haven't had any issues although I'm running the beta.
  13. There is a known memory leak with drivers below 248.
  14. Update your virtio drivers.
  15. Ah so the key is <model fallback='allow'>Skylake-Client-noTSX-IBRS</model> does that impact performance?
  16. Do you have an Intel CPU? I've been trying to run WSL on a 12700k for so long now. Is this working now in 7.0.0 beta2?
  17. It's not possible with Windows. The second you enable hyper-v the VM doesn't boot. You have to go in to recovery and run dism /Disable-Feature /FeatureName:Microsoft-Hyper-V /Image:C:\ at a command prompt.
  18. Not sure, maybe try the Unraid beta?
  19. Strange bug, my parity check ran today. My email notification says 1 error. However the Unraid Main page says 0 errors. The duration is also different between the main page which shows 0 errors and the notification which shows 1.
  20. Yup that's it. If you are seeing CPU core spikes and gradual sluggishness with your Windows VM and other VMs you'll want to look into hugepages.
  21. Have you tried on Unraid 7.0-beta1? There are a lot of improvements @SimonF made. If you are still having stability issues try my guide to enable hugepages, you just need enough RAM to always reserve and have to mind any docker containers (usually anything with a database engine) that will use them before the VM can.
  22. Fair enough. Looking forward to an official implementation!
  23. Hugepages also fixes memory fragmentation that causes other VMs not in the shared memory pool to get sluggish.
  24. I got the blank screen and watched the syslog when for it was done. In the second tab I got a prompt to reboot as well. After my server wouldn't boot. I had to put the USB into my PC and run make_bootable.bat and then I was able to boot into Unraid 7 just fine. I was coming from 6.13-beta2.
  25. Just a shot in the dark, maybe try hugepages to see if it helps you.
×
×
  • Create New...