• Content Count

  • Joined

  • Last visited

Community Reputation

3 Neutral

About TheFullTimer

  • Rank

Recent Profile Visitors

663 profile views
  1. I've had issues with deleting files from folders, and users report issues uploading. Running 19.0.3 and also had issues with the updater coming back with errors once or twice. Not sure how to fix or rebuild.
  2. I recently moved to a new house and my server is assigned a new Lan address. The port forwarding is set correctly but Nextcloud is unresponsive. When I attempt to access via 192.168.1.*:444 I receive this message. The error log shows Not sure how to proceed with correcting this issue.
  3. I’ve had the same problem. Not sure if you found a cause yet. I’m also using a Gigabyte board and Threadripper. X399 Designare 1900X Threadripper 64GB of RAM I’ve juggled my three cards between every slot on the board, but only the same one is recognized by Unraid as available to VM’s. The board itself can be assigned to boot graphics to any slot that I want, successfully. 42:00.0, 42:00.1, 43:00.0, & 43:00.1 Aren’t detected in the system devices by Unraid, but are recognized at a lspci request from the terminal. Example photo attached
  4. Taken from the Ubuntu VM log after starting it and waiting.
  5. Just a minute ago it worked for my Ubuntu VM again until I shut it down. Then I tried my Windows VM and nothing at all. Went back to Ubuntu and now it won't output.
  6. Rather suddenly my Nvidia GPU no longer passes through to my VM's. About two weeks ago I changed my cache drive from SATA to NVME and my VM's still booted and played just fine. Then my windows VM would not output to my monitor, but my Ubuntu VM would, so I continued to use that one. Now neither output to the monitor and I'm not sure what happened. I never keep precious data in my VM's so I've deleted and started new ones, which didn't fix it. I've changed the bios the GPU was booting with and checked the Nvidia .rom file. I just haven't been able to figure it out with the free
  7. Found what may be the cause for my issue. System Thread Exception Not Handled during my Avast Antivirus installation. Repeated a clean install of Windows 10 and it happens even during a minimal installation of Avast on both 1709 & 1803 Win 10 Pro.
  8. I also clean installed 1803 last week and experienced my issues. I'll find a 17xx image and try that instead. I wonder what was changed that would cause this trouble. I had previously tried installations with a single core and 2gb of ram, and other combinations, but all experienced the bsod after a few installations and reboots.
  9. Bump, anyone with this System Thread Exception issue?
  10. Recently switched to Threadripper 1900X & X399 Designaire. SVM enabled, fresh Unraid installation on USB, everything looks great with any VM except Windows 10. Every single installation will BSOD w/ System Thread Exception Not Handled. This happens after Key Activation & in four different installations it doesn't seem to matter which drivers I install first, nor whether I am using Windows ID or offline. Only thing that comes to mind as I write this is that I've been using Ninite to install applications and I usually BSOD a few reboots after that as I get more
  11. I've heard that, but my thought is always that with so much changing something has to go awry somewhere.
  12. This is probably answered, and I'll close the thread & delete if necessary, but I wanted to confirm for myself. Being in a bit of a time crunch, and as stubborn as I am... Transitioning from C204 and 1155, Cougar Point & Sandy Bridge, to X99 and 2011-v3, Haswell-E. Any known issues or alterations that should be made to VM XML's? There will be a big change in Memory due to the Chipset and architecture change, DDR3-ECC to DDR4-nonECC. The quantity memory with both configurations is 32GB, what other issues could this cause? A big reason for the change is for be
  13. The solution to the issue I was having was resolved through an update to my antivirus software. I was using Avast Pro and it featured a port scan feature which would check every port when you opened a connection to a local device. This would result in Unraid closing connections for some time, or until rebooted. If you are using Avast we worked out a solution in this topic, If you use a different antivirus or firewall it may be a similar issue. Let us know and maybe we can help.
  14. Because I forgot to check before posting yesterday; I can say that with my MoBo switching to EHCI had no effect in altering the groups or devices listed above.
  15. Here is a dump of my devices and you can see that it only passes through the VL805. If I didn't stub it I wouldn't be able to pass it to anything. If I cannot figure out how to make it work with USB audio without freezing the other devices on the controller then I'll swap it for something else. Bus 1 --> 0000:00:1a.0 (IOMMU group 3)Bus 001 Device 003: ID 0781:5575 SanDisk Corp. Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching HubBus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hubBus 2 --> 0000:00:1d.0 (IOMMU group 7)Bus 002 Device 004: ID 051