Econaut

Members
  • Posts

    148
  • Joined

  • Last visited

Everything posted by Econaut

  1. Hello fellow Ultra owners. Dumb question... If I have a Ryzen 2400G, is that a reason for why the 2nd PCIe slot does not show up at all? I have '3' GPUs (slot 1 & slot 2) and the Ryzen iGPU. UNRAID can only see the GPU in slot 1 and the iGPU. I do also have two m.2 sticks installed and can see both of those. Sometimes the m.2 lanes overlap PCIe GPU slots.
  2. Thanks for that guide - I actually found it referenced somewhere else and followed it pretty much to the letter with the most recent Win10 VM attempt (stopping short of the virt-manager section). After reading countless forum posts, articles, and watching videos I've seen everything all over the map recommended for any possible scenario (SeaBIOS vs OVMF, Q35 vs i440fx, use vbios or don't) - the community doesn't seem to have any reliable consensus aside from 'use whatever works' & 'try everything' which is infuriating haha. I may not be having the exact same issue, in fact I don't think anyone in the world is having my exact issue since my hardware configuration (and most folks) are rather unique, but I am on 6.9.1 and I cannot get GPU passthrough working for the life of me despite following every guide I could get my hands on. Behold:
  3. Not currently. I did install teamviewer with VNC when initially installing Ubuntu and while I can actually see the teamviewer ID populate in the systems list when I start it up in passthrough mode, I cannot actually connect to it. I would probably be able to SSH in if that is what you mean but I don't have that enabled currently.
  4. I had successful GPU passthrough (tested acceleration) on a Ubuntu host on 6.9.1 one time. It did not have the audio device configured correctly (strange UNRAID bug that's been lingering for years apparently) so I did a clean shutdown, tweaked it per the space invader advanced GPU tweaks video (added multifunction='on' and set correct values for audio device) and started it back up again. No output whatsoever - not even the bios. Even reverting back to the broken audio configuration (or removing audio altogether) still resulted in no output at all. Rebooted UNRAID and same thing again, no output. Been pulling my hair out over this maddening inconsistency. Why would it work once and then not again? The configuration that did work once was with latest Q35 and OVMF bios, no attached vbios (AMD GPU). I am not seeing any errors or even warnings anywhere in UNRAID log or VM log that would indicate an issue. It should work - but it doesn't. I've spent probably about 16 hours across 3 days hammering on various Windows 10 Pro configurations to get a GPU passed through and never had any success. I swear I must have tried every combination by now... Why would a core feature be broken in the latest stable release? This is my first foray into UNRAID and I just started with the latest which happened to be 6.9.1 - so no previous success from which to compare to older versions. Having a miserable time so far 😆.
  5. So to be clear, this cache pool is actually protected similarly to a RAID 1? If one m.2 dies for example, would I be able to replace it and retain all the data that was in the cache pool?
  6. Yes the secondary USB drive was also named UNRAID. Good to know!
  7. Will the SSD TRIM work for m.2 SSD's in the parity & data disk slots or just cache slots?
  8. So this is what I have and it is not allowing me to start the array: The USB drive in the Disk 1 slot is sdb but is the same model of the boot device. Edit: Seems UNRAID does not like that I am using two of the same drive. Trial is being disabled when I plug the second one in. Got passed that by unplugging data disk, reloading page, starting array, plugging drive back in, formatting, etc. Since the GUI remembered the sdb selection for Disk 1, it thought it had a disk to start with (even though it was unplugged) so that was lucky but it seems to be working now.
  9. Oops my mistake - I did mean RAID1 (RAID1 is parallel RAID0 is serial, more or less) - edited original.
  10. Ok cool. And the data flash drive can be any size? I certainly don't have a 1TB to match (16GB & 32GB) So does the cache pool work in parallel (if 2x 1TB m.2 = 1TB cache pool it's basically a raid1 in that case?) Sorry I cannot yet think in terms of btrfs 😄
  11. Alright so just one flash drive as the parity drive and no data drives needed? Forgive my naivety but with the m.2's assigned as cache, does that provide persistent VM storage? Can I merge them into a single redundant cache block? (assuming I would have to get the motherboard RAID 1 working for a redundant cache block) In essence, I am hoping to run two GPU pass-through systems (and probably some other headless container/VMs) from this one system.
  12. Oh good tip, yeah I wouldn't be making use of it if it's just flash drives. I would be able to add a few flash drives. Would that let me use the two m.2 modules as a single redundant block for VMs?
  13. Spoiler alert... not really; I already built this system thinking I could do one thing but finding out evidently it's not so straight forward: Gigabyte Aorus X570 Ultra Ryzen APU 2x 1TB m.2 SSD 2x AMD GPUs (different models) Suitable PSU And that's it. No HDD's just a really lean GPU pass-through system is what I was going for with the m.2 in RAID 1 (if I can figure that out). So I was able to load up UNRAID and discovered I can't do anything with VMs without first having an array setup... ok. Added an m.2 as parity and the 2nd m.2 as the first data disk and then did some reading and apparently UNRAID can't work this way because TRIM commands won't be issued and the performance will start hemorrhaging over time. Ok, so I tried adding cache only or data only disks and I cannot do much of anything without a parity drive that seemingly has to be an HDD. As luck would have it... this case and build can't really accommodate a HDD. I can add more storage via PCIe and that's about it (+ one other m.2 on the motherboard). If it were even possible, which I'm sure it's not, adding a mini 2.5 HDD via PCIe sounds pretty dumb (just wasting the bandwidth). My goal here was to have simple GUI-based pass-through configuration which supposedly UNRAID delivers. Am I understanding everything correctly in that what I am trying to do with UNRAID is impossible right now? This no TRIM thing seems like a pretty major limitation that hardware manufacturers should be rolling into the firmware... in my humble opinion. My original plan was to just do a motherboard based RAID 1 with the two m.2 and use it as the sole data drive in UNRAID but the bios is a little screwy and even if I create such a RAID 1 it doesn't seem to go live. Even so, seems like that's a non-starter with UNRAID anyways. I do plan on eventually making an actual HDD storage UNRAID someday but that's a major investment I can't make at this time. This recent build was just a replacement motherboard and some m.2s.
  14. Thanks that ended up working but it was a "EFI-" > "EFI". Interestingly, it failed when I interrupted autostart and tried manually picking items saying for each: Failed to allocate initramfs memory, failing out Booting kernel failed: Bad file number
  15. Ah, no I did not. In the inverse scenario (non-UEFI boot), must that folder contain the dash?
  16. Yeah I did try that as well and ran the .bat as admin. It looks like it worked but the host system won't boot the drive. Tried booting UEFI and legacy - neither worked. Ordered some 2.0 flash drives to try anyway but now I need to return the 3.0 ones I got.
  17. Same issue - this is a pretty frustrating limitation: This drive is plugged into a 2.0 port but the drive is a SanDisk 3.2Gen1.