Jump to content

metathias

Members
  • Content Count

    23
  • Joined

  • Last visited

Community Reputation

7 Neutral

About metathias

  • Rank
    Member

Recent Profile Visitors

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

  1. Interesting. The ACS override, and VFIO unsafe are known to both be very unstable and could be an issue. While in my limited attempts to use ACS override it did function to allow me to split off devices not normally allowed to do (more IOMMU groups) When attempting to separate those things into either separate VMs or just one VM (taking the bus away from just Unraid) would cause hanging, halting, And other ghostly phenomenon. As for your USB drive not showing up without UEFI enabled. Sounds like a bios settings might have something to do with that. Try to find a legacy/compatibility mode for your bios to turn off UEFI altogether on the BIOS side. Also clearing your boot keys might be necessary (Its seems like every generation they try to make it harder just to turn UEFI off) Then confirm the USB device is showing up in your bootable options in the BIOS. You might also through your bios carefully for IOMMU related options (there should be one somewhere) I looked through your MB manual for your motherboard (ROG Strix X570-E Gaming) and it was pretty useless for bios settings info. So you might have to hunt a bit to find the options your looking for.
  2. Passing a USB device through to a VM using the Form view ticker method is pretty inconsistent. Something i try to do as little as possible. What i've done for a USB drive based VM is to use the manual Primary Vdisk Location method. And direct the path to the device-id of the drive. Like so. Supplementing your specific drive after the /dev/disk/by-id/ Using this method the VM will have total access to the drive as a SATA style device. Allowing you to format and partition it how you see fit. Also has the side benefit of storing the data as actual separate file data instead of a .vdisk img of the data. Edit - You can look up your exact device-id using the unraid terminal. Just execute "cd /dev/disk/by-id" command at root And then execute "dir" to get a listing of all the drives available to you. Make sure to use the first listing of your device. The one without the part whatever at the end.
  3. Unraid not being bootable without UEFI sounds a bit odd to me. Its bootable either way for me. Having it on presented a host of issues for me in the past (Cant speak for recent versions of unraid). The most notable of which was the inability to actually grab the video card from unraid and give it back when the VM was strarting/ending. When i speak of a malformed XML i am speaking to a possible misconfiguration or incompatibility with a setting you have set in your VM. Perhaps you could post a copy of your VMs XML. And a copy of your IOMMU groups for further examination.
  4. Sorry to hear that. Based on where your system seems to start showing issues AFTER the VM attempt to boot. The most likely culprit is a malformed VM config XML. Through this thread im seeing quite a few suggestions to use all manner of hacks. Which should not be necessary AFAIK at this point in time. Im pretty sure Unraid gladly gives up the primary GPU for instance so long as you dont use UEFI, And dont run the graphical version of unraid on boot. To enjoy VM rebootability though you have to deploy the VM with a link to its Vbios.
  5. I dont think your gonna find anything hardware specific for your chipset in any of the current builds. So the previous build should be pretty much the same (compatibility wise). For how difficult it is to try the lower versions. 6.5 or 6.6 (Not very). Its worth a shot IMO.
  6. Are you running 6.7? And the parity build/sync is going? If so I would be willing to bet it is the 6.7 File system performance bug many of us have been experiencing.
  7. Supposedly its fixed in 6.8 but that has'nt been released yet. Soon they say. There have been significant changes to the underlying kernel in recent iterations. It is very difficult to keep up with the latest and greatest patchs, and feature improvements that go into it. And unfortunately some of those underlying systems have changed significantly just in the past few iterations. Which has a tendency to break things in unexpected ways. You have to keep in mind that the technologies being employed on Unraid. Such as the new KVM with passthrough support are bleeding edge new software. And have only been practical for a couple years now. But i can say from using it for the past 14 months of so. Its been as absolute god send of an OS. And has been really incredibly flexible environment for me to work, play, and experiment in. With next to no down sides. Other than my wife and childs VMs are taking up all my cores =P. And to be totally fair. A downgrade is like the easiest thing in the world. You throw all your current file from the USB drive into a backup folder on the drive (a 4GB thumb drive can store the entire OS like 4x with that) And then just unzip the downgraded zip files right in the root. Bam downgraded. Just dont forget to copy and paste in your license file.
  8. I actually have one VM sitting directly on the cache drive as an image. Another gets passed through an NVMe drive. The last and latest one currently manul method described above. All of the above work great at the same time. So long as the resource distribution is not overly optimistic. I save about 80% 20% of my total ram (currently only 32GB) to unraid and for a few dockers.
  9. Ahh ok. Yes that the way i pass through my SSDs as well. The hanging your experiencing in Unraid seems to me. Very likely a lack of resources on unraids part somewhere. Or the 6.7 bug that choking everyones bandwidth to death when it start doing multiple parallel file operations. To be honest im still running 6.5.x .
  10. I do wonder exactly what you mean by Unraid crash's. Do you get a full system reset back to post? I've yet to have unraid actually crash on me. Its possible that by passing through a SATA controller the system might become destabilized. As far as my system goes (X399 Asus Prime board, With Threadripper 1950x) There are no SATA ports that get IOMMUs that dont also have several system critical parts attached to them. Thus disabling me from attempting to passthrough a SATA controller directly. Instead i use VMdisks Which have dedicated SSDs meant to host only those singular images (1 SSD per VM).
  11. Sorry to hear that. Unraid is certainly not for the faint of heart. Particularly the KVM aspects. And to be honest that why the trial license is a reasonable way to allow people to attempt to make it work for them without being on the hook immediately for the cost of the OS/Hypervisor. On the subject of your issues. While i couldn't begin to solve your issues within a singular post here. Im fairly optimistic that it would be possible to make unraid work for you. Should you decide to give it another try. Lemme me know. Would be happy to attempt to help you remedy your issues.
  12. Alot of people are chasing ghosts right now. Mostly due to some issues with the latest version of unraid. You might try going down to a 6.6.x or lower version of Unraid. And see if that improves your conditions any.
  13. Are all you you guys with issues possibly trying to run this with a single video card installed IE Unraid in a Headless mode. Dedicating your one GPU to the SteamOS? If so. Are yall all remembering to use a known good Video bios? The issues many of you are describing sounds very similar to what happens when you attempt to do the same with a windows installation. Windows installs/loads fine without a good video bios, but goes to crap right after installation of video drivers. Which is what it sounds like SteamOS might be doing shortly after its install.
  14. The problem your describing sounds verbatim like the issue i had when my vbios was no good. Windows would install, and boot up. But right when it would attempt to install the proper video drivers it would black out. Then restart and fail to boot again. So i have a strong feeling it your vbios. I've seen the space invader solution, But have never tried it myself. Having failed to backup and use my own bios file. I ended up using someone else that worked fine ever since. And really its only necessary for when your trying to grab your systems primary video card. Such as in a headless config. Like your trying to do. This is also my configuration.
  15. You can add me to the list of people incapable of using the latest version of unraid. Due to extremely low simultaneous read bandwidth from the array. Multiple users trying to access data are get halting, And extremely low read and write rates (were talking low KB/s).