Jump to content

bastl

Members
  • Content Count

    567
  • Joined

  • Last visited

Community Reputation

63 Good

4 Followers

About bastl

  • Rank
    Advanced Member

Recent Profile Visitors

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

  1. Just to clear things up, isolating cores means you isolate them from unraid to use. Core 0 is ALWAYS used by unraid itself, no matter if you isolate them or not or using it by a VM or docker. Unraid will always use that core for itself. @thatnovaguy I have a 1950x and have the following cores isolated. All these cores are used by my main Windows 10 VM for almost 2 years now and I also use a 1080ti and a NVME in this VM. No issues or performance degredations so far. How much RAM do you have and how much is assogned to that VM? Edit: What does the Windows defragmentation tool shows you? And please post your xml of that VM.
  2. most of the time is a sign the USB disk is broken. You still can read files most of the time, but writing to it or even formating it will always fail.
  3. The chipset in the VM isn't a AMD chipset or Intel nor is it possible to directly set it to the exact one your board is using. Chipset drivers never will be installable inside a VM like on a bare metal system. So you loose some features like controlling your fan or RGB controllers, flashing BIOS with software from inside the VM etc. Most of the stuff you have to set in the BIOS (fan speed, RGB, OC etc.) EDIT check the clock speeds of your CPU if the VM is running with the following command on Unraid to see which core is running at which speed. The speed the windows task manager or other tools are reporting are wrong. watch grep \"cpu MHz\" /proc/cpuinfo
  4. If you have a mirrored cache with 2 SSDs you will be save if one drive fails. On an unassigned device this isn't the case. There is no option yet to mirror devices in an RAID using unassigned devices. If you only use 1 cache device you also don't have any safety. If the drive fails, your data is gone. Having a VM on the array with a parity of one or 2 drives you won't have the performanceas on a single drive, also to be mentioned, the array doesn't support SSDs. You can use them in an array, but TRIM won't work and the drives will get slow relativly quick if you have lots of r/w operations on it. There are a couple options to backup your VMs. There are scripts available you can use to backup the vdisks and the xml of the VMs on a scheduled plan or you use a BTRFS formatted drive hosting the vdisks and use the BTRFS snapshot feature to "backup" your vdisks.
  5. Try the MSI_util on the passed through controller. It's a a PCI device and should work the same way as with a PCI audio device. Maybe that fixes it for you.
  6. You can give a VM a dedicated SSD via passthrough so it can utilize the whole disk. No other VM/docker is able to use it than, also unraid can't use it. This is one option, if you want a VM with a "real" harddrive/ssd. The question is, is a VM working with a OS already installed on that SSD before? For example let me explain my switch to unraid. I'am using a 16core AMD TR4 chip and had a Win10 installed on an NVME drive. After stumblin across Unraid and playin around with it, the first try passing through that NVME to Windows VM workted perfectly fine. Drives recognized and windows booted from it. In an worst case scenario where unraid won't boot up, I still can boot directly from that NVME and have my main system. I never did that with a "real" Linux install, passing that drive to a VM. You might run in some driver issues. Other option is to have a vdisk sitting on the SSD used by the VM. Doesn't really matter if the SSD is used as a cache drive or a unassigned device, the performance is almost the same as in a real system. Keep in mind if it sits on a cache drive, copying files to unraid and having a VM running at the same time are multiple operations at the same time and can slow down the r/w performance in parallel operations.
  7. For crackling sound, mostly happens on GPU passthrough with HDMI audio there is a fix. Search for "MSI util" in the forums or for crackling sound fix and you will find the tool. I don't know if there is a solution for MacOS, but that tool works for windows just fine.
  8. Sounds like a power saving issue in your VM. Set your power plan to high performance in the VM and try again. Windows on default powers down unused devices after a while to save energy. USB devices and harddrives are goin to a "sleep" state and can cause that issue. Connected devices like USB thumbdrives or hdds rarely have issues with this, but some USB splitters or external sound devices won't wake up again.
  9. VNC doesn't transfer sound neither emulated nor hardware sound. RDP and Nomachine are the only ones i know where you can use sound. Nomachine itself installs its own virtual soundcard if I remember correctly and RDP is emulating one too. You don't need to specify/change anything in the default xml unraid creates to use it.
  10. You might wait till the next platform releases, to see which new features they offer which are missing on x399. I guess PCIe 4.0 is one of it, maybe onboard 10gig nics and the amount of PCI lanes are a important info for the future x499/x599 we are missing right now. Also the TDPs of the next Threadripper chips I'am kinda curious. On older boards the VRMs might not be enough to handle high core count next gen TR4s. Better wait for the first boards and tests.
  11. Thats board/vendor specific. You might have to search the specific forums to find an answer how to flash an older BIOS version for your motherboard or contact AsRock support directly.
  12. You might have another issue a couple people already reporting. Newer BIOS revisions for AM4 on different boards have that issue. Reverting back to an older Bios version is the only fix currently. If you search the forum there are a couple more posts about this topic.
  13. IOMMU groups can change with a BIOS update. Make sure you pass through the right devices. Also the core numberings can change.
  14. You can mount it to a Linux VM and try to recover important files if you need to. Recover a corrupted vdisk file itself, I don't know if there is a way. If you aren't able to mount the vdisk to a VM and can't access the filesystem, the chances are really low to get any data back. For the future, here is a easy way to backup your VMs via script. Have a look into it. I'am using Jtoks script over a year now and it just works. If you need to recover a VM just replace the vdisk with the file from the backup. With the plugin userscripts you can run the script automated every day, week or how you like. Add the path where to store the backup, the name of the VM you wanna backup and some options for example how many backups to keep, reset state of the VM after the backup, compression etc. https://github.com/JTok/unraid-vmbackup