manHands

Members
  • Posts

    25
  • Joined

  • Last visited

Everything posted by manHands

  1. It's still been 4 months, but note that RC2 didn't come out until November.
  2. I had the same issue. I moved all the data off the drive in question, removed from array, re-formatted, and then added back to the array. All good now.
  3. Genious! Sound like I have my Windows backup solution now. One other quick question on your unRAID borg backup. How do you have the unassigned drive formatted? Did you just stick with XFS, or use something else for greater compatibility just in case you had to put the disk in another machine as part of a restore?
  4. Ah yes, totally overlooked the write speed. Thanks for pointing that out. Curious on your thinking on this approach as well. Why not back up everything listed above directly to the unassigned drive that serves as your borg backup? Because essentially don't you end up having 4 copies of everything that is backed up to your unRAID "backup" share? Original copy unRAID "backup" share borg funnel backup of "backup" share remote backup Having an additional backup definitely doesn't harm anything (other than space I suppose), but again just curious on your approach as I have a similar set-up. I need to backup an iMac, Macbook, and PC in additional to the various shares on unRAID. I was going to try out Vorta (borg client for macOS). And with that, set up a similar backup schedule that I'll have with your borg container on unRAID. However, rather than back up my mac devices to a backup share on the unRAID array, create multiple borg repos for each "device" (unRAID, Macbook, iMac, etc.) on the unassigned disk. And then of course sync each repo to a remote backup location. Still tying to figure out my PC solution. Does that make sense? Anything I might be missing with this approach or any other thoughts you may have? I appreciate the help.
  5. Why is the repo recommended to be on an unassigned drive? What are the downsides to using a disk in the array that is only used for backups? You then also get the parity protection. Generally curious on this one. Thanks.
  6. Any luck figuring this out? I'm stuck on 6.8.3 for the exact same reason.
  7. Sounds like our use cases are very similar, so glad to hear you're happy with the build. Are you passing through just the one GPU or possibly a 2nd? I'd be looking to pass through two 3080s for some mining myself.
  8. I've been looking to do a similar build using the same Asrock W480 Creator MB with the W-1290P. Aren't you able to use the built-in iGPU to transcode 4K content? That's one of the reasons I've been looking at this CPU along with the ECC support. Also, I'd be looking to passthrough some PCIe devices to a Windows VM. Are you able to share the W480 Creator IOMMU groupings? Overall, how happy are you with the build?
  9. Do you perhaps have bonding enabled under network settings? I have the same board with an extra NIC as well, and am able to stub two of them on 6.8.3 and passthrough to two separate VMs. I tried 6.9 at one point too and didn't have any issue there either.
  10. Once you start the VM, get into the VNC window fast. There's a prompt to "press any key" to get into the Windows installation.
  11. Yeah, I know. I ended up just selling my 2840a card, and swapping it out for a LSI. I sent HighPoint an email, but never heard anything back.
  12. That card doesn't have out-of-tree drivers in the new Linux kernel. According to the New Features Summary... These drivers are omitted: Highpoint RocketRaid r750 (does not build) Highpoint RocketRaid rr3740a (does not build) Tehuti Networks tn40xx (does not build) If you require one of these drivers, please create a Bug Report and we'll spend some time looking for alternatives. Better yet, pester the manufacturer of the controller and get them to update their drivers.
  13. When routing another download client like binhex-sabnzbd through delugevpn, should I be adding both the 8080 and 8090 ports to the ADDITIONAL_PORTS variable and adding the port(s) to access the web UI, or just 8080?...
  14. Are you on 6.8.3 or 6.9 rc2? Have you tried w/out passing through the GPU?
  15. That guide is still relevant outside of not needing the VFIO-PCI config plug-in to stub your NVMe controller. This functionality is built into 6.9 rc2 under Tools => System Devices.
  16. Right, iGPU isn't usable unless you install 6.9 rc2. I had initial struggles with the 2.5GbE controller if used as the primary NIC for unRAID on 6.8.3; I'm not sure if they've been worked out. From what I've read and gathered, if you have a choice between Intel vs Realtek, use the Intel for unRAID. That said, I opted to purchase a separate Intel PCIe NIC (group 33) for use by unRAID. And then I stub and pass through the 2.5GbE NIC to my Windows VM, and the onboard Intel I219-V NIC to my macOS VM. This just made sense in my use case since I can pass both onboard sound and a supported NIC to macOS.
  17. Here's my IOMMU groups with PCIe ACS override set to Both; only way I could get my two GPUs into their own group. I'm currently on the latest 1.80 BIOS, but it was no different than 1.70 or the 1.72 beta. Two settings I needed to change in the BIOS to get GPU passthrough to work in addition to the defaults... Advanced > CPU Configuration > Primary Graphics Adapter = Onboard Advanced > CPU Configuration > IGPU Multi-Monitor = Enable I'm currently on 6.8.3 w/o any issues other than not being able to take advantage of HW transcoding in Plex because of the 10th Gen i9-10850K. I was on 6.9 rc2 for a bit, but my Windows VM kept freezing at random times and oddly bringing down my entire network. So I've since downgraded back to 6.8.3 and back to normal. IOMMU group 0:[8086:9b33] 00:00.0 Host bridge: Intel Corporation Device 9b33 (rev 05) IOMMU group 1:[8086:1901] 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor PCIe Controller (x16) (rev 05) IOMMU group 2:[8086:1905] 00:01.1 PCI bridge: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor PCIe Controller (x8) (rev 05) IOMMU group 3:[8086:9bc5] 00:02.0 VGA compatible controller: Intel Corporation Device 9bc5 (rev 05) IOMMU group 4:[8086:06f9] 00:12.0 Signal processing controller: Intel Corporation Device 06f9 IOMMU group 5:[8086:06ed] 00:14.0 USB controller: Intel Corporation Device 06ed [8086:06ef] 00:14.2 RAM memory: Intel Corporation Device 06ef IOMMU group 6:[8086:06e0] 00:16.0 Communication controller: Intel Corporation Device 06e0 IOMMU group 7:[8086:06d2] 00:17.0 SATA controller: Intel Corporation Device 06d2 IOMMU group 8:[8086:06c0] 00:1b.0 PCI bridge: Intel Corporation Device 06c0 (rev f0) IOMMU group 9:[8086:06c2] 00:1b.2 PCI bridge: Intel Corporation Device 06c2 (rev f0) IOMMU group 10:[8086:06ac] 00:1b.4 PCI bridge: Intel Corporation Device 06ac (rev f0) IOMMU group 11:[8086:06b9] 00:1c.0 PCI bridge: Intel Corporation Device 06b9 (rev f0) IOMMU group 12:[8086:06ba] 00:1c.2 PCI bridge: Intel Corporation Device 06ba (rev f0) IOMMU group 13:[8086:06bb] 00:1c.3 PCI bridge: Intel Corporation Device 06bb (rev f0) IOMMU group 14:[8086:06bc] 00:1c.4 PCI bridge: Intel Corporation Device 06bc (rev f0) IOMMU group 15:[8086:06be] 00:1c.6 PCI bridge: Intel Corporation Device 06be (rev f0) IOMMU group 16:[8086:06bf] 00:1c.7 PCI bridge: Intel Corporation Device 06bf (rev f0) IOMMU group 17:[8086:06b0] 00:1d.0 PCI bridge: Intel Corporation Device 06b0 (rev f0) IOMMU group 18:[8086:06b5] 00:1d.5 PCI bridge: Intel Corporation Device 06b5 (rev f0) IOMMU group 19:[8086:0685] 00:1f.0 ISA bridge: Intel Corporation Device 0685 [8086:06c8] 00:1f.3 Audio device: Intel Corporation Device 06c8 [8086:06a3] 00:1f.4 SMBus: Intel Corporation Device 06a3 [8086:06a4] 00:1f.5 Serial bus controller [0c80]: Intel Corporation Device 06a4 [8086:0d4d] 00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (11) I219-V IOMMU group 20:[10de:1f0a] 01:00.0 VGA compatible controller: NVIDIA Corporation Device 1f0a (rev a1) IOMMU group 21:[10de:10f9] 01:00.1 Audio device: NVIDIA Corporation TU106 High Definition Audio Controller (rev a1) IOMMU group 22:[1022:1470] 02:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 1470 (rev c3) IOMMU group 23:[1022:1471] 03:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 1471 IOMMU group 24:[1002:687f] 04:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Vega 10 XL/XT [Radeon RX Vega 56/64] (rev c3) IOMMU group 25:[1002:aaf8] 04:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Vega 10 HDMI Audio [Radeon Vega 56/64] IOMMU group 26:[15b7:5002] 05:00.0 Non-Volatile memory controller: Sandisk Corp WD Black 2018/PC SN720 NVMe SSD IOMMU group 27:[1b21:3242] 06:00.0 USB controller: ASMedia Technology Inc. Device 3242 IOMMU group 28:[144d:a808] 07:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981/PM983 IOMMU group 29:[1b73:1100] 08:00.0 USB controller: Fresco Logic FL1100 USB 3.0 Host Controller (rev 10) IOMMU group 30:[14e4:43a0] 09:00.0 Network controller: Broadcom Inc. and subsidiaries BCM4360 802.11ac Wireless Network Adapter (rev 03) IOMMU group 31:[10ec:8125] 0a:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller (rev 05) IOMMU group 32:[1000:0087] 0b:00.0 Serial Attached SCSI controller: Broadcom / LSI SAS2308 PCI-Express Fusion-MPT SAS-2 (rev 05) IOMMU group 33:[8086:10d3] 0c:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection IOMMU group 34:[144d:a808] 0e:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981/PM983 IOMMU group 35:[1b21:0612] 0f:00.0 SATA controller: ASMedia Technology Inc. ASM1062 Serial ATA Controller (rev 02)
  18. No luck I just ordered an Inateck card on Amazon that has two 3.0 ports as well as an internal 3.0 header I can use to connect the front 3.0 ports on my case. It uses the FL1100 controller which from what I gather has native macOS support. Only $20 and I've got an open PCI-E x1 slot, so what the heck.
  19. It does not... IOMMU group 4 00:14.0 USB controller [0c03]: Intel Corporation Comet Lake USB 3.1 xHCI Host Controller [8086:06ed] 00:14.2 RAM memory [0500]: Intel Corporation Comet Lake PCH Shared SRAM [8086:06ef] Which is kind of what I figured when looking at System Devices in the unRAID TOOLS page. That's got to be the reason why I'm seeing USB issues on a VM restart, right? There is a separate ASM3242 USB 3.2 controller on board that's reset capable and in it's own IOMMU group... [RESET] 05:00.0 USB controller [0c03]: ASMedia Technology Inc. ASM3242 USB 3.2 Host Controller [1b21:3242] However, I don't think macOS has native support for this controller.
  20. Sorry for the delayed reply because I appreciate the response. I've been spending way too much time trying to troubleshoot this on my own. Yes, no issues on a real hack. I'm using the latest OpenCore bootloader with the same config/files for both the real hack and vm. The only SSDT I'm using related to USB is SSDT-EC-USBX which I've configured for my board. All that said, I think I'm on to something. The USB issues occur after a VM restart/shutdown. On a fresh unRAID reboot and on the first VM start, the controller is loaded with AppleIntelCNLUSBXCHI and all the ports work as intended as configured with my USBMap.kext to stay under the 15 port limit. As far as I can tell, the USB controllable cannot be reset. And this may be why the ports don't work or are flaky after a VM restart. Thoughts?
  21. I've successfully set up a bare metal macOS Big Sur VM passing through GPU (Vega 56), NVME (where OS is installed), onboard sound card, and Broadcom wireless/bluetooth adapter (and oh boy was it a project). Everything is working wonderfully except being able to passthrough the onboard Comet Lake USB 3.1 xHCI controller. I can see the controller in System Info, but actually using the USB ports is another story. Sometimes it'll recognize the device (most of the time not), hot plugging is non-existent, and sometimes plugging something in will lock up the entire server. In theory, should passing through the USB controller work? I'm using an ASROCK Z490 Taichi board. I can boot directly to the OS (not through unRAID) w/out issue and w/out any additional kexts to use the USB controller/ports. Which to me would mean that I wouldn't need any kexts/drivers or other OpenCore configuration to get the USB controller to work in unRAID and the VM other than stubbing it and passing it through. Thoughts? I can share additional info like libvirt xml, opencore files, etc. if needed to help troubleshoot. However, first I just wanted to throw this out there to see if I'm just missing something obvious or if getting a 3rd party controller that'll work under macOS is my only option.
  22. Yes, I believe it does. Thanks, and I'll try to get in contact with them.
  23. Upgraded from 6.8.3. HighPoint RocketRAID 2840a controller recognized in System Devices, but none of the attached SATA drives (my entire array) are. Controller and drives all recognized in 6.8.3. Had to downgrade.