Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

52 Good


Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. @SpecFroce One or two users have reported switching the machine type to Q35, they are able to use newer drivers. Maybe worth a try setting up a new VM to test.
  2. I did a couple more tests and another thing what I noticed with 1903, as soon as I login with a user no matter if I use VNC or RDP all cores spike up to 100% for maybe 20-30 seconds. A short spike is normal but this amount of load is unusual. Remember it's a fresh install without any passthrough. I went a bit further and stripped down the install iso and removed a couple of the junk, all the useless apps and services and preconfigured the install, removed or disabled all the tracking functionality as far as I know of. Same behaviour. After the first login it looks like everything settles down and works as normal, only the first seconds the cores are all pegged more than on older versions. Not exactly sure what causes this, maybe microsofts newest implementations to prevent all the spectre meltdown zombieload attack surfaces. Maybe on older CPU architectures like on Piledriver and Bulldozer in a virtual environment this is an issue now. Let's hope maybe some other users can report back if they have the same issue as you on similar hardware. Have you tried it with Q35 as machine type instead of i440fx? @Tucubanito07
  3. @AntaresUK The 2 best choices are still VirtIO and SCSI and is adviced by the Unraid team. Both have the least amount of overhead but for both you need the drivers during the OS install. Windows doesn't have any drivers for these devices out of the box. The advantage of SCSI is you can pass through trim operations from within the guest to the host. This isn't possible with SATA or IDE devices. Windows in this case is aware of an underlying SSD an optimizes the disk like a normal SSD. For older operating systems and some linux distros only SATA devices are recognised.
  4. On a clean fresh install of 1903 I don't see any issues like yours. The only thing I had is on a local account on first login OnDriveSetup.exe pegged all the cores, in my case to 100% for maybe a minute. Also some Windows apps had to update itself + 3 or 4 Windows updates needed to be installed on a fresh install. 4 vcpu's, 8GB RAM, 30GB vdisk scsi the rest is on default and no passthrough.
  5. @MothyTim Does it happen if you dissable all your docker?
  6. let it run a couple hours. More is better. Fingers crossed 😉
  7. That's the usual behaviour if you started memtest in uefi mode not in bios/legacy mode. Are you sure you made the right selection in your boot menu? F11 F12 or whatever it is on your board and select the USB stick without the uefi option
  8. You're not able to boot unraid in legacy mode because it crashes? Did you get the boot selection where you can choose unraids boot options and the memtest option or does it crash when selecting memtest?
  9. Try to boot your Unraid USB stick in legacy mode not uefi. This way memtest should work.
  10. Is your CPU overclocked and your RAM? Maybe try to turn back your OC and check if it's stable or try to run the memtest for a while.
  11. From your screenshots above if you're running your 3 VMs at the same time you allocating 15GB of your 16 available. 1GB for Unraid itself and all the dockers is definitly to little. Without the Ubuntu VM and only the Windows and PBX VM running you shouldn't have any issues if your dockers are setup correctly.
  12. bastl

    Dup Files

    dup-xxxxxx files are created by duplicati. Check which folders you have mounted in your duplicati docker or which folder you selected in a duplicati client to save your backups in. I bet you've mounted the /mnt/user instead of a sub folder.
  13. Please add the the pci ids of your card to your syslinux config so unraid won't pickup the card and restart the server. Go to main tab and click "Flash". There you find the config. Example of my entry for the default boot option without pci ids: append isolcpus=8-15,24-31 pcie_aspm=off initrd=/bzroot and with ids added: append vfio-pci.ids=10de:1b06,10de:10ef isolcpus=8-15,24-31 pcie_aspm=off initrd=/bzroot If you are on 6.7 you can also try the new method with BIND instead.
  14. Can you please setup a VM without any devices like GPU or sound/mouse/keyboard, only VNC? Basic install, nothing else. Enable RDP or install Teamviewer or Nomaschine and make sure you can connect to the VM. After that shut down the VM, add your GPU + GPU audio and start it up.